The Estonian real-estate portal City24 — 453 requests, 282 nodes, a 41-minute recording. A gigantic advertising stack: hundreds of IAB TCF advertising vendors. The OneTrust consent platform is installed, but tracking starts before the user's choice: Gemius web analytics goes out at +248 ms, and Google Analytics sends data with the consent marker gcs=G100 earlier than the OneTrust banner loaded. The banner itself presents vendor checkboxes pre-ticked to consent.
Request timeline
Declared versus actual
Transfer timings
Gemius web analytics, identifier d60wsoNu7…, 63 requests.
Google Ads AW-999125225.
Facebook pixel/SDK.
Google DoubleClick.
GA4 G-CP61K2W67H, page_view, gcs=G100.
OneTrust, IAB TCF banner, checkboxes pre-ticked.
Detected trackers
Show data recipients (75)
- Taboola Europe Limited (accessrequest.taboola.com) — advertising/RTB
- Onfocus (Adagio) (adagio.io) — advertising/RTB
- AddApptr GmbH (addapptr.com) — advertising/RTB
- Adhese (adhese.com) — advertising/RTB
- Anzu Virtual Reality LTD (admins-api.anzu.io) — advertising/RTB
- Admixer EU GmbH (admixer.com) — advertising/RTB
- Adserve.zone / Adserve AS (adserve.zone) — advertising/RTB
- adsquare GmbH (adsquare.com) — advertising/RTB
- Adzymic Creavibes (adzymic.com) — advertising/RTB
- 2KDirect, Inc. (dba iPromote) (app.ipromote.com) — advertising/RTB
- Sharethrough, Inc (assets.sharethrough.com) — advertising/RTB
- BeeswaxIO Corporation (beeswax.com) — advertising/RTB
- Blockthrough, Inc. (blockthrough.com) — advertising/RTB
- Ask Locala (cdn-ui-pub.asklocala.com) — advertising/RTB
- Adobe Audience Manager, Adobe Experience Platform (cdn.audiencemanager.de) — advertising/RTB
- Blue Billywig Group BV (cdn.bluebillywig.com) — advertising/RTB
- Index Exchange Inc. (cdn.indexexchange.com) — advertising/RTB
- Kwanko (cdn.kwanko.com) — advertising/RTB
- Sirdata (cdn.sirdata.eu) — advertising/RTB
- Clipcentric, Inc. (clipcentric.com) — advertising/RTB
- Consumable, Inc (consumable.com) — advertising/RTB
- Content Ignite (contentignite.com) — advertising/RTB
- Pexi B.V. (dash.pexi.nl) — advertising/RTB
- Converge-Digital (data.converge-digital.com) — advertising/RTB
- DEFINE MEDIA GMBH (definemedia.de) — advertising/RTB
- adbility media GmbH (device.adbility-media.com) — advertising/RTB
- Yieldmo, Inc. (devicestoragedisclosureurl.yieldmo.com) — advertising/RTB
- Good-Loop Ltd (gvl.good-loop.com) — advertising/RTB
- Effiliation / Effinity (hosting.effiliation.com) — advertising/RTB
- MEDIARITHMICS SAS (iab-tcf.mediarithmics.com) — advertising/RTB
- Nativo, Inc. (iab.nativo.com) — advertising/RTB
- NEURAL.ONE (iab.neural.one) — advertising/RTB
- Liftoff Monetize and Vungle Exchange (liftoff.ai) — advertising/RTB
- LoopMe Limited (loopme.ai) — advertising/RTB
- GumGum, Inc. (marketing.gumgum.com) — advertising/RTB
- InMobi Technology Services Pte. Ltd. (mobitech.io) — advertising/RTB
- NC Audience Exchange, LLC (ncaudienceexchange.com) — advertising/RTB
- The Ozone Project Limited (prebid.the-ozone-project.com) — advertising/RTB
- BidTheatre AB (privacy.bidtheatre.com) — advertising/RTB
- Ogury Ltd (privacy.ogury.co) — advertising/RTB
- Verve Group Europe GmbH (resources.verve.com) — advertising/RTB
- Visarity Technologies GmbH (script.visarity.com) — advertising/RTB
- Improve Digital (sellers.improvedigital.com) — advertising/RTB
- Bannerflow AB (shared.bannerflow.com) — advertising/RTB
- Adform A/S (site.adform.com) — advertising/RTB
- Smartme Analytics (smartmeanalytics.com) — advertising/RTB
- Smile Wanted Group (smilewanted.com) — advertising/RTB
- Hybrid Adtech GmbH (tcf.adtech.app) — advertising/RTB
- Appier PTE Ltd (tcf.appier.com) — advertising/RTB
- emetriq GmbH (tcf.emetriq.de) — advertising/RTB
- MEDIAMETRIE (tcf.mediametrie.com) — advertising/RTB
- Seedtag Advertising S.L (tcf.seedtag.com) — advertising/RTB
- Protected Media LTD (ui.protected.media) — advertising/RTB
- ViewPay (viewpay.tv) — advertising/RTB
- SunMedia (vod.sunmedia.tv) — advertising/RTB
- Firstlead GmbH (ADCELL) (www.adcell.de) — advertising/RTB
- AdDefend GmbH (www.addefend.com) — advertising/RTB
- Alliance Gravity Data Media (www.alliancegravity.com) — advertising/RTB
- AllMediaDesk GmbH (www.allmediadesk.com) — advertising/RTB
- AUDIOMOB LTD (www.audiomob.com) — advertising/RTB
- BIDSWITCH GmbH (www.bidswitch.com) — advertising/RTB
- Cloud Technologies S.A. (www.cloudtechnologies.pl) — advertising/RTB
- Eyeota Pte Ltd (www.eyeota.com) — advertising/RTB
- Justtag Sp. z o.o. (www.justtag.com) — advertising/RTB
- Localsensor B.V. (www.localsensor.com) — advertising/RTB
- Sift Media, Inc (www.media.net) — advertising/RTB
- OnAudience Ltd (www.onaudience.com) — advertising/RTB
- OpenX (www.openx.com) — advertising/RTB
- OS Data Solutions GmbH (www.osdatasolutions.de) — advertising/RTB
- Pinpoll GmbH (www.pinpoll.com) — advertising/RTB
- Quantcast (www.quantcast.com) — advertising/RTB
- RTB House S.A. (www.rtbhouse.com) — advertising/RTB
- Skaze (www.skaze.com) — advertising/RTB
- The MediaGrid Inc. (www.themediagrid.com) — advertising/RTB
- usemax advertisement (Emego GmbH) (www.usemax.de) — advertising/RTB
Indicators of GDPR non-compliance
- ePrivacy — Directive 2002/58/EC, Art. 5(3) (in conjunction with GDPR Art. 6(1)(a))The consent-management platform OneTrust with an IAB Transparency and Consent Framework banner is installed on the site, but advertising and analytics tracking starts before the user's choice. Gemius web analytics starts at +248 ms, Google Tag Manager at +957 ms, Google Ads at +955 ms, Facebook at +1223 ms, DoubleClick at +1237 ms, and Google Analytics 4 sends data with the consent-mode marker gcs=G100 at +1388 ms. The OneTrust consent-platform script, meanwhile, loads only at +3981 ms. That is, dozens of trackers run before and irrespective of the user's choice, and the banner itself, as its configuration shows, presents vendor checkboxes pre-ticked to consent.
- GDPR Art. 13(1)(e) — disclosure of recipientsThe privacy policy names Gemius, Google and Facebook and lists their cookies, and also refers to the TCF partner list. But the actual composition of recipients is incomparably broader: 282 third-party nodes were recorded over the session — hundreds of real-time advertising vendors. Samba TV TV-tracking and the Adition banner network are not disclosed in the policy by name, as is the overwhelming majority of the advertising recipients.
- GDPR Art. 7 — validity of consentThe IAB TCF banner presents a list of vendors with checkboxes pre-ticked to consent and an 'Agree to all' button in a prominent place. Pre-ticked checkboxes do not constitute valid consent within the meaning of the GDPR: consent must be freely given, specific and expressed by an affirmative action, not deducted from an already-ticked default state. Combined with the fact that tracking starts before any interaction with the banner, the user's choice effectively has no bearing on anything.
Context
city24.ee is a large Estonian real-estate portal, City24: listings for the sale and rent of apartments, houses, commercial premises and land. The controller is Kinnisvaraportaal OÜ, registry code 10680295, Pärnu mnt 141, Tallinn 11314. The site is served through Cloudflare (server: cloudflare); the content is in Estonian, Russian and English.
The recording: 453 requests, 282 third-party nodes, a recording length of about forty-one minutes. This is one of the most advertising-infrastructure-heavy recordings in the series: besides the own nodes and Gemius analytics, the page addresses the OneTrust consent platform with an IAB Transparency and Consent Framework banner and hundreds of real-time (RTB) advertising vendors — from Criteo, OpenX, PubMatic and Magnite to Taboola, Outbrain and RTB House.
The processing is described by Kinnisvaraportaal OÜ’s data-protection terms and the text of the OneTrust consent banner; a list of TCF partners is attached to the materials.
Who receives data directly
Gemius, Google (Analytics, Ads, Tag Manager, DoubleClick), Facebook, Samba TV, Adition and hundreds of TCF advertising vendors.
Declared versus actual
Tracking starts before the choice in the consent banner. The consent-management platform OneTrust with an IAB Transparency and Consent Framework banner — the very one where the user is asked to consent to hundreds of advertising vendors — is installed on the site. But the actual tracking does not wait for it. Gemius web analytics starts at +248 ms, Google Ads at +955 ms, Google Tag Manager at +957 ms, Facebook at +1223 ms, DoubleClick at +1237 ms, and Google Analytics 4 sends data with the gcs=G100 marker at +1388 ms. The OneTrust script loads only at +3981 ms. That is, by the time the consent mechanism appears, the analytics and advertising have already run.
The banner is pre-ticked to consent. The OneTrust “vendor list” banner presents vendor checkboxes ticked by default, with an “Agree to all” button in a prominent place. The main banner screen states the essence of the processing directly: data is processed to show content and advertising and is passed to Transparency and Consent Framework partners. Pre-ticked checkboxes do not constitute valid consent: under the GDPR it must be expressed by an affirmative action, not deducted from an already-ticked state.
Some recipients are disclosed, but the composition is incomparably broader. The policy names Gemius, Google and Facebook and lists their cookies (hit.gemius.pl, fr, NID, IDE), and also refers to the TCF partner list. This is disclosure of the core. But 282 third-party nodes were recorded over the session, and Samba TV TV-tracking, the Adition banner network and the overwhelming majority of the advertising vendors are not named in the policy.
Security headers are set. The site sets strict transport with subdomain inclusion and preload, the frame-embedding ban SAMEORIGIN, a referrer policy, a permissions policy and a content-security-policy. However, the content-security-policy itself is broad (default-src 'self' https:), which, given such a volume of third-party nodes, restricts little.
Consent: what is proven and what is not
Proven: tracking starts before the consent platform loads. Gemius (+248 ms), Google Ads (+955 ms), Facebook (+1223 ms), DoubleClick (+1237 ms) and Google Analytics 4 (+1388 ms) are initiated by the markup and precede the OneTrust script (+3981 ms).
Proven: Google Analytics sends data with a granted-consent marker. The GA4 request carries gcs=G100.
Proven: the banner presents checkboxes pre-ticked to consent. The OneTrust banner configuration contains vendors with a consent state ticked by default and an “Agree to all” button.
Not proven and not unambiguously established: the origin of the consent marker. The gcs=G100 marker could have been set either as a default value in the consent-mode configuration or as a saved choice from an earlier visit. Response bodies and cookie headers were removed from the published file during sanitisation, so the source of the marker cannot be reconstructed from the recording. What is recorded is the observable: the trackers send data before the consent banner loaded in this session.
Not proven and not asserted: the state of cookies on the device. Cookie headers were removed from the published file during sanitisation. Full identifiers are not reproduced in the analysis.
Separately: the browser was sending the DNT: 1 header during capture. This had no effect on the composition and addressing of the requests.
Boundaries of observation
The recording covers the home page and sections of the portal over a long session. The observation records the browser’s behaviour, not the services’ internal workings: server-side processing, contractual relationships with recipients and settings on their side are not verified by a browser recording. The legal assessment is made by the competent authority — Andmekaitse Inspektsioon.
A significant part of the 282 nodes are the disclosure and registration endpoints of IAB TCF advertising vendors (the paths tcf.*, gdpr.*, privacy.*), which are addressed at the initialisation of the advertising chain. Their presence in itself indicates the scale of the advertising circuit; which of them actually received personal data and which are only declared in the consent chain is not separated individually by a browser recording and requires separate analysis. The full list of nodes is attached to the materials for the archive.
The file is published sanitised of personal data: cookie headers in requests and response bodies were removed. The conclusion that tracking starts before consent rests on the network level — the timings, addresses and initiators of the requests are read from the recording.
The identification of services rests on domains and address patterns: Gemius — by hit.gemius.pl and the identifier; Google Analytics 4 — by google-analytics.com/g/collect and the property G-CP61K2W67H; Google Ads — by googleadservices.com and AW-999125225; Facebook — by connect.facebook.net; OneTrust — by cookielaw.org and onetrust.com; the advertising vendors — by the domains of the TCF standard.
Conclusion
The Estonian real-estate portal City24 carries one of the heaviest advertising circuits in the series: 282 third-party nodes, hundreds of real-time IAB TCF advertising vendors. The OneTrust consent-management platform is installed, but the actual tracking does not wait for it: Gemius web analytics goes out at +248 ms, and Google Analytics sends data with a granted-consent marker gcs=G100 earlier than the OneTrust banner loaded at +3981 ms. The banner, meanwhile, presents vendors with checkboxes pre-ticked to consent, which does not constitute valid consent under the GDPR.
The policy names Gemius, Google and Facebook, but the actual composition of recipients is incomparably broader, and Samba TV TV-tracking, the Adition banner network and the overwhelming majority of the advertising vendors are not disclosed by name.
Remediation: make the actual loading of all advertising and analytics tracking — including Gemius, Google, Facebook and the TCF advertising vendors — conditional on the user’s choice in OneTrust, so that before consent no data, including the gcs=G100 marker, is sent; remove the checkboxes pre-ticked to consent in the banner and the “Agree to all” button as the primary scenario; bring the list of recipients in the policy into line with the actual composition.
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.
43437e71d883ed71e19bdb64e5abbfbf1d0117cbb4c18551c777f72c17d4d505Want 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) — city24.ee Кому: [укажите адрес компании — DPO / поддержка / юридический отдел] От: [Ваше имя], [контактный email] Прошу предоставить доступ к моим персональным данным, обрабатываемым в связи с использованием сайта city24.ee. 1. Категории данных и цели обработки (ст. 15(1)(a)-(c)) На основании независимого технического анализа сайта прошу подтвердить и подробно раскрыть следующие категории обработки: 1) На сайте установлена платформа управления согласием OneTrust с баннером стандарта IAB Transparency and Consent Framework, но рекламный и аналитический трекинг стартует до выбора пользователя. Веб-аналитика Gemius стартует на +248 мс, Google Tag Manager на +957 мс, Google Ads на +955 мс, Facebook на +1223 мс, DoubleClick на +1237 мс, а Google Analytics 4 отправляет данные с признаком режима согласия gcs=G100 на +1388 мс. Скрипт платформы согласия OneTrust при этом загружается только на +3981 мс. То есть десятки трекеров отрабатывают до и помимо выбора пользователя, а сам баннер, как видно по составу его конфигурации, предъявляет предустановленные на согласие галочки вендоров. 2) Политика конфиденциальности называет Gemius, Google и Facebook и перечисляет их cookie, а также ссылается на список партнёров стандарта TCF. Но фактический состав получателей несопоставимо шире: за запись зафиксировано 282 сторонних узла — сотни рекламных вендоров реального времени. ТВ-трекинг Samba TV и баннерная сеть Adition поимённо в политике не раскрыты, как и подавляющее большинство рекламных получателей. 3) Баннер стандарта IAB TCF предъявляет список поставщиков с галочками, предустановленными на согласие, и кнопкой «Согласиться на все» на видном месте. Предварительно проставленные галочки не образуют действительного согласия по смыслу GDPR: согласие должно быть свободным, конкретным и выражаться активным действием, а не сниматься с уже отмеченного по умолчанию состояния. В сочетании с тем, что трекинг стартует ещё до взаимодействия с баннером, выбор пользователя фактически ни на что не влияет. 2. Получатели, сроки хранения и передача за пределы ЕЭЗ (ст. 15(1)(c)-(d), 46) Прошу также указать полный список третьих лиц-получателей, применимые сроки хранения по каждой категории и правовые основания передачи данных за пределы ЕЭЗ, если таковая происходит. Полный технический разбор с доказательствами (сохранённый сетевой журнал, контрольная сумма SHA-256) опубликован по адресу: https://gdpru.eu/en/audits/ee-city24-ee/ 3. Автоматизированная обработка и профилирование (ст. 15(1)(h)) Прошу сообщить, применяется ли в отношении меня автоматизированное принятие решений или профилирование, и если да — раскрыть логику такой обработки. С уважением, [Ваше имя] [контактный email] [Страна] [Дата]
Subject: Data access request (GDPR Art. 15) — city24.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 city24.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) The consent-management platform OneTrust with an IAB Transparency and Consent Framework banner is installed on the site, but advertising and analytics tracking starts before the user's choice. Gemius web analytics starts at +248 ms, Google Tag Manager at +957 ms, Google Ads at +955 ms, Facebook at +1223 ms, DoubleClick at +1237 ms, and Google Analytics 4 sends data with the consent-mode marker gcs=G100 at +1388 ms. The OneTrust consent-platform script, meanwhile, loads only at +3981 ms. That is, dozens of trackers run before and irrespective of the user's choice, and the banner itself, as its configuration shows, presents vendor checkboxes pre-ticked to consent. 2) The privacy policy names Gemius, Google and Facebook and lists their cookies, and also refers to the TCF partner list. But the actual composition of recipients is incomparably broader: 282 third-party nodes were recorded over the session — hundreds of real-time advertising vendors. Samba TV TV-tracking and the Adition banner network are not disclosed in the policy by name, as is the overwhelming majority of the advertising recipients. 3) The IAB TCF banner presents a list of vendors with checkboxes pre-ticked to consent and an 'Agree to all' button in a prominent place. Pre-ticked checkboxes do not constitute valid consent within the meaning of the GDPR: consent must be freely given, specific and expressed by an affirmative action, not deducted from an already-ticked default state. Combined with the fact that tracking starts before any interaction with the banner, the user's choice effectively has no bearing on anything. 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-city24-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]
Teema: Isikuandmetele juurdepääsu taotlus (IKÜM art 15) — city24.ee Kellele: [märkige ettevõtte aadress — DPO / tugi / juriidiline osakond] Kellelt: [Teie nimi], [kontakt-e-post] Palun anda mulle juurdepääs minu isikuandmetele, mida töödeldakse seoses veebisaidi city24.ee kasutamisega. 1. Andmekategooriad ja töötlemise eesmärgid (IKÜM art 15(1)(a)-(c)) Sõltumatu tehnilise analüüsi põhjal palun kinnitada ja üksikasjalikult avaldada järgmised töötlemiskategooriad: 1) Saidil on OneTrusti nõusoleku haldamise platvorm koos IAB läbipaistvuse ja nõusoleku raamistiku bänneriga, kuid reklaami ja analüütilist jälgimist alustatakse enne kasutaja valimist. Gemiuse veebianalüütika algab +248 ms-st, Google Tag Manager +957 ms-st, Google Ads +955 ms-st, Facebook +1223 ms-st, DoubleClick +1237 ms-st ja Google Analytics 4 saadab +1388 ms-le gcs=G100 nõusoleku režiimiga andmed. OneTrusti nõusolekuplatvormi skript on laaditud ainult +3981 ms-le. See tähendab, et kümned jälgijad töötavad enne ja lisaks kasutaja valikule ning bänner ise, nagu on näha selle konfiguratsiooni koosseisust, esitab nõusoleku saamiseks müüjate eelinstallitud märked. 2) Privaatsuspoliitikas nimetatakse Gemius, Google ja Facebook ning loetletakse nende küpsised ja viidatakse ka TCF-i partnerite nimekirjale. Kuid vastuvõtjate tegelik koosseis on võrreldamatult laiem: rekordile on salvestatud 282 kolmanda osapoole sõlme - sadu reaalajas reklaamimüüjaid. Samba TV-jälgimis- ja Adition-bännerivõrku ei avalikustata poliitikas nime järgi, nagu ka enamik reklaamisaajaid. 3) IAB TCF standard bänner kuvab tarnijate nimekirja, millel on eelnevalt määratud märked nõusoleku saamiseks ja "nõustud kõigile" nupp silmapaistvas kohas. Eelkontrollid ei kujuta endast kehtivat nõusolekut GDPRi tähenduses: nõusolek peaks olema vaba, konkreetne ja väljenduma aktiivses tegevuses ning seda ei tohiks vaikimisi eemaldada. Koos asjaoluga, et jälgimine algab juba enne bänneriga suhtlemist, ei mõjuta kasutaja valik tegelikult midagi. 2. Vastuvõtjad, säilitustähtajad ja edastamine väljapoole EMP-d (IKÜM art 15(1)(c)-(d), 46) Palun samuti esitada täielik loetelu kolmandatest isikutest vastuvõtjatest, iga kategooria puhul kohaldatavad säilitustähtajad ning andmete EMP-välisele edastamisele kohaldatav õiguslik alus, kui selline edastamine toimub. Täielik tehniline analüüs koos tõenditega (salvestatud võrgulogi, SHA-256 kontrollsumma) on avaldatud aadressil: https://gdpru.eu/en/audits/ee-city24-ee/ 3. Automatiseeritud töötlemine ja profiilianalüüs (IKÜM art 15(1)(h)) Palun teatada, kas minu suhtes kohaldatakse automatiseeritud otsuste tegemist või profiilianalüüsi, ning kui jah, siis avaldada selle loogika. Lugupidamisega, [Teie nimi] [kontakt-e-post] [Riik] [Kuupäev]
RIA DigiDoc — phone · Smart-ID / Mobile-ID
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)
Тема: Жалоба на обработку персональных данных — city24.ee 1. Предмет жалобы Я подаю жалобу в отношении обработки моих персональных данных сайтом city24.ee. 2. Обстоятельства Я посетил сайт city24.ee и обнаружил признаки несоответствия обработки моих персональных данных требованиям GDPR. Технический разбор, опубликованный на gdpru.eu 06.09.2026 (открытая методология, воспроизводимые измерения), документирует следующие признаки: 1) На сайте установлена платформа управления согласием OneTrust с баннером стандарта IAB Transparency and Consent Framework, но рекламный и аналитический трекинг стартует до выбора пользователя. Веб-аналитика Gemius стартует на +248 мс, Google Tag Manager на +957 мс, Google Ads на +955 мс, Facebook на +1223 мс, DoubleClick на +1237 мс, а Google Analytics 4 отправляет данные с признаком режима согласия gcs=G100 на +1388 мс. Скрипт платформы согласия OneTrust при этом загружается только на +3981 мс. То есть десятки трекеров отрабатывают до и помимо выбора пользователя, а сам баннер, как видно по составу его конфигурации, предъявляет предустановленные на согласие галочки вендоров. 2) Политика конфиденциальности называет Gemius, Google и Facebook и перечисляет их cookie, а также ссылается на список партнёров стандарта TCF. Но фактический состав получателей несопоставимо шире: за запись зафиксировано 282 сторонних узла — сотни рекламных вендоров реального времени. ТВ-трекинг Samba TV и баннерная сеть Adition поимённо в политике не раскрыты, как и подавляющее большинство рекламных получателей. 3) Баннер стандарта IAB TCF предъявляет список поставщиков с галочками, предустановленными на согласие, и кнопкой «Согласиться на все» на видном месте. Предварительно проставленные галочки не образуют действительного согласия по смыслу GDPR: согласие должно быть свободным, конкретным и выражаться активным действием, а не сниматься с уже отмеченного по умолчанию состояния. В сочетании с тем, что трекинг стартует ещё до взаимодействия с баннером, выбор пользователя фактически ни на что не влияет. Полная техническая документация опубликована по адресу: https://gdpru.eu/en/audits/ee-city24-ee/ 3. Положения GDPR, соблюдение которых прошу проверить ePrivacy — Директива 2002/58/EC, ст. 5(3) (в связке с GDPR Art. 6(1)(a)); GDPR Art. 13(1)(e) — раскрытие получателей; GDPR Art. 7 — действительность согласия 4. Требование Прошу проверить изложенные обстоятельства и, если несоответствие подтвердится, принять меры, предусмотренные статьёй 58(2) GDPR. 5. Приложения Полная доказательная база — HAR-файл, контрольная сумма SHA-256 и цитата из политики конфиденциальности сайта, документирующая указанное противоречие — опубликована и проверяема по ссылке в пункте 2 выше. С уважением, [Ваше имя] [контактный email] [Страна] [Дата]
Subject: Complaint regarding personal data processing — city24.ee 1. Subject of the complaint I am filing a complaint regarding the processing of my personal data by the website city24.ee. 2. Circumstances I visited the website city24.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 6 September 2026 (open methodology, reproducible measurements) documents the following indications: 1) The consent-management platform OneTrust with an IAB Transparency and Consent Framework banner is installed on the site, but advertising and analytics tracking starts before the user's choice. Gemius web analytics starts at +248 ms, Google Tag Manager at +957 ms, Google Ads at +955 ms, Facebook at +1223 ms, DoubleClick at +1237 ms, and Google Analytics 4 sends data with the consent-mode marker gcs=G100 at +1388 ms. The OneTrust consent-platform script, meanwhile, loads only at +3981 ms. That is, dozens of trackers run before and irrespective of the user's choice, and the banner itself, as its configuration shows, presents vendor checkboxes pre-ticked to consent. 2) The privacy policy names Gemius, Google and Facebook and lists their cookies, and also refers to the TCF partner list. But the actual composition of recipients is incomparably broader: 282 third-party nodes were recorded over the session — hundreds of real-time advertising vendors. Samba TV TV-tracking and the Adition banner network are not disclosed in the policy by name, as is the overwhelming majority of the advertising recipients. 3) The IAB TCF banner presents a list of vendors with checkboxes pre-ticked to consent and an 'Agree to all' button in a prominent place. Pre-ticked checkboxes do not constitute valid consent within the meaning of the GDPR: consent must be freely given, specific and expressed by an affirmative action, not deducted from an already-ticked default state. Combined with the fact that tracking starts before any interaction with the banner, the user's choice effectively has no bearing on anything. Full technical documentation is published at: https://gdpru.eu/en/audits/ee-city24-ee/ 3. GDPR provisions I ask you to examine ePrivacy — Directive 2002/58/EC, Art. 5(3) (in conjunction with GDPR Art. 6(1)(a)); GDPR Art. 13(1)(e) — disclosure of recipients; GDPR Art. 7 — validity of consent 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]
1. Kaebuse ese Esitan kaebuse seoses minu isikuandmete töötlemisega veebisaidil city24.ee. 2. Asjaolud Külastasin veebisaiti city24.ee ja tuvastasin märke sellest, et minu isikuandmete töötlemine ei vasta isikuandmete kaitse üldmääruse (IKÜM) nõuetele. Tehniline analüüs, mis on avaldatud aadressil gdpru.eu 06.09.2026 (avatud metoodika, korratavad mõõtmised), dokumenteerib järgmist: 1) Saidil on OneTrusti nõusoleku haldamise platvorm koos IAB läbipaistvuse ja nõusoleku raamistiku bänneriga, kuid reklaami ja analüütilist jälgimist alustatakse enne kasutaja valimist. Gemiuse veebianalüütika algab +248 ms-st, Google Tag Manager +957 ms-st, Google Ads +955 ms-st, Facebook +1223 ms-st, DoubleClick +1237 ms-st ja Google Analytics 4 saadab +1388 ms-le gcs=G100 nõusoleku režiimiga andmed. OneTrusti nõusolekuplatvormi skript on laaditud ainult +3981 ms-le. See tähendab, et kümned jälgijad töötavad enne ja lisaks kasutaja valikule ning bänner ise, nagu on näha selle konfiguratsiooni koosseisust, esitab nõusoleku saamiseks müüjate eelinstallitud märked. 2) Privaatsuspoliitikas nimetatakse Gemius, Google ja Facebook ning loetletakse nende küpsised ja viidatakse ka TCF-i partnerite nimekirjale. Kuid vastuvõtjate tegelik koosseis on võrreldamatult laiem: rekordile on salvestatud 282 kolmanda osapoole sõlme - sadu reaalajas reklaamimüüjaid. Samba TV-jälgimis- ja Adition-bännerivõrku ei avalikustata poliitikas nime järgi, nagu ka enamik reklaamisaajaid. 3) IAB TCF standard bänner kuvab tarnijate nimekirja, millel on eelnevalt määratud märked nõusoleku saamiseks ja "nõustud kõigile" nupp silmapaistvas kohas. Eelkontrollid ei kujuta endast kehtivat nõusolekut GDPRi tähenduses: nõusolek peaks olema vaba, konkreetne ja väljenduma aktiivses tegevuses ning seda ei tohiks vaikimisi eemaldada. Koos asjaoluga, et jälgimine algab juba enne bänneriga suhtlemist, ei mõjuta kasutaja valik tegelikult midagi. Täielik tehniline dokumentatsioon on avaldatud aadressil: https://gdpru.eu/en/audits/ee-city24-ee/ 3. Sätted, mille järgimist palun kontrollida e-privaatsus – direktiiv 2002/58/EÜ, artikli 5 lõige 3 (koosmõjus GDPRi artikli 6 lõike 1 punktiga a); GDPR – artikli 13 lõike 1 punkt e – vastuvõtjate avalikustamine; GDPR artikkel 7 – Nõusoleku kehtivus 4. Nõue Palun kontrollida kirjeldatud asjaolusid ja mittevastavuse kinnitamisel kohaldada IKÜM artikli 58 lõikes 2 ette nähtud meetmeid. 5. Lisad Täielik tõendusmaterjal — HAR-fail, kontrollsumma SHA-256 ning veebisaidi privaatsuspoliitika tsitaat, mis dokumenteerib nimetatud vastuolu — on avaldatud ja kontrollitav punktis 2 viidatud lingil. Lugupidamisega, [Teie nimi] [kontakt-e-post] [Riik] [Kuupäev]