frontex.europa.eu
Policy changed — see what exactly · 2026-07-11 →
The EU's border agency — 23 domains, the most tracker-heavy site in the institutions series. YouTube fires at +0 ms. UA, retired in 2024, is still running. Google Ads appears on the site of an agency with no commercial activity.
Timeline of the leak
Declared versus actual
Transfer timings
log_event before the page loads
Twitter widgets
GTM-K7BJHN6
UA analytics.js — service discontinued in 2024
Google Ads pagead/id
Detected trackers
- Google Tag Manager (GTM-K7BJHN6)
- Google Analytics UA (www.google-analytics.com) — deprecated
- Google Analytics GA4 (G-Y2F9EGZV5D)
- Google Ads / DoubleClick (googleads.g.doubleclick.net)
- YouTube (loaded directly, no consent)
- Twitter / X widgets (platform.twitter.com)
- Cloudflare Turnstile (challenges.cloudflare.com)
- Google Fonts (fonts.googleapis.com)
- Piwik (lens.frontex.europa.eu) — blocked
- Bootstrap CDN (cdn.jsdelivr.net)
- jQuery CDN (code.jquery.com)
Indicators of GDPR non-compliance
- Regulation 2018/1725 Art. 5The YouTube log_event call (+0 ms) — the first request of the session, even before the page loads. GTM (+528 ms), UA (+633 ms), GA collect (+690 ms), Twitter widgets (+228 ms), Google Ads (+2322 ms) — all with no consent. A cookie-script loads at +226 ms but does not block the trackers.
- Regulation 2018/1725 Art. 5 — additionallyGoogle Analytics UA was officially retired as of July 2024. UA's analytics.js loads and sends a pageview. Google Ads DoubleClick (pagead/id) — advertising infrastructure on the site of an agency with no commercial activity.
Context
Frontex is the European Border and Coast Guard Agency, headquartered in Warsaw. It coordinates the protection of the EU’s external borders, conducts joint operations with member states, and processes data on individuals crossing the border. Governed by Regulation (EU) 2018/1725 and the specific Regulation (EU) 2019/1896. HAR: 131 requests, 23 domains.
The most tracker-heavy site in the institutions series
Against the backdrop of the European Parliament (2 domains), Europol (2 domains), the ECB (1 domain), and the Commission (5 domains) — Frontex, with 23 domains, stands out entirely. This is not technical carelessness — it reflects deliberate decisions: to integrate YouTube, Twitter, Google Ads, GTM.
YouTube at +0 ms — before the page loads
The first request in the HAR is www.youtube.com/youtubei/v1/log_event, at the +0 ms mark. This means the YouTube API initializes before the browser has even loaded the page’s HTML — the video was preloaded from a prior navigation or cached. View data goes to Google before any user interaction.
UA after retirement — again
As with ekel.ee and eua.eu — Frontex loads UA’s analytics.js (+633 ms) and sends a pageview collect (+690 ms). UA was retired as of July 2024. GA4 (G-Y2F9EGZV5D) runs in parallel. Two GA counters, one of them dead.
Google Ads on an EU agency
googleads.g.doubleclick.net/pagead/id (+2322 ms) is a Google advertising identifier, used to configure advertising audiences. Frontex is not a commercial organization and does not purchase Google advertising. The appearance of DoubleClick may mean it is configured within the GTM container and activates by default.
Piwik blocked
lens.frontex.europa.eu/piwik/piwik.js (+815 ms) — Frontex’s own Piwik instance, status 0 (connection blocked). Unlike EBA and eu-LISA, where Matomo operates correctly, Frontex’s self-hosted analytics is blocked, while external trackers run freely.
Sensitivity context
Frontex processes data on individuals crossing the EU’s external borders — including asylum data, border-crossing violations, and biometric data. The agency’s public website is visited by human rights advocates, journalists, researchers, and people who have filed complaints against the agency’s actions. Twitter widgets and Google Ads on such a site are architectural decisions warranting particular scrutiny.
Conclusion
23 domains, UA discontinued since 2024, Google Ads with no commercial purpose, YouTube with no consent, Twitter widgets — Frontex sits at the opposite pole from Europol and the ECB. All of this is wired through GTM — disabling GTM, or correctly configuring Consent Mode, would resolve most of these issues. A proprietary Piwik instance is already deployed — it just needs fixing, alongside the removal of the external trackers.
f51e254a37ef1b11f779e0d66828eb414f0c806d65a65982d0b2c70995488169Where 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 frontex.europa.eu. 2. Circumstances I visited the website frontex.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) The YouTube log_event call (+0 ms) — the first request of the session, even before the page loads. GTM (+528 ms), UA (+633 ms), GA collect (+690 ms), Twitter widgets (+228 ms), Google Ads (+2322 ms) — all with no consent. A cookie-script loads at +226 ms but does not block the trackers. 2) Google Analytics UA was officially retired as of July 2024. UA's analytics.js loads and sends a pageview. Google Ads DoubleClick (pagead/id) — advertising infrastructure on the site of an agency with no commercial activity. Full technical documentation is published at: https://gdpru.eu/en/audits/eu-frontex-europa-eu/ 3. Provisions violated Regulation 2018/1725 Art. 5; Regulation 2018/1725 Art. 5 — additionally 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]