RU EN
www.
Technical audit · 13.05.2026

cor.europa.eu

CoR — the EU's Advisory Body Representing Regional and Local Authorities
EU-INSTITUTIONS

Policy changed — see what exactly · 2026-09-12 →

The EU's Committee of the Regions — 6 domains. The Facebook SDK loads 6 times per session with no consent. Analytics run via webanalytics.op.europa.eu — the EU's own infrastructure. op.europa.eu serves as a widget platform.

Request timeline

+220 ms · load
webtools.europa.eu — the standard set of EU components.
+10368 ms · without consent
Facebook SDK (connect.facebook.net/en_US/sdk.js) — first appearance. No banner.
+20618 ms
op.europa.eu — Publications Office widgets. Search across EU publications.
+24012 ms
analytics.webanalytics.op.europa.eu — analytics via the EU Publications Office.
+27476 ms
cdnjs.cloudflare.com — Font Awesome 6.6.0. USA.

Declared versus actual

+ Facebook SDK (connect.facebook.net) — not declared
+ cdnjs.cloudflare.com (Font Awesome) — not declared

Transfer timings

+10368 ms connect.facebook.net

Facebook SDK — 6 requests per session

+24012 ms analytics.webanalytics.op.europa.eu

EU Publications Office analytics

+27476 ms cdnjs.cloudflare.com

Font Awesome. USA

Detected trackers

Indicators of GDPR non-compliance

Context

The European Committee of the Regions (CoR) is the EU’s advisory body representing the regional and local authorities of member states. It advises the Council of the EU and the European Parliament on matters affecting regions. Governed by Regulation (EU) 2018/1725. HAR: 203 requests, 6 domains, 4 pages per session.

The Facebook SDK — why?

connect.facebook.net/en_US/sdk.js loads 6 times across a 4-page session — once per page, plus additional calls. This means the Facebook SDK is baked into the site template. CoR is an advisory body with no commercial activity. The Facebook SDK is typically used for “share” buttons, “log in with Facebook,” or a pixel. None of these scenarios require loading the SDK with no consent.

webanalytics.op.europa.eu — Publications Office analytics

analytics.webanalytics.op.europa.eu is the EU Publications Office’s analytics platform. Pan-European infrastructure for analytics, with data staying within europa.eu. The correct choice — unlike Frontex’s use of Google Analytics.

op.europa.eu — publication widgets

op.europa.eu is the EU’s Publications Office. CoR embeds an EU-publications search widget with its own Bootstrap, jQuery, jQuery UI, and Font Awesome — all served from op.europa.eu, with data on EU infrastructure.

cdnjs.cloudflare.com — Font Awesome, again

As with ENISA and ACER — Font Awesome served from cdnjs.cloudflare.com instead of being self-hosted. The same problem, the same fix.

Conclusion

CoR uses the correct analytics (webanalytics.op.europa.eu) and the correct widget platform (op.europa.eu). The Facebook SDK loading with no consent is the main issue. Self-hosting Font Awesome and either removing or correctly configuring the Facebook SDK would resolve both points.

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/cor-europa-eu-2026-05-13.har
SHA-256: 5b8d6640565d189ac2d78e781f04cf03b8d2775d31315db66cd81896f8d23c26
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) — cor.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 cor.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) The Facebook SDK (+10368 ms) loads with no consent. Over a 4-page session, connect.facebook.net receives 6 requests. Every visitor's IP address is transmitted to Meta (USA) with no consent banner.

2) cdnjs.cloudflare.com (+27476 ms) — Font Awesome, served from an American CDN. Data to the USA.


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

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

2. Circumstances
I visited the website cor.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 Facebook SDK (+10368 ms) loads with no consent. Over a 4-page session, connect.facebook.net receives 6 requests. Every visitor's IP address is transmitted to Meta (USA) with no consent banner.

2) cdnjs.cloudflare.com (+27476 ms) — Font Awesome, served from an American CDN. Data to the USA.

Full technical documentation is published at: https://gdpru.eu/en/audits/eu-cor-europa-eu/

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