Respectlytics Respect lytics
Menu
Replace Branch EU data residency

Replace Branch for EU data residency

Migrate from Branch to Respectlytics for EU-only data storage. Helps developers avoid collecting personal data and simplifies vendor reviews.

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,
])

Cross-border data transfers from the EU to non-adequate jurisdictions tightened significantly after the Schrems II ruling (2020). For B2B SaaS sold to European enterprises or to public-sector buyers, EU data residency is increasingly a gating procurement requirement. Respectlytics's managed cloud stores all event data on EU infrastructure (currently Frankfurt, DigitalOcean eu-central-1).

Remove Branch cleanly

  1. 1

    Remove Branch from your build (Branch / io.branch.sdk.android:library / react-native-branch / flutter_branch_sdk)

  2. 2

    Remove Branch.getInstance().initSession(...) and userCompletedAction(...) call sites

  3. 3

    Decide what replaces Branch's deep-link routing — Universal Links + App Links are first-party alternatives (no SDK; OS-handled)

  4. 4

    Remove Branch URL schemes from your Info.plist and AndroidManifest.xml

  5. 5

    Delete the Branch app dashboard entry once events stop flowing

Branch vs Respectlytics — eu data residency

BranchRespectlytics
Default storage region— see tool note above (often US)EU (Frankfurt)
Cross-border transfer mechanism neededSCCs typicallyNone (EU-to-EU)
Self-host fallback for stricter residency— variesYes (operator-chosen region)
Backups stored in same region— variesYes (EU only)

Frequently asked questions

What does *Schrems II* actually require?

The ruling invalidated the EU-US Privacy Shield and significantly tightened the bar for cross-border transfers from the EU to non-adequate jurisdictions. Standard Contractual Clauses are still permitted but require a Transfer Impact Assessment per case. Keeping data in the EU avoids the question. Consult your legal team to determine your specific situation.

Does Respectlytics process anything outside the EU?

Stored event data: no. Some operational metadata (admin user accounts, billing) may be processed in regions outside the EU per our privacy policy; consult that document for the authoritative breakdown. Stored event data from your apps stays in the EU on the cloud product.

Can we pin to a specific EU country?

On the cloud product, we currently deploy in Germany (DO eu-central-1). For country-specific pinning (e.g., "data must reside in France"), self-hosting on infrastructure of your choice is the path — Respectlytics's server is AGPL-3.0 and runs on standard Postgres + Python.

What about backups and disaster recovery?

Backups are stored in the same EU region as the primary database, encrypted at rest. There is no cross-region replication on the cloud product.

Related migration guides

Track what matters. Collect nothing you don't.

Five-field event schema, RAM-only event queue, no IDFA, no AAID, no persistent user IDs. Helps developers avoid collecting personal data in the first place.