By · Last updated 2026-06-05

Späť na blogGDPR a Dodržiavanie

DSB Rakusko: Schrems a prenosy dat

Rakuske DSB je domacim dozorovym organom NOYB (422 saznosti vybavenych v rokoch 2022-2024). Rozhodnutie o Google Analytics, riziko Schrems III a 78 % pripadov DSB zamerane na prenosy.

June 5, 20268 min čítania
Austria DSBNOYBSchremsGDPR data transfersEU-US privacy

DSB Rakusko: Schrems a prenosy dat

Rakusky Datenschutzbehorde (DSB) je domacim regulatorom organizacie NOYB. NOYB znamena None of Your Business. Skupinu zalozil Max Schrems. Od roku 2018 podala viac ako 1 000 staznosti v ramci GDPR. DSB vybavil 422 z tychto pripadov v rokoch 2022 az 2024.

Tento vysledok je dolezity. DSB stoji v centre dvoch pravnych bojov, ktore uz pretvorili europske pravo v oblasti prenosov dat.

NOYB a DSB: vzorec konania

Schrems I (2015): Schrems podal staznost tykajucu sa tokov dat medzi EÚ a USA v ramci Facebooku. Sudny dvor EU zrusil Safe Harbor. V tomto ramci vtedy fungovalo viac ako 4 000 spolocnosti.

Schrems II (2020): Druha vyzva zasiahla Privacy Shield. Na neho sa spolahalo viac ako 5 000 spolocnosti. Jeho zanik prinutil k novym rokovaniam. Vysledkom bol Ramec ochrany osobnych udajov EÚ-USA (DPF). DPF vstupil do platnosti v roku 2023.

Ocakavany Schrems III (2025-2026): NOYB napadol rozhodnutie o primeranosti DPF. Argument: FISA Section 702 je stale v rozpore s GDPR. Ocakava sa postoupenie na SDEU.

78 % pripadov DSB sa tyka cezhranicnych prenosov alebo nastrojov tretich stran. Toto zameranie odlisuje rakuskych regulatorov od inych organov v EU.

Rozhodnutie DSB o Google Analytics

Rozhodnutie DSB o Google Analytics z januara 2022 nastavilo vzor pre transferove pripady.

Vyplynuli z neho tri klucove zistenia:

  1. IP adresy su osobne udaje. Dokonca aj skratene IP adresy mozu umoznit re-identifikaciu v systemoch Google. Zaznamy o relacii situaciu zhorsuju.
  2. Pristup poskytovatelom v USA sa povazuje za prenos. Ked americti inzinieri maju pristup k zaznamom pouzivatelov z EU, tento pristup je prenosom podla GDPR. Vzatahuje sa to na podporu, udrzbu aj pravne prikazy.
  3. SCC bez TIA nestacia. Standardne zmluvne dolohy potrebuju posudenie vplyvu prenosu. TIA musi preukaza, ze americke spionazne zakony nezrusuju ochranu poskytovanu SCC.

DSB uznal zodpovednym rakuskeho prevadzkovatela stranky -- nie Google. Prevadzkovatel bol spravcom. To plati pre kazdy podnik v EU, ktory vklada skripty tretich stran. Pozri nasu prirucku pre suplad s GDPR pre povinnosti spravcu.

Doplnkove technicke opatrenia

Po Schrems II vydala EDPB usmernenie k doplnkovym technickym opatreniam. Tieto sa uplatnia, ked SCC samotne nestacia. DSB toto usmernenie presadzuje.

Tri pristupy spriaju kontrolu DSB:

Sifrovanie s klucmi ulozenymi v EU. Zaznamy zasifrovajte este pred odchodom z EU. Desifrovacie kluce ponechajte v rukach EU. Ak americke organy prikazu predajcovi odovzdat subory, dostanu sifrovany text, ktory nevedia precitat.

Pseudonymizacia pred prenosom. Posielajte cez hranice len pseudonymne tokeny. Kluc pre re-identifikaciu uchovávaite v EU. Prenesene subory neobsahuju ziadne priame osobne udaje.

Lokalne spracovanie. Celé spracovanie vykonavajte na serveroch v EU. Cezhraniczne prenasajte iba agregované, skutocne anonymne statistiky. Ziadne osobne zaznamy neprekrocuju hranice.

