▸Example Firebase Analytics call (the "before")
import FirebaseAnalytics
// Default Firebase event with rich per-user metadata:
Analytics.logEvent("purchase", parameters: [
"value": price,
"currency": "USD",
"transaction_id": UUID().uuidString,
"user_id": userId,
])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 Firebase Analytics cleanly
-
1
Remove
pod 'Firebase/Analytics'fromPodfile(and anyFirebase/Corepulled by it that isn't needed elsewhere) -
2
Remove
implementation 'com.google.firebase:firebase-analytics-ktx'frombuild.gradle.kts -
3
Remove
@react-native-firebase/analyticsfrompackage.json -
4
Remove
firebase_analytics:frompubspec.yaml -
5
Remove
FirebaseApp.configure()andAnalytics.logEventcall sites — replace withRespectlytics.configure()andRespectlytics.track("event_name") -
6
Delete the
GoogleService-Info.plistandgoogle-services.jsonif no other Firebase product remains in the app -
7
Run
./gradlew :app:dependenciesand confirmplay-services-ads-identifieris no longer in the runtime classpath
⇋Firebase Analytics vs Respectlytics — eu data residency
| Firebase Analytics | Respectlytics | |
|---|---|---|
| Default storage region | — see tool note above (often US) | EU (Frankfurt) |
| Cross-border transfer mechanism needed | SCCs typically | None (EU-to-EU) |
| Self-host fallback for stricter residency | — varies | Yes (operator-chosen region) |
| Backups stored in same region | — varies | Yes (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.