Contents
In Germany, tracking in apps requires prior user consent in most cases, based on Section 25 TDDDG together with the GDPR. This applies not only to browser cookies but also to device IDs, advertising IDs and data stored locally by analytics and marketing SDKs. This article explains when consent is needed, what a proper consent dialogue looks like and how to implement it technically.
The TDDDG in brief: from TTDSG to TDDDG
The Telecommunications Digital Services Data Protection Act (TDDDG) is the new name of the former TTDSG; it was renamed in 2024 alongside the Digital Services Act implementation in Germany. The rule that matters for apps stayed the same: Section 25 TDDDG protects users' "terminal equipment", which includes smartphones and tablets. Anyone storing information on the device or accessing information already stored there generally needs consent. It implements the ePrivacy Directive, so similar rules exist across the EU.
The rule is technology-neutral. It covers cookies as well as local app storage, advertising IDs, device fingerprinting and SDKs that store identifiers on the device. This article is a practical overview and not legal advice.
When is no consent needed?
Section 25(2) TDDDG contains two exceptions. No consent is required if access serves solely to transmit a message, or if it is strictly necessary for the provider to deliver a service explicitly requested by the user. This exception is interpreted narrowly.
| Access / storage | Purpose | Consent under TDDDG needed? |
|---|---|---|
| Login token, session data | Staying logged in | usually no |
| Cart, language setting, offline data | Providing a requested feature | usually no |
| Push token | Notifications enabled by the user | mostly no, push permission is requested anyway |
| Security mechanisms, fraud detection | Protecting the service | case by case, often justifiable without consent |
| Audience measurement / usage analytics | Improving the product | usually yes |
| Crash reporting with device ID | Fixing bugs | disputed, consent often recommended |
| Advertising ID, attribution, retargeting | Marketing | yes |
| Personalised advertising | Monetisation | yes |
Important: the TDDDG only governs access to the device. Subsequent processing of personal data also needs a legal basis under the GDPR. In practice, a combined consent is usually obtained for tracking. Our GDPR checklist for apps summarises the broader privacy requirements.
Requirements for valid consent
Consent is only valid if it is freely given, informed, unambiguous and specific to defined purposes. For the consent dialogue in apps this means:
- Before access: tracking SDKs may only be initialised after consent, not at app start.
- Equal options: "Reject" must be as easy to reach and as visible as "Accept", ideally on the first layer.
- No pre-ticked boxes: optional purposes are disabled by default.
- Clear purposes: instead of "We improve your experience", name them specifically: usage analytics, ad measurement, personalised ads, and the providers involved.
- Granularity: separate consent by purpose so users can allow analytics but reject advertising, for example.
- Withdrawal at any time: a menu item like "Privacy settings" lets users change their decision as easily as they gave it.
- Proof: time, dialogue version and selected options are logged.
Manipulative design ("dark patterns"), such as a highlighted accept button with a hidden reject option, is viewed increasingly critically by authorities and courts.
Apple ATT and the Android advertising ID: platform rules on top
Besides the law, platform rules apply:
- iOS – App Tracking Transparency (ATT): anyone tracking users across other companies' apps and websites or accessing the advertising ID (IDFA) must show Apple's system prompt. However, the ATT prompt does not automatically replace consent under the TDDDG and GDPR, as it does not explain purposes and providers in the required detail.
- Android – advertising ID: apps must declare access to the advertising ID, and users can reset or delete it. Legal consent is required here too.
- Order: a proven approach is to show your own consent dialogue first and trigger the ATT prompt only if the user agrees to tracking purposes. Check Apple's current design requirements.
Technical implementation in five steps
- Create an SDK inventory: which libraries access the device or send data? Capturing network traffic on first launch often reveals surprises.
- Initialise SDKs based on consent: disable automatic initialisation and start them manually only after consent.
- Integrate consent management: your own solution or a consent management platform with native SDKs for iOS and Android.
- Manage consent status centrally: on withdrawal, stop SDKs and delete stored identifiers where possible.
- Test and document: for every combination of acceptance and rejection, verify that only permitted data actually flows.
The TDDDG also provides for recognised consent management services through which users can manage their decisions centrally. How widely these will be adopted remains to be seen; it does not change your app's duty to show a proper consent dialogue.
Privacy-friendly alternatives to classic tracking
Not every app needs extensive tracking. Aggregated metrics are often enough for product decisions: server-side analysis of your own backend logs without device identifiers, self-hosted analytics with short retention, or the anonymised statistics the App Store and Google Play provide anyway. Our article on app analytics and KPIs explains which metrics really matter. Whether such solutions work without consent depends on the specific implementation and should be reviewed.
When developing apps, we plan the consent dialogue and consent-based SDK initialisation from the start. You can get a fixed-price offer through our offer wizard; for integrating the related legal texts, see legal notice, privacy policy and terms in your app.
Agentic coding workshop for your team? From €799 net – request a quote by e-mailConclusion
The TDDDG does not make tracking in apps impossible, but it requires a genuine, informed user decision before analytics or advertising SDKs access the device. The keys are a fair consent dialogue, technically clean deferred SDK initialisation and easy withdrawal. If you also rely on privacy-friendly measurement, you reduce legal risk and earn user trust.
Frequently Asked Questions
Does the TDDDG apply to apps or only to websites?
It applies to apps too. Section 25 TDDDG protects all terminal equipment, including smartphones and tablets, regardless of whether cookies or other storage techniques are used.
Is Apple's ATT prompt enough as consent?
Usually not, because it does not sufficiently explain purposes and providers. The common approach is your own consent dialogue supplemented by the ATT prompt; this article is not legal advice.
Do I need consent for crash reporting?
This is disputed and depends on the implementation, for example whether device IDs are stored. Many providers obtain consent as a precaution or use privacy-friendly variants without persistent identifiers.
What happens if users reject tracking?
The app must remain fully usable and tracking SDKs must not start. You lose measurement data but can still make informed decisions using aggregated statistics.