RU EN
www.
Technical audit · 13.05.2026

euaa.europa.eu

EUAA — the EU Agency Coordinating Asylum Policy
EU-INSTITUTIONS

Policy changed — see what exactly · 2026-08-14 →

The EU's asylum agency — 175 requests, 5 domains. Flourish transmits data to the USA with no consent. YouTube is embedded via webtools CRS — the European Commission's delayed-consent mechanism. A weak CSP.

Request timeline

+255 ms · load
webtools.europa.eu — shared EU components.
+1456 ms · without consent
Flourish (public.flourish.studio) — Open Sans fonts for visualizations. IP address to the USA.
+7464 ms
europa.eu/webtools/crs/iframe?oriurl=youtube.com — YouTube via CRS. A delayed-consent mechanism.

Declared versus actual

+ Flourish (public.flourish.studio) — not declared

Transfer timings

+1456 ms public.flourish.studio

Flourish fonts. USA

+7464 ms europa.eu/webtools/crs

YouTube via the EC's consent mechanism

Detected trackers

Indicators of GDPR non-compliance

Context

The European Union Agency for Asylum (EUAA) coordinates the asylum systems of EU member states. It processes sensitive data on refugees and asylum seekers. Governed by Regulation (EU) 2018/1725. HAR: 175 requests, 5 domains. The session covered three pages.

webtools CRS — the right approach to YouTube

When a HAR records YouTube, it usually means a direct load with no consent. EUAA uses a different mechanism: europa.eu/webtools/crs/iframe?oriurl=youtube.com/embed/.... CRS — the Content Rendering Service — is a European Commission tool that intercepts embedding of external content and shows the user a consent prompt before YouTube loads. This is the correct architecture — the same principle as youtube-nocookie with lazy loading, but implemented centrally via webtools.

Flourish — the same problem seen at EBA

public.flourish.studio (+1456 ms) loads fonts for embedded visualizations — Open Sans Bold and Regular. As with EBA, Flourish transmits visitors’ IP addresses to American infrastructure with no consent. Datawrapper (a German, DSGVO-compliant platform) or a self-hosted solution would replace Flourish.

A weak CSP

Content-Security-Policy: report-uri /report-csp-violation — the policy contains only a report-uri directive, with no actual restrictions. This means the CSP is configured in violation-logging mode without any real blocking. In effect, the CSP does not function as protection.

Sensitivity context

EUAA coordinates the processing of data on refugees and asylum seekers — one of the most vulnerable groups. Information about who visits an asylum agency’s website can be sensitive in itself. Flourish, with no consent, transmits information about every visit to the USA.

Conclusion

EUAA uses webtools CRS for YouTube — the correct architectural choice, worth noting. Flourish with no consent and the absence of a functioning CSP are the two issues. Self-hosting Flourish’s fonts, or replacing it with a European visualization platform, would resolve the first.

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/euaa-europa-eu-2026-05-13.har
SHA-256: b2809e980a47f166832d7e94e0dc067d6c4b2d90c1760d2eff1dddb48c73cf60
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) — euaa.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 euaa.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) Flourish (+1456 ms) loads with no consent — fonts and CSS from public.flourish.studio. Visitors' IP addresses go to Flourish's American infrastructure.


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

1. Subject of the complaint
I am filing a complaint regarding the processing of my personal data by the website euaa.europa.eu.

2. Circumstances
I visited the website euaa.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) Flourish (+1456 ms) loads with no consent — fonts and CSS from public.flourish.studio. Visitors' IP addresses go to Flourish's American infrastructure.

Full technical documentation is published at: https://gdpru.eu/en/audits/eu-euaa-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]