Contents
A GDPR-compliant app is not created by adding a privacy policy just before launch, but by decisions made in concept, architecture and operations. This checklist walks you through every phase, from data collection and third-party SDKs to retention periods and data breaches. It helps you avoid expensive retrofitting, app store problems and the risk of fines.
Why data protection starts at the concept stage
Article 25 GDPR requires "data protection by design and by default". In practice, this means that when a feature is designed, it must already be clear which data it needs, how long the data is stored and who can access it. Retrofitting is expensive because changes often touch the data model, backend and app at the same time. Violations can also be fined up to 20 million euros or 4 % of worldwide annual turnover. These maximums are rarely reached in practice, but the reputational risk is real for every app.
If privacy is considered from the start, the extra effort is manageable, mainly for consent management, deletion features and documentation. It gets expensive when a tracking SDK has to be removed later or a data model has to be rebuilt for retention rules. With us, GDPR-compliant development and hosting is standard and included in the fixed-price offer; see our price overview for ranges.
One note up front: this checklist describes general requirements and is not legal advice. For your specific app, involve your data protection officer or a specialised law firm.
Phase 1: concept and data collection
- Build a data inventory: which personal data does each feature process? This includes device IDs, IP addresses, location and usage data.
- Define a legal basis per purpose: contract performance, consent, legitimate interest or legal obligation (Art. 6 GDPR).
- Data minimisation: question every field. Does the app really need a date of birth, or is an age confirmation enough?
- Identify special categories: health, biometric or religious data (Art. 9) require stronger safeguards and usually explicit consent.
- Check whether a data protection impact assessment is needed (Art. 35), for example for large-scale processing of sensitive data, profiling or systematic location tracking.
- Create or update the record of processing activities (Art. 30).
Phase 2: architecture, hosting and third parties
Most privacy problems in apps do not come from your own code but from embedded services. An analytics or advertising SDK may transmit data as soon as the app starts, before the user has consented to anything.
| Checkpoint | What to look for | Typical solution |
|---|---|---|
| Hosting location | Prefer processing in the EU, document third-country transfers | Data centre in Germany or the EU |
| Processors | A data processing agreement under Art. 28 for every provider with data access | Maintain a DPA list, review sub-processors |
| SDKs and libraries | Which data do they send, when and where? | SDK inventory, capture network traffic in tests |
| Analytics and crash reporting | Consent requirements, data minimisation | Initialise only after consent, IP truncation, self-hosted alternatives |
| Push services | Tokens and metadata pass through Apple or Google | No sensitive content in the notification text |
| AI services | Are inputs stored or used for training? | Providers with EU processing and contractual exclusion of training |
For US-based services, check whether the provider is certified under the EU-US Data Privacy Framework or whether other safeguards such as standard contractual clauses apply. Our article on data processing agreements for app development and hosting covers contracts with service providers, and data storage in the EU covers server location.
Phase 3: implementation in the app
- Consent dialogue: for non-essential access to the device, such as tracking, Germany's TDDDG applies alongside the GDPR. Rejecting must be as easy as accepting; see our article on tracking consent under the TDDDG.
- Request permissions sparingly: ask for camera, location or contacts only when the feature is used, with a clear explanation.
- Make the privacy policy accessible: within two taps in the app and in the store listing.
- Encryption: TLS for all connections, sensitive data on the device in secure storage (Keychain or Keystore), encryption in the backend.
- Access control: enforce roles and permissions on the server, not just in the UI.
- Logging without personal data: logs and crash reports must not contain passwords, health data or full message content.
Phase 4: enabling data subject rights technically
Users have, among others, the right of access (Art. 15), rectification, erasure (Art. 17) and data portability (Art. 20). Build features for these instead of handling every request manually:
- Account and data deletion directly in the app, which Apple and Google also require for apps that offer account creation.
- Export of the user's own data in a common format (e.g. JSON or CSV).
- Ability to edit the profile and withdraw consent at any time.
- Deletion in backups and at processors within defined periods.
Phase 5: operations, breaches and maintenance
- Implement the deletion concept: automatic deletion of inactive accounts and old logs after defined periods.
- Breach notification process: notifications to the supervisory authority are generally due within 72 hours of becoming aware (Art. 33). Define responsibilities in advance.
- Review SDK updates: new versions can introduce new data flows.
- Keep store disclosures current: Apple's privacy details and Google's data safety section must match actual processing.
- Regularly review technical and organisational measures (Art. 32).
Conclusion
A GDPR-compliant app is the result of many small, deliberate decisions: collect little data, choose providers carefully, obtain consent properly, support data subject rights technically and review operations continuously. Use the checklist as a guide in every project phase and have the legal assessment for your specific case confirmed by experts.
Frequently Asked Questions
Does every app need a privacy policy?
In practice yes, as soon as personal data is processed, and IP addresses or device IDs already count. Apple and Google also require a link to the privacy policy in the store listing.
Can I use Google Analytics or Firebase in a GDPR-compliant app?
It is possible in principle, but for analytics purposes it generally requires prior consent, a data processing agreement and an assessment of the third-country transfer. Privacy-friendly or self-hosted alternatives make the assessment much simpler.
Who is liable for data protection violations in an app, the client or the agency?
The controller under the GDPR is usually the app provider, i.e. the client. The agency is liable as a processor for its own obligations; this article is not legal advice.
When is a data protection impact assessment required?
When processing is likely to result in a high risk to individuals, for example large-scale processing of health data, profiling or location tracking. Supervisory authorities publish lists of processing operations for which it is generally required.