Attribution & Measurement

GDPR (General Data Protection Regulation)

Also known asGeneral Data Protection RegulationEU GDPR

The EU's General Data Protection Regulation — the foundational privacy law governing how mobile apps collect, process, and share personal data of European users.

pillar

Key takeaways

  1. 01GDPR (effective May 2018) governs personal data of EU residents — including IDFA / GAID, behavior data, IP addresses.
  2. 02Requires explicit consent for ad tracking — most apps implement via IAB TCF (Transparency & Consent Framework).
  3. 03Fines: up to 4% of global annual revenue or €20M, whichever is higher. Real-world enforcement primarily targets large platforms.
  4. 04Applies to any app serving EU residents, regardless of where the company is headquartered.

GDPR (General Data Protection Regulation) is the EU's foundational privacy law, effective May 2018. It governs how mobile apps (and any business) collect, process, and share personal data of EU residents — defined broadly to include device identifiers (IDFA, GAID), behavioral data, IP addresses, location, contact information, and anything else that can identify a person. GDPR applies to any app serving EU residents, regardless of where the company is headquartered — a US-based app with EU users is subject to GDPR.

The core consent requirement: GDPR requires explicit, informed, freely-given consent before processing personal data for purposes like ad tracking, behavioral retargeting, or sharing with third parties. "Explicit" means an affirmative action (toggle, button, checkbox); pre-checked boxes don't count. "Informed" means the user understood what they were consenting to. "Freely given" means refusing consent shouldn't cost them access to the service. For mobile apps, this typically means showing a consent dialog at first launch that asks the user to opt in to ad-tracking-related data processing, with clear explanation of what data is collected and who receives it.

IAB TCF (Transparency & Consent Framework): most mobile apps don't build consent dialogs from scratch — they use the IAB's standard framework. TCF defines:

TCF 2.2 (current version as of 2026) refined the framework to address regulator feedback. Most major MMPs (AppsFlyer, Adjust, Singular) and ad networks (Meta, TikTok, Google) integrate with TCF natively. Consent management platforms (OneTrust, TrustArc, Sourcepoint, Cookiebot, Didomi) provide pre-built TCF-compliant consent UIs.

Real-world enforcement

What every consumer mobile app needs

  1. Privacy policy clearly explaining what data is collected, why, and who receives it. Updated when practices change.
  2. Consent dialog at first launch — TCF-compliant, with granular opt-in / opt-out for ad tracking specifically.
  3. Data subject rights handling — users can request access to their data, correction, deletion, portability. Have a process for these requests.
  4. Data breach response plan — required to notify regulators within 72 hours if breach involves personal data.
  5. Vendor management — ensure your MMP, ad networks, analytics platforms all process EU data in GDPR-compliant ways (DPAs — Data Processing Agreements).

GDPR vs CCPA — key differences for mobile apps

AspectGDPR (EU)CCPA / CPRA (California)
Consent modelOpt-IN (explicit consent required first)Opt-OUT (tracking permitted by default)
User action requiredClick "Allow" or grant via system prompt"Do Not Sell or Share My Personal Information" link
Maximum fine4% of global annual revenue or €20M$7,500 per intentional violation
Private right of actionLimited (regulator-led enforcement)Yes ($100-$750 per breach incident)
Effective dateMay 2018CCPA Jan 2020, CPRA Jan 2023
Geographic scopeEU residents (anywhere)California residents (anywhere)

Most mobile apps designed for GDPR compliance largely meet CCPA / CPRA requirements too — GDPR is the stricter standard. Build for GDPR + add the CCPA "Do Not Sell or Share" link and you're covered in most of the regulated world.

Quick answers

Does GDPR apply to my mobile app?

If you have any EU residents using your app, yes — regardless of where your company is headquartered. GDPR applies based on user location, not company location. A US-based app with EU users is subject to GDPR. The same is largely true for similar privacy regulations like UK GDPR (essentially identical post-Brexit) and laws in Norway, Switzerland, and Iceland that align with GDPR.

What does GDPR require for mobile app ad tracking?

Explicit, informed, freely-given consent before processing personal data for ad-tracking purposes. "Explicit" = affirmative action (toggle, button); pre-checked boxes don't count. "Informed" = user understood what they consented to. "Freely given" = refusing consent shouldn't cost them service access. Most apps implement consent via IAB TCF (Transparency & Consent Framework), often through a consent management platform (OneTrust, Cookiebot, Didomi).

What is the GDPR fine structure?

Up to **4% of global annual revenue or €20M, whichever is higher**. Smaller infractions can fall under a lower tier (up to 2% / €10M). Largest fines historically have targeted big platforms — Meta (€1.2B for cross-border data transfers), Amazon (€746M), Google (€90M cookie consent issues). Typical mobile-app exposure is much lower in practice, but theoretical maximum is severe.

What is IAB TCF?

**IAB TCF (Transparency & Consent Framework)** is the standard framework for GDPR consent management in ad tech. It defines: (1) standardized consent UI patterns, (2) a consent string format passed to every ad network call, (3) a vendor ID list so users can grant consent per ad-tech vendor. TCF 2.2 is the current version. Most major MMPs and ad networks integrate with TCF natively. Consent management platforms (OneTrust, TrustArc, Sourcepoint, Cookiebot, Didomi) provide pre-built TCF-compliant consent UIs.

Back to glossary