RU EN
www.
Technical audit · 29.05.2026

bamf.de

German Federal Office for Migration and Refugees
DE

Federal Office for Migration and Refugees — the body that processes asylum applications. 58 requests, 1 domain. BundesSans and BundesSerif served locally. Matomo is documented in the policy with opt-out — entirely absent from the HAR. Not a single external domain. Full compliance.

Request timeline

+77 ms · load
All CSS, JS, icons, and images load from www.bamf.de. Leichte Sprache (easy language) and Gebärdensprache (sign language) symbols — SVG icons, local.
+166 ms · fonts
www.bamf.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.bamf.de. No Matomo, no YouTube, no Google. Set-Cookie — zero.

Declared versus actual

✓ Matomo — documented in the policy with an opt-out mechanism — declared
✓ YouTube — mentioned in the policy for embedded videos — declared
✓ Session cookies — documented as strictly necessary — declared

Context

BAMF (Bundesamt für Migration und Flüchtlinge) is the federal agency that decides asylum applications, manages integration programs, and maintains records of foreign nationals. Sensitivity is high: the site’s visitors include asylum seekers, refugees, and migrants. HAR: 58 requests, 1 domain.

Architectural discipline

All 58 requests are directed exclusively to www.bamf.de. BundesSans and BundesSerif — the state Bundesdesign font standard — are hosted locally at /static/fonts/BundesSchrift/. Leichte Sprache and Gebärdensprache icons are SVG files on the proprietary server. No Google Fonts, no CDN, no external JS libraries.

Matomo in the policy — not in the HAR

BAMF’s privacy policy describes Matomo (formerly Piwik) as an anonymous visit-statistics tool: “Rückschlüsse auf die Identität der Nutzer und Teilnehmer sind nicht möglich.” An opt-out is provided — the user can decline. Legal basis: Art. 6(1)(f) DS-GVO (legitimate interest). In the HAR from May 2026, Matomo is entirely absent: no matomo.js, no piwik.php, no requests of any kind to a Matomo domain. It is possible the audit was conducted in an opt-out state carried over from a previous session, or that Matomo was disabled during the audit period.

YouTube — in the policy, not in the HAR

The policy mentions embedded YouTube videos using the enhanced data protection mode (erweiterter Datenschutzmodus). No YouTube embeds were recorded on the homepage at the time of the audit.

Easy language and sign language

The homepage offers links to versions of the site in Leichte Sprache (easy language for people with cognitive differences) and Gebärdensprache (sign language). For an agency working with refugees from various countries with varying levels of German proficiency, this is a critically important feature. The corresponding SVG icons are implemented with no external dependencies.

Conclusion

bamf.de — an agency serving one of the most vulnerable categories of visitors to state websites — demonstrates an architecture with zero external domains. This is the second zero result in the German series, after bundespolizei.de. Both are federal law-enforcement and security bodies. A pattern is already emerging in the German series: the more sensitive the data being processed, the cleaner the architecture.

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/bamf-de-2026-05-29.har
SHA-256: 23a0f305c719d7ed146d37dbe576db824208e081dc3f02df79b13961f3549f12
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) — bamf.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 bamf.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-bamf-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]