RU EN
www.
Technical audit · 31.05.2026

cif.ie

Construction Industry Federation of Ireland
IE

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

The Irish Construction Industry Federation — 149 requests, 19 domains. GTM and external CDNs load roughly 300 ms before Cookiebot. Vimeo with dnt=1 is a deliberate choice. Stripe is a payment service. The policy is outdated — it references the Data Protection Acts 1988/2002.

Request timeline

+135 ms · before the banner
FontAwesome CDN (use.fontawesome.com) — icons. USA.
+141 ms · before the banner
Cloudflare cdnjs — Modernizr 2.8.3. USA.
+161 ms · before the banner
GTM (GTM-MC3SR8J) — loads before Cookiebot.
+170 ms · before the banner
Google Fonts — Lato. IP address to Google, USA.
+418 ms · before the banner
Vimeo player (dnt=1) — a Do Not Track parameter is transmitted.
+455 ms · banner
Cookiebot (consent.cookiebot.eu) — the GDPR banner.
+509 ms · prior to consent
Stripe (js.stripe.com/v3/) — the payment SDK.
+2563 ms · after the banner
GA4 collect (G-DXTJPWR4N0) — data sent after the banner loads.

Declared versus actual

+ FontAwesome CDN — not declared
+ Cloudflare cdnjs — not declared
+ Stripe — not declared

Transfer timings

+161 ms www.googletagmanager.com

GTM-MC3SR8J — 294 ms before Cookiebot

+455 ms consent.cookiebot.eu

Cookiebot GDPR CMP

+509 ms js.stripe.com

Stripe v3 — payment SDK

Detected trackers

Indicators of GDPR non-compliance

Context

The Construction Industry Federation (CIF) is the leading representative body for Ireland’s construction industry, bringing together contractors and construction companies. Ireland’s supervisory authority is the DPC (Data Protection Commission). HAR: 149 requests, 19 domains.

The policy is outdated

The privacy policy references the Data Protection Acts of 1988 and 2002 — pre-GDPR legislation. The GDPR has been in force in Ireland since 25 May 2018, meaning the policy has not been updated in over eight years. There is no mention of the GDPR, Art. 13, or the rights of data subjects under the regulation. For an organization subject to the GDPR, this is a critical documentation gap.

Vimeo with dnt=1 — a deliberate choice

The Vimeo player loads with the parameter dnt=1 (Do Not Track). This means Vimeo does not set tracking cookies and does not collect viewing data for targeting purposes. A deliberate decision — unlike most sites, which embed Vimeo without the dnt parameter.

Stripe — a payment SDK

js.stripe.com/v3/ (+509 ms) — the Stripe payment SDK loads on every page, not only on the payment page. Stripe collects browser and behavioral data for fraud detection. It loads prior to Cookiebot consent.

GTM ahead of Cookiebot — a standard problem

GTM loads at +161 ms; Cookiebot at +455 ms. The gap is 294 ms. The fix: configure Cookiebot via the GTM template — this way, Cookiebot initializes first and blocks the remaining tags until consent is given.

Conclusion

For CIF, Vimeo with dnt=1 is a good practice. But the policy is eight years out of date, GTM loads before Cookiebot, and Stripe runs on every page without consent. For an Irish organization under DPC oversight, updating the policy and correctly configuring Cookiebot via the GTM template should be priorities.

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: ie/cif-ie-2026-05-31.har
SHA-256: 97a528f3e88e3c5653575872d91aa42e11494946b306d2abbf2a0fc3af553bc0
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) — cif.ie

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 cif.ie.

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) GTM (+161 ms), Google Fonts (+170 ms), the FontAwesome CDN (+135 ms), and cdnjs.cloudflare.com (+141 ms) load 290–320 ms before Cookiebot (+455 ms). The GA collect call goes out at +2563 ms — after the banner — but GTM data collection begins earlier.


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/ie-cif-ie/

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: Data Protection Commission (DPC) — dataprotection.ie

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 — cif.ie

1. Subject of the complaint
I am filing a complaint regarding the processing of my personal data by the website cif.ie.

2. Circumstances
I visited the website cif.ie and found indications that the processing of my personal data does not comply with the GDPR. The technical analysis published on gdpru.eu on 31 May 2026 (open methodology, reproducible measurements) documents the following indications:

1) GTM (+161 ms), Google Fonts (+170 ms), the FontAwesome CDN (+135 ms), and cdnjs.cloudflare.com (+141 ms) load 290–320 ms before Cookiebot (+455 ms). The GA collect call goes out at +2563 ms — after the banner — but GTM data collection begins earlier.

Full technical documentation is published at: https://gdpru.eu/en/audits/ie-cif-ie/

3. GDPR provisions I ask you to examine
GDPR Art. 6(1), Art. 5(1)(a)

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]