GDPR Implications for iOS Apps

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.

When GDPR Applies

GDPR applies if your app processes personal data of people in the EU/EEA, regardless of where your company is based.

  • Users in the EU create accounts
  • You use analytics, advertising, location, or identifiers (including IDFA)
  • You monitor behaviour of people in the EU

Core Obligations

RequirementWhat It Means for iOSApple 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 rightsLink required in App Store Connect and inside the app
ConsentFreely given, specific, informed, and easy to withdrawATT is not a substitute for GDPR consent
Data subject rightsAccess, rectification, erasure, portability, objectionIn-app account deletion helps with erasure
EU Representative (Art. 27)Required if no EU establishment and you process EU personal dataSeparate from DSA trader status

ATT vs GDPR Consent

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).

  • An “Allow” on the ATT prompt is not valid GDPR consent.
  • Personalized advertising typically needs both.
  • Recommended flow for EU users: show your CMP first, then the ATT prompt.

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.

Account Deletion

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).

  • Deletion must remove the account and associated personal data (except what you are legally required to keep).
  • Temporary deactivation is not enough.
  • The option should be easy to find (usually in account settings).

What Testers Should Verify

  • Privacy policy is easy to find and opens correctly
  • Consent banner / CMP appears and works as expected
  • ATT prompt behaviour (especially EU versions)
  • Account creation → full account deletion flow
  • Data access / export options (if offered)
  • Clear language about what data is collected and why

Need Real-Device Testing for Privacy Flows?

TestLancer provides real iPhone and iPad testers for TestFlight builds so you can verify compliance-related journeys before submission.

View iPhone Testing Packages