The Hungarian Education System Portal (oktatas.hu, operated by Oktatási Hivatal) — 47 requests, 6 domains. Prior to consent, only the Usercentrics consent management platform (Germany/EU) loads, along with resources from the first-party domain; no Google, analytics, advertising pixels, or third-party trackers fire. Set-Cookie is zero. Consent is requested before any non-essential service launches. No violations have been recorded.
Request timeline
Declared versus actual
Transfer timings
Usercentrics CMP — loads first, before any trackers. Germany/EU.
Detected trackers
- No third-party trackers are present prior to consent — the only external contact before the user makes a choice is the Usercentrics consent management platform (Germany/EU)
Context
oktatas.hu is the central portal of Hungary’s education system, operated by the Educational Authority (Oktatási Hivatal, OH). The portal provides access to information on examinations, registers, and educational services; a number of subsystems operate behind authentication. The data controller is OH. The site is served by an nginx server, with HSTS present. Capture: 47 requests, 6 domains, recorded in a clean browser.
Direct Recipients of Data (prior to consent)
Prior to consent — only the Usercentrics consent management platform (Germany/EU), which loads to display the banner. There are no third-party trackers or advertising recipients in the capture.
Declared versus Actual
The site’s footer contains “Data Protection” (ADATVÉDELEM) and “Cookie Notice” (SÜTI TÁJÉKOZTATÓ) sections, and consent on the site is governed by the Usercentrics manager. OH’s internal data protection and information security regulations are addressed to the authority’s staff and do not describe web cookies, so the portal’s own cookie notice was used for this review.
The capture shows an implementation that is correctly structured. The only external resource that connects before any choice is made by the visitor is the Usercentrics consent manager itself: it loads its loader and SDK, pulls configuration, and renders the banner. No analytics, advertising, or other third-party services fire prior to consent — the capture contains no Google Analytics, no Google Tag Manager, no Google Fonts, no reCAPTCHA, no Facebook, and no pixels of any kind. Not a single cookie is set during the session (Set-Cookie is zero).
In other words, no discrepancy between “declared” and “actual” arises: non-essential services are held back until consent, and the only outbound call prior to the user’s choice is to the consent mechanism itself. This is precisely the sequencing a prior-consent model calls for.
Timing Relative to Consent
The consent manager loads at +146 ms, first among external resources; no trackers that it would need to hold back appear before it. No consent was given during the session, and in this state no third-party services are connected (Set-Cookie is zero).
What Cannot Be Asserted from This Capture
The capture covers the pre-consent state. Analytics or advertising services, if declared in the portal’s cookie notice, should by design launch only after acceptance — and in this capture they indeed do not fire; their behavior after consent cannot be assessed from this snapshot. Usercentrics is a consent management platform (Germany/EU); its own service calls transmit the IP address to Usercentrics, but this is a necessary part of the consent mechanism, and the recipient is located in the EU. Individual OH subsystems and authenticated sections are not covered by this capture. Server-side processing is not visible in a browser-based capture.
Conclusion
The Hungarian education system portal implements consent correctly: prior to any choice by the visitor, only the Usercentrics consent manager loads, and any non-essential services are held back until acceptance. The capture contains no analytics, advertising pixels, Google Fonts, or other third-party trackers; no data is transferred to a third-party recipient in a third country prior to consent, and the sole external contact is the consent mechanism itself, hosted in the EU. The site’s behavior matches a prior-consent model. No violations have been recorded in the capture.
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.
0360ebacec60a7807177ce2410941f3faf5a621dedebedeb981428fb1aaa2686Want 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) — oktatas.hu Кому: [укажите адрес компании — DPO / поддержка / юридический отдел] От: [Ваше имя], [контактный email] Прошу предоставить доступ к моим персональным данным, обрабатываемым в связи с использованием сайта oktatas.hu. 1. Категории данных и цели обработки (ст. 15(1)(a)-(c)) Прошу предоставить информацию по всем категориям, целям и получателям обработки моих данных на этом сайте — независимо от того, выявлены ли на сегодняшний день какие-либо несоответствия. 2. Получатели, сроки хранения и передача за пределы ЕЭЗ (ст. 15(1)(c)-(d), 46) Прошу также указать полный список третьих лиц-получателей, применимые сроки хранения по каждой категории и правовые основания передачи данных за пределы ЕЭЗ, если таковая происходит. Полный технический разбор с доказательствами (сохранённый сетевой журнал, контрольная сумма SHA-256) опубликован по адресу: https://gdpru.eu/en/audits/hu-oktatas-hu/ 3. Автоматизированная обработка и профилирование (ст. 15(1)(h)) Прошу сообщить, применяется ли в отношении меня автоматизированное принятие решений или профилирование, и если да — раскрыть логику такой обработки. С уважением, [Ваше имя] [контактный email] [Страна] [Дата]
Subject: Data access request (GDPR Art. 15) — oktatas.hu 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 oktatas.hu. 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/hu-oktatas-hu/ 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]