▸Example mParticle call (the "before")
import mParticle_Apple_SDK
let options = MParticleOptions(key: "YOUR_KEY", secret: "YOUR_SECRET")
options.identifyRequest = MPIdentityApiRequest.withEmptyUser()
options.identifyRequest?.email = email
options.identifyRequest?.customerId = userId
MParticle.sharedInstance().start(with: options)
let event = MPEvent(name: "Paywall Purchase", type: .transaction)
event?.customAttributes = ["value": price, "currency": "USD"]
MParticle.sharedInstance().logEvent(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 mParticle cleanly
-
1
Remove the mParticle SDK from your build (
mParticle-Apple-SDK/mparticle-android-sdk/react-native-mparticle/mparticle_flutter_sdk) -
2
Remove
MParticle.start()andMParticle.logEvent(...)call sites -
3
Critically: review your mParticle output forwarders and decide which downstream destinations you still need data flowing to (most don't — Respectlytics is direct)
-
4
Delete
Identity.identify()andmodify()calls — those drive the identity merge graph -
5
Delete the mParticle workspace's mobile input once events have stopped flowing
⇋mParticle vs Respectlytics — ram-only event queue
| mParticle | 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.