Contents
- Which legal texts does an app need?
- Legal notice in the app: easy to find and quick to reach
- Privacy policy: what is different in an app
- Terms, withdrawal and subscriptions: contracts in the app
- Technical implementation: keeping legal texts maintainable
- Common mistakes that trigger warning letters or rejections
- Conclusion
- Frequently Asked Questions
Under German law, an app usually needs a legal notice (Impressum), a privacy policy and, as soon as contracts are concluded, terms and conditions plus consumer information. What matters is not only the content but also where and how users can reach these texts in the app. This article explains the mandatory disclosures, how to integrate them technically and which mistakes commonly lead to warning letters or store problems.
Which legal texts does an app need?
Which texts you need depends on your business model. The overview below is guidance for apps offered in Germany; it is not legal advice and does not replace review by a lawyer or a specialised legal-text service.
| Legal text | When required | Legal basis (selection) |
|---|---|---|
| Legal notice (Impressum) | For commercial digital services, i.e. nearly all company apps | Section 5 DDG (formerly Section 5 TMG), possibly Section 18 MStV |
| Privacy policy | As soon as personal data is processed, which is practically always | Art. 13, 14 GDPR |
| Terms and conditions / terms of use | When you want to set usage rules, liability or contract conditions | Sections 305 et seq. BGB |
| Withdrawal notice and consumer information | For distance contracts with consumers, e.g. subscriptions or orders | Sections 312 et seq. BGB, Art. 246a EGBGB |
| Accessibility statement | For services covered by the BFSG | BFSG |
| Licence notices (open source) | When open-source libraries with attribution requirements are used | respective licence |
Legal notice in the app: easy to find and quick to reach
The provider identification must be easily recognisable, directly accessible and permanently available. For websites, German case law has established the rule of thumb that the legal notice should be reachable within two clicks. The same applies to apps by analogy.
- Placement: in a clearly visible menu item such as "Legal" or "Legal notice" in the settings or profile area, not hidden in a third-level submenu.
- Reachable without login: users should find the legal notice before registering, for example on the start screen or in the login dialogue.
- Labelling: use clear terms such as "Legal notice" or "Impressum", not creative paraphrases.
- Store listing: link to your website's legal notice in the App Store and Google Play. A legal notice only in the store listing may be enough in some situations, but having it in the app itself is the safe option.
The content includes name and address, legal form and authorised representatives, contact details including e-mail, commercial register entry and VAT ID where applicable, and further details for regulated professions.
Privacy policy: what is different in an app
An app's privacy policy differs from a website's. Do not simply copy the website version; describe the actual processing in the app:
- Permissions such as camera, location, contacts or microphone and what they are used for.
- Push notifications and the Apple and Google services involved.
- Embedded SDKs for analytics, crash reporting, login, payments or advertising.
- Backend hosting, processors and any third-country transfers.
- Retention periods, account deletion and data subject rights.
The privacy policy must also match the privacy disclosures in the stores. Contradictions surface at the latest during app review or when a complaint is filed. Our GDPR checklist for apps covers the technical requirements behind it; for the tracking consent dialogue, see tracking consent under the TDDDG.
Terms, withdrawal and subscriptions: contracts in the app
Once users conclude contracts in the app, things get more demanding. Under German law, terms and conditions only become part of the contract if the user is referred to them before conclusion and can reasonably take note of them. In practice this means:
- Link directly at the order or registration step, not just in the menu.
- Mobile-friendly display: long texts structured with subheadings, not a PDF download as the only option.
- Storability: consumers must be able to save the contract terms, for example via a confirmation e-mail including the terms.
- Withdrawal notice and mandatory information for consumer contracts, including clear details on price, term and cancellation.
- Label the order button unambiguously, for example "order with obligation to pay" or "buy now".
For in-app purchases via Apple or Google, their terms also apply, and payment and refunds are partly handled by the platform. For subscriptions concluded outside the stores, check the German rules on online cancellation. Read more about designing subscription models in subscription apps: pricing and churn.
Technical implementation: keeping legal texts maintainable
Legal texts change due to new SDKs, changes in law or new features. Texts hard-coded into the app require a new release and another store review for every change. These approaches have proven themselves:
- Central source: legal texts live on the website or in a CMS and are loaded and displayed in the app.
- Offline fallback: a bundled version is shown when there is no connection.
- Versioning: when terms change, store which version a user accepted and ask for renewed consent for material changes.
- Multilingual: provide texts in all languages the app supports.
- Accessible reading: scalable text and screen reader support for legal texts too.
In our projects we plan a "Legal" area by default; the content is supplied by the client or their legal advisors. You can get a fixed-price offer through our offer wizard.
Common mistakes that trigger warning letters or rejections
- Legal notice only on the website, not in the app and not linked in the store.
- Website privacy policy with no reference to app permissions and SDKs.
- Broken privacy policy link in the store listing, a classic cause of app store rejection.
- Terms only visible after purchase or only as a hard-to-read PDF.
- Missing or incorrect withdrawal notice for subscriptions sold outside the stores.
Conclusion
A legal notice, privacy policy and terms are mandatory in an app when you act commercially and process data or conclude contracts. Place the texts where they are easy to find, even without login, and tailor the privacy policy to the actual app. Technically, a central, versioned source pays off so changes are possible without a new release. Have the content itself reviewed by legal experts.
Frequently Asked Questions
Does an app need its own legal notice?
For commercial apps offered in Germany, provider identification under Section 5 DDG is generally required. The safest option is a clearly visible menu item in the app, reachable without login, in addition to the link in the store listing.
Can I use my website's privacy policy for the app?
Only if it fully describes the processing in the app, including permissions, SDKs, push services and backend. Usually a dedicated app section or a separate app privacy policy is needed.
Do I need terms and conditions for a free app?
They are not legally mandatory, but they are useful for setting usage rules, liability and rules for user content. This article is not legal advice; have your texts reviewed individually.
How do I keep legal texts in the app up to date?
Load the texts from a central source such as your website or CMS and bundle an offline version. This allows changes without a new app release.