app-entwickeln-lassen.de LogoApp entwickeln lassen

Legal, Privacy & Security

Data Processing Agreements (DPA) for App Development and Hosting

app-entwickeln-lassen.de editorial team 6 min read
Contents
  1. What is a DPA and why is it mandatory?
  2. When do you need a DPA in an app project?
  3. Mandatory content of a DPA under Art. 28 GDPR
  4. The provider chain: keeping track of sub-processors
  5. Technical and organisational measures: what to look for
  6. Practical checklist for clients
  7. Conclusion
  8. Frequently Asked Questions

A data processing agreement (DPA, in German "AVV") is required in app development whenever a service provider processes personal data on your behalf, for example in hosting, maintenance with access to production data or support. Under Art. 28 GDPR it ensures that the provider processes the data only on your instructions and with appropriate security measures. This article explains when you need a DPA, what it must contain and how to keep the chain of providers under control.

What is a DPA and why is it mandatory?

The GDPR distinguishes between the controller, who decides on the purposes and means of processing, and the processor, who processes data on the controller's behalf. For an app, the provider, usually you as the client, is the controller. Hosting providers, agencies with data access or services such as e-mail delivery are typically processors.

Art. 28 GDPR requires processing on behalf of a controller to be governed by a contract with certain minimum content. Without such a contract, there may be a data protection violation for both the controller and the provider. This article is a practical overview and not legal advice.

When do you need a DPA in an app project?

SituationPersonal data involved?DPA needed?
Agency develops with test data only, no access to production systemsnousually no, a confidentiality agreement is often enough
Agency uses a copy of real user data for testing or migrationyesyes
Agency operates or maintains the production systemyesyes
Hosting, cloud or database provideryesyes
E-mail, SMS or push delivery serviceyesyes, or review the provider's terms
Crash reporting, monitoring, analytics toolsmostly yesusually yes
AI service receiving user inputoften yesusually yes, also check use for training
Payment service provideryesoften the provider acts as its own controller, check case by case

Not every provider is a processor. Payment providers or the app stores often process data as independent controllers because they have their own purposes and legal obligations. The classification depends on the specific service.

Mandatory content of a DPA under Art. 28 GDPR

A DPA must cover at least the following points:

  • Subject matter and duration of the processing.
  • Nature and purpose of the processing.
  • Type of personal data (e.g. contact data, usage data, health data) and categories of data subjects (e.g. app users, employees).
  • Instructions: processing only on documented instructions from the controller.
  • Confidentiality of the persons involved.
  • Technical and organisational measures under Art. 32, usually described in an annex.
  • Sub-processors: only with authorisation; with general authorisation, a right to be informed and to object.
  • Assistance duties for data subject rights, data breaches and data protection impact assessments.
  • Deletion or return of data at the end of the engagement.
  • Evidence and audit rights, including inspections.

The European Commission has published standard contractual clauses for controller-processor relationships, and many contracts follow them. Large cloud providers offer their own data processing terms, which you usually cannot negotiate but should review and file.

The provider chain: keeping track of sub-processors

App projects quickly create a long chain: your agency hosts with a cloud provider and uses an e-mail service, a monitoring tool and perhaps an AI service. Each of these is a sub-processor. As the controller, you should:

  1. Request a list: have all sub-processors named with their location, processing location and purpose.
  2. Check third-country transfers: is data processed outside the EU/EEA, or can it be accessed from there? Then appropriate safeguards are needed, such as an adequacy decision, certification under the EU-US Data Privacy Framework or standard contractual clauses.
  3. Control changes: the DPA should require that you are informed about new sub-processors in advance and can object.
  4. Document: all DPAs and sub-processors belong in your record of processing activities.

Hosting in Germany or the EU simplifies this review considerably. Read more in cloud hosting for apps in Germany and data storage in the EU: server location and third-country transfers.

Technical and organisational measures: what to look for

