Replace Kochava: RAM-only events

Q: 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.

▸Example Kochava call (the "before")

swift Respectlytics

import KochavaTracker

KochavaTracker.shared.registerWithAppGUID("YOUR_APP_GUID")

let event = KochavaEvent(eventTypeEnum: .purchase)
event.appStoreReceiptBase64EncodedString = receiptBase64
event.priceDoubleNumber = NSNumber(value: price)
event.currencyString = "USD"
event.userIdString = userId
KochavaTracker.shared.send(event: 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 Kochava cleanly

1
Remove pod 'KochavaTracker' from Podfile
2
Remove implementation 'com.kochava.tracker:tracker:...' from build.gradle
3
Remove react-native-kochava-tracker from package.json if used
4
Remove KochavaTracker.shared.registerWithAppGUID(...) and sendEvent(...) call sites
5
Remove NSUserTrackingUsageDescription from Info.plist if Kochava was the only ATT-needing SDK
6
Remove AD_ID permission from the merged Android manifest if no remaining SDK contributes it

⇋Kochava vs Respectlytics — ram-only event queue

	Kochava	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.

⇢Related migration guides

Replace Kochava: no att prompt Same tool, No ATT prompt Replace Kochava: no pii collected Same tool, No PII collected Replace Kochava: no phi collected Same tool, No PHI collected Replace Kochava: 5-field event schema Same tool, 5-field event schema Replace Kochava: fewer third-party sdks Same tool, Fewer third-party SDKs Replace Kochava: smaller app binary Same tool, Smaller app binary Replace Kochava: faster cold start Same tool, Faster cold start Replace Kochava: eu data residency Same tool, EU data residency Replace Kochava: self-hosted deployment Same tool, Self-hosted deployment Replace Kochava: open-source sdk + server Same tool, Open-source SDK + server Replace Firebase Analytics: ram-only event queue Same outcome, Firebase Analytics Replace Google Analytics for Firebase: ram-only event queue Same outcome, Google Analytics for Firebase

Replace Kochava with a RAM-only event queue