App analytics without the ATT prompt or the AD_ID permission
The Respectlytics SDKs never read the IDFA, the IDFV, the Android Advertising ID or anything that could fingerprint a device. Adding analytics adds no tracking prompt on iOS and no advertising permission on Android.
14-day free trial, no credit card. The demo runs on sample data, no signup.
What the SDKs never read
The current SDKs for Swift, Kotlin, Flutter and React Native read none of these.
- IDFA
- Apple's advertising identifier
- IDFV
- Apple's identifier for the vendor
- Advertising ID
- Google's identifier on Android
- Device details
- Model, OS version and other traits that could fingerprint a phone
The only thing about the device that reaches the server is the platform name, such as iOS or Android. The country comes from the IP address, which is discarded after the lookup.
On iOS: no reason to ask
What App Tracking Transparency is for, and why Respectlytics stays outside it.
Apple asks apps to request permission through App Tracking Transparency before they track users across other companies' apps and websites, or read the IDFA. Respectlytics does neither, so it never calls the prompt.
That means analytics adds no permission screen to your first launch. If another library in your app tracks users, your app may still need the prompt for that library.
On Android: no AD_ID permission
What Google Play asks about advertising IDs, and what Respectlytics adds to the answer.
Apps that target Android 13 or newer must declare the AD_ID permission to read the Advertising ID, and Google Play asks every app to complete an advertising ID declaration.
The Respectlytics SDK declares no such permission and reads no advertising ID, so it adds nothing to that declaration. Analytics libraries that do declare it, often through their dependencies, are a common reason the permission shows up in a merged manifest.
How sessions are counted instead
A random ID per session, never per person or per device.
- When the app starts, the SDK creates a random session ID and keeps it in memory.
- It replaces the ID after two hours, and every time the app restarts.
- The server stores a hash of the ID, salted with your app and the date, so the same ID gives a different value the next day.
- The original ID is never stored, and nothing links one session to another.
Install it on your platform
Each guide covers install, configuration and the first event.
Questions buyers ask
Straight answers, including the ones that might send you elsewhere.
Does this mean my app does not need the ATT prompt?
Not by itself. Whether your app needs the prompt depends on everything it does. Respectlytics gives it no reason to show one, because it never reads the IDFA and never links your data with other companies' data.
What should I answer in the Play Console advertising ID declaration?
That depends on the other libraries in your build. Respectlytics declares no AD_ID permission and reads no advertising ID, so it adds nothing to that answer.
Can I still count unique users?
No. Respectlytics counts sessions, not people. A session ends after two hours or when the app restarts, and nothing links it to the next one.
Does the SDK fingerprint devices instead?
No. It reads no device model, OS version or other attribute that could be combined into a fingerprint, and the server stores only the platform name.
The other design choices
Each one removes something else from your privacy work.
Try it on your own app
14-day free trial, no credit card. Unlimited apps on every plan.
This information is provided for educational purposes and does not constitute legal advice. Regulations vary by jurisdiction and change over time. Consult your legal team to determine the requirements that apply to your situation.