DSA, opt-out, location and app-ads.txt

DSA transparency, opt-out, approximate location and app-ads.txt

EU Digital Services Act. If your app is an "online platform" under the DSA (it hosts user-generated content, a marketplace, or otherwise disseminates third-party content to the public), declare it in your attestation. TapMind then passes the IAB DSA transparency signals to partners and, where TapMind enables the DSA hook for your app, makes the winning ad's transparency information available through the SDK so you can show an "about this ad" control where you render the ad. If your app is not an online platform, nothing changes for you.

Opt-out. Nothing to build. The SDK honours device settings (resetting or deleting the advertising ID, App Tracking Transparency), your consent platform's changes, the consent API, and requests made at tapmind.com/privacy/choices, on the next ad request. Link tapmind.com/privacy/choices from your privacy policy.

Approximate location (from the December 2026 release). Off unless TapMind enables it for your app, which we do only after you confirm that your Data Safety section declares approximate location as collected and shared for advertising. The SDK uses location only if your app already has the location permission for its own features; it never requests the permission, never reads precise location off the device, and rounds the location on the device before it is sent.

app-ads.txt. Publish the line shown in your TapMind dashboard (tapmind.com, [your seller ID], DIRECT) in the app-ads.txt file on your developer website within 30 days of onboarding. Buyers use it, with TapMind's sellers.json, to confirm that your inventory is sold through TapMind.

Canada. TapMind serves contextual ads only in Canada at present.