Privacy & Consent

TapMind adapters operate within your existing mediation stack. Your app is responsible for collecting user consent and passing signals to the mediation or ads SDK before ad requests are made. This applies to Mediation Adapters (GMA SDK) and Mediation Adapters (GMA Next-Gen SDK).

Mediation Adapters

1. Implement a consent mechanism appropriate for your users' jurisdiction (GDPR/TCF, US state privacy laws, and other applicable regulations).
2. Pass consent signals to your mediation SDK using that platform's recommended API before initializing ads or requesting fill.
3. TapMind receives consent indirectly through the mediation layer - configure consent at the mediation SDK level first.

Partner-specific consent APIs

iOS: App Tracking Transparency (ATT)

• Request ATT authorization when required before accessing IDFA-dependent ad features.
• Configure your Info.plist with NSUserTrackingUsageDescription when using ATT.
• Pass consent/ATT state to your mediation SDK per Apple's and your mediation partner's guidance.

iOS: Privacy Manifest

• Declare required-reason API usage and data collection in your app's Privacy Manifest (PrivacyInfo.xcprivacy) per Apple requirements.
• Include third-party SDK privacy manifests bundled with Google Mobile Ads and your mediation SDKs.
• Review TapMind adapter dependencies when submitting App Store privacy nutrition labels.

Android: Google Play Data Safety

• Complete the Data Safety section in Google Play Console to reflect data collected through ads SDKs in your app.
• Disclose ad-related data types (device identifiers, diagnostics, etc.) per Google's form guidance.
• Coordinate declarations with your mediation SDK vendor documentation.

Questions

For account-specific privacy questions, data processing agreements, or regional compliance, contact your TapMind account manager.