centralbank.ie
The Central Bank of Ireland — the financial regulator and a member of the Eurosystem. 50 requests, 5 domains. No GTM, no analytics, no advertising. OtAutoBlock fails to block Cludo and Google Fonts — both load 104 ms before the banner. The Cookie Policy names categories without naming recipients.
Request timeline
Declared versus actual
Transfer timings
OtAutoBlock.js. OneTrust UUID 01926dd3.
Lato, 5 weights. Google servers. USA.
Cludo search. CSS + JS + fonts. Denmark.
otBannerSdk.js — the banner becomes visible.
Detected trackers
- Cludo search engine (customer.cludo.com)
- Google Fonts (fonts.googleapis.com)
- OneTrust CMP (cdn.cookielaw.org, geolocation.onetrust.com)
Context
The Central Bank of Ireland is the country’s independent financial regulator and a member of the European System of Central Banks (ESCB/Eurosystem). It regulates banks, insurers, investment funds, and financial markets. HAR: 50 requests, 5 domains. 32 requests go to the first-party domain www.centralbank.ie, and 18 to four external domains, of which 11 go to the OneTrust CDN.
A relatively clean architecture
By the standards of the Irish series, centralbank.ie demonstrates a restrained technical architecture: no Google Tag Manager, no Google Analytics, no Facebook SDK, no advertising pixels, no Hotjar. The FontAwesome 4.6.3, Glyphicons, and icomoon fonts are hosted locally (/Theme/fonts/). There is a self-hosted exchange-rate API (/api/exchangerates). Three languages (EN/IE/GA) with no external CDN involved. This reflects a deliberate, technically informed choice to minimize dependencies.
OtAutoBlock: the 2 milliseconds that decide everything
OneTrust’s OtAutoBlock.js loads at +74 ms. Google Fonts loads at +75 ms. Cludo loads at +76 ms. Between the loading of the blocker and the first external requests, there is only a 1–2 ms gap. OtAutoBlock works as follows: it modifies the type attribute of <script> tags, replacing text/javascript with a blocked type, and restores them once consent is given. For this to work correctly, the blocker must load and execute before the parser reaches the tags it is meant to block. 1–2 ms is not enough: the browser has already begun parsing the HTML and has initiated requests to external resources by the time OtAutoBlock executes. This is a structural loading-order problem common to many sites that reference external resources inline.
Cludo — a search engine with no disclosure
Cludo is a Danish SaaS site-search platform used by the Central Bank to power its search function. It loads CSS, JS, and two font files (Source Sans Pro via TTF) from customer.cludo.com. Every visitor to the home page transmits their IP address and browser data to Cludo’s Danish servers. It is not mentioned in the Cookie Policy. Functionally, Cludo can be compared to Lunr.js or Pagefind — static search alternatives with no external dependencies.
Cookie Policy: types without names
The Cookie Policy (October 2024) describes three cookie types — First Party, Third Party, and Session — and explains how to manage cookie settings in popular browsers. Specific data recipients are not named. Under Art. 13(1)(e), the data subject must know the recipients or categories of recipients; listing cookie types without names does not constitute sufficient disclosure.
Set-Cookie — zero
None of the 50 requests sets a cookie via Set-Cookie.
Conclusion
centralbank.ie has built a technically minimalist architecture — no advertising networks, no third-party analytics, with locally hosted fonts. Two findings are procedural in nature: OtAutoBlock fails to block Cludo and Google Fonts in time because of loading order (fixable by moving the external scripts further down in the HTML), and the Cookie Policy names categories without naming recipients (fixable by updating the documentation). For a financial regulator that itself publishes data-protection requirements for financial institutions serving customers, the accuracy of its own documentation is a standard the site does not yet meet.
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.
0c0baa76e7608ee9aa467abb678effe95b24bb2e2c3718fef35edc35f78d57faWant 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.
RIA DigiDoc — phone · Smart-ID / Mobile-ID
Send this letter directly to the company first — before contacting the regulator it has the right to respond (GDPR Art. 12(3) — 30 days).
Тема: Запрос доступа к персональным данным (ст. 15 GDPR) — centralbank.ie Кому: [укажите адрес компании — DPO / поддержка / юридический отдел] От: [Ваше имя], [контактный email] Прошу предоставить доступ к моим персональным данным, обрабатываемым в связи с использованием сайта centralbank.ie. 1. Категории данных и цели обработки (ст. 15(1)(a)-(c)) На основании независимого технического анализа сайта прошу подтвердить и подробно раскрыть следующие категории обработки: 1) OneTrust OtAutoBlock.js загружается на +74 мс. Cludo (customer.cludo.com) загружается на +76 мс — через 2 мс после OtAutoBlock, до завершения его инициализации. Google Fonts (fonts.googleapis.com, Lato) — на +75 мс. Баннер OneTrust (otBannerSdk.js) появляется на +180 мс. Оба внешних сервиса загружаются за 104–105 мс до баннера, несмотря на наличие OtAutoBlock. 2) Cookie Policy (октябрь 2024) описывает типы cookies (First Party, Third Party, Session) без идентификации конкретных получателей. Cludo (датская компания, поисковый движок) и Google Fonts не упомянуты поимённо. Политика указывает: «Read our full Data Protection Privacy Notice» — последняя также не содержит имён внешних технических провайдеров сайта. 2. Получатели, сроки хранения и передача за пределы ЕЭЗ (ст. 15(1)(c)-(d), 46) Прошу также указать полный список третьих лиц-получателей, применимые сроки хранения по каждой категории и правовые основания передачи данных за пределы ЕЭЗ, если таковая происходит. Полный технический разбор с доказательствами (сохранённый сетевой журнал, контрольная сумма SHA-256) опубликован по адресу: https://gdpru.eu/en/audits/ie-centralbank-ie/ 3. Автоматизированная обработка и профилирование (ст. 15(1)(h)) Прошу сообщить, применяется ли в отношении меня автоматизированное принятие решений или профилирование, и если да — раскрыть логику такой обработки. С уважением, [Ваше имя] [контактный email] [Страна] [Дата]
Subject: Data access request (GDPR Art. 15) — centralbank.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 centralbank.ie. 1. Categories of data and purposes of processing (Art. 15(1)(a)-(c)) I request information on all categories, purposes, and recipients of my data processed on this site — regardless of whether any non-compliance has been identified to date. 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-centralbank-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]
RIA DigiDoc — phone · Smart-ID / Mobile-ID
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)
Тема: Жалоба на обработку персональных данных — centralbank.ie 1. Предмет жалобы Я подаю жалобу в отношении обработки моих персональных данных сайтом centralbank.ie. 2. Обстоятельства Я посетил сайт centralbank.ie и обнаружил признаки несоответствия обработки моих персональных данных требованиям GDPR. Технический разбор, опубликованный на gdpru.eu 31.05.2026 (открытая методология, воспроизводимые измерения), документирует следующие признаки: 1) OneTrust OtAutoBlock.js загружается на +74 мс. Cludo (customer.cludo.com) загружается на +76 мс — через 2 мс после OtAutoBlock, до завершения его инициализации. Google Fonts (fonts.googleapis.com, Lato) — на +75 мс. Баннер OneTrust (otBannerSdk.js) появляется на +180 мс. Оба внешних сервиса загружаются за 104–105 мс до баннера, несмотря на наличие OtAutoBlock. 2) Cookie Policy (октябрь 2024) описывает типы cookies (First Party, Third Party, Session) без идентификации конкретных получателей. Cludo (датская компания, поисковый движок) и Google Fonts не упомянуты поимённо. Политика указывает: «Read our full Data Protection Privacy Notice» — последняя также не содержит имён внешних технических провайдеров сайта. Полная техническая документация опубликована по адресу: https://gdpru.eu/en/audits/ie-centralbank-ie/ 3. Положения GDPR, соблюдение которых прошу проверить GDPR Art. 6(1), Art. 7; ePrivacy Regulations (SI 336/2011); GDPR Art. 13(1)(e) 4. Требование Прошу проверить изложенные обстоятельства и, если несоответствие подтвердится, принять меры, предусмотренные статьёй 58(2) GDPR. 5. Приложения Полная доказательная база — HAR-файл, контрольная сумма SHA-256 и цитата из политики конфиденциальности сайта, документирующая указанное противоречие — опубликована и проверяема по ссылке в пункте 2 выше. С уважением, [Ваше имя] [контактный email] [Страна] [Дата]
Subject: Complaint regarding personal data processing — centralbank.ie 1. Subject of the complaint I am filing a complaint regarding the processing of my personal data by the website centralbank.ie. 2. Circumstances I visited the website centralbank.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: Full technical documentation is published at: https://gdpru.eu/en/audits/ie-centralbank-ie/ 3. GDPR provisions I ask you to examine 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]