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.
Timeline of the leak
Declared versus actual
Transfer timings
Matomo matomo.js on an external domain. Behind Cloudflare.
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 identificationThe 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 recipientsThe 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.
Direct Recipients of Data (prior to consent)
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.
Timing Relative to Consent
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, constitutes a violation of 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.
fee70891f7e50cfd3d809c08cd388e3c413ea1555ca2ff58bfe99f9e4afb76d1Where to file: Commission for Personal Data Protection (CPDP) — file a complaint online →
To: Commission for Personal Data Protection (CPDP)
From: [Your name], [contact email]
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. Provisions violated
ePrivacy (Bulgarian implementation) + Art. 5(1)(a) — consent and identification; GDPR Art. 13(1)(e) — disclosure of recipients
4. Request
I request that you investigate the violations described and 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.
[Date] [Signature / name]