RU EN
www.
Technical audit · 29.05.2026

fitko.de

Executive Body of the IT Planning Council
DE

The executive body of the IT-Planungsrat — the intergovernmental coordination body for the digitalization of German public administration. 33 requests, 2 domains. TYPO3, nginx. Prompt served locally, Fira Sans via unpkg.com (the Kern design system). Matomo on IT-Planungsrat's own servers — activates only after consent. Set-Cookie — zero.

Request timeline

+0 ms · homepage
www.fitko.de/ — HTML, nginx, TYPO3. A strict CSP with a nonce: script-src permits only self, unpkg.com, and matomo.it-planungsrat.de. The Feature-Policy explicitly disallows fullscreen, geolocation, camera, and microphone.
+258 ms · styles and Kern
Local TYPO3 CSS files (init-fitko, news-basic, cookie_consent). unpkg.com/@kern-ux/native@2.6.2/dist/fonts/fira-sans.css — Fira Sans font declarations from the federal Kern design system, loaded from a CDN.
+261 ms · Kern JS component
unpkg.com/@kern-ux/native@2.6.2/dist/js/kern-kopfzeile.js — a header JavaScript component from Kern. Both unpkg resources are cached for one year (max-age=31536000).
+289 ms · Prompt, local
prompt-v5-latin-regular.woff2 and prompt-v5-latin-600.woff2 — the Prompt typeface (Regular, SemiBold), served locally from _assets/Fonts/fitko/.
+345 ms · cookie_consent
cookie_consent.js and cookie_consent.css — FITKO's proprietary consent-management implementation, with no external CMP platform.

Declared versus actual

✓ Matomo (matomo.it-planungsrat.de) — only after consent, Art. 6(1)(e) DSGVO in conjunction with § 3 HDSIG, cookies _pk_id and _pk_ses (13 months) — declared
✓ PHPSESSID — a session CMS cookie, technically necessary — declared
✓ cookie_consent — the consent cookie, 1 year — declared
✓ YouTube — mentioned for embedded videos on internal pages — declared
✓ LinkedIn, Mastodon (social.bund.de) — mentioned as FITKO's social networks — declared
+ unpkg.com (Cloudflare CDN) — not mentioned in the policy — not declared

Context

FITKO (Föderale IT-Kooperation) is the executive body of the IT-Planungsrat, the intergovernmental coordination body for information technology across Germany’s federal and state administrations. Legal basis: the IT-Staatsvertrag (Art. 91c GG). Data controller: FITKO, as a legal entity under public law (Anstalt des öffentlichen Rechts). Sector-specific legislation: HDSIG (Hessisches Datenschutz- und Informationsfreiheitsgesetz). TYPO3, nginx. HAR: 33 requests, 2 domains.

Kern — the federal design system via unpkg.com

FITKO uses Kern — the federal design system for Germany’s digital government services (@kern-ux/native@2.6.2). Two components load from unpkg.com: the Fira Sans font CSS declarations and the header JS component, kern-kopfzeile.js. unpkg.com is a public npm CDN operated by Cloudflare. Loading these resources transmits the visitor’s IP address to Cloudflare’s servers. Both files are cached by the browser for one year.

The Prompt typeface (Regular, SemiBold) — FITKO’s second font — is hosted locally, which makes the reliance on unpkg.com an inconsistent architectural choice: one font local, the other via an external CDN.

CSP with a nonce — a strong security policy

The Content-Security-Policy uses a per-request nonce (nonce-Ed2pqSURk1qzRMye…) for all scripts and styles. script-src permits only: self, unpkg.com, and matomo.it-planungsrat.de. img-src — only self and data:. frame-ancestors 'none' — a full ban on embedding. The Feature-Policy explicitly disallows geolocation, camera, and microphone. report-uri is configured to a proprietary internal endpoint.

Matomo on IT-Planungsrat infrastructure — only after consent

The CSP discloses the Matomo domain: matomo.it-planungsrat.de — a centralized analytics instance for bodies under the IT-Planungsrat. Legal basis: Art. 6(1)(e) DSGVO combined with § 3 HDSIG (public task). Cookies: _pk_id and _pk_ses, retained for 13 months. Activated exclusively after user consent. There are no requests to matomo.it-planungsrat.de in the HAR.

cookie_consent — a proprietary implementation with no external CMP

cookie_consent.js and cookie_consent.css are implemented as a FITKO TYPO3 extension, with no OneTrust, Usercentrics, or other commercial CMP.

Conclusion

www.fitko.de has one finding: unpkg.com is not declared in the privacy policy. The rest of the architecture demonstrates a high level of GDPR compliance: a strict CSP with a nonce, a proprietary CMP, Matomo activated only after consent, and a Feature-Policy with explicit denials of browser APIs.

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/fitko-de-2026-05-29.har
SHA-256: e39c613024c1af1d132a5d80f91c23a245d2ae54f030aaff1a7ec9c818ee1a65
Re-check snapshot
Awaiting changes
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) — fitko.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 fitko.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-fitko-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]
IMPORTANT: before filing a complaint with the regulator, first contact the company directly and give it 30 days to respond. Without this step the regulator may reject the complaint. Details and a template letter to the company are in the Methodology.
Ready-to-send complaint letter

Where to file: Federal Commissioner for Data Protection (BfDI) — file a complaint online →

The regulator reviews complaints in its national language. There is an officially translated template from the European Data Protection Board (EDPB) — you can use it instead of or alongside this letter: Official EDPB complaint form (PDF, your language)

Subject: Complaint regarding personal data processing — fitko.de

1. Subject of the complaint
I am filing a complaint regarding the processing of my personal data by the website fitko.de.

2. Circumstances
I visited the website fitko.de and found indications that the processing of my personal data does not comply with the GDPR. The technical analysis published on gdpru.eu on 29 May 2026 (open methodology, reproducible measurements) documents the following indications:

Full technical documentation is published at: https://gdpru.eu/en/audits/de-fitko-de/

3. GDPR provisions I ask you to examine


4. Request
I request that you examine the circumstances described and, if non-compliance is confirmed, apply the measures provided for in Article 58(2) GDPR.

5. Attachments
The full evidence base — the HAR file, its SHA-256 checksum and the quotation from the site's privacy policy documenting the stated contradiction — is published and verifiable at the link in point 2 above.

Sincerely,

[Your name]
[contact email]
[Country]


[Date]