▸Example Countly call (the "before")
import ly.count.android.sdk.Countly
import ly.count.android.sdk.CountlyConfig
val config = CountlyConfig(application, "YOUR_APP_KEY", "https://your-countly-server.com")
.setLoggingEnabled(true)
.setIdMode(DeviceIdType.OPEN_UDID)
Countly.sharedInstance().init(config)
Countly.sharedInstance().events().recordEvent(
"purchase",
mapOf("user_id" to userId, "value" to price, "currency" to "USD"),
1
)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 Countly cleanly
-
1
Remove the Countly SDK from your build (
Countly/ly.count.android:sdk/countly-sdk-react-native-bridge/countly_flutter) -
2
Remove
Countly.sharedInstance().start(with:)initialisation andrecordEvent(...)call sites -
3
Decide whether you'll keep the Countly server running for other apps, or decommission it as part of the migration
-
4
If you used Countly's crash reporting alongside analytics, plan a separate crash-reporter migration (Sentry / Crashlytics / Bugsnag)
⇋Countly vs Respectlytics — ram-only event queue
| Countly | 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.