Policy changed — see what exactly · 2026-08-12 →
German Federal Police. 47 requests, 1 domain. BundesSans and BundesSerif served locally. A proprietary consent overlay and cookieBannerFull — no external CMP platforms. Not a single request outside bundespolizei.de. Full compliance.
Request timeline
Context
Bundespolizei is Germany’s federal police, subordinate to the Federal Ministry of the Interior. It secures state borders and safeguards federal railways and airports. Sensitivity is high. HAR: 47 requests, 1 domain.
Clean architecture
All 47 requests go exclusively to bundespolizei.de. The stack: proprietary Typo3 CMS CSS files, BundesSans-Web and BundesSerif-Web — Germany’s state design-standard fonts (Bundesdesign), hosted locally. Swiper.js, Solr — all local. Social media icons (Facebook, YouTube, Instagram, X, WhatsApp) — static SVGs with no external SDK.
Consent management is implemented with no external CMP platforms: a proprietary consent-overlay.js (+301 ms), cookieBannerFull.js (+350 ms), and consent.html (+353 ms). The policy describes only session cookies, technically necessary for the site’s operation, referencing § 25 para. 2 TDDDG (Telekommunikation-Digitale-Dienste-Datenschutz-Gesetz) — Germany’s implementation of ePrivacy. No OneTrust, no Cookiebot, no Cookie Script.
BundesDesign as a privacy factor
Using the federal BundesSans/BundesSerif font family is not merely a matter of corporate identity. These fonts are part of the state design standard and are distributed centrally. Hosting them locally removes the need to contact external CDNs (Google Fonts, Adobe Fonts) on every visit — itself an architectural decision in favor of privacy.
Place within the German series
bundespolizei.de opens the German series the same way cao.ie opened the Irish one — with zero external domains and zero violations. Germany, with its established GDPR enforcement practice (BfDI rulings, the Munich court’s Google Fonts decision, DSK positions on cookie banners), historically forms a stricter supervisory environment. This first site sets the benchmark for comparison.
Conclusion
bundespolizei.de violates nothing: one domain, local resources, a proprietary consent mechanism, a policy with specific legal bases (TDDDG, BDSG, BSIG). For the website of the federal police, whose visitors may be in sensitive circumstances, this is the correct standard.
How to verify: download the file and compute its checksum — sha256sum file.har (Linux, macOS) or certutil -hashfile file.har SHA256 (Windows); it must match the one shown. The conclusions apply to the scope of this measurement — see the limitations of the method.
47a7cf09b15cfe7275bf06407c3960f67a04f57a95a1fbb19aee954571e03cdcWant a response from the company about this audit? → Open the tool
Fill in once — it will be inserted into every letter below:
All fields are required to print the document — this is a formal requirement of the letter itself (the particulars of an official submission), not data collection: nothing is sent or saved anywhere, it all stays in your browser and disappears when you close the page. See the methodology for details.
RIA DigiDoc — phone · Smart-ID / Mobile-ID
Send this letter directly to the company first — before contacting the regulator it has the right to respond (GDPR Art. 12(3) — 30 days).
Тема: Запрос доступа к персональным данным (ст. 15 GDPR) — bundespolizei.de Кому: [укажите адрес компании — DPO / поддержка / юридический отдел] От: [Ваше имя], [контактный email] Прошу предоставить доступ к моим персональным данным, обрабатываемым в связи с использованием сайта bundespolizei.de. 1. Категории данных и цели обработки (ст. 15(1)(a)-(c)) Прошу предоставить информацию по всем категориям, целям и получателям обработки моих данных на этом сайте — независимо от того, выявлены ли на сегодняшний день какие-либо несоответствия. 2. Получатели, сроки хранения и передача за пределы ЕЭЗ (ст. 15(1)(c)-(d), 46) Прошу также указать полный список третьих лиц-получателей, применимые сроки хранения по каждой категории и правовые основания передачи данных за пределы ЕЭЗ, если таковая происходит. Полный технический разбор с доказательствами (сохранённый сетевой журнал, контрольная сумма SHA-256) опубликован по адресу: https://gdpru.eu/en/audits/de-bundespolizei-de/ 3. Автоматизированная обработка и профилирование (ст. 15(1)(h)) Прошу сообщить, применяется ли в отношении меня автоматизированное принятие решений или профилирование, и если да — раскрыть логику такой обработки. С уважением, [Ваше имя] [контактный email] [Страна] [Дата]
Subject: Data access request (GDPR Art. 15) — bundespolizei.de To: [insert the company's address — DPO / support / legal department] From: [Your name], [contact email] I request access to my personal data processed in connection with the website bundespolizei.de. 1. Categories of data and purposes of processing (Art. 15(1)(a)-(c)) I request information on all categories, purposes, and recipients of my data processed on this site — regardless of whether any non-compliance has been identified to date. 2. Recipients, retention periods, and transfers outside the EEA (Art. 15(1)(c)-(d), 46) I also request the full list of third-party recipients, the applicable retention period for each category, and the legal basis for any transfer of data outside the EEA. The full technical audit with evidence (saved network log, SHA-256 checksum) is published at: https://gdpru.eu/en/audits/de-bundespolizei-de/ 3. Automated processing and profiling (Art. 15(1)(h)) Please state whether I am subject to automated decision-making or profiling, and if so, disclose the logic involved. Sincerely, [Your name] [contact email] [Country] [Date]