Developer Privacy

Privacy & consent with the TapMind SDK

The short version. The TapMind SDK ships with every privacy feature off. Nothing beyond what our previous releases collected is sent until you've signed the Data Processing Addendum, completed your attestation with us, and we've enabled features for your app. The SDK reads the consent signals your CMP or your own dialog sets and forwards them unchanged; it never writes to them, never shows a prompt, and never collects precise location, hardware identifiers or contact data. Where we're allowed to use the device's advertising identifier, it stays in memory on the device and is used only for the purposes, and in the countries, where your users' choices and the law permit.

What you need to do

• Sign the Data Processing Addendum and complete the attestation with your account manager.
• Add the TapMind disclosure text to your privacy policy and update your Google Play Data Safety (and, when applicable, Apple privacy label) declarations — see Data Safety & privacy labels.
• If you use a consent management platform, add TapMind and your enabled advertising partners as vendors. If you use your own notice, pass its result via the consent API — see Consent.
• Verify with inspection mode — see Verifying your setup.
• Ask your account manager to enable features.

These pages cover the Orchestration SDKs. Publishers integrating TapMind's display tag, video player or CTV/OTT/audio tags: your obligations are in the Data Processing Addendum (Schedule 6) and the Publisher Policies; what the tag and player store in browsers is at Platform Cookies. Tag-integration privacy documentation will be added here.

Pages: What the SDK collects · Consent · Data Safety & privacy labels · Verifying your setup · Partners & vendor IDs · Children, Families & age signals · DSA & opt-out handling.

Applies to CA-SDK [current version] and later and Orchestration SDK [current version] and later. Identifier and consent features described here ship in CA-SDK [TT increment version].