RU EN
www.
Technical audit · 13.05.2026

enisa.europa.eu

ENISA — EU Agency for Network and Information Security
EU-INSTITUTIONS

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.

Request timeline

+229 ms · without consent
cdnjs.cloudflare.com — Font Awesome 6.6.0. IP address to Cloudflare, USA.
+230 ms · without consent
AddToAny (static.addtoany.com) — 'share' buttons. USA.
+265 ms
videos.enisa.europa.eu — ENISA's own PeerTube server. Data stays within ENISA's infrastructure.

Declared versus actual

+ AddToAny (static.addtoany.com) — not declared
+ cdnjs.cloudflare.com (Font Awesome) — not declared

Transfer timings

+229 ms cdnjs.cloudflare.com

Font Awesome. USA

+230 ms static.addtoany.com

AddToAny share. USA

Detected trackers

Indicators of GDPR non-compliance

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.

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: eu/enisa-europa-eu-2026-05-13.har
SHA-256: 8304f9fcaff5f7ceae8e034c8c6f3a805081dcf9a511e5a9e85aa7a536615c5f
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) — enisa.europa.eu

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 enisa.europa.eu.

1. Categories of data and purposes of processing (Art. 15(1)(a)-(c))
Based on an independent technical analysis of the site, I request confirmation and detailed disclosure of the following categories of processing:

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.


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/eu-enisa-europa-eu/

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: European Data Protection Supervisor (EDPS) — edps.europa.eu

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 — enisa.europa.eu

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. GDPR provisions I ask you to examine
Regulation 2018/1725 Art. 5

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]