By · Last updated 2026-05-08

Rudi kwa BlogGDPR & Ufuatiliaji

Kutokujulikana dhidi ya Uficho wa Majina: Euro Milioni 20 Ziko Hatarini

GDPR inashughulikia data iliyotokujulikana na iliyofichwa majina kwa njia tofauti kabisa. Kutokujulikana kweli kunaondoa wigo wa GDPR kabisa. Uficho wa majina unashikilia wigo wa GDPR.

May 8, 20268 dakika kusoma
GDPR anonymization pseudonymizationArticle 4 recital 26personal data scope20 million EUR fineanonymization compliance determination

Kutokujulikana dhidi ya Uficho wa Majina: Euro Milioni 20 Ziko Hatarini

Kifungu cha 83 kinaweka faini za juu zaidi kwa euro milioni 20 au asilimia 4 ya mapato ya kila mwaka duniani. Swali moja la kisheria linasababisha hatari hiyo: je, sheria inatumika kwa seti yako ya data?

Kutokujulikana kunaondoa wigo. Uficho wa majina hauondoi. Pengo hilo ni kubwa.

Ufafanuzi Wote Wawili kwa Lugha Rahisi

Kirefu cha 26 kinaweka kiwango cha kutokujulikana. Mtu lazima "asitambulike au asitambulike tena." Kipimo ni kipana. Kinashughulikia kila njia "inayoweza kutumika kwa uwezekano mkubwa." Hiyo inajumuisha mdhibiti. Pia inashughulikia msambazaji yeyote na mtu mwingine yeyote wa tatu.

Kifungu cha 4(5) kinaelezea uficho wa majina. Rekodi zimefichwa majina pale ufunguo unaweza kuzigeuza. Ondoa ufunguo, bado una data. Data hiyo ya ziada lazima ibaki tofauti. Si kutokujulikana.

Rekodi zilizofichwa majina bado ni rekodi za kibinafsi. Sheria inatumika kikamilifu. Hakuna exemption ya wigo. Kabisa.

Gharama ya Lebo Isiyo Sahihi

Kushughulikia seti ya data iliyofichwa majina kama isiyo na utambulisho kunasababisha matatizo matano mara moja:

  • Ingizo zisizo sahihi za ROPA chini ya Kifungu cha 30
  • Hakuna mchakato wa haki za mada kwa ufikiaji, kufutwa, au uhamishaji
  • Hakuna ratiba ya kuhifadhi - kizuizi cha ufutaji hakipo
  • Hakuna dhamana za uhamisho kwa kazi za mpaka-mstari
  • Hakuna njia ya kufuta kwa maombi ya haki ya kufutwa

Kila pengo ni ukiukaji tofauti. Yote matano yanaweza kukaa katika mstari mmoja.

Ishara ya Utekelezaji ya 2025

Mnamo 2025, EDPB ilifanya zoezi la pamoja la utekelezaji. Ripoti ilieleza kushindwa mara kwa mara: "mbinu zisizo na ufanisi za kutokujulikana zinazotumika kama mbadala wa kufutwa." DPAs sasa zinakagua ubora wa kutokujulikana. Zinachunguza zaidi ya kama hatua ipo. Hatua lazima ifanye kazi.

Seti ya data iliyotokenizwa na jedwali la utafutaji imefichwa majina. Si isiyo na utambulisho. Ina ufunguo. Ufunguo unaweza kuigeuza. Kuiita isiyo na utambulisho ni hasa kushindwa ambako ripoti ya 2025 inalenga.

Kuchagua Njia Sahihi

Kutokujulikana kweli - nje ya wigo. Tumia Futa. PII imeenda bila kiungo cha nyuma. Unaweza pia Hesabu maadili ya entropy ya juu bila njia ya picha ya awali. Rekodi msingi. Hakuna wajibu wa kisheria unaoshikamana na matokeo.

Uficho wa majina - ndani ya wigo. Tumia Badilisha, Ficha, au Simba. Sheria inatumika kikamilifu. Uficho wa majina unapunguza madhara kutoka kwa uvunjaji. Hauondoi wajibu wa kisheria.

Ugeuzaji unaodhibitiwa - utafiti au ukaguzi. Tumia Simba na funguo zinazoshikiliwa na mteja. Ulinzi wa ufunguo lazima ukidhi sheria za utengano wa ufunguo za EDPB 05/2022. Kumbuka uwanja katika DPIA.

Mfano Halisi wa Matumizi

Kampuni inauza rekodi za "zisizo na utambulisho" za wateja kwa watafiti. Wanaomba njia ya Futa. PII imeenda. Hakuna jedwali la tokeni. Hakuna picha ya awali ya uhesabu. Utambuzi upya hauna njia.

DPO anaandika hili katika DPIA. Njia iliyotumika. Aina za utambulisho. Kwa nini haiwezi kugeuzwa. Kiwango cha hatari iliyobaki. Matokeo yanaanguka nje ya wigo. Haki za mada na sheria za uhamisho hazitumiki kwa nakala za utafiti.

Njia inalingana na dai. Hiyo ndiyo mchakato sahihi. Unashikilia katika ukaguzi.

Kwa Nini Rekodi Ina Umuhimu

Kampuni haiwezi kudai tu kutokujulikana. Dai lazima liwe na rekodi. DPIA lazima ionyeshe mambo manne. Ni vitambulisho vipi vilivyoshughulikiwa. Ni njia gani iliyotumika. Kwa nini utambuzi upya hauna njia. Ni kiwango gani cha hatari iliyobaki.

Bila rekodi hiyo, ukaguzi unashughulikia seti ya data kama iko ndani ya wigo. Seti kamili ya wajibu inatumika. Ingizo la ROPA lazima liwepo. Dhamana za uhamisho lazima ziwepo. Njia ya kufuta lazima iwepo. Hakuna wajibu unaoondoka bila ushahidi.

Kwa jinsi haki za kufuta zinavyoingiliana na rekodi zilizotokujulikana, angalia haki ya GDPR ya kufutwa na mwongozo wa EDPB 2025. Kwa sheria za uhamisho pale kushiriki rekodi mpaka mstari, angalia utiifu wa uhamisho wa data na faini ya TikTok.

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.