enisa.europa.eu
Policy changed — see what exactly · 2026-08-14 →
The EU's cybersecurity agency uses its own PeerTube server for video — an exemplary choice. But AddToAny and Cloudflare cdnjs load with no consent. An agency that publishes data-protection guidance itself transmits visitor data to the USA.
Timeline of the leak
Declared versus actual
Transfer timings
Font Awesome. USA
AddToAny share. USA
Detected trackers
- AddToAny (static.addtoany.com)
- Cloudflare cdnjs (cdnjs.cloudflare.com)
Indicators of GDPR non-compliance
- Regulation 2018/1725 Art. 5AddToAny (+230 ms) and cdnjs.cloudflare.com (+229 ms) load with no consent when the homepage opens. Data goes to the USA. There is no consent banner.
Context
The European Union Agency for Cybersecurity (ENISA) is the EU’s agency for network and information security, headquartered in Athens. It publishes cybersecurity guidance, the annual threat report (ENISA Threat Landscape), and methodologies for national CSIRTs. Governed by Regulation (EU) 2018/1725. HAR: 120 requests, 5 domains.
PeerTube — an exemplary choice
The main finding of this audit is videos.enisa.europa.eu. This is ENISA’s own PeerTube instance, a decentralized open-source video-hosting platform. ENISA hosts video on its own infrastructure instead of YouTube. When a video plays, data goes exclusively to ENISA’s servers — no Google, no YouTube. Russian-language localization (ru-RU/player.json) is also loaded from the proprietary server.
This is the same principle as eu-LISA’s use of Matomo — a deliberate choice of a European, self-hosted alternative over an American service.
AddToAny — the same problem seen at ACER
static.addtoany.com (+230 ms) is an American “share” button service. ENISA uses it on two pages of the session. On the second page (+12107 ms), separate JS modules load for Facebook, Twitter, and LinkedIn icons. Visit data goes to AddToAny (USA) with no consent. The same observation applies here as at ACER — a “share” function can be implemented without external JavaScript.
cdnjs.cloudflare.com — Font Awesome
Font Awesome 6.6.0 loads from Cloudflare’s American CDN (+229 ms). The visitor’s IP address is transmitted to the USA on every page load. Fix: self-host Font Awesome (a set of openly licensed SVG files).
Irony of context
ENISA publishes annual cyber-threat reports and data-protection guidance for EU organizations — while simultaneously loading AddToAny and cdnjs with no consent on every visit to its own site. Using PeerTube instead of YouTube shows the agency understands data-minimization principles — applying that same principle to its remaining services would logically extend what’s already been started.
Conclusion
ENISA is a strong result structurally: its own PeerTube instance, webtools.europa.eu, zero advertising trackers. Two issues — AddToAny and cdnjs — are fixable by self-hosting Font Awesome and removing the “share” script.
8304f9fcaff5f7ceae8e034c8c6f3a805081dcf9a511e5a9e85aa7a536615c5fWhere to file: European Data Protection Supervisor (EDPS) — edps.europa.eu
To: European Data Protection Supervisor (EDPS) 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 enisa.europa.eu. 2. Circumstances I visited the website enisa.europa.eu and found indications that the processing of my personal data does not comply with the GDPR. The technical analysis published on gdpru.eu on 13 May 2026 (open methodology, reproducible measurements) documents the following indications: 1) AddToAny (+230 ms) and cdnjs.cloudflare.com (+229 ms) load with no consent when the homepage opens. Data goes to the USA. There is no consent banner. Full technical documentation is published at: https://gdpru.eu/en/audits/eu-enisa-europa-eu/ 3. Provisions violated Regulation 2018/1725 Art. 5 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]