RU EN
www.
Technical audit · 03.06.2026

iizi.ee

Estonia's Largest Insurance Broker — Part of the Austrian GrECo Group
EE

An insurance broker handling clients' health and financial data explicitly declares no data transfer outside the EEA. The HAR records Google Analytics, Facebook SDK, and Google Ads — all before the consent banner, all in the USA.

Request timeline

+82 ms · before consent
Google Fonts (fonts.googleapis.com) and Google Storage (storage.googleapis.com) — data to Google, USA. Simultaneously.
+188 ms · before consent
Crisp Chat (client.crisp.chat) — the support chat, status 304. A WebSocket connection at +956 ms.
+354 ms · before consent
Google Analytics (analytics.js) — data to Google, USA.
+355 ms · before consent
Facebook SDK (connect.facebook.net/et_EE/sdk.js) — data to Meta, USA.
+686 ms · before consent
Sentry (ingest.de.sentry.io) — error monitoring, servers in Germany (EU).
+1345 ms · banner
Cookiebot loads. By this point, 5 external services are already active.
+6294 ms · after the banner
GTM (GTM-3Z8T) — loads. Google Ads and a GA collect follow.
+6459 ms
Google Ads (pagead2.googlesyndication.com) — a page_view collect. USA.
+6644 ms
Google DoubleClick (ade.googlesyndication.com) — a retargeting pixel.

Declared versus actual

✓ Data transfer only within the EEA — declared in the policy — declared
✓ Volitatud töötlejad (IT support and web-hosting providers) — a general formulation — declared
+ Google Analytics — USA — not declared
+ Google Tag Manager — USA — not declared
+ Google Fonts — USA — not declared
+ Google Storage (storage.googleapis.com) — USA — not declared
+ Google Ads / DoubleClick — USA — not declared
+ Facebook SDK — USA — not declared
+ Crisp Chat — USA — not declared

Transfer timings

+82 ms fonts.googleapis.com

Google Fonts Open Sans. IP address to the USA

+82 ms storage.googleapis.com

SVG files from Google Storage. USA

+188 ms client.crisp.chat

The support chat. WebSocket at +956 ms

+354 ms www.google-analytics.com

analytics.js loaded before the banner

+355 ms connect.facebook.net

Facebook SDK et_EE. Meta, USA

+1345 ms consent.cookiebot.com

Cookiebot appears

+6294 ms www.googletagmanager.com

GTM-3Z8T loads

+6459 ms pagead2.googlesyndication.com

Google Ads page_view

+6644 ms ade.googlesyndication.com

DoubleClick retargeting

Detected trackers

Indicators of GDPR non-compliance

Context

IIZI Kindlustusmaakler AS is Estonia’s largest insurance broker, part of the Austrian GrECo group. It processes insurance contracts across all categories: motor comprehensive, liability, medical insurance, property insurance. The privacy policy explicitly mentions processing clients’ health data (section 3.16). A DPO is appointed (andmekaitse@iizi.ee). Policy updated 31.12.2025. HAR: 167 requests, 17 domains.

Two documents, one contradiction

IIZI has two versions of its privacy policy: a 2024 version (detailed, 5 pages) and the current one dated 31.12.2025 (condensed, 4 pages). Both declare the same thing: data is not transferred outside the EU/EEA.

The current policy (31.12.2025) contains a direct statement: “Me ei edasta isikuandmeid väljapoole Euroopa Liidu/Euroopa Majanduspiirkonna piire” — we do not transfer personal data outside the EU/EEA. The HAR from June 3, 2026, disproves this for at least six American domains, including Google Analytics, Facebook SDK, and Google Ads.

Cookiebot appears at +1345 ms. By this point, the following are already active:

+82 ms — Google Fonts (fonts.googleapis.com) and Google Storage (storage.googleapis.com) — SVG icons for insurance products are stored in Google Cloud. The user’s IP address goes to Google, USA.

+188 ms — Crisp Chat (client.crisp.chat) — the support chat. A WebSocket connection is established at +956 ms, before the banner.

+354 ms — Google Analytics (analytics.js) — the older UA version loads before consent.

+355 ms — Facebook SDK (connect.facebook.net/et_EE/sdk.js) — data to Meta (USA). Estonian locale, but American servers.

