bauindustrie.de

Hauptverband der Deutschen Bauindustrie — the German construction industry federation. 69 requests, 1 domain. Matomo self-hosted at /matomo/ — all data stays on the proprietary server. The policy states consent (Einwilligung) as the legal basis. But Matomo fires with no recorded consent in the HAR.

Timeline of the leak

+211 ms · load

CSS, JS bundles, images — all from www.bauindustrie.de. Roboto (Regular, Light, Medium, Bold, Black) — served locally from /_assets/Fonts/.

+212 ms · consent

Consent-938150a02ba8f92b05cbc2453b5b4166.js — a TYPO3 consent extension. Loads before Matomo.

+348 ms · Matomo JS

www.bauindustrie.de/matomo/matomo.js — the Matomo JS loads from the proprietary server.

+456 ms · tracking request

www.bauindustrie.de/matomo/matomo.php — a Matomo tracking request. Cookieless, AnonymizeIP enabled.

Indicators of GDPR non-compliance

GDPR Art. 7; TDDDG § 25 — Matomo before recorded consent

The policy declares Matomo on the basis of Art. 6(1)(a) DSGVO (Einwilligung — consent). Consent-938150a02ba8f92b05cbc2453b5b4166.js loads at +212 ms. Matomo.js loads at +348 ms. Matomo.php sends a tracking request at +456 ms with action_name=Hauptverband der Deutschen Bauindustrie. The HAR shows neither a SET-Cookie from a banner nor any explicit user interaction with a consent interface before tracking fires. If consent is the stated legal basis (Einwilligung), Matomo should activate only after it has been obtained.

Context

Hauptverband der Deutschen Bauindustrie (HDB) is the federal industry federation of Germany’s construction sector, representing around 2,000 companies. TYPO3 CMS. HAR: 69 requests, 1 domain — all to www.bauindustrie.de.

Self-hosted Matomo — good architecture, a problematic legal basis

HDB uses Matomo, hosted on its own server at the path /matomo/. This means analytics data is not transmitted to third parties, does not go to any cloud, and is processed exclusively on bauindustrie.de’s infrastructure. AnonymizeIP is enabled — IP addresses are anonymized. The policy states an opt-out mechanism.

The problem lies in the legal basis. The policy states explicitly: Art. 6(1)(a) DSGVO (Einwilligung) — consent. This means HDB itself classified Matomo as a tool requiring consent. Yet Matomo loads at +348 ms and sends a tracking request at +456 ms. The HAR shows neither an interactive banner, nor a SET-Cookie from a consent mechanism, nor any explicit user interaction before Matomo fires.

The contrast with bamf.de is instructive: there, Matomo is documented with opt-out and is absent from the HAR. Here, Matomo is documented with Einwilligung — and is present in the HAR before consent.

Roboto served locally

Five Roboto weights (Regular, Light, Medium, Bold, Black) are hosted locally in /_assets/Fonts/. No Google Fonts.

Conclusion

bauindustrie.de chose the right technical architecture (self-hosted Matomo, local fonts, one domain) and the correct legal basis (Einwilligung). The mismatch lies in the implementation: Matomo fires before confirmed consent is obtained. The fix is straightforward: ensure Matomo initializes only after the user’s consent decision has been recorded by the TYPO3 consent extension.

Evidence

Original (audit)

HAR file: de/bauindustrie-de-2026-05-29.har

SHA-256: a8d650c39a39fb357923ccde52c150057d9fdde8cb7cfca93d0bd80afdd7ee41

Re-check snapshot

Awaiting changes

HAR files are stored on EU infrastructure (Proton Drive). SHA-256 is published for integrity verification.

Ready-to-send complaint letter

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

To: Federal Commissioner for Data Protection (BfDI)
From: [Your name], [contact email]

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

2. Circumstances
I visited the website bauindustrie.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:

1) The policy declares Matomo on the basis of Art. 6(1)(a) DSGVO (Einwilligung — consent). Consent-938150a02ba8f92b05cbc2453b5b4166.js loads at +212 ms. Matomo.js loads at +348 ms. Matomo.php sends a tracking request at +456 ms with action_name=Hauptverband der Deutschen Bauindustrie. The HAR shows neither a SET-Cookie from a banner nor any explicit user interaction with a consent interface before tracking fires. If consent is the stated legal basis (Einwilligung), Matomo should activate only after it has been obtained.

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

3. Provisions violated
GDPR Art. 7; TDDDG § 25 — Matomo before recorded consent

4. Request
I request that you investigate the violations described and 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.

[Date]                                    [Signature / name]