DSB toto stanovisko potvrdil. Skupiny pouzivajuce americke SaaS nastroje pre osobne udaje EU musia uplatnit najmenej jedno z tychto opatreni. Alebo musia preukaza, ze preneseny obsah je skutocne anonymny.

Riziko Schrems III

Spolocnosti, ktore sa spolahaju iba na DPF, celja zretelnemu riziku. Ak bude vyzva NOYB na SDEU uspesna, budu musiet rychlo najst nove nastroje na prenos. Presne to sa stalo v rokoch 2015 a 2020.

Skupiny pouzivajuce doplnkove technicke opatrenia su chranene. Ak je obsah skutocne anonymny, nevznikne ziadny prenos podla GDPR. Zrútenie DPF pre ne nic nemeni.

Pre rakuske prevadzky: analytické nastroje (Google Analytics, Mixpanel, Amplitude) vytvaraju expozíciu voci DSB. Takisto systemy CRM s americkymi matermi spolocnostami (Salesforce, HubSpot). Cloudove platformy, kde maju americti zamestnanci administratorsky pristup, nesú rovnake riziko.

Riesenie je vo vsetkych pripadoch rovnake. Pred odovzdanim zaznamov poskytovatelovi sa uistite, ze osobne zaznamy su skutocne anonymne. Alebo ich zasifrovajte klucmi, ktore ma vyhradne k dispozicii controller v EU. Nase prehladne informacie o bezpecnosti a sulade s predpismi vysvetluju, ako design zero-knowledge odstranuuje problem prenosu pri zdroji.

Zdroje

Pripravení chrániť vaše údaje?

Začnite anonymizovať PII s 285+ typmi entít v 48 jazykoch.

About this page

We update this page when our platform or the law changes.

Read our founder note for how we work.

Each change shows up in the timestamp at the top.

Related reading

We follow these rules

  • GDPR (EU 2016/679).
  • ISO/IEC 27001:2022.
  • NIS2 (EU 2022/2555).
  • HIPAA safe harbor under 45 CFR § 164.514(b)(2).

Our promise

We do not sell your data.

We do not train models on your text.

We store your files in Germany.

You can delete your account at any time.

You own your work.

Where we run

Our servers live in Falkenstein, Germany.

We use Hetzner. They hold ISO 27001 certification.

All data stays in the EU.

Backups run every day.

Need help?

Email support@anonym.legal.

We reply within one business day.

How we test

We run a full check suite on every release.

Each surface gets its own sweep script and report.

Human reviewers spot-check the output each week.

We track recall and precision on a labelled set.

Bad runs block the deploy.

What we never do

  • We never sell your information to third parties.
  • We never train models on what you upload.
  • We never keep your work after you delete it.
  • We never share keys with any outside firm.
  • We never run ads inside the product.

Plans in plain words

We sell credits, not seats.

One credit covers one short job.

Long jobs use a few credits each.

You can top up at any time.

Unused credits roll over each month.

Read the plans page for current rates.

Who built this

A small team of engineers and lawyers built this.

We ship from Europe and work in the open.

Our founder note spells out why we started.

Where to start

How the parts fit

A browser add-on cleans text inside Chrome.

A Word plug-in handles drafts in Office.

A small desktop tool works on whole folders.

An agent protocol link feeds large models safely.

All four share one core engine and one rule set.

Words from our team

We started this work after a lunch about cookies.

One friend kept getting odd ads on her phone.

We asked why a court file leaked through a draft.

We sketched the first build on a napkin that week.

By month three we had a tiny demo for a friend.

She used it on her first case the next day.

Common questions we hear

Can the tool read scanned PDFs? Yes, with OCR.

Does it work on long files? Yes, in small chunks.

Can I roll my own rule set? Yes, save it as a preset.

Does it run offline? The desktop build runs offline.

Do you keep my files? No, the cloud build wipes after each run.

Will it learn from my work? No, we never train on inputs.

A short tour of the workflow

Upload a file or paste a snippet of prose.

Pick the entities you want gone from the draft.

Choose a method: replace, mask, hash, encrypt, or redact.

Press run and watch the side panel show each hit.

Skim the result and tweak any rule that misfired.

Save the cleaned file or send it to a teammate.