Compliance
Does the privacy policy need to be called Datenschutzerklärung
What 13x checks
This is rule compliance.datenschutz in the public registry: Datenschutzerklärung is a separate page. It runs on every audit, against the pages we actually fetched, and its result is derived from the response rather than estimated.
- Surface
- Compliance
- Score weight
- 8 of the readiness score
- Scope
- Runs on every audited page
- Applies
- Only where the market or the page shape makes it relevant
Registry version 2026-07-30. Every rule is published, and the audit is deterministic — the same page produces the same finding every time.
The fix
The same text the audit hands you when this check fails on your own site.
Publish a Datenschutzerklärung as its own page at /datenschutz, linked from the footer, and label the link with that word — German visitors and German authorities look for it specifically.
Folding it into the Impressum does not satisfy Art. 13 GDPR; it needs to be separately reachable.
If your site is bilingual, keep both: /datenschutz and /privacy, each linked from the matching language version.
Does your site have this problem?
13x checks this and 112 others against your live URL in about 30 seconds. No account, and every finding comes with the fix for your framework.
No signup. Results in 30 seconds.
More compliance checks
- Does my site need a privacy policyPrivacy policy is linked
- Does my website need an ImpressumImpressum is linked and reachable
- My analytics fires before consentNo trackers fire before consent
- Do I need a cookie consent bannerConsent banner present when third-party scripts load
- Is loading Google Fonts from the CDN a GDPR problemNo fonts loaded from Google's CDN
- Do I need a Do Not Sell My Personal Information linkCalifornia opt-out link present