The website of the MyBee long-term car rental service — one page, 393 requests. A Cookiebot banner with a 'Keeldu' button on the first screen, and Google obeys it. The Meta pixel does not: 16 events before any choice and 15 after refusal. In parallel, events go to a server-side Meta Conversions API gateway on Amazon in the US, and the Eskimi advertising platform opens a tracking session in the third second. Neither Meta, nor Eskimi, nor the US gateway is named in the privacy policy.
Request timeline
Declared versus actual
Transfer timings
Eskimi tracking session, tracker 36684.
First Meta pixel event.
Server-side Meta Conversions API gateway in the US.
logconsent, action=decline.
An event to the Conversions API gateway after refusal.
The fifteenth Meta pixel event after refusal.
Detected trackers
- Meta Pixel (997635436272572) — connect.facebook.net, www.facebook.com/tr; 16 events before any choice and 15 after a recorded refusal
- Server-side Meta Conversions API gateway on AWS (d3-…ecs.us-east-1.on.aws, capi-automation.s3.us-east-2.amazonaws.com) — events before any choice and after refusal
- Eskimi DSP (dsp-media.eskimi.com, dsp-trk.eskimi.com, dsp-ap.eskimi.com, tracker 36684) — advertising platform; a session at +2.9 s before any choice
- Google Analytics 4 (G-ZFZP3WGBQG) and Google Ads AW-10959715733 — gcs=G100; after refusal, the mode records the denial. The denial is respected
- Google Maps, Sentry (sentry.nordcode.io), Cookiebot
- First party: mybee.ee, api.mybee.lt, images.mybee.lt
Indicators of GDPR non-compliance
- ePrivacy — Directive 2002/58/EC, Art. 5(3) (in conjunction with GDPR Art. 6(1)(a)) — the Meta pixel, the Conversions API gateway, and Eskimi before any choiceThe Cookiebot banner offers 'Keeldu' on the first screen, and Google obeys it: every request carries gcs=G100. The other advertising services do not. At +2.9 s, the Eskimi advertising platform opens a tracking session (tracker 36684) with the page address. At +3.4 s, the Meta pixel (997635436272572) sends its first event. At the same time, an event goes to a server-side Meta Conversions API gateway hosted on Amazon Web Services in the us-east-1 region, i.e. in the United States. Before the visitor decides, the Meta pixel manages to send 16 events. Cookiebot's own declaration classifies _fbp as a marketing cookie.
- ePrivacy — Directive 2002/58/EC, Art. 5(3) (in conjunction with GDPR Art. 6(1)(a)) — the Meta pixel and the Conversions API gateway after refusalAt +149.1 s, the visitor presses 'Keeldu', and Cookiebot records the refusal (action=decline). Google switches to a denial updated by the visitor's decision. The Meta pixel does not notice the refusal: by the end of the capture, it sends 15 more events. At +155.3 s, an event again goes to the Conversions API gateway on AWS. The server-side channel is especially significant: it transmits Meta events bypassing the browser, and a blocker on the visitor's side cannot stop it.
- GDPR Art. 13(1)(e), 13(1)(f) / Art. 5(1)(a) — Meta, Eskimi, and the US gateway are not named in the policyMyBee Estonia OÜ's privacy policy lists recipients by section — the Modus Mobility group, CityBee Solutions, Twilio Sendgrid, and others — and, among transfers to the US, names only Sendgrid. Meta, Eskimi, and the server-side Conversions API gateway on AWS in the US are not mentioned in the policy. Meta and the eskimi.com domain appear only in the Cookiebot cookie declaration. The visitor has no way of learning about the server-side transmission of events to the US.
Context
mybee.ee is the website of the MyBee long-term car rental service in Estonia. The controller is MyBee Estonia OÜ, part of the Modus Mobility group, which also includes CityBee. The site is a single-page application, with data loaded from the group’s Lithuanian servers api.mybee.lt and images.mybee.lt. Consent is managed by Cookiebot.
The measurement is a single load of the homepage with navigation inside the application. In total, 393 requests. Processing is described by the MyBee Estonia privacy policy and the Cookiebot declaration.
Who receives data directly
Meta — through the pixel in the browser and through a server-side gateway on Amazon Web Services in the US. Eskimi — advertising platform. Google — Analytics and Ads in denied mode, Maps. Sentry — error monitoring.
Declared versus actual
The banner is set up correctly: “Keeldu” on the first screen, categories switched off, and the refusal is recorded. Google complies: before the decision, every request carries a denial, and after refusal, the denial is updated by the visitor’s decision. The discrepancies lie in the rest of the advertising stack.
First — Meta and Eskimi run before any choice. In the third second, Eskimi opens a tracking session with the page address. Next, the Meta pixel sends its first event, and in parallel an event goes to the server-side Meta Conversions API gateway. While the visitor reads the banner, the pixel sends 16 events.
Second — after refusal, Meta carries on, including via the server. The refusal is recorded at +149.1 s. After that, the pixel sends 15 more events, and at +155.3 s an event again goes to the Conversions API gateway. The server-side gateway deserves special mention: it is hosted on Amazon Web Services in the us-east-1 region and transmits Meta events bypassing the browser. The visitor’s blocker cannot see it, and only the site itself can stop it.
Third — the policy says nothing about this. The MyBee policy lists in detail the recipients within the group and the Sendgrid mailing service, with a transfer to the US. Meta, Eskimi, and the server-side gateway in the US are not mentioned. Meta and the Eskimi domain appear only in the technical cookie declaration. The visitor will learn nowhere about the server-side channel to the US.
Consent: what is proven and what is not
Proven: Meta, the Conversions API gateway, and Eskimi run before any choice. Eskimi at +2.9 s, the Meta pixel and the gateway at +3.4 s, and 16 pixel events before the decision is recorded.
Proven: a refusal took place. The Cookiebot log records action=decline at +149.1 s.
Proven: the Meta pixel and the gateway run after refusal. 15 pixel events and an event to the gateway at +155.3 s.
Proven: Google respects the denial. Every request carries gcs=G100, and after refusal, a denial updated by the decision.
Not established: the content of the Meta and gateway events. They were sent via POST, and the bodies were removed during cleaning. The gateway was identified by the Meta Conversions API script loaded from capi-automation.s3.us-east-2.amazonaws.com and by the address of the event endpoint.
Boundaries of this observation
The measurement covers the site’s homepage. Registration, the account area, and rental checkout were not examined. The observation records browser behavior, not server-side processing. The file has been published cleaned: Cookie headers and POST request bodies were removed.
Legal assessment falls to the competent authority — the Andmekaitse Inspektsioon.
Conclusion
MyBee has installed an exemplary banner and configured Google correctly, but the Meta pixel and the Eskimi advertising platform do not listen to it. Meta receives events before any choice and after refusal, not only through the browser but also through a server-side gateway in the US that no blocker can stop. Neither Meta, nor Eskimi, nor this gateway is named in the privacy policy.
Remedy: bring the Meta pixel, the Conversions API gateway, and Eskimi under Cookiebot — do not load them or send events without consent to marketing, and stop sending after refusal, including on the server side; name Meta, Eskimi, and the server-side gateway in the policy, stating the transfer to the US and its legal basis.
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.
6b769c21256975e69a9b712ff9a1f3d0705b6ece82e57902a4ceed865bed53c7
Want 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) — mybee.ee Кому: [укажите адрес компании — DPO / поддержка / юридический отдел] От: [Ваше имя], [контактный email] Прошу предоставить доступ к моим персональным данным, обрабатываемым в связи с использованием сайта mybee.ee. 1. Категории данных и цели обработки (ст. 15(1)(a)-(c)) На основании независимого технического анализа сайта прошу подтвердить и подробно раскрыть следующие категории обработки: 1) Баннер Cookiebot предлагает «Keeldu» на первом экране, и Google его слушается: все обращения идут с gcs=G100. Остальные рекламные сервисы — нет. На +2,9 с рекламная платформа Eskimi открывает сеанс отслеживания (трекер 36684) с адресом страницы. На +3,4 с пиксель Meta (997635436272572) отправляет первое событие. Одновременно событие уходит на серверный шлюз Meta Conversions API, размещённый в Amazon Web Services в регионе us-east-1, то есть в США. До решения посетителя пиксель Meta успевает отправить 16 событий. Собственная декларация Cookiebot относит _fbp к маркетинговым cookie. 2) На +149,1 с посетитель нажимает «Keeldu», и Cookiebot записывает отказ (action=decline). Google переключается на запрет, обновлённый решением посетителя. Пиксель Meta отказа не замечает: до конца записи он отправляет ещё 15 событий. На +155,3 с событие снова уходит на серверный шлюз Conversions API в AWS. Серверный канал особенно важен: он передаёт события Meta в обход браузера, и блокировщик на стороне посетителя его не остановит. 3) Политика конфиденциальности MyBee Estonia OÜ перечисляет получателей по разделам — группу Modus Mobility, CityBee Solutions, Twilio Sendgrid и других — и из передач в США называет только Sendgrid. Meta, Eskimi и серверный шлюз Conversions API в AWS в США в политике не упомянуты. Meta и домен eskimi.com встречаются лишь в декларации cookie Cookiebot. О серверной передаче событий в США посетитель узнать не может ниоткуда. 2. Получатели, сроки хранения и передача за пределы ЕЭЗ (ст. 15(1)(c)-(d), 46) Прошу также указать полный список третьих лиц-получателей, применимые сроки хранения по каждой категории и правовые основания передачи данных за пределы ЕЭЗ, если таковая происходит. Полный технический разбор с доказательствами (сохранённый сетевой журнал, контрольная сумма SHA-256) опубликован по адресу: https://gdpru.eu/en/audits/ee-mybee-ee/ 3. Автоматизированная обработка и профилирование (ст. 15(1)(h)) Прошу сообщить, применяется ли в отношении меня автоматизированное принятие решений или профилирование, и если да — раскрыть логику такой обработки. С уважением, [Ваше имя] [контактный email] [Страна] [Дата]
Subject: Data access request (GDPR Art. 15) — mybee.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 mybee.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 Cookiebot banner offers 'Keeldu' on the first screen, and Google obeys it: every request carries gcs=G100. The other advertising services do not. At +2.9 s, the Eskimi advertising platform opens a tracking session (tracker 36684) with the page address. At +3.4 s, the Meta pixel (997635436272572) sends its first event. At the same time, an event goes to a server-side Meta Conversions API gateway hosted on Amazon Web Services in the us-east-1 region, i.e. in the United States. Before the visitor decides, the Meta pixel manages to send 16 events. Cookiebot's own declaration classifies _fbp as a marketing cookie. 2) At +149.1 s, the visitor presses 'Keeldu', and Cookiebot records the refusal (action=decline). Google switches to a denial updated by the visitor's decision. The Meta pixel does not notice the refusal: by the end of the capture, it sends 15 more events. At +155.3 s, an event again goes to the Conversions API gateway on AWS. The server-side channel is especially significant: it transmits Meta events bypassing the browser, and a blocker on the visitor's side cannot stop it. 3) MyBee Estonia OÜ's privacy policy lists recipients by section — the Modus Mobility group, CityBee Solutions, Twilio Sendgrid, and others — and, among transfers to the US, names only Sendgrid. Meta, Eskimi, and the server-side Conversions API gateway on AWS in the US are not mentioned in the policy. Meta and the eskimi.com domain appear only in the Cookiebot cookie declaration. The visitor has no way of learning about the server-side transmission of events to the US. 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-mybee-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) — mybee.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 mybee.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) Cookiebot'i bänner pakub esimesel ekraanil nuppu „Keeldu“ ja Google arvestab sellega: kõik päringud saadetakse väärtusega gcs=G100. Ülejäänud reklaamiteenused aga mitte. +2,9 s juures avab reklaamiplatvorm Eskimi jälgimisseansi (jälgija 36684) koos lehe aadressiga. +3,4 s juures saadab Meta piksel (997635436272572) esimese sündmuse. Samal ajal saadetakse sündmus Meta Conversions API serveripoolsesse lüüsi, mis asub Amazon Web Servicesis piirkonnas us-east-1 ehk Ameerika Ühendriikides. Enne külastaja otsust jõuab Meta piksel saata 16 sündmust. Cookiebot'i enda deklaratsioon liigitab _fbp turundusküpsiste hulka. 2) +149,1 s juures vajutab külastaja „Keeldu“ ja Cookiebot salvestab keeldumise (action=decline). Google lülitub külastaja otsusega uuendatud keelule. Meta piksel keeldumist ei märka: salvestuse lõpuni saadab see veel 15 sündmust. +155,3 s juures saadetakse sündmus taas AWS-i Conversions API serveripoolsesse lüüsi. Serveripoolne kanal on eriti oluline: see edastab Meta sündmused brauserist mööda ja külastaja poolne blokeerija seda ei peata. 3) MyBee Estonia OÜ privaatsuspoliitika loetleb vastuvõtjad jaotiste kaupa – Modus Mobility kontsern, CityBee Solutions, Twilio Sendgrid ja teised – ning nimetab USA-sse edastamise puhul üksnes Sendgridi. Metat, Eskimit ja AWS-i Conversions API serveripoolset lüüsi USA-s privaatsuspoliitikas ei mainita. Meta ja domeen eskimi.com esinevad üksnes Cookiebot'i küpsiste deklaratsioonis. Sündmuste serveripoolsest edastamisest USA-sse ei saa külastaja kusagilt teada. 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-mybee-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)
Тема: Жалоба на обработку персональных данных — mybee.ee 1. Предмет жалобы Я подаю жалобу в отношении обработки моих персональных данных сайтом mybee.ee. 2. Обстоятельства Я посетил сайт mybee.ee и обнаружил признаки несоответствия обработки моих персональных данных требованиям GDPR. Технический разбор, опубликованный на gdpru.eu 29.09.2026 (открытая методология, воспроизводимые измерения), документирует следующие признаки: 1) Баннер Cookiebot предлагает «Keeldu» на первом экране, и Google его слушается: все обращения идут с gcs=G100. Остальные рекламные сервисы — нет. На +2,9 с рекламная платформа Eskimi открывает сеанс отслеживания (трекер 36684) с адресом страницы. На +3,4 с пиксель Meta (997635436272572) отправляет первое событие. Одновременно событие уходит на серверный шлюз Meta Conversions API, размещённый в Amazon Web Services в регионе us-east-1, то есть в США. До решения посетителя пиксель Meta успевает отправить 16 событий. Собственная декларация Cookiebot относит _fbp к маркетинговым cookie. 2) На +149,1 с посетитель нажимает «Keeldu», и Cookiebot записывает отказ (action=decline). Google переключается на запрет, обновлённый решением посетителя. Пиксель Meta отказа не замечает: до конца записи он отправляет ещё 15 событий. На +155,3 с событие снова уходит на серверный шлюз Conversions API в AWS. Серверный канал особенно важен: он передаёт события Meta в обход браузера, и блокировщик на стороне посетителя его не остановит. 3) Политика конфиденциальности MyBee Estonia OÜ перечисляет получателей по разделам — группу Modus Mobility, CityBee Solutions, Twilio Sendgrid и других — и из передач в США называет только Sendgrid. Meta, Eskimi и серверный шлюз Conversions API в AWS в США в политике не упомянуты. Meta и домен eskimi.com встречаются лишь в декларации cookie Cookiebot. О серверной передаче событий в США посетитель узнать не может ниоткуда. Полная техническая документация опубликована по адресу: https://gdpru.eu/en/audits/ee-mybee-ee/ 3. Положения GDPR, соблюдение которых прошу проверить ePrivacy — Директива 2002/58/EC, ст. 5(3) (в связке с GDPR Art. 6(1)(a)) — пиксель Meta, шлюз Conversions API и Eskimi до выбора; ePrivacy — Директива 2002/58/EC, ст. 5(3) (в связке с GDPR Art. 6(1)(a)) — пиксель Meta и шлюз Conversions API после отказа; GDPR Art. 13(1)(e), 13(1)(f) / Art. 5(1)(a) — Meta, Eskimi и шлюз в США не названы в политике 4. Требование Прошу проверить изложенные обстоятельства и, если несоответствие подтвердится, принять меры, предусмотренные статьёй 58(2) GDPR. 5. Приложения Полная доказательная база — HAR-файл, контрольная сумма SHA-256 и цитата из политики конфиденциальности сайта, документирующая указанное противоречие — опубликована и проверяема по ссылке в пункте 2 выше. С уважением, [Ваше имя] [контактный email] [Страна] [Дата]
Subject: Complaint regarding personal data processing — mybee.ee 1. Subject of the complaint I am filing a complaint regarding the processing of my personal data by the website mybee.ee. 2. Circumstances I visited the website mybee.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 29 September 2026 (open methodology, reproducible measurements) documents the following indications: 1) The Cookiebot banner offers 'Keeldu' on the first screen, and Google obeys it: every request carries gcs=G100. The other advertising services do not. At +2.9 s, the Eskimi advertising platform opens a tracking session (tracker 36684) with the page address. At +3.4 s, the Meta pixel (997635436272572) sends its first event. At the same time, an event goes to a server-side Meta Conversions API gateway hosted on Amazon Web Services in the us-east-1 region, i.e. in the United States. Before the visitor decides, the Meta pixel manages to send 16 events. Cookiebot's own declaration classifies _fbp as a marketing cookie. 2) At +149.1 s, the visitor presses 'Keeldu', and Cookiebot records the refusal (action=decline). Google switches to a denial updated by the visitor's decision. The Meta pixel does not notice the refusal: by the end of the capture, it sends 15 more events. At +155.3 s, an event again goes to the Conversions API gateway on AWS. The server-side channel is especially significant: it transmits Meta events bypassing the browser, and a blocker on the visitor's side cannot stop it. 3) MyBee Estonia OÜ's privacy policy lists recipients by section — the Modus Mobility group, CityBee Solutions, Twilio Sendgrid, and others — and, among transfers to the US, names only Sendgrid. Meta, Eskimi, and the server-side Conversions API gateway on AWS in the US are not mentioned in the policy. Meta and the eskimi.com domain appear only in the Cookiebot cookie declaration. The visitor has no way of learning about the server-side transmission of events to the US. Full technical documentation is published at: https://gdpru.eu/en/audits/ee-mybee-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)) — the Meta pixel, the Conversions API gateway, and Eskimi before any choice; ePrivacy — Directive 2002/58/EC, Art. 5(3) (in conjunction with GDPR Art. 6(1)(a)) — the Meta pixel and the Conversions API gateway after refusal; GDPR Art. 13(1)(e), 13(1)(f) / Art. 5(1)(a) — Meta, Eskimi, and the US gateway are not named in the policy 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 mybee.ee. 2. Asjaolud Külastasin veebisaiti mybee.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 29.09.2026 (avatud metoodika, korratavad mõõtmised), dokumenteerib järgmist: 1) Cookiebot'i bänner pakub esimesel ekraanil nuppu „Keeldu“ ja Google arvestab sellega: kõik päringud saadetakse väärtusega gcs=G100. Ülejäänud reklaamiteenused aga mitte. +2,9 s juures avab reklaamiplatvorm Eskimi jälgimisseansi (jälgija 36684) koos lehe aadressiga. +3,4 s juures saadab Meta piksel (997635436272572) esimese sündmuse. Samal ajal saadetakse sündmus Meta Conversions API serveripoolsesse lüüsi, mis asub Amazon Web Servicesis piirkonnas us-east-1 ehk Ameerika Ühendriikides. Enne külastaja otsust jõuab Meta piksel saata 16 sündmust. Cookiebot'i enda deklaratsioon liigitab _fbp turundusküpsiste hulka. 2) +149,1 s juures vajutab külastaja „Keeldu“ ja Cookiebot salvestab keeldumise (action=decline). Google lülitub külastaja otsusega uuendatud keelule. Meta piksel keeldumist ei märka: salvestuse lõpuni saadab see veel 15 sündmust. +155,3 s juures saadetakse sündmus taas AWS-i Conversions API serveripoolsesse lüüsi. Serveripoolne kanal on eriti oluline: see edastab Meta sündmused brauserist mööda ja külastaja poolne blokeerija seda ei peata. 3) MyBee Estonia OÜ privaatsuspoliitika loetleb vastuvõtjad jaotiste kaupa – Modus Mobility kontsern, CityBee Solutions, Twilio Sendgrid ja teised – ning nimetab USA-sse edastamise puhul üksnes Sendgridi. Metat, Eskimit ja AWS-i Conversions API serveripoolset lüüsi USA-s privaatsuspoliitikas ei mainita. Meta ja domeen eskimi.com esinevad üksnes Cookiebot'i küpsiste deklaratsioonis. Sündmuste serveripoolsest edastamisest USA-sse ei saa külastaja kusagilt teada. Täielik tehniline dokumentatsioon on avaldatud aadressil: https://gdpru.eu/en/audits/ee-mybee-ee/ 3. Sätted, mille järgimist palun kontrollida Eraelu puutumatust ja elektroonilist sidet käsitlev direktiiv 2002/58/EÜ art 5 lg 3 (koostoimes IKÜM art 6 lg 1 p-ga a) — Meta piksel, Conversions API lüüs ja Eskimi enne valikut; Eraelu puutumatust ja elektroonilist sidet käsitlev direktiiv 2002/58/EÜ art 5 lg 3 (koostoimes IKÜM art 6 lg 1 p-ga a) — Meta piksel ja Conversions API lüüs pärast keeldumist; IKÜM art 13 lg 1 p e ja f / art 5 lg 1 p a — Meta, Eskimi ja USA-s asuv lüüs ei ole privaatsuspoliitikas nimetatud 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]