By · Last updated 2026-06-05

Rudi kwa BlogGDPR & Ufuatiliaji

DSB Austria: Schrems na Uhamishaji wa Data

DSB ya Austria ni DPA ya nyumbani ya NOYB (malalamiko 422 yalishughulikiwa 2022-2024). Uamuzi wa Google Analytics, hatari ya Schrems III, na asilimia 78 ya kesi za DSB zinazolenga uhamishaji wa mipakani.

June 5, 20268 dakika kusoma
Austria DSBNOYBSchremsGDPR data transfersEU-US privacy

DSB Austria: Schrems na Uhamishaji wa Data

Datenschutzbehörde (DSB) ya Austria ni msimamizi wa nyumbani wa NOYB. NOYB inamaanisha None of Your Business. Max Schrems alianzisha kikundi hicho. Imefungua malalamiko zaidi ya 1,000 ya GDPR tangu 2018. DSB ilishughulikia malalamiko 422 kati ya hayo kati ya 2022 na 2024.

Hiyo ni rekodi muhimu. DSB iko katikati ya vita viwili vya kisheria ambavyo tayari vilibadilisha sheria ya uhamishaji wa EU.

NOYB na DSB: Mfumo

Schrems I (2015): Schrems alifungua malalamiko kuhusu mtiririko wa EU-US wa Facebook. CJEU ilipiga marufuku Safe Harbor. Zaidi ya makampuni 4,000 yalitumia mfumo huo wakati huo.

Schrems II (2020): Changamoto ya pili iliipiga Privacy Shield. Makampuni zaidi ya 5,000 yalitegemea. Kuanguka kwake kukulazimisha mazungumzo mapya. Matokeo yalikuwa EU-US Data Privacy Framework (DPF). DPF ilianza kutumika mwaka 2023.

Schrems III Inayotarajiwa (2025-2026): NOYB imepinga uamuzi wa kutosha wa DPF. Hoja yake: Kifungu cha 702 cha FISA bado kinakinzana na GDPR. Kuelekeza kwa CJEU kunatarajiwa.

Asilimia 78 ya kesi za DSB zinahusiana na uhamishaji wa mipakani au zana za wahusika wengine. Uzingatifu huo unabainisha wasimamizi wa Austria kutoka miili mingine ya EU.

Uamuzi wa DSB wa Google Analytics

Uamuzi wa DSB wa Januari 2022 wa Google Analytics uliweka kiolezo kwa kesi za uhamishaji.

Matokeo matatu makuu yalitoka kwake:

  1. Anwani za IP ni data ya kibinafsi. Hata IP zilizofupishwa zinaweza kuwezesha utambulisho upya ndani ya mifumo ya Google. Rekodi za kikao huzidisha hilo.
  2. Upatikanaji wa muuzaji wa Marekani huhesabika kama uhamishaji. Wahandisi wa Marekani wanapoweza kufikia rekodi za watumiaji wa EU, upatikanaji huo ni uhamishaji chini ya GDPR. Hii inajumuisha usaidizi, matengenezo, na amri za kisheria.
  3. SCCs bila TIA hazitoshi. Vipengele vya Kimkataba Bora vinahitaji Tathmini ya Athari ya Uhamishaji. TIA lazima ionyeshe kwamba sheria za upelelezi za Marekani haziuui ulinzi wa SCC.

DSB iligundua kwamba msimamizi wa tovuti wa Austria ndiye aliyebeba dhamana — si Google. Msimamizi ndiye aliyekuwa kidhibiti. Hii inatumika kwa kila biashara ya EU inayoingiza hati za maudhui za wahusika wengine. Angalia mwongozo wetu wa utiifu wa GDPR kwa wajibu wa kidhibiti.

Hatua za Ziada za Kiufundi

Baada ya Schrems II, EDPB ilichapisha mwongozo wa hatua za ziada za kiufundi. Zinatumika SCCs zinaposhindwa peke yake. DSB inatekeleza mwongozo huu.

Mbinu tatu zinapita ukaguzi wa DSB:

Usimbaji fiche wenye funguo za EU. Simba fiche rekodi kabla hazijaondoka EU. Weka funguo za usimbuaji mikononi mwa EU. Mamlaka ya Marekani yakimshawishi muuzaji kukabidhi faili, wataapata maandishi ya usimbuaji ambayo hawawezi kusoma.

Pseudonymization kabla ya uhamishaji. Tuma tu alama za pseudonymous mipakani. Weka funguo ya utambulisho upya ndani ya EU. Faili zilizohamishiwa hazibeba data yoyote ya moja kwa moja ya kibinafsi.

Uchakataji wa ndani. Endesha uchakataji wote kwenye seva zilizopangishwa na EU. Hamisha tu takwimu za jumla, zisizo na utambulisho kweli kweli. Hakuna rekodi za kibinafsi zinazovuka mipaka.

DSB imethibitisha msimamo huu. Vikundi vinavyotumia wachuuzi wa SaaS wa Marekani kwa data ya kibinafsi ya EU lazima vitumie angalau moja ya mbinu hizi. Au lazima vithibitishe kwamba maudhui yaliyohamishwa yana anonymization ya kweli.

Hatari ya Schrems III

Makampuni yanayotegemea DPF peke yake yanakabiliwa na hatari iliyo wazi. Changamoto ya CJEU ya NOYB ikifaulu, makampuni hayo lazima yatafute zana mpya za uhamishaji haraka. Hiyo ni hasa kilichotokea mwaka 2015 na 2020.

Vikundi vinavyotumia hatua za ziada za kiufundi vinalindwa. Ikiwa maudhui yana anonymization ya kweli, hakuna uhamishaji wa GDPR unaotokea. Kuanguka kwa DPF hakubadilishi chochote kwao.

Kwa shughuli za Austria: zana za uchanganuzi (Google Analytics, Mixpanel, Amplitude) zote zinaunda mfiduo wa DSB. Vivyo hivyo mifumo ya CRM yenye makampuni mama ya Marekani (Salesforce, HubSpot). Majukwaa ya wingu ambapo wafanyakazi wa Marekani wana upatikanaji wa msimamizi yanabeba hatari sawa.

Suluhisho ni sawa katika kila kesi. Hakikisha rekodi za kibinafsi zina anonymization ya kweli kabla hazijafika kwa muuzaji. Au simba fiche kwa funguo ambazo kidhibiti cha EU tu kinamiliki. Muhtasari wetu wa usalama na utiifu unaelezea jinsi muundo wa zero-knowledge unavyoondoa tatizo la uhamishaji chanzo chake.

Vyanzo

Tayari kulinda data yako?

Anza kuanonymisha PII na aina 285+ za vitu katika lugha 48.

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.