▸Example Singular call (the "before")
import com.singular.sdk.Singular
import com.singular.sdk.SingularConfig
val config = SingularConfig("YOUR_API_KEY", "YOUR_API_SECRET")
config.withIMEICollection()
Singular.init(applicationContext, config)
Singular.event("sng_purchase", JSONObject().apply {
put("revenue", price)
put("currency", "USD")
put("user_id", userId)
})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 Singular cleanly
-
1
Remove the Singular SDK from your build (
Singular-SDK/singular_sdk/singular-react-native) -
2
Remove
Singular.start(YOUR_API_KEY, YOUR_API_SECRET)andSingular.event(...)call sites -
3
Decide ATT posture — remove
NSUserTrackingUsageDescriptionif Singular was the only ATT-triggering SDK -
4
Remove the AD_ID permission from the Android merged manifest if no remaining SDK contributes it
-
5
Plan SKAdNetwork + Google Play Install Referrer as the first-party attribution replacement
⇋Singular vs Respectlytics — ram-only event queue
| Singular | 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.