RU EN
www.
Technical audit · 29.05.2026

bundesverfassungsgericht.de

German Federal Constitutional Court
DE

German Federal Constitutional Court. 18 requests, 1 domain. GSB platform, ITZBund, Apache. AkkoPaneuropean and Sabon LT Pro — corporate typefaces, served locally. An extremely strict CSP with a sha256 hash, self only. No analytics, no banner, no trackers. ITZBund declared. Set-Cookie — zero. Full compliance.

Request timeline

+0 ms · homepage
www.bundesverfassungsgericht.de — GSB, Apache, ITZBund. Brotli compression. CSP: default-src 'self' with a sha256 hash for the inline script, connect-src and media-src permit only self and multimedia.gsb.bund.de. block-all-mixed-content.
+265 ms · GSB styles
Responsive GSB CSS bundles (small, medium, large, xlarge, xxlarge, custom, addon_usability, addon_print) — all local.
+301 ms · global.js
SiteGlobals/Frontend/JavaScript/init/global.js — the only JS file, local.
+317 ms · fonts
AkkoPaneuropean (Light, LightItalic, Medium) and SabonLTW05-Bold — four woff files from /static/fonts/, local. No Google Fonts, no Adobe Fonts.
+386 ms · slideshow
bundle_slideshow_dots.js — the news slider, local.

Declared versus actual

✓ ITZBund — declared as Auftragsverarbeiter (Art. 28 DSGVO), hosting on secured servers — declared
✓ X (Twitter International Unlimited Company) — the court's external channel only, no embedding on the site — declared
✓ YouTube (Google Ireland Limited) — the court's external channel only, no embedding on the site — declared
✓ Temporary session cookies — technically necessary, Art. 6(1)(f) DSGVO i.V.m. § 3 BDSG — declared

Context

Bundesverfassungsgericht is Germany’s constitutional review body, based in Karlsruhe. It hears complaints of violations of constitutional rights, disputes between branches of government, and reviews the constitutionality of laws. Sensitivity is high. GSB platform, Apache, ITZBund. HAR: 18 requests, 1 domain.

The strictest CSP in the German series

The Content-Security-Policy uses default-src 'self' with a sha256 hash for the single inline script ('sha256-TSvMvR1KhNSMgA0cXCcbJuroB+o1McSEH4wxscOg1hc='). connect-src and media-src permit only 'self' and multimedia.gsb.bund.de. frame-src 'self', frame-ancestors 'self', form-action 'self'. block-all-mixed-content and upgrade-insecure-requests. No external domain is permitted for scripts or data — this is the most restrictive CSP among all sites in the German series.

AkkoPaneuropean and Sabon LT Pro — corporate typefaces

BVerfG uses two licensed typeface families: AkkoPaneuropean (Light, LightItalic, Medium) — a humanist sans-serif from the Akkurat foundry, and SabonLTW05-Bold — the classical serif Sabon by Jan Tschichold. Both in woff format from /static/fonts/, local. No Google Fonts.

ITZBund — declared as the data processor

The policy explicitly names ITZBund as the data processor (Auftragsverarbeiter, Art. 28 DSGVO) and links to ITZBund’s privacy policy. Processing is confined to servers in Germany.

X and YouTube — external channels only

The policy describes X and YouTube exclusively as the court’s external social channels. It states explicitly that users cannot reply to posts or send direct messages — no interactive SDKs are embedded on the site. There are no requests to Twitter or Google in the HAR.

Conclusion

www.bundesverfassungsgericht.de is an exemplary minimal technical stack for a state body of the highest jurisdiction: one domain, 18 requests, an extremely strict CSP, corporate typefaces served locally, no analytics, and ITZBund declared. No GDPR violations recorded at the time of the audit.

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/bundesverfassungsgericht-de-2026-05-29.har
SHA-256: 14c1daac78b5475109bda24c2dc204b68f4123485049767d46ecbc0ba1fff114
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) — bundesverfassungsgericht.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 bundesverfassungsgericht.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-bundesverfassungsgericht-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]