▸Example Google Analytics for Firebase call (the "before")
import com.google.firebase.analytics.ktx.analytics
import com.google.firebase.ktx.Firebase
// GA4 event with user_id and freeform parameters:
Firebase.analytics.logEvent("level_up") {
param("level", 7L)
param("character", "Aragorn")
param("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 Google Analytics for Firebase cleanly
-
1
Remove the Firebase Analytics dependency from your build (CocoaPods / SPM / Gradle / npm / pub)
-
2
Remove the GA4 property's data stream linkage from your Firebase console — the data stops flowing as soon as the SDK is removed, but the property remains until manually deleted
-
3
Replace
Analytics.logEventcall sites withRespectlytics.track("event_name") -
4
Re-audit your
Info.plistandAndroidManifest.xmlfor IDFA / AD_ID surfaces that GA for Firebase contributed -
5
Confirm
play-services-ads-identifieris no longer in the Android runtime classpath
⇋Google Analytics for Firebase vs Respectlytics — eu data residency
| Google Analytics for Firebase | 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.