RU EN
www.
Technical audit · 29.05.2026

bbk.bund.de

German Federal Office of Civil Protection and Disaster Assistance
DE

Policy changed — see what exactly · 2026-10-08 →

BBK — the federal civil protection agency, issuing hazard warnings and guidance for public preparedness. 65 requests, 1 domain. BundesSans and BundesSerif served locally. Matomo is documented as opt-in via a cookie banner — absent from the HAR. ReadSpeaker — local JS with no external requests. Full compliance.

Request timeline

+177 ms · load
All CSS, JS, SVG icons — from www.bbk.bund.de. Leichte Sprache icons, the NINA logo, Cell Broadcast — all local.
+187 ms · ReadSpeaker
www.bbk.bund.de/readSpeaker/webReader.js — ReadSpeaker (a text-to-speech tool) loads as local JS with no external calls. The IP address is transmitted to ReadSpeaker only when the 'Vorlesen' button is clicked.
+474 ms · fonts
www.bbk.bund.de/static/fonts/BundesSchrift — BundesSansWeb (Regular, Bold, BoldItalic, Italic) and BundesSerifWeb (Regular, Bold). The state font standard, fully local.
No external domains
Not a single request outside www.bbk.bund.de. Matomo is not activated — no consent. Set-Cookie — zero.

Declared versus actual

✓ Matomo — documented as opt-in via a cookie banner (Statistikcookies) — declared
✓ ReadSpeaker webReader — documented (IP transmitted only on activation) — declared
✓ JSESSIONID — a technically necessary session cookie, documented — declared
✓ Hosting: ITZBund — documented as a data recipient — declared

Context

BBK (Bundesamt für Bevölkerungsschutz und Katastrophenhilfe) is the federal agency responsible for warning the public of hazards (the NINA system, Cell Broadcast), coordinating civil protection, and publishing the “Ratgeber für Notfallvorsorge und richtiges Handeln in Notsituationen.” It reports to the BMI. HAR: 65 requests, 1 domain.

Matomo opt-in — correctly implemented

The privacy policy contains an unambiguous statement: “Die Webanalyse wird jedoch nur aktiviert, sofern Sie über das Cookie-Banner ausdrücklich in die Nutzung von „Statistikcookies” eingewilligt haben (‘Opt-In’)." This is a correct implementation of the requirements of TDDDG § 25 and Art. 6(1)(a) DSGVO. In the HAR from May 2026, there are no Matomo requests: neither matomo.js nor matomo.php. The opt-in mechanism works as documented — unlike bauindustrie.de, where Matomo fires before consent despite an identical declaration.

Matomo is hosted on ITZBund (Informationstechnikzentrum Bund) infrastructure — Germany’s federal IT center. Data is processed within Germany’s state infrastructure.

ReadSpeaker — accessibility without tracking

ReadSpeaker webReader is a text-to-speech tool for people with visual or reading impairments. It loads as a local JS file (/readSpeaker/webReader.js). The policy clearly states that the IP address is transmitted to ReadSpeaker GmbH’s servers (Bad Wörishofen) only when the “Vorlesen” button is clicked — not on page load. This is a correct implementation of accessibility without background data transfer. Legal basis: Art. 6(1)(b) DSGVO (performance of a contract / a user’s request).

BundesDesign and state infrastructure

BundesSansWeb and BundesSerifWeb are hosted locally. All images, icons, and SVG graphics are on the proprietary server. CMS: the standard bundesgov platform. Hosting via ITZBund — a state provider.

Conclusion

bbk.bund.de is the third zero result in the German series, after bundespolizei.de and bamf.de. All three are federal security bodies. The pattern is consistent: Germany’s federal security and critical-infrastructure bodies build architectures with zero external domains, state hosting, and correct implementation of opt-in consent. BBK additionally demonstrates an exemplary implementation of an accessibility tool: ReadSpeaker transmits data only on the user’s explicit request.

Evidence

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.

Original (audit)
HAR file: de/bbk-bund-de-2026-05-29.har
SHA-256: 7e8fe09977bf21412103c031d5bde7ed661346e690b8904ec1194c773e25cbeb
HAR files are stored on EU infrastructure (Proton Drive). SHA-256 is published for integrity verification.
Want 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.

Step 1. Data access request (GDPR Art. 15)

Send this letter directly to the company first — before contacting the regulator it has the right to respond (GDPR Art. 12(3) — 30 days).

Subject: Data access request (GDPR Art. 15) — bbk.bund.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 bbk.bund.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-bbk-bund-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]