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:
- Standardized consent UI patterns that ad networks and MMPs recognize.
- A consent string format that the app passes to every ad network call, indicating exactly which categories the user consented to.
- A list of vendor IDs so users can grant / deny consent per ad network (or per ad-tech vendor).
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
- Largest fines historically: Meta (€1.2B in 2023 for cross-border data transfers), Amazon (€746M), Google (€90M cookie consent banner), TikTok (multiple fines for kids' data).
- Mobile-app specific enforcement: less aggressive than enforcement against large platforms, but rising. EU Data Protection Authorities have audited dozens of mobile apps for tracking-without-consent.
- Reality for typical mobile apps: implement TCF-compliant consent, integrate with major MMPs in consent-respecting modes, and you're protected from typical enforcement. Edge cases (children's apps, health data, financial data) warrant additional legal review.
What every consumer mobile app needs
- Privacy policy clearly explaining what data is collected, why, and who receives it. Updated when practices change.
- Consent dialog at first launch — TCF-compliant, with granular opt-in / opt-out for ad tracking specifically.
- Data subject rights handling — users can request access to their data, correction, deletion, portability. Have a process for these requests.
- Data breach response plan — required to notify regulators within 72 hours if breach involves personal data.
- 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
| Aspect | GDPR (EU) | CCPA / CPRA (California) |
|---|---|---|
| Consent model | Opt-IN (explicit consent required first) | Opt-OUT (tracking permitted by default) |
| User action required | Click "Allow" or grant via system prompt | "Do Not Sell or Share My Personal Information" link |
| Maximum fine | 4% of global annual revenue or €20M | $7,500 per intentional violation |
| Private right of action | Limited (regulator-led enforcement) | Yes ($100-$750 per breach incident) |
| Effective date | May 2018 | CCPA Jan 2020, CPRA Jan 2023 |
| Geographic scope | EU 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.