Privacy in AI-built apps: what the radar measured
Trackers before consent, cookies without agreement, missing legal notice: three findings from 3,728 scanned apps with a DACH connection, with count and base.
13% of the AI-built apps checked in a browser contacted trackers before any consent existed (13% (420 of 3,280)). 7% already set tracking cookies, and 11% of all apps had no recognisable link to a legal notice or privacy policy. Source: decivo AI App Radar DACH, run “2026-Q4-recall”, 3,728 apps.
Key points
- 13% of the 3,280 AI-built apps with a DACH connection that were checked in a browser (420 apps) contacted trackers on first load before any consent was given.
- 11% of the 3,728 discoverable AI-built apps with a DACH connection (424 apps) had no recognisable link to a legal notice or a privacy policy.
- 7% of the 3,280 AI-built apps with a DACH connection that were checked in a browser (243 apps) set tracking cookies before any consent was given.
The three figures
All three findings carry severity “high”. A single one prevents a “Go”.
- Trackers fire before consent
- Legal notice or privacy policy not linked
- Tracking cookies set before consent
Trackers and cookies can only be observed in a real browser. These two rows therefore count across the apps with a browser run.
Sentences to quote
You can use these sentences word for word. Each one names share, base and count. Please include the source line below.
13% of the 3,280 AI-built apps with a DACH connection that were checked in a browser (420 apps) contacted trackers on first load before any consent was given.
11% of the 3,728 discoverable AI-built apps with a DACH connection (424 apps) had no recognisable link to a legal notice or a privacy policy.
7% of the 3,280 AI-built apps with a DACH connection that were checked in a browser (243 apps) set tracking cookies before any consent was given.
Why this matters
In Germany, section 25 TDDDG requires consent before a site stores or reads anything on the device that is not strictly necessary for the requested service. Whether personal data is involved does not matter. An analytics script that loads on the first visit is therefore the breach itself, not merely its consequence.
The error is almost always unintended. An AI builder places the script in the page head, the consent banner is added later and does not control the script. The banner is then visible but has no effect.
In Germany, legal notice and privacy policy must be easy to recognise and reachable from every page (section 5 DDG, Art. 13 GDPR). The rule only checks whether both are linked. It says nothing about their content.
What the figures do not say
The radar measures what can be found. The 3,728 apps are not a random sample of all AI-built apps. The correct phrasing is “x% of the 3,728 discoverable AI-built apps with a DACH connection”, never “x% of all Lovable apps”.
The check runs from the outside and without logging in: what the page ships and what a browser observes while loading. The radar does not see database rules, roles or anything behind the login. A share says for how many apps a rule fired. It does not say whether the finding holds in each case, and it is not legal advice.
The report deliberately does not cite everything. At the time, for fonts, trackers, contacted services and findings in shipped code a mere mention also counted, for example in an embedded third-party script. Since methodology 2026.43 only what the page demonstrably loads or contains in its own code counts; exception: if the page ships no code of its own, the rules for database write calls and role comparisons check an embedded third-party script. These shares may be lower when measured again. Those shares are in the dataset, but not in this text.
The figures are decivo's own survey. decivo itself offers to fix such findings. They have not been independently verified so far; the dataset is open for that purpose.
The scan clicks “Reject” once at most. It does not measure what happens after agreeing.
The basis is the run “2026-Q4-recall”, closed on 8 November 2026. Across all 14 runs since September 2026 the radar has scanned 4,402 apps; the report uses the single run because it has one methodology and a fixed address.
Check your own app
Open your app in a private window, open the network view of the developer tools and reload the page without touching the banner. If calls to analytics or advertising services show up there, the tracker fires before consent.
The free scan observes this automatically in a browser and names the services. The other figures are in the AI App Report DACH 2026.
Sources
Every share comes from the radar run named below. Its fixed address shows exactly these figures; the legal sources are the statutes themselves.
Whether your app is part of these shares, the free scan shows in a few minutes: from the outside, without access, with evidence for each finding.
Check your app for freeQuestions about privacy
How many AI-built apps load trackers without consent?
13% of the 3,280 AI-built apps with a DACH connection that were checked in a browser (420 apps) contacted trackers on first load before any consent was given.
Is a cookie banner enough?
Only if it really holds the scripts back. A banner that appears while the tracker has long since loaded does not change the finding.
Does the radar say whether an app is GDPR compliant?
No. It counts findings visible from the outside. It does not see contracts, records or anything behind the login.
Related articles
- AI code quality
Accessibility of AI-built apps: radar figures 2026
The most frequent finding in the AI App Radar DACH: serious accessibility violations in the fully loaded page. Figure, method, limits and a sentence to quote.
- AI code quality
AI-built apps in Germany and Switzerland compared
How many AI-built apps pass the scan without an urgent finding? The verdicts of the AI App Radar DACH, split by country and by builder.
- Vibe Code Rescue
Lovable DPA & GDPR: Plans, Sub-processors, Data Location
Lovable ties its DPA to Business and Enterprise, Lovable Cloud stores data in the chosen region — AI requests not. How Supabase, Base44 and Bolt differ, which obligations your app has itself (legal notice, Art. 13, § 25 TDDDG, AI Act Art. 50, BFSG) a 12-point checklist and our own data from 454 AI-built apps in the DACH region.
Where does your app stand by comparison?
The decivo Scan checks your app from the outside, with the rules as they stand today, and names every finding with evidence.
30 minutes, free. You talk to us directly.