The TOM annex is the heart of a DPA but often only skimmed. In app projects, pay particular attention to:

  • Encryption in transit and at rest, including backups.
  • Need-to-know access model, two-factor authentication for admin access.
  • Logging of administrative access to production data.
  • Separate environments for development, testing and production; no real data in development without anonymisation.
  • Rules for handling credentials and secrets, including in AI-assisted development.
  • Backup and recovery concept with tested recovery times.
  • A process for notifying you of data breaches without undue delay.

Practical checklist for clients

  1. Sketch the app's data flows: which providers see which personal data?
  2. Clarify each provider's role: processor, independent controller or joint controller.
  3. Sign a DPA with the agency as soon as it gets access to production data.
  4. Review and file the data processing terms of cloud and SaaS services.
  5. Obtain the list of sub-processors and processing locations.
  6. Check the TOMs for plausibility, especially encryption and access.
  7. Agree on deletion or return of data at the end of the contract, which also matters if you later change agencies.

Our GDPR checklist for apps covers further privacy points around your app. In our projects, GDPR-compliant development and hosting in Germany is standard, and we provide a DPA as soon as we process data on your behalf. You can get a fixed-price offer through our offer wizard.

Agentic coding workshop for your team? From €799 net – request a quote by e-mail

Conclusion

A DPA is not a formality; it governs who may process which data in your app and how. The key is knowing your data flows, classifying each provider correctly and keeping the chain of sub-processors transparent. With EU hosting, clear TOMs and clean documentation you create a solid foundation for data protection audits as well as for questions from business customers.

Frequently Asked Questions

Does my app agency need a DPA?

Yes, as soon as it processes personal data on your behalf, for example in hosting, maintaining the production system or testing with real data. If it works exclusively with test data, a DPA is usually not required.

Who has to draw up the DPA, the client or the provider?

The controller, i.e. the client, is responsible for concluding it. In practice, providers often supply their own template, which you should review; this article is not legal advice.

Is a DPA with a US cloud provider enough?

The DPA alone is not sufficient if data is transferred to a third country or can be accessed from there. Appropriate safeguards such as the EU-US Data Privacy Framework or standard contractual clauses are also required.

What happens to the data if we change agencies?

The DPA should require the previous provider to return or delete the data after the contract ends. Plan the handover early so that operations and data protection remain seamless.

This article was written by the editorial team of app-entwickeln-lassen.de – the app and AI development service of jocapps GmbH, based in Freiburg, Germany, and building apps since 2014. The content is for general information and does not replace individual (legal) advice.

You might also like

Legal, Privacy & SecurityTracking Consent in Apps: What Germany's TDDDG Requires

Tracking consent in apps under Germany's TDDDG: when you need consent, what a compliant consent dialogue looks like and how to start SDKs correctly.

6 min read
Legal, Privacy & SecurityCopyright of AI-Generated Code: Who Owns What?

Copyright of AI-generated code explained: when code is protected, what tool terms and open-source licences mean, and how to secure your rights by contract.

7 min read
Legal, Privacy & SecurityLegal Notice, Privacy Policy and Terms in Your App: A Guide

Legal notice (Impressum), privacy policy and terms in your app: which disclosures German law requires, where they belong and how to integrate them cleanly.

6 min read
Legal, Privacy & SecurityNIS2 and the Cyber Resilience Act: What Applies to Software and Apps?

NIS2 and the Cyber Resilience Act explained: who is covered, which obligations apply to software and apps, and how to prepare your products and processes now.

6 min read
Legal, Privacy & SecurityAvoiding App Store Rejection: Common Reasons and Fixes

Avoid app store rejection: the most common reasons at Apple and Google Play, how to respond correctly and a pre-submission checklist to prevent rejections.

6 min read
Legal, Privacy & SecurityApp Penetration Testing: When and How You Should Test

App penetration testing explained: when a pentest pays off, what gets tested, how the process works and what to look for in provider, scope and final report.

6 min read