What the General Data Protection Regulation requires when your iOS app processes personal data of people in the EU/EEA — and how it interacts with Apple’s rules.
GDPR applies if your app processes personal data of people in the EU/EEA, regardless of where your company is based.
| Requirement | What It Means for iOS | Apple Overlap |
|---|---|---|
| Lawful basis (Art. 6) | Every processing purpose needs a basis (consent, contract, legitimate interest, etc.) | Privacy Nutrition Labels + Privacy Manifest |
| Transparency (Arts. 13–14) | Privacy policy must list controller, purposes, legal bases, recipients, transfers, retention, and rights | Link required in App Store Connect and inside the app |
| Consent | Freely given, specific, informed, and easy to withdraw | ATT is not a substitute for GDPR consent |
| Data subject rights | Access, rectification, erasure, portability, objection | In-app account deletion helps with erasure |
| EU Representative (Art. 27) | Required if no EU establishment and you process EU personal data | Separate from DSA trader status |
ATT is Apple’s platform rule that controls access to the IDFA and cross-app tracking.
GDPR consent is a legal requirement under EU law, usually collected via a Consent Management Platform (CMP).
2026 note: Starting with iOS 27.2, a new full-page ATT prompt is mandatory in Germany, France, Italy, Poland, and Romania. Elsewhere in the EU it is optional. Apps may re-prompt once per year.
Apple requires in-app account deletion if accounts can be created (Guideline 5.1.1(v)). This aligns closely with the GDPR right to erasure (Art. 17).
TestLancer provides real iPhone and iPad testers for TestFlight builds so you can verify compliance-related journeys before submission.
View iPhone Testing Packages