Countly — guides
If a privacy review, App Store rejection, or ATT prompt is forcing a rethink, these guides cover the move off the most-used mobile analytics SDKs. Each page is tool × outcome: what the tool collects today, what to remove, and the comparison vs Respectlytics.
9 guides published
-
Replace Countly to remove the ATT prompt
Migrate from Countly to Respectlytics so your iOS app doesn't need to show the ATT prompt. Helps developers avoid collecting personal data.
Read guide -
Replace Countly to stop collecting personal data in analytics
Migrate from Countly to Respectlytics. 5-field event schema enforces no PII at the API boundary. Helps developers avoid collecting personal…
Read guide -
Replace Countly so analytics never touches PHI
Migrate from Countly to Respectlytics so analytics doesn't store the data HIPAA classifies as PHI. Helps developers avoid collecting person…
Read guide -
Replace Countly with a strict 5-field event schema
Migrate from Countly to a 5-field event schema. Extras rejected at the API. Helps developers avoid collecting personal data in the first pl…
Read guide -
Replace Countly with a RAM-only event queue
Migrate from Countly to a RAM-only event queue. Zero bytes written to disk for analytics. Helps developers avoid collecting personal data.
Read guide -
Replace Countly to ship fewer third-party SDKs
Migrate from Countly to Respectlytics to reduce your dependency tree. Helps developers avoid collecting personal data.
Read guide -
Replace Countly to shrink your app binary
Migrate from Countly to a lighter analytics SDK. Helps developers avoid collecting personal data and ship smaller binaries.
Read guide -
Replace Countly to speed up cold start
Migrate from Countly to a lighter analytics SDK to reduce cold-start latency. Helps developers avoid collecting personal data.
Read guide -
Replace Countly for EU data residency
Migrate from Countly to Respectlytics for EU-only data storage. Helps developers avoid collecting personal data and simplifies vendor revie…
Read guide