▸Example Adjust call (the "before")
import AdjustSdk
let config = ADJConfig(appToken: "YOUR_APP_TOKEN", environment: ADJEnvironmentProduction)
config?.logLevel = ADJLogLevelInfo
Adjust.appDidLaunch(config)
let event = ADJEvent(eventToken: "purchase_token")
event?.setRevenue(price, currency: "USD")
event?.addCallbackParameter("user_id", value: userId)
Adjust.trackEvent(event)Most analytics SDKs back the unsent event queue with SQLite or UserDefaults / SharedPreferences — so a phone that's been confiscated, jailbroken, or restored from backup still contains analytics state. Respectlytics's queue is RAM-only, flushed on a 30-second timer; unsent events on force-quit are lost by design, in exchange for zero on-device forensic surface.
☑Remove Adjust cleanly
-
1
Remove the Adjust SDK from your build (
Adjust/adjust-android/react-native-adjust/adjust_sdk) -
2
Remove
Adjust.appDidLaunch(config)andAdjust.trackEvent(...)call sites -
3
Decide whether you still need ATT — if Adjust was your only ATT-triggering SDK, remove
NSUserTrackingUsageDescriptionfromInfo.plist -
4
Remove the AD_ID permission from the merged Android manifest if no other SDK needs it
-
5
Plan SKAdNetwork / Google Play Install Referrer as the first-party attribution replacement
⇋Adjust vs Respectlytics — ram-only event queue
| Adjust | Respectlytics | |
|---|---|---|
| Event queue persistence | SQLite / UserDefaults / SharedPreferences | In-memory ring buffer |
| Disk usage for analytics | 0.5–10 MB typical | 0 bytes |
| Forensic data on jailbroken / rooted devices | Persistent identifiers + queued events | None |
| Survives force-quit before flush | Yes | No (events lost — by design) |
❓Frequently asked questions
Doesn't this reduce data quality?
Marginally — typical force-quit-before-flush event loss is 0.5–2% depending on platform. For aggregate metrics (funnel rates, feature adoption, release deltas) this is invisible. For per-event reconciliation it would be a problem, but per-event reconciliation isn't a use case Respectlytics supports.
What's the actual flush cadence?
30 seconds by default, plus a flush on applicationDidEnterBackground (iOS) / onPause (Android). Most events reach the network within seconds of being fired.
Is this safe for crash analytics?
Crash analytics is a separate concern — use Sentry, Crashlytics, or Bugsnag (with their own crash-aware queues). Respectlytics is product analytics; crash data has different recoverability requirements and lives in different tools.
Why is this a privacy feature?
Devices that are jailbroken, rooted, restored from backup, or forensically imaged routinely surface analytics artifacts — distinct_ids, queued events, user properties — that survive uninstall in some cases. RAM-only storage moves the dump-recovery surface to zero.