After Cookiebot appears, GTM (+6294 ms), Google Ads (+6459 ms), and Google DoubleClick retargeting (+6644 ms) activate. This may mean they fire by default with no explicit consent given — or that Cookiebot is configured with categories pre-selected.

Sensitivity context

IIZI sells medical insurance and processes clients’ health data — an Art. 9 GDPR category. A Facebook SDK on the homepage of an insurance broker handling such data is not a matter of technical carelessness. It is a matter of architectural choice that contradicts the declared processing standard.

Sentry — the exception

The one external service in this HAR that meets the EEA declaration: Sentry uses European servers (ingest.de.sentry.io — Germany). This is a deliberate choice — the EU instance of Sentry, not the American one. The same choice could have been made for analytics.

Conclusion

IIZI has a DPO, a current privacy policy, and Cookiebot. The documentation appears to have been prepared in good faith. But the policy declares no data transfer outside the EEA — and the HAR records Google Analytics, Facebook SDK, and Google Ads, all American, all before consent. The gap between the document and reality here is not technical — it is direct and specific. The choice of Sentry with EU servers shows the team knows how to make this distinction. The question is whether the same principle is applied to the rest of the services.

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: ee/iizi-ee-2026-06-03.har
SHA-256: 0800cb9c069dbdbffa1735df81887410850635100af06fd4f7aeb7c259d046c6
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) — iizi.ee

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 iizi.ee.

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) Google Fonts (+82 ms), Google Storage (+82 ms), Crisp Chat (+188 ms), Google Analytics (+354 ms), and the Facebook SDK (+355 ms) all fire before Cookiebot appears (+1345 ms). Data goes to the USA more than a second before the consent banner.

2) Cookiebot appears at 1345 ms. By this point, five external services are already active. After the banner appears, GTM (+6294 ms), Google Ads (+6459 ms), and GA collect (+6533 ms) activate — this may indicate default activation with no explicit consent required.

3) The privacy policy (version dated 31.12.2025) declares no data transfer outside the EEA. The HAR records transfers to the USA via Google Analytics, Facebook SDK, Google Ads, Crisp Chat, Google Fonts, and Google Storage. Not one of these recipients is mentioned.

4) The policy states directly: 'Me ei edasta isikuandmeid väljapoole EL/EMP piire' (we do not transfer personal data outside the EU/EEA). The HAR disproves this for at least six American domains.

5) IIZI processes clients' health data (medical insurance, policy section 3.16). An insurance broker handling health data — with a Facebook SDK on its homepage and no consent.


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/ee-iizi-ee/

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: Estonian Data Protection Inspectorate (AKI) — write to info@aki.ee

Important: AKI only handles submissions in Estonian. Translate the letter before sending.

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 — iizi.ee

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

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

1) Google Fonts (+82 ms), Google Storage (+82 ms), Crisp Chat (+188 ms), Google Analytics (+354 ms), and the Facebook SDK (+355 ms) all fire before Cookiebot appears (+1345 ms). Data goes to the USA more than a second before the consent banner.

2) Cookiebot appears at 1345 ms. By this point, five external services are already active. After the banner appears, GTM (+6294 ms), Google Ads (+6459 ms), and GA collect (+6533 ms) activate — this may indicate default activation with no explicit consent required.

3) The privacy policy (version dated 31.12.2025) declares no data transfer outside the EEA. The HAR records transfers to the USA via Google Analytics, Facebook SDK, Google Ads, Crisp Chat, Google Fonts, and Google Storage. Not one of these recipients is mentioned.

4) The policy states directly: 'Me ei edasta isikuandmeid väljapoole EL/EMP piire' (we do not transfer personal data outside the EU/EEA). The HAR disproves this for at least six American domains.

5) IIZI processes clients' health data (medical insurance, policy section 3.16). An insurance broker handling health data — with a Facebook SDK on its homepage and no consent.

Full technical documentation is published at: https://gdpru.eu/en/audits/ee-iizi-ee/

3. GDPR provisions I ask you to examine
GDPR Art. 6(1), Art. 5(1)(a); GDPR Art. 7; GDPR Art. 13(1)(e); GDPR Art. 5(1)(a), Art. 13(1)(f), Chapter V; GDPR Art. 9 (potentially)

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]