Data Safety
TapMind trust and compliance information for publishers' engineers.
Google Play Data Safety & Apple privacy-label guidance
Applies to CA-SDK [version] / Orchestration SDK [version]. Category names follow Google's Data Safety form and are verified against the current form at each release.
Add the following to your Data Safety declaration if you use the TapMind SDK. Entries marked "if enabled" apply only when TapMind identifier features are enabled for your app on the TapMind platform.
Scroll horizontally to view all columns on smaller screens.
| Data type | Collected | Shared | Purposes | Required / optional |
|---|---|---|---|---|
| Device or other IDs | Yes | Yes (advertising partners) — if enabled | Advertising or marketing; Analytics; Fraud prevention, security and compliance | Required (installation identifier); advertising ID if enabled |
| App activity — app interactions | Yes | No | Analytics; Advertising or marketing | Required |
| App info and performance — diagnostics | Yes | No | Analytics; App functionality | Required |
| Location — Approximate location (derived from IP address on TapMind's servers) | Yes | Yes (country/region to advertising partners) | Advertising or marketing; Analytics; Fraud prevention, security, and compliance | Required |
| Personal info; Financial info; Health and fitness; Messages; Photos and videos; Audio; Files and docs; Calendar; Contacts | No | No | — | — |
Data is encrypted in transit. Users can request deletion at Privacy Choices or through your app's privacy contact. The TapMind SDK collects no precise location, no hardware identifiers, and — in apps declared child-directed — nothing beyond what contextual ads need.
Partner SDKs. If you integrate an advertising partner's SDK alongside ours, declare that SDK per the partner's own guidance — links on Partners & vendor IDs.
Apple privacy labels. Guidance for the iOS SDK will be published here when the iOS release that includes consent and identity features ships.