Technical audit · 29.05.2026

nhif.bg

National Health Insurance Fund of Bulgaria

The National Health Insurance Fund of Bulgaria — 47 requests, 2 domains. Matomo analytics on the external domain track.uslugi.io fires prior to consent, transmitting the page title, URL, a visitor identifier, and screen resolution. Matomo is not named in the policy.

Request timeline

+0 ms · portal load

Content, stylesheets, scripts, and icons are served from the first-party domain nhif.bg.

+609 ms · analytics script

track.uslugi.io/matomo.js — Matomo loads from an external domain (a shared instance).

+687 ms · data transfer without consent

track.uslugi.io/matomo.php — the beacon transmits the page title, URL, a visitor identifier (_id), and screen resolution.

Declared versus actual

✓ The policy mentions cookies and consent in generic terms — declared

+ Matomo (track.uslugi.io) — the actual tracker, hosted on an external domain, prior to consent, carrying a visitor identifier and screen resolution; not named in the policy — not declared

+ No consent management platform is detected on the site — not declared

Transfer timings

+609 ms track.uslugi.io

Matomo matomo.js on an external domain. Behind Cloudflare.

+687 ms track.uslugi.io

Matomo beacon: page title + URL + visitor identifier + screen resolution. idsite=37.

Detected trackers

Matomo (track.uslugi.io) — on an external domain

Indicators of GDPR non-compliance

ePrivacy (Bulgarian implementation) + Art. 5(1)(a) — consent and identification
The capture shows Matomo running, hosted on the external domain track.uslugi.io (a shared instance, idsite=37, behind Cloudflare). The matomo.js script loads at +609 ms, and the matomo.php beacon at +687 ms transmits the page title ('Начало - Национална здравноосигурителна каса'), the URL nhif.bg/bg, a visitor identifier (_id), and screen resolution (1536x864). No consent management platform is detected, Set-Cookie across the entire session is zero, and no choice has been made by the user — analytics carrying a visitor identifier fire prior to consent.
GDPR Art. 13(1)(e) — disclosure of recipients
The NHIF's privacy policy mentions cookies and consent in generic terms but names neither Matomo nor the domain track.uslugi.io to which the analytics data is transmitted.

Context

nhif.bg is the website of the National Health Insurance Fund of Bulgaria (Национална здравноосигурителна каса, NHIF), the state body for mandatory health insurance. The data controller is the NHIF. A privacy notice (approximately 24,500 characters) was provided. Capture: 47 requests, 2 domains, recorded in a clean browser.

track.uslugi.io (Matomo) — page title, URL, visitor identifier, screen resolution.

Declared versus Actual

The NHIF’s privacy notice mentions the use of cookies and consent in general terms, but names no specific analytics tool.

The capture shows Matomo running, hosted not on the NHIF’s own domain but on the external domain track.uslugi.io (a shared analytics instance behind Cloudflare infrastructure, site identifier idsite=37). The matomo.js script loads at +609 ms, and at +687 ms the matomo.php beacon transmits the page title (“Начало - Национална здравноосигурителна каса”), the address nhif.bg/bg, a visitor identifier (_id), and screen resolution. The session state at this point is one of no consent: no consent management platform is detected, not a single cookie is set across the entire session, and no choice has been made by the user. Thus, analytics carrying a persistent visitor identifier fire prior to consent, and neither the tool nor the external recipient domain is disclosed in the policy. The social media icons (YouTube, Facebook) on the page are static SVGs served from nhif.bg itself and do not constitute third-party calls.

The Matomo script loads at +609 ms; the beacon carrying the data at +687 ms. No consent mechanism is present; the transfer of data with a visitor identifier occurs prior to any choice (Set-Cookie is zero).

What Cannot Be Asserted from This Capture

The capture covers the home page. The visitor identifier is not reproduced in full in this publication. A properly anonymized Matomo configuration may qualify for an exemption from consent; in this case, the beacon carries a visitor identifier and screen resolution, a matter for assessment by the competent authority (the CPDP). The domain track.uslugi.io is served via Cloudflare; the capture does not establish the geography of processing. Server-side processing is not visible in a browser-based capture.

Conclusion

The website of the National Health Insurance Fund of Bulgaria uses Matomo analytics, hosted on the external domain track.uslugi.io, which fires prior to consent and transmits the page title, URL, a visitor identifier, and screen resolution. No consent management platform is present, and the tool is not named in the policy. The firing of analytics carrying a visitor identifier prior to consent, together with the non-disclosure of the external recipient, indicates non-compliance with the requirements concerning consent and disclosure of recipients. Remedy: make Matomo’s firing conditional on consent (implement a consent management platform that holds back analytics until a choice is made), consider hosting analytics on the site’s own infrastructure with anonymization, and name the tool and recipient in the policy.

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: bg/nhif-bg-2026-05-29.har

SHA-256: fee70891f7e50cfd3d809c08cd388e3c413ea1555ca2ff58bfe99f9e4afb76d1

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:

Filing date:

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).

Тема: Запрос доступа к персональным данным (ст. 15 GDPR) — nhif.bg

Кому: [укажите адрес компании — DPO / поддержка / юридический отдел]
От: [Ваше имя], [контактный email]

Прошу предоставить доступ к моим персональным данным, обрабатываемым в связи с использованием сайта nhif.bg.

1. Категории данных и цели обработки (ст. 15(1)(a)-(c))
На основании независимого технического анализа сайта прошу подтвердить и подробно раскрыть следующие категории обработки:

1) В замере работает Matomo, размещённый на внешнем домене track.uslugi.io (общий инстанс, idsite=37, за Cloudflare). Скрипт matomo.js загружается на +609 мс, а beacon matomo.php на +687 мс передаёт заголовок страницы («Начало - Национална здравноосигурителна каса»), URL nhif.bg/bg, идентификатор посетителя (_id) и разрешение экрана (1536x864). Consent-менеджер не обнаружен, Set-Cookie за весь сеанс ноль, выбор пользователем не сделан — аналитика с идентификатором посетителя срабатывает до согласия.

2) Политика конфиденциальности НЗОК упоминает бисквитки (cookie) и согласие обобщённо, но не называет ни Matomo, ни домен track.uslugi.io, на который передаются аналитические данные.


2. Получатели, сроки хранения и передача за пределы ЕЭЗ (ст. 15(1)(c)-(d), 46)
Прошу также указать полный список третьих лиц-получателей, применимые сроки хранения по каждой категории и правовые основания передачи данных за пределы ЕЭЗ, если таковая происходит. Полный технический разбор с доказательствами (сохранённый сетевой журнал, контрольная сумма SHA-256) опубликован по адресу: https://gdpru.eu/en/audits/bg-nhif-bg/

3. Автоматизированная обработка и профилирование (ст. 15(1)(h))
Прошу сообщить, применяется ли в отношении меня автоматизированное принятие решений или профилирование, и если да — раскрыть логику такой обработки.

С уважением,

[Ваше имя]
[контактный email]
[Страна]


[Дата]

Subject: Data access request (GDPR Art. 15) — nhif.bg

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 nhif.bg.

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 capture shows Matomo running, hosted on the external domain track.uslugi.io (a shared instance, idsite=37, behind Cloudflare). The matomo.js script loads at +609 ms, and the matomo.php beacon at +687 ms transmits the page title ('Начало - Национална здравноосигурителна каса'), the URL nhif.bg/bg, a visitor identifier (_id), and screen resolution (1536x864). No consent management platform is detected, Set-Cookie across the entire session is zero, and no choice has been made by the user — analytics carrying a visitor identifier fire prior to consent.

2) The NHIF's privacy policy mentions cookies and consent in generic terms but names neither Matomo nor the domain track.uslugi.io to which the analytics data is transmitted.

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/bg-nhif-bg/

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]

30 days have passed since contacting the company with no response? → Show the regulator complaint letter

Ready-to-send complaint letter

Where to file: Commission for Personal Data Protection (CPDP) — file a complaint online →

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)

Тема: Жалоба на обработку персональных данных — nhif.bg

1. Предмет жалобы
Я подаю жалобу в отношении обработки моих персональных данных сайтом nhif.bg.

2. Обстоятельства
Я посетил сайт nhif.bg и обнаружил признаки несоответствия обработки моих персональных данных требованиям GDPR. Технический разбор, опубликованный на gdpru.eu 29.05.2026 (открытая методология, воспроизводимые измерения), документирует следующие признаки:

1) В замере работает Matomo, размещённый на внешнем домене track.uslugi.io (общий инстанс, idsite=37, за Cloudflare). Скрипт matomo.js загружается на +609 мс, а beacon matomo.php на +687 мс передаёт заголовок страницы («Начало - Национална здравноосигурителна каса»), URL nhif.bg/bg, идентификатор посетителя (_id) и разрешение экрана (1536x864). Consent-менеджер не обнаружен, Set-Cookie за весь сеанс ноль, выбор пользователем не сделан — аналитика с идентификатором посетителя срабатывает до согласия.

2) Политика конфиденциальности НЗОК упоминает бисквитки (cookie) и согласие обобщённо, но не называет ни Matomo, ни домен track.uslugi.io, на который передаются аналитические данные.

Полная техническая документация опубликована по адресу: https://gdpru.eu/en/audits/bg-nhif-bg/

3. Положения GDPR, соблюдение которых прошу проверить
ePrivacy (болгарская имплементация) + Art. 5(1)(a) — согласие и идентификация; GDPR Art. 13(1)(e) — раскрытие получателей

4. Требование
Прошу проверить изложенные обстоятельства и, если несоответствие подтвердится, принять меры, предусмотренные статьёй 58(2) GDPR.

5. Приложения
Полная доказательная база — HAR-файл, контрольная сумма SHA-256 и цитата из политики конфиденциальности сайта, документирующая указанное противоречие — опубликована и проверяема по ссылке в пункте 2 выше.

С уважением,

[Ваше имя]
[контактный email]
[Страна]


[Дата]

Subject: Complaint regarding personal data processing — nhif.bg

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

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

1) The capture shows Matomo running, hosted on the external domain track.uslugi.io (a shared instance, idsite=37, behind Cloudflare). The matomo.js script loads at +609 ms, and the matomo.php beacon at +687 ms transmits the page title ('Начало - Национална здравноосигурителна каса'), the URL nhif.bg/bg, a visitor identifier (_id), and screen resolution (1536x864). No consent management platform is detected, Set-Cookie across the entire session is zero, and no choice has been made by the user — analytics carrying a visitor identifier fire prior to consent.

2) The NHIF's privacy policy mentions cookies and consent in generic terms but names neither Matomo nor the domain track.uslugi.io to which the analytics data is transmitted.

Full technical documentation is published at: https://gdpru.eu/en/audits/bg-nhif-bg/

3. GDPR provisions I ask you to examine
ePrivacy (Bulgarian implementation) + Art. 5(1)(a) — consent and identification; GDPR Art. 13(1)(e) — disclosure of recipients

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]