RU EN
www.
Technical audit · 29.05.2026

bfdi.bund.de

Federal Commissioner for Data Protection and Freedom of Information
DE

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

BfDI — Germany's federal data protection regulator, overseeing GDPR enforcement. 38 requests, 2 domains. The only external one is social.bund.de (a state Mastodon server). Source Sans Pro and Source Serif 4 served locally. No analytics, no trackers, only session cookies under § 25 Abs. 2 TDDDG. Full compliance.

Request timeline

+81 ms · load
CSS, SVG icons, images — all from www.bfdi.bund.de. On the homepage: Cookie-Banner.jpg, Datenschutz-Schild-mit-Haken.jpg — visual content about data protection.
+231 ms · Mastodon
social.bund.de/system/accounts/avatars/000/000/003/original/a85f358db65f96d5.gif — BfDI's account avatar on the state Mastodon server. The only external request.
+233 ms · JS
www.bfdi.bund.de/global.js — the only JS file.
+262 ms · fonts
Source Sans Pro (Regular, Bold, BoldIt, It) and Source Serif 4 (SemiboldIt) — all local, at /static/fonts/. No BundesSans — BfDI uses its own font choice.
No trackers
No Matomo, no etracker, no analytics. No cookie banner — nothing to ask: only technically necessary session cookies under § 25 Abs. 2 TDDDG are used. Set-Cookie — zero.

Declared versus actual

✓ Session cookies — § 25 Abs. 2 TDDDG (technisch notwendig) — declared
✓ Log file (Protokolldatei, 30 days, ITZBund) — documented — declared
✓ No analytics or advertising cookies — explicitly declared — declared

Transfer timings

+231 ms social.bund.de

BfDI's Mastodon avatar. State infrastructure.

Context

BfDI (Der Bundesbeauftragte für den Datenschutz und die Informationsfreiheit) is the independent federal body overseeing GDPR compliance by Germany’s federal agencies, as well as by telecommunications companies. BfDI is the body that issues TDDDG guidance and rules on GDPR complaints at the federal level. HAR: 38 requests, 2 domains.

Zero analytics — an explicit policy stance

BfDI’s privacy policy states directly: “Techniken, wie zum Beispiel Java-Applets oder Active-X-Controls, die es ermöglichen, das Zugriffsverhalten der Nutzer nachzuvollziehen, werden nicht eingesetzt.” This is a declared rejection of any behavioral-tracking tools — not merely documenting an absence, but an explicit policy statement. There is no Matomo, no etracker, no Piano Analytics, no GTM in the HAR. Only session cookies are used, classified as technisch notwendig under § 25 Abs. 2 TDDDG — with no banner, which is correct for this category.

Source Sans Pro and Source Serif — not BundesSans

BfDI uses Source Sans Pro (Adobe Open Source) and Source Serif 4 — both hosted locally — instead of the standard state platform’s BundesSansWeb. This indicates that BfDI does not use the standard BUND-CMS platform operated by ITZBund, but manages its site through a separate CMS installation. Nonetheless, the principle of local font hosting is upheld.

social.bund.de — the only external domain

Like BMI, BfDI uses the state Mastodon server social.bund.de to display a feed of posts. One request — BfDI’s account avatar. State infrastructure, with no data transfer outside the state perimeter on page load.

Place within the German series

BfDI joins the reference-standard row of the German series. For a regulator whose function is to oversee GDPR compliance by other federal bodies, a zero result is the baseline expectation. dataprotection.ie (one request against one statement) and comreg.ie (the ePrivacy regulator with a 1299 ms gap before the banner), both from the Irish series, form a direct contrast. BfDI demonstrates what the DPC and ComReg failed to achieve: full compliance with their own standards.

Conclusion

bfdi.bund.de is the ninth zero result in the German series. Germany’s federal data protection regulator implements the principle of minimal data processing on its own site, explicitly declaring its rejection of behavioral tracking. This is not merely technical compliance — it is institutional consistency.

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/bfdi-bund-de-2026-05-29.har
SHA-256: 2dc0b56ef1a590efd797cb0ef7f94f933585df2988af33ed144a712b55e5863c
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) — bfdi.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 bfdi.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-bfdi-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]