Technical audit · 26.05.2026

parlament.gv.at

Austrian Parliament

Austrian Parliament — 84 requests, 1 domain. Self-hosted Matomo loads at 91 ms and pings at 241 ms. The policy states plainly: consent required. There is none.

Request timeline

+91 ms · Matomo scripts
pdpiwik.js and piwik/piwik.js load from www.parlament.gv.at alongside the CSS. There is no consent banner.
+241 ms · tracking ping
piwik.php sends a POST with action_name=Startseite and idsite=1. Visit data is recorded before any user choice.
Session total
84 requests, 1 domain. Zero external services. Matomo is the only tracker, self-hosted.

Declared versus actual

✓ Matomo — declared in the policy, which explicitly states 'Mit Ihrer Einwilligung', appears in the HAR before consent — declared

Transfer timings

+91 ms www.parlament.gv.at/piwik/piwik.js

The Matomo script loads without consent.

+241 ms www.parlament.gv.at/piwik/piwik.php

Tracking ping: action_name=Startseite, idsite=1. Before consent.

Detected trackers

Indicators of GDPR non-compliance

Context

Österreichisches Parlament is Austria’s legislative body, comprising the Nationalrat and the Bundesrat. The Parlamentsdirektion is its administrative apparatus. HAR: 84 requests, 1 domain.

The parliament’s privacy policy is carefully written: a dedicated “Webanalyse-Cookie” section states explicitly that Matomo runs only with the user’s consent, that the IP address is anonymized, and that data is stored on Parlamentsdirektion servers. Not a word about external recipients.

The HAR shows something different: pdpiwik.js loads at +91 ms, piwik.js follows, and the tracking ping goes out at +241 ms. There is no consent banner in the session. The gap between what is declared and what is implemented is precise and documented.

Matomo is deployed entirely on the parliament’s own infrastructure — /piwik/ on the same domain. Data is not sent to third parties, and the IP address is anonymized. Architecturally, this is correct. But firing before consent, while explicitly declaring the opposite, makes this an indicator of non-compliance — one the parliament itself documented in its own policy.

Conclusion

84 requests, 1 domain, zero external dependencies. Self-hosted Matomo is a good solution. But the Austrian Parliament does not comply with its own privacy policy: the tracker fires without the consent the policy calls a mandatory condition.

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: at/parlament-gv-at-2026-05-26.har
SHA-256: 5b6789973887b79e26c018ffff42a43b509c752e56d3ba5b435fce6328217bd8
Re-check snapshot
Awaiting changes
HAR files are stored on EU infrastructure (Proton Drive). SHA-256 is published for integrity verification.