Data safety
Play Data safety answers
Your answers for the AdHedge SDK in Play Console's Data safety form.
Does the SDK collect or share user data?
Yes.
Data types
| Play category | Collected | Shared | Ephemeral | Required | Purposes |
|---|---|---|---|---|---|
| Device or other IDs | Yes | Yes | No | Yes | Fraud prevention, security, and compliance; Analytics |
| App activity: in-app actions | Yes | Yes | No | Yes | Fraud prevention, security, and compliance; Analytics |
| App info and performance: diagnostics | Yes | Yes | No | Yes | Fraud prevention, security, and compliance; Analytics |
- Device or other IDs: a random install ID and the Play App Set ID. No advertising ID or Android ID.
- App activity: tap counts and timing on install day, and whether the app opened on day one.
- App info and performance: installer, install times, build, debug flags, emulator and root checks, and the Play Integrity token.
Purposes
Fraud prevention, security, and compliance. Analytics. Never advertising or personalization.
Shared
With AdHedge, as your service provider. We don't sell it, link it across apps, or join it to ad IDs or personal data.
Handling
- Encrypted in transit: yes.
- Deletion: from your dashboard or API, within 30 days of a request.
- Retention: signals and events 90 days. IP address 30 days, IP prefix 13 months. Installs 13 months.
- Optional collection: none.
Never collected
- Advertising ID, Android ID, Firebase installation ID
- IMEI, serial, MAC address, SSID
- Phone number, phone state, SIM, contacts, SMS, call logs
- Location
- Installed app lists
- Touch coordinates, screen content, text input, names, email
Permissions: INTERNET and ACCESS_NETWORK_STATE only.
Play Integrity
One token per install, under a Cloud project linked to your app. No tracking across apps.