Replace Branch: 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 Branch call (the "before")

swift Respectlytics

import BranchSDK

Branch.getInstance().initSession(launchOptions: launchOptions) { params, error in
    // Branch fingerprint + IDFA matching happens here.
    if let referringLink = params?["~referring_link"] as? String {
        // Route the user based on the deep link...
    }
}

Branch.getInstance().userCompletedAction("Paywall Purchase", withState: [
    BranchStandardEventTransactionId: orderId,
    "revenue": price,
])

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 Branch cleanly

1
Remove Branch from your build (Branch / io.branch.sdk.android:library / react-native-branch / flutter_branch_sdk)
2
Remove Branch.getInstance().initSession(...) and userCompletedAction(...) call sites
3
Decide what replaces Branch's deep-link routing — Universal Links + App Links are first-party alternatives (no SDK; OS-handled)
4
Remove Branch URL schemes from your Info.plist and AndroidManifest.xml
5
Delete the Branch app dashboard entry once events stop flowing

⇋Branch vs Respectlytics — ram-only event queue

	Branch	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 Branch: no att prompt Same tool, No ATT prompt Replace Branch: no pii collected Same tool, No PII collected Replace Branch: no phi collected Same tool, No PHI collected Replace Branch: 5-field event schema Same tool, 5-field event schema Replace Branch: fewer third-party sdks Same tool, Fewer third-party SDKs Replace Branch: smaller app binary Same tool, Smaller app binary Replace Branch: faster cold start Same tool, Faster cold start Replace Branch: eu data residency Same tool, EU data residency Replace Branch: self-hosted deployment Same tool, Self-hosted deployment Replace Branch: 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 Branch with a RAM-only event queue