A real-estate classifieds portal — a single capture across ten pages, 1469 requests, 282 nodes. The site has the OneTrust consent platform and Google Consent Mode installed, defaulting to denied storage, and the user never grants consent: they open and close the preference center, and the consent state across all analytics pings stays 'denied'. Even so, the Adform advertising pixel and the Google DoubleClick creative fire within the first ~900 ms — before the consent banner even loads at +1735 ms — and GA4 transmits the visitor's behaviour to Google in cookieless mode throughout the session. Moreover, the IP address and a referer pointing to kv.ee reach more than 240 IAB TCF advertising nodes, some of them outside the EU — before and without any consent. Yet the binding data-protection terms state that the operator does not transfer data to third parties and does not transfer it outside the EU.
Request timeline
Declared versus actual
Transfer timings
GTM, container G-XSSYYGNPKF, inserted into the page markup.
GA4 page_view, gcs=G100. Page URL and title, language, screen resolution, browser client hints.
Adform 1x1inv=1 pixel, before the consent banner, consent macros unpopulated. 302 response.
Google DoubleClick ad creative, pulled from ad_images.
Repeat Adform request, 1x1 gif response.
The OneTrust platform loads only after the advertising requests.
Error report to the operator's own endpoint.
No exact timing
Detected trackers
Show data recipients (62)
- OneTrust (cdn.cookielaw.org, privacyportal-eu.onetrust.com) — consent management platform; 124 requests, the CMP script loads at +1735 ms, already after the first advertising requests
- Google Analytics 4 (region1.google-analytics.com, G-XSSYYGNPKF) — analytics, loaded by the GTM container; 46 pings, consent state gcs=G100 (both storages denied), pings are cookieless, yet Google receives the IP address, the full page URL and title, language, screen resolution, browser client hints and click events
- Google Tag Manager (www.googletagmanager.com) — the container from which GA4 starts; 10 requests
- Google DoubleClick / 2mdn (s0.2mdn.net) together with code.createjs.com — ad creative in the page's ad slot, served before consent
- Google Fonts (fonts.googleapis.com, fonts.gstatic.com) — web fonts; 69 requests, the IP address goes to Google
- Google APIs (storage.googleapis.com, www.gstatic.com) — static-content delivery network
- Adform (track.adform.net, site.adform.com) — advertising network; an invisible 1x1 pixel (bn=90091642, 1x1inv=1) fires at +838 ms, before the consent banner, with unpopulated macros gdpr=${GDPR} and gdpr_consent=${GDPR_CONSENT_50}
- Sentry (browser.sentry-cdn.com — SDK; sentry.allepal.ee — the operator AllePal's own endpoint) — functional error monitoring
- IAB TCF (tcf.adtech.app) — service endpoint of the Transparency and Consent Framework; 4 requests
- Quantcast (www.quantcast.com) — analytics and consent platform
- Index Exchange (cdn.indexexchange.com) — ad exchange
- Beeswax (beeswax.com) — DSP, real-time bidding (RTB)
- Adikteev (tcf-registrationprocess.adikteev.com) — advertising, retargeting
- RTB House (www.rtbhouse.com) — advertising (RTB)
- Yahoo (meta.legal.yahoo.com) — advertising
- TripleLift (cdn.3lift.com) — advertising
- Xandr / AppNexus (acdn.adnxs.com) — ad exchange
- Taboola (accessrequest.taboola.com) — native advertising
- Equativ / Smart (apps.smartadserver.com) — ad server
- Adman (static.adman.gr) — advertising
- Magnite / Rubicon (gdpr.rubiconproject.com) — ad exchange (SSP)
- GumGum (marketing.gumgum.com) — advertising
- OpenX (www.openx.com) — ad exchange (SSP)
- Yieldlab (ad.yieldlab.net) — ad exchange (SSP)
- PubMatic (cdn.pubmatic.com) — ad exchange (SSP)
- Sharethrough (assets.sharethrough.com) — native advertising
- Criteo (privacy.criteo.com) — advertising, retargeting
- Lotame (tags.crwdcntrl.net) — data management platform (DMP)
- LiveRamp (tcf.ats.rlcdn.com) — identity / DMP
- Rich Audience (cdnj.richaudience.com) — advertising / DMP
- IPONWEB (www.bidswitch.com, www.iponweb.com) — RTB infrastructure
- AdRoll (s.adroll.com) — advertising, retargeting
- ID5 (id5-sync.com) — cross-site identity (RTB)
- Teads (iab-cookie-disclosure.teads.tv) — advertising
- Media.net (www.media.net) — advertising network
- Connatix (connatix.com) — video advertising (native)
- ADman Media (admanmedia.com) — advertising
- Seedtag (tcf.seedtag.com) — contextual advertising
- Outbrain (www.outbrain.com) — native advertising
- YieldMo (devicestoragedisclosureurl.yieldmo.com) — advertising
- remerge (assets.remerge.io) — advertising, retargeting
- Improve Digital (cdn.360yield.com, sellers.improvedigital.com) — ad exchange (SSP)
- RevContent (sothebys.revcontent.com) — native advertising
- OneTag (onetag-cdn.com) — advertising (RTB)
- Yieldlove (cdn-a.yieldlove.com) — ad exchange
- Bounce Exchange (assets.bounceexchange.com) — advertising, behavioural signals
- BannerFlow (shared.bannerflow.com) — ad creative production
- Integral Ad Science (static.adsafeprotected.com) — ad verification
- Weborama (cstatic.weborama.fr) — advertising / DMP
- FreeWheel (iab.fwmrm.net) — video advertising
- Jivox (cdn.jivox.com) — dynamic advertising
- Roq.ad (zd.rqtrk.eu) — cross-device identity
- Gemius (gemius.com) — audience measurement
- InMobi (publisher.inmobi.com) — mobile advertising
- Kantar Operations (secure.insightexpressai.com) — audience measurement
- MGID (www.mgid.com) — native advertising
- AudienceProject (sak.userreport.com) — measurement / DMP
- Adtelligent (adtelligent.com) — advertising (RTB)
- Cxense (cdn.cxense.com) — data management platform (DMP)
- Verve Group (resources.verve.com) — advertising
- Dailymotion (statics.dmcdn.net) — video / advertising
- OnAudience (www.onaudience.com) — data management platform (DMP)
Indicators of GDPR non-compliance
- ePrivacy — Directive 2002/58/EC, Art. 5(3) (in conjunction with GDPR Art. 6(1)(a)) — tracking before consentThe portal has the OneTrust consent management platform and Google Consent Mode installed, defaulting to denied storage. Nevertheless, third-party advertising requests go out before the banner appears. The Adform pixel (track.adform.net, bn=90091642, 1x1inv=1) fires at +821 ms and receives a gif response at +960 ms; the Google DoubleClick ad creative (s0.2mdn.net) loads at +866 ms. The CMP script itself (cdn.cookielaw.org) is not fetched until +1718 ms — that is, after the advertising requests have already taken place. Across the entire session (10 pages, 1469 requests) consent was never given: the OneTrust events record only 'Preference Center Opened From Banner' and 'Preferences Close Button', there is no Accept/Reject choice, and the consent state across all 46 analytics pings stays gcs=G100. The Adform request meanwhile carries unpopulated consent macros gdpr=${GDPR} and gdpr_consent=${GDPR_CONSENT_50}: the platform exists, but this advertising beacon is not conditioned on it and fires unconditionally as the page is parsed.
- GDPR Art. 5(1)(a) / Art. 13(1)(e) — transparency and recipients, a contradiction within the operator's own documentsThe binding AllePal data-protection terms, in the section 'Isikuandmete edastamine ja volitatud töötlejad', state plainly: 'Me ei edasta isikuandmeid kolmandatele isikutele' (we do not transfer personal data to third parties, except where a legal basis exists) and 'me ei edasta isikuandmeid Euroopa Liidust väljapoole' (we do not transfer data outside the European Union). The wording is confirmed on the live site (kv.ee/info/151). In fact GA4 and DoubleClick transmit the IP address and browsing data to Google — a recipient in the United States. Neither Google, nor Adform, nor OneTrust is named in the terms themselves; the list of processors is reduced to categories ('accounting, IT solutions and others'). At the same time the same operator's own cookie declaration (the 'Küpsised' page) and the IAB TCF banner disclose data-sharing with 240–264 advertising partners and name Google, Adform, DoubleClick and Facebook explicitly. The operator's two documents contradict each other: one denies transfers to third parties and outside the EU, the other describes an advertising stack of more than 240 partners.
- GDPR Art. 6(1)(b) — basing cookies on performance of a contractIn the terms' summary table, the row 'Veebilehe kasutamise võimaldamine (kuulutuste vaatamine, brausimine) — Küpsised' is assigned to the basis IKÜM artikkel 6 (1) (b) — performance of a contract. Consent (6(1)(a)) in the document is tied only to newsletters. Meanwhile the OneTrust consent platform treats advertising (Sihipärased) and statistics (Jõudlusküpsised) cookies as consent-based. Placing analytics and advertising cookies under 'contractual necessity' diverges both from the site's actual architecture and from the operator's own consent panel.
Context
kv.ee is a real-estate classifieds portal operated by AllePal OÜ, registry code 12209337, Pärnu mnt 141, Tallinn 11314. Under its own terms, AllePal acts as the controller (vastutav töötleja). Contact details are info@kv.ee, +372 6718 103; the document does not name a dedicated data-protection officer. The site is served via Cloudflare and sets a full set of security headers: HSTS with preload, Content-Security-Policy, Referrer-Policy strict-origin-when-cross-origin, Permissions-Policy, X-Content-Type-Options nosniff — at the header level there is nothing to object to.
The capture is a single recording across ten pages: the Estonian homepage, the Russian version, a search, and several price-statistics pages. In total 1469 requests, 282 nodes, about twelve minutes, recorded on 6 September 2026, in a browser with language ru. The site runs the OneTrust consent management platform and Google Consent Mode, which defaults to denying the advertising and analytics storages.
Processing is described by two of the operator’s documents: the binding data-protection terms (andmekaitsetingimused, revision of 02.05.2024) and a separate OneTrust-based cookie declaration with the full IAB TCF list.
Who receives data directly
Google (Analytics, Tag Manager, DoubleClick/2mdn, Fonts), Adform. Functionally — the operator’s own Sentry (sentry.allepal.ee).
Declared vs. actual
AllePal’s document is tidy: definitions, processing bases, a purpose table, data-subject rights, the supervisory authority. It says little about the site, but what it says is definite — and it is precisely in those definite places that the discrepancies arise.
First — advertising requests go out before a consent that is never given. The consent infrastructure is in place: OneTrust and Google Consent Mode, defaulting to denied storage. But the load order bypasses that infrastructure. The tag container starts at +371 ms straight from the page markup, analytics goes out at +645 ms, the Adform pixel at +821 ms, the DoubleClick creative at +866 ms. The consent platform’s own script does not load until +1718 ms — that is, after the advertising beacon has already fired. Across the whole session, consent was never given: the OneTrust events show only the opening and closing of the preference center, and the consent state across all forty-six analytics pings stays denied. The Adform request meanwhile contains unpopulated consent macros gdpr=${GDPR} and gdpr_consent=${GDPR_CONSENT_50} — meaning not even a consent string is passed to the advertising partner. The platform exists, but this beacon is not conditioned on it.
Second — the terms deny what actually happens. The data-transfer section is categorical: data is not transferred to third parties, not transferred outside the EU. The wording is reproduced on the live site as well. In fact GA4 and DoubleClick transmit the IP address and browsing data to Google — a recipient in the United States. A direct contradiction: the document denies exactly the kind of transfer that the capture records.
Third — recipients are named in one document and denied in another. The binding terms name no web recipient explicitly: the list of processors is reduced to categories. The same operator’s own cookie declaration and the IAB TCF banner, by contrast, disclose data-sharing with 240–264 advertising partners and name Google, Adform, DoubleClick and Facebook directly. So the operator’s recipients are disclosed — but in a document that contradicts the main one. A user reading the binding terms is told ‘we do not transfer to third parties’; a user opening the cookie declaration sees an advertising stack of more than two hundred partners.
And this contradiction does not stay on paper. In the recording, each of the 240–264 IAB TCF nodes received a GET request, and with it the visitor’s IP address and the header Referer: https://www.kv.ee/; the IP address is personal data, and among the nodes are recipients outside the EU. Consent was never given throughout the session. So the clauses ‘we do not transfer to third parties’ and ‘we do not transfer outside the EU’ are refuted not by a discrepancy between documents, but by data actually delivered: connection metadata reached more than two hundred advertising nodes before and without any consent. A profile assembled from behaviour is a separate matter — in this capture it goes to Google and Adform — but the very fact of transferring the IP address to third-party recipients, which the terms deny, is recorded at the scale of the entire advertising list.
Fourth — cookies for viewing listings are assigned to performance of a contract. In the purpose table, the row on using the site via cookies is based on Article 6(1)(b) — contract — whereas consent in the document is tied only to newsletters. The OneTrust panel, meanwhile, honestly splits cookies into strictly necessary, functional, statistics and advertising, and describes the last two categories as operating on consent. Assigning analytics and advertising cookies to ‘contractual necessity’ diverges both from the site’s actual scheme and from the operator’s own consent panel.
Separately, note that Google analytics behaves correctly as far as storage is concerned: the consent state is denied, the pings are cookieless, the client identifier is new on each page. This does not remove the transfer of the IP address and behaviour to Google, but the reading or writing of storage by analytics is not recorded in this capture — unlike the advertising pixel, which fires unconditionally.
Consent: what is proven and what is not
Proven: consent was not given during the session. Across ten pages and 1469 requests, the OneTrust events record only ‘Preference Center Opened From Banner’ and ‘Preferences Close Button’. There is no Accept/Reject choice at any point, and the consent state across all forty-six analytics pings is gcs=G100 (both storages denied).
Proven: the advertising requests are not conditioned on consent. The Adform pixel goes out at +821 ms, the DoubleClick creative at +866 ms, whereas the consent platform’s script does not load until +1718 ms. The Adform request carries unpopulated consent macros. There is no condition before these requests in the load order.
Proven: analytics honours the storage denial. The GA client identifier is stable within a page and changes ten times across the ten pages — there is no persistent cookie binding, consistent with the denied consent state. At the same time, Google receives the page URL, title, language, screen resolution and browser client hints.
Proven: recipients are disclosed in the cookie declaration but not in the binding terms. Google, Adform, DoubleClick, Facebook and the IAB TCF list are present in the ‘Küpsised’ declaration and absent from the main document, which additionally denies transfers to third parties.
Not proven: reading or writing of storage by the advertising pixel. Whether Adform sets a cookie via the 302 chain is not established from the published (redacted) headers. What is recorded is the beacon firing before consent and the delivery of a response; the finding rests on that, not on a presumed cookie write.
Observation boundaries
The capture covers ten pages of the portal and records browser behaviour, not the services’ internal workings: server-side processing, contracts with recipients and their own settings are not verified by a browser-level capture.
The tail of 240–264 IAB TCF nodes needs to be stated precisely. Each of them received a GET request, and with it the visitor’s IP address, User-Agent and the header Referer: https://www.kv.ee/. The IP address is personal data, so by the very fact of the request these nodes are recipients (har-check recognised 67; the rest are classified as third-party domains of undetermined purpose). What the recording does not contain is a payload sent to them: all the requests are GETs for static device-disclosure files (deviceStorage.json, disclosure.json), 270 requests and not a single POST; a profile assembled from behaviour is not transmitted to these nodes in this capture. They fired when the vendor list was opened in the OneTrust preference center — which explains why the requests occurred, but does not undo the fact that the IP address and referer reached those nodes. In other words, ‘addressed and delivered’ here refers to connection metadata (the IP address, a referer pointing to kv.ee), whereas the transfer of a behavioural profile in this capture is recorded to Google and Adform.
The file is published redacted of personal data: cookie values in requests have been removed. Response bodies and markup are preserved, so tag insertion, load order and request parameters are verified directly against the published file. The full client identifier is not reproduced in the analysis; its cookieless nature is established from the Google requests themselves. The operator’s own Sentry (sentry.allepal.ee) is functional error monitoring, unrelated to advertising tracking, and is not recorded as a violation.
The legal assessment is made by the competent authority — Andmekaitse Inspektsioon, whose supervision is named in the terms themselves.
Conclusion
The real-estate classifieds portal has an outwardly correct consent infrastructure — OneTrust and Google Consent Mode with storage denied by default — but it does not cover everything that loads on the page. The Adform advertising pixel and the Google DoubleClick creative fire within the first ~900 ms, before the consent banner even appears at +1718 ms, and consent is never given for the whole session. Google analytics honours the storage denial, but still transmits the IP address and the visitor’s behaviour to the United States.
At the same time the binding data-protection terms state plainly that the operator does not transfer data to third parties and does not transfer it outside the EU — whereas the same operator’s own cookie declaration discloses an advertising stack of more than 240 partners and names Google, Adform and DoubleClick explicitly. The operator’s two documents say different things about one and the same matter.
Remediation: condition the advertising requests (Adform, DoubleClick) and the loading of analytics on actual consent, so that no advertising beacon fires before the user’s choice; pass advertising partners a valid TCF consent string instead of unpopulated macros; bring the binding data-protection terms into line with the facts — either name Google, Adform and the advertising partners as recipients and disclose the transfer to the US under Chapter V, or stop those transfers; and reconcile the basis for analytics and advertising cookies between the terms (where they are assigned to contract) and the consent panel (where they are consent-based).
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.
0bf3ca6e939680ab3443e0813eac8184b3ea6c9a6b579323422aad789557dc4fWant 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) — kv.ee
Кому: [укажите адрес компании — DPO / поддержка / юридический отдел]
От: [Ваше имя], [контактный email]
Прошу предоставить доступ к моим персональным данным, обрабатываемым в связи с использованием сайта kv.ee.
1. Категории данных и цели обработки (ст. 15(1)(a)-(c))
На основании независимого технического анализа сайта прошу подтвердить и подробно раскрыть следующие категории обработки:
1) На портале установлены платформа управления согласием OneTrust и режим согласия Google, по умолчанию запрещающий хранилища. Тем не менее сторонние рекламные обращения уходят раньше, чем появляется баннер. Пиксель Adform (track.adform.net, bn=90091642, 1x1inv=1) срабатывает на +821 мс и получает ответ-gif на +960 мс; рекламный креатив Google DoubleClick (s0.2mdn.net) загружается на +866 мс. Сам скрипт CMP (cdn.cookielaw.org) подтягивается только на +1718 мс — то есть после того, как рекламные обращения уже состоялись. За весь сеанс (10 страниц, 1469 запросов) согласие не давалось: в событиях OneTrust зафиксированы лишь «Preference Center Opened From Banner» и «Preferences Close Button», выбора Accept/Reject нет, а статус согласия во всех 46 пингах аналитики остаётся gcs=G100. Обращение Adform при этом несёт незаполненные макросы gdpr=${GDPR} и gdpr_consent=${GDPR_CONSENT_50}: платформа существует, но этот рекламный маяк ею не обусловлен и уходит безусловно при разборе страницы.
2) Обязывающие условия защиты данных AllePal в разделе «Isikuandmete edastamine ja volitatud töötlejad» прямо заявляют: «Me ei edasta isikuandmeid kolmandatele isikutele» (данные третьим лицам не передаются, кроме случаев наличия законного основания) и «me ei edasta isikuandmeid Euroopa Liidust väljapoole» (за пределы ЕС данные не передаются). Формулировка подтверждена на живом сайте (kv.ee/info/151). Фактически GA4 и DoubleClick передают адрес IP и данные о просмотре в Google — получателю в США. Ни Google, ни Adform, ни OneTrust в самих условиях не названы; перечень обработчиков сведён к категориям («бухгалтерия, ИТ-решения и прочие»). Одновременно собственная декларация cookie того же оператора (страница «Küpsised») и баннер IAB TCF раскрывают обмен данными с 240–264 рекламными партнёрами и поимённо называют Google, Adform, DoubleClick, Facebook. Два документа оператора противоречат друг другу: один отрицает передачу третьим лицам и за пределы ЕС, другой описывает рекламный стек на 240 с лишним партнёров.
3) В сводной таблице условий строка «Veebilehe kasutamise võimaldamine (kuulutuste vaatamine, brausimine) — Küpsised» отнесена к основанию IKÜM artikkel 6 (1) (b) — исполнение договора. Согласие (6(1)(a)) в документе привязано лишь к рассылкам. При этом платформа согласия OneTrust трактует рекламные (Sihipärased) и статистические (Jõudlusküpsised) cookie как основанные на согласии. Помещение аналитических и рекламных cookie под «договорную необходимость» расходится и с фактической архитектурой сайта, и с собственной панелью согласия.
2. Получатели, сроки хранения и передача за пределы ЕЭЗ (ст. 15(1)(c)-(d), 46)
Прошу также указать полный список третьих лиц-получателей, применимые сроки хранения по каждой категории и правовые основания передачи данных за пределы ЕЭЗ, если таковая происходит. Полный технический разбор с доказательствами (сохранённый сетевой журнал, контрольная сумма SHA-256) опубликован по адресу: https://gdpru.eu/en/audits/ee-kv-ee/
3. Автоматизированная обработка и профилирование (ст. 15(1)(h))
Прошу сообщить, применяется ли в отношении меня автоматизированное принятие решений или профилирование, и если да — раскрыть логику такой обработки.
С уважением,
[Ваше имя]
[контактный email]
[Страна]
[Дата]Subject: Data access request (GDPR Art. 15) — kv.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 kv.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 portal has the OneTrust consent management platform and Google Consent Mode installed, defaulting to denied storage. Nevertheless, third-party advertising requests go out before the banner appears. The Adform pixel (track.adform.net, bn=90091642, 1x1inv=1) fires at +821 ms and receives a gif response at +960 ms; the Google DoubleClick ad creative (s0.2mdn.net) loads at +866 ms. The CMP script itself (cdn.cookielaw.org) is not fetched until +1718 ms — that is, after the advertising requests have already taken place. Across the entire session (10 pages, 1469 requests) consent was never given: the OneTrust events record only 'Preference Center Opened From Banner' and 'Preferences Close Button', there is no Accept/Reject choice, and the consent state across all 46 analytics pings stays gcs=G100. The Adform request meanwhile carries unpopulated consent macros gdpr=${GDPR} and gdpr_consent=${GDPR_CONSENT_50}: the platform exists, but this advertising beacon is not conditioned on it and fires unconditionally as the page is parsed.
2) The binding AllePal data-protection terms, in the section 'Isikuandmete edastamine ja volitatud töötlejad', state plainly: 'Me ei edasta isikuandmeid kolmandatele isikutele' (we do not transfer personal data to third parties, except where a legal basis exists) and 'me ei edasta isikuandmeid Euroopa Liidust väljapoole' (we do not transfer data outside the European Union). The wording is confirmed on the live site (kv.ee/info/151). In fact GA4 and DoubleClick transmit the IP address and browsing data to Google — a recipient in the United States. Neither Google, nor Adform, nor OneTrust is named in the terms themselves; the list of processors is reduced to categories ('accounting, IT solutions and others'). At the same time the same operator's own cookie declaration (the 'Küpsised' page) and the IAB TCF banner disclose data-sharing with 240–264 advertising partners and name Google, Adform, DoubleClick and Facebook explicitly. The operator's two documents contradict each other: one denies transfers to third parties and outside the EU, the other describes an advertising stack of more than 240 partners.
3) In the terms' summary table, the row 'Veebilehe kasutamise võimaldamine (kuulutuste vaatamine, brausimine) — Küpsised' is assigned to the basis IKÜM artikkel 6 (1) (b) — performance of a contract. Consent (6(1)(a)) in the document is tied only to newsletters. Meanwhile the OneTrust consent platform treats advertising (Sihipärased) and statistics (Jõudlusküpsised) cookies as consent-based. Placing analytics and advertising cookies under 'contractual necessity' diverges both from the site's actual architecture and from the operator's own consent panel.
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-kv-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) — kv.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 kv.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) Portaalis on OneTrusti nõusoleku haldamise platvorm ja Google'i nõusoleku režiim, mis vaikimisi keelab salvestamise. Kolmandate osapoolte reklaamikaebused lahkuvad aga enne bänneri ilmumist. Adformi piksel (rada adform.net, bn=90091642, 1x1inv=1) käivitub +821 ms-s ja saab vastuse-gifi +960 ms-s; Google DoubleClicki reklaamiloov (s0. 2mdn.net) on laaditud +866 ms-s. CMP skript ise (cdn. cookielaw.org) tõmmatakse üles ainult +1718 ms - see tähendab pärast seda, kui aadress on juba toimunud. Kogu seansi jaoks (10 lehekülge, 1469 taotlust) ei antud nõusolekut: OneTrusti sündmustes registreeriti ainult «Preference Center Opened From Banner» ja «Preferences Close Button», aktsepteerimise / tagasilükkamise valikut ei ole ja nõusoleku staatus kõigis 46 analüüsi pingis jääb gcs=G100. Samal ajal kannab Adformi aadress täitmata makrosid gdpr=${GDPR} ja gdpr consent=${GDPR CONSENT 50}: platvorm on olemas, kuid see reklaamimajakas ei ole põhjustatud sellest ja kaob lehe parsimisel tingimusteta.
2) AllePal’i siduvad andmekaitsetingimused jaotises «Isikuandmete edastamine ja volitatud töötlejad» sätestavad selgesõnaliselt: «Me ei edasta isikuandmeid kolmandatele isikutele» (andmeid ei edastata kolmandatele isikutele, kui selleks puudub õiguslik alus) ja «me ei edasta isikuandmeid Euroopa Liidust väljapoole» (andmeid ei edastata väljapoole ELi). Sõnastus on kinnitatud otse veebisaidil (kv.ee/info/151). Tegelikult edastavad GA4 ja DoubleClick IP-aadressi ja sirvivad andmeid USA-s asuvale vastuvõtjale. Google'it, Adformi ega OneTrusti ei nimetata terminites ise; protsessorite loend on vähendatud kategooriatesse („raamatupidamine, IT-lahendused jne). Samal ajal avalikustavad operaatori enda küpsisedeklaratsioon («Küpsised» lehekülg) ja IAB TCF bänner andmevahetuse 240-264 reklaamipartneriga ning nende nimed on Google, Adform, DoubleClick, Facebook. Kaks dokumenti on omavahel vastuolus: üks eitab üleandmist kolmandatele isikutele ja väljaspool ELi, teine kirjeldab enam kui 240 partneri reklaami.
3) Tingimuste koondtabelis viidatakse reale "Veebilehe kasutamise soodustamine (kuulutuste vaatamine, brausimine) - Küpsised" IKÜMi artikli 6 lõike 1 punkti b alusel - lepingu täitmine. Dokumendis olev nõusolek (6(1)(a)) on seotud ainult uudiskirjadega. Nõusolekuplatvorm OneTrust käsitleb reklaami (Sihimoodid) ja statistilisi (Jõudlusküpsised) küpsiseid nõusolekupõhistena. Analüütiliste ja reklaamiküpsiste paigutamine "lepingulise vajaduse" alla erineb nii saidi tegelikust arhitektuurist kui ka selle enda nõusoleku paneelist.
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-kv-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)
Тема: Жалоба на обработку персональных данных — kv.ee
1. Предмет жалобы
Я подаю жалобу в отношении обработки моих персональных данных сайтом kv.ee.
2. Обстоятельства
Я посетил сайт kv.ee и обнаружил признаки несоответствия обработки моих персональных данных требованиям GDPR. Технический разбор, опубликованный на gdpru.eu 06.09.2026 (открытая методология, воспроизводимые измерения), документирует следующие признаки:
1) На портале установлены платформа управления согласием OneTrust и режим согласия Google, по умолчанию запрещающий хранилища. Тем не менее сторонние рекламные обращения уходят раньше, чем появляется баннер. Пиксель Adform (track.adform.net, bn=90091642, 1x1inv=1) срабатывает на +821 мс и получает ответ-gif на +960 мс; рекламный креатив Google DoubleClick (s0.2mdn.net) загружается на +866 мс. Сам скрипт CMP (cdn.cookielaw.org) подтягивается только на +1718 мс — то есть после того, как рекламные обращения уже состоялись. За весь сеанс (10 страниц, 1469 запросов) согласие не давалось: в событиях OneTrust зафиксированы лишь «Preference Center Opened From Banner» и «Preferences Close Button», выбора Accept/Reject нет, а статус согласия во всех 46 пингах аналитики остаётся gcs=G100. Обращение Adform при этом несёт незаполненные макросы gdpr=${GDPR} и gdpr_consent=${GDPR_CONSENT_50}: платформа существует, но этот рекламный маяк ею не обусловлен и уходит безусловно при разборе страницы.
2) Обязывающие условия защиты данных AllePal в разделе «Isikuandmete edastamine ja volitatud töötlejad» прямо заявляют: «Me ei edasta isikuandmeid kolmandatele isikutele» (данные третьим лицам не передаются, кроме случаев наличия законного основания) и «me ei edasta isikuandmeid Euroopa Liidust väljapoole» (за пределы ЕС данные не передаются). Формулировка подтверждена на живом сайте (kv.ee/info/151). Фактически GA4 и DoubleClick передают адрес IP и данные о просмотре в Google — получателю в США. Ни Google, ни Adform, ни OneTrust в самих условиях не названы; перечень обработчиков сведён к категориям («бухгалтерия, ИТ-решения и прочие»). Одновременно собственная декларация cookie того же оператора (страница «Küpsised») и баннер IAB TCF раскрывают обмен данными с 240–264 рекламными партнёрами и поимённо называют Google, Adform, DoubleClick, Facebook. Два документа оператора противоречат друг другу: один отрицает передачу третьим лицам и за пределы ЕС, другой описывает рекламный стек на 240 с лишним партнёров.
3) В сводной таблице условий строка «Veebilehe kasutamise võimaldamine (kuulutuste vaatamine, brausimine) — Küpsised» отнесена к основанию IKÜM artikkel 6 (1) (b) — исполнение договора. Согласие (6(1)(a)) в документе привязано лишь к рассылкам. При этом платформа согласия OneTrust трактует рекламные (Sihipärased) и статистические (Jõudlusküpsised) cookie как основанные на согласии. Помещение аналитических и рекламных cookie под «договорную необходимость» расходится и с фактической архитектурой сайта, и с собственной панелью согласия.
Полная техническая документация опубликована по адресу: https://gdpru.eu/en/audits/ee-kv-ee/
3. Положения GDPR, соблюдение которых прошу проверить
ePrivacy — Директива 2002/58/EC, ст. 5(3) (в связке с GDPR Art. 6(1)(a)) — трекинг до согласия; GDPR Art. 5(1)(a) / Art. 13(1)(e) — прозрачность и получатели, противоречие внутри документов оператора; GDPR Art. 6(1)(b) — обоснование cookie исполнением договора
4. Требование
Прошу проверить изложенные обстоятельства и, если несоответствие подтвердится, принять меры, предусмотренные статьёй 58(2) GDPR.
5. Приложения
Полная доказательная база — HAR-файл, контрольная сумма SHA-256 и цитата из политики конфиденциальности сайта, документирующая указанное противоречие — опубликована и проверяема по ссылке в пункте 2 выше.
С уважением,
[Ваше имя]
[контактный email]
[Страна]
[Дата]Subject: Complaint regarding personal data processing — kv.ee
1. Subject of the complaint
I am filing a complaint regarding the processing of my personal data by the website kv.ee.
2. Circumstances
I visited the website kv.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 portal has the OneTrust consent management platform and Google Consent Mode installed, defaulting to denied storage. Nevertheless, third-party advertising requests go out before the banner appears. The Adform pixel (track.adform.net, bn=90091642, 1x1inv=1) fires at +821 ms and receives a gif response at +960 ms; the Google DoubleClick ad creative (s0.2mdn.net) loads at +866 ms. The CMP script itself (cdn.cookielaw.org) is not fetched until +1718 ms — that is, after the advertising requests have already taken place. Across the entire session (10 pages, 1469 requests) consent was never given: the OneTrust events record only 'Preference Center Opened From Banner' and 'Preferences Close Button', there is no Accept/Reject choice, and the consent state across all 46 analytics pings stays gcs=G100. The Adform request meanwhile carries unpopulated consent macros gdpr=${GDPR} and gdpr_consent=${GDPR_CONSENT_50}: the platform exists, but this advertising beacon is not conditioned on it and fires unconditionally as the page is parsed.
2) The binding AllePal data-protection terms, in the section 'Isikuandmete edastamine ja volitatud töötlejad', state plainly: 'Me ei edasta isikuandmeid kolmandatele isikutele' (we do not transfer personal data to third parties, except where a legal basis exists) and 'me ei edasta isikuandmeid Euroopa Liidust väljapoole' (we do not transfer data outside the European Union). The wording is confirmed on the live site (kv.ee/info/151). In fact GA4 and DoubleClick transmit the IP address and browsing data to Google — a recipient in the United States. Neither Google, nor Adform, nor OneTrust is named in the terms themselves; the list of processors is reduced to categories ('accounting, IT solutions and others'). At the same time the same operator's own cookie declaration (the 'Küpsised' page) and the IAB TCF banner disclose data-sharing with 240–264 advertising partners and name Google, Adform, DoubleClick and Facebook explicitly. The operator's two documents contradict each other: one denies transfers to third parties and outside the EU, the other describes an advertising stack of more than 240 partners.
3) In the terms' summary table, the row 'Veebilehe kasutamise võimaldamine (kuulutuste vaatamine, brausimine) — Küpsised' is assigned to the basis IKÜM artikkel 6 (1) (b) — performance of a contract. Consent (6(1)(a)) in the document is tied only to newsletters. Meanwhile the OneTrust consent platform treats advertising (Sihipärased) and statistics (Jõudlusküpsised) cookies as consent-based. Placing analytics and advertising cookies under 'contractual necessity' diverges both from the site's actual architecture and from the operator's own consent panel.
Full technical documentation is published at: https://gdpru.eu/en/audits/ee-kv-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)) — tracking before consent; GDPR Art. 5(1)(a) / Art. 13(1)(e) — transparency and recipients, a contradiction within the operator's own documents; GDPR Art. 6(1)(b) — basing cookies on performance of a contract
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 kv.ee.
2. Asjaolud
Külastasin veebisaiti kv.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) Portaalis on OneTrusti nõusoleku haldamise platvorm ja Google'i nõusoleku režiim, mis vaikimisi keelab salvestamise. Kolmandate osapoolte reklaamikaebused lahkuvad aga enne bänneri ilmumist. Adformi piksel (rada adform.net, bn=90091642, 1x1inv=1) käivitub +821 ms-s ja saab vastuse-gifi +960 ms-s; Google DoubleClicki reklaamiloov (s0. 2mdn.net) on laaditud +866 ms-s. CMP skript ise (cdn. cookielaw.org) tõmmatakse üles ainult +1718 ms - see tähendab pärast seda, kui aadress on juba toimunud. Kogu seansi jaoks (10 lehekülge, 1469 taotlust) ei antud nõusolekut: OneTrusti sündmustes registreeriti ainult «Preference Center Opened From Banner» ja «Preferences Close Button», aktsepteerimise / tagasilükkamise valikut ei ole ja nõusoleku staatus kõigis 46 analüüsi pingis jääb gcs=G100. Samal ajal kannab Adformi aadress täitmata makrosid gdpr=${GDPR} ja gdpr consent=${GDPR CONSENT 50}: platvorm on olemas, kuid see reklaamimajakas ei ole põhjustatud sellest ja kaob lehe parsimisel tingimusteta.
2) AllePal’i siduvad andmekaitsetingimused jaotises «Isikuandmete edastamine ja volitatud töötlejad» sätestavad selgesõnaliselt: «Me ei edasta isikuandmeid kolmandatele isikutele» (andmeid ei edastata kolmandatele isikutele, kui selleks puudub õiguslik alus) ja «me ei edasta isikuandmeid Euroopa Liidust väljapoole» (andmeid ei edastata väljapoole ELi). Sõnastus on kinnitatud otse veebisaidil (kv.ee/info/151). Tegelikult edastavad GA4 ja DoubleClick IP-aadressi ja sirvivad andmeid USA-s asuvale vastuvõtjale. Google'it, Adformi ega OneTrusti ei nimetata terminites ise; protsessorite loend on vähendatud kategooriatesse („raamatupidamine, IT-lahendused jne). Samal ajal avalikustavad operaatori enda küpsisedeklaratsioon («Küpsised» lehekülg) ja IAB TCF bänner andmevahetuse 240-264 reklaamipartneriga ning nende nimed on Google, Adform, DoubleClick, Facebook. Kaks dokumenti on omavahel vastuolus: üks eitab üleandmist kolmandatele isikutele ja väljaspool ELi, teine kirjeldab enam kui 240 partneri reklaami.
3) Tingimuste koondtabelis viidatakse reale "Veebilehe kasutamise soodustamine (kuulutuste vaatamine, brausimine) - Küpsised" IKÜMi artikli 6 lõike 1 punkti b alusel - lepingu täitmine. Dokumendis olev nõusolek (6(1)(a)) on seotud ainult uudiskirjadega. Nõusolekuplatvorm OneTrust käsitleb reklaami (Sihimoodid) ja statistilisi (Jõudlusküpsised) küpsiseid nõusolekupõhistena. Analüütiliste ja reklaamiküpsiste paigutamine "lepingulise vajaduse" alla erineb nii saidi tegelikust arhitektuurist kui ka selle enda nõusoleku paneelist.
Täielik tehniline dokumentatsioon on avaldatud aadressil: https://gdpru.eu/en/audits/ee-kv-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) – jälgimine enne nõusoleku saamist; GDPR artikli 5 lõike 1 punkt a/artikli 13 lõike 1 punkt e – läbipaistvus ja saajad, vastuolud operaatori dokumentides; GDPR artikli 6 lõike 1 punkt b – küpsiste põhjendamine lepingu täitmisega
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]