By · Last updated 2026-06-03

Rudi kwa BlogGDPR & Ufuatiliaji

Faragha ya Mifumo Mingi na Zana Moja

Timu za utiifu zinazodhibiti GDPR, HIPAA, na CCPA lazima zitumie viwango tofauti vya kusiriwa kulingana na muktadha wa hati.

June 3, 20267 dakika kusoma
GDPR HIPAA CCPAmulti-framework complianceprivacy regulationcompliance presetsDPO tools

Zana Moja, Mifumo Mitatu

Timu ya faragha inasindika faili za wateja wa EU chini ya GDPR Jumatatu. Rekodi za afya chini ya HIPAA Jumanne. Data ya watumiaji wa California chini ya CCPA Jumatano.

Kila sheria ina kanuni tofauti. Kila hati inahitaji usanidi tofauti.

Kubadilisha kati ya seti tatu za kanuni kila siku kunaunda makosa. Usanidi mbaya kwenye faili mbaya unasababisha kushindwa kwa utiifu au kupoteza data.

Wasifu wa utiifu wenye majina hurekebisha hili. Usanidi mmoja uliohifadhiwa kwa kila sheria. Hakuna usanidi tena kwa mkono.

GDPR - Inashughulikia Nini

GDPR inashughulikia data yote ya kibinafsi. Inatumika kwa mtu yoyote wa EU anayeweza kutambuliwa. Hakuna orodha ya kile kinachohesabiwa. Habari yoyote inayohusiana na mtu iko ndani ya upeo.

Kategoria maalum - data ya afya, imani za kidini, maoni ya kisiasa - zinapata ulinzi wa ziada chini ya Ibara ya 9.

Aina za kawaida za kitengo kwa kazi ya hati: majina, anwani, vitambulisho vya kitaifa, barua pepe, nambari za simu, anwani za IP, kadi za mkopo.

Uamuzi sahihi unategemea muktadha. GDPR haina orodha ya kawaida.

HIPAA - Inashughulikia Nini

HIPAA Safe Harbor inafafanua aina 18 haswa za vitambulisho. Zote 18 lazima ziondolewe kutoka kwa rekodi za afya.

Kanuni mbili zinashangaza timu:

  • Tarehe zinapunguzwa hadi mwaka peke yake. Mwezi na siku zinaondolewa. Mwaka unabaki.
  • Maeneo ya kijiografia madogo kuliko jimbo lazima yaondolewe.

Kanuni hizi zinatumika tu kwa mashirika yanayohusika na washirika wao wa biashara.

CCPA - Inashughulikia Nini

CCPA inashughulikia maelezo ya kibinafsi yanayounganishwa na wakazi wa California. Upeo ni mpana. Unajumuisha vitambulisho vya moja kwa moja, shughuli za mtandao, historia ya ununuzi, data ya mahali, data ya biometric, na makisio ya wasifu.

Kwa kazi ya hati, zingatia vitambulisho vya moja kwa moja: majina, SSN, leseni za udereva, nambari za pasipoti, barua pepe, nambari za akaunti, anwani za IP, vitambulisho vya vifaa.

Historia ya ununuzi na kumbukumbu za kuvinjari mara chache huonekana kama maandishi ya kawaida kwenye hati.

Kwa Nini Kubadilisha kwa Mkono Kunashindwa

Kubadilisha kwa mkono kunaunda makosa. Faili ya GDPR iliyoendeshwa na usanidi wa HIPAA huchukua kanuni za tarehe ambazo GDPR haihitaji. Faili ya HIPAA iliyoendeshwa na usanidi wa GDPR hukosa kanuni za kijiografia ambazo Safe Harbor inahitaji.

Mafunzo yanaonyesha kwamba ubadilishaji wa mwongozo wa mfumo hutengeneza makosa karibu asilimia 15. Kila kosa ni kukosa utiifu au tukio la kupoteza data.

Wafanyakazi lazima wabaki na seti tatu za kanuni akilini na zitumie ile inayofaa kila wakati. Hiyo si mchakato. Ni nadhani inayofanywa kila siku.

Usanidi Tatu Unaojulikana

"Kiwango cha GDPR - Wateja wa EU"

Hugundua: majina, anwani, vitambulisho vya kitaifa, barua pepe, nambari za simu, anwani za IP, kadi za mkopo.

Njia: Futa.

Acha tarehe isipokuwa tarehe ya kuzaliwa iko ndani ya upeo. Jumuisha anwani za IP kwa kazi ya data ya mtandao.


"HIPAA Safe Harbor - Huduma za Afya"

Hugundua: majina ya watu, tarehe, maeneo ya chini ya jimbo, simu, faksi, barua pepe, SSN, nambari za rekodi za matibabu, vitambulisho vya mpango wa afya, nambari za akaunti, nambari za cheti, vitambulisho vya magari, vitambulisho vya vifaa, URL, anwani za IP, vitambulisho vya biometric. Hiyo inashughulikia aina zote 18 za Safe Harbor.

Njia: Futa. Kwa tarehe: baki na mwaka. Ondoa mwezi na siku.

Ongeza mfumo maalum kwa muundo wa nambari ya rekodi ya matibabu ya kituo chako.


"CCPA - Mtumiaji wa California"

Hugundua: majina, anwani, nambari za simu, barua pepe, SSN, leseni za udereva, nambari za pasipoti, kadi za mkopo, anwani za IP, URL, nambari za akaunti, vitambulisho vya vifaa.

Njia: Badilisha (bora kwa uchanganuzi) au Futa.


Kila usanidi uliohifadhiwa unazuia uamuzi wa utiifu. Mtumiaji huchagua wasifu unaofaa na muktadha wa kisheria wa hati. Hakuna orodha ya kitengo ya kujenga. Hakuna njia ya kuchagua.

Viwango vya Makosa Kabla na Baada

Kabla ya wasifu wenye majina: Wafanyakazi hurekebisha kwa mkono kwa kila sheria. Kiwango cha makosa ni karibu asilimia 15. Ukaguzi wa kila mwaka unagundua matokeo ya utekelezaji wa mfumo kila mwaka.

Baada ya wasifu wenye majina: Wafanyakazi huchagua wasifu uliohifadhiwa. Usanidi ni wa kawaida. Kiwango cha makosa kinapungua chini ya asilimia 2. Makosa yaliyobaki yanatoka kwa kuchagua wasifu mbaya. Ukaguzi wa QA hugundua hayo. Ukaguzi hupita bila matokeo.

Badiliko kuu: uamuzi wa utiifu unabadilika kutoka utekelezaji wa kila siku hadi uundaji wa wasifu. Mtaalamu anaamua mara moja. Kila mtumiaji anatumia bila kufikiria.

Kuendesha Timu ya Mifumo Mingi

Panga umiliki. Mkuu mmoja kwa kila sheria. Mkuu wa GDPR anamiliki wasifu wa GDPR. Afisa wa HIPAA anamiliki usanidi wa HIPAA. Kila mkuu anakagua wasifu wao kila robo mwaka.

Elekeza kwa chanzo. Data ya wateja wa EU hutumia wasifu wa GDPR. Data ya afya ya Marekani hutumia wasifu wa HIPAA. Data ya watumiaji wa California hutumia wasifu wa CCPA.

Rekodi kila utekelezaji. Rekodi za usindikaji zinaandika wasifu uliostumika kwenye kila kundi. Mkaguzi anapouliza jinsi faili ilivyoshughulikiwa, jibu ni jina la wasifu, tarehe, na rekodi ya usanidi.

Tuma masasisho. EDPB inapotoa mwongozo mpya, mkuu wa GDPR anasasisha usanidi ulioshirikiwa. Utekelezaji wote wa baadaye unachukua mabadiliko. Hakuna mtu anayehitaji kuambiwa.

Kwa mtazamo wa kina zaidi wa usimamizi wa wasifu na ushahidi wa ukaguzi, angalia mipangilio ya kusiriwa na uthabiti wa ukaguzi wa GDPR. Kwa mfuniko wa kitengo cha HIPAA Safe Harbor kwa undani, angalia kutoweza utambulisho wa HIPAA Safe Harbor kwa utafiti wa afya.

Hitimisho

Sheria tatu. Wasifu tatu uliohifadhiwa. Zana moja.

Ugumu unaishi katika kiwango cha ufafanuzi wa wasifu. Si katika usindikaji wa kila siku. Watumiaji hawahitaji kujua kanuni za tarehe za HIPAA. Wanahitaji kujua wasifu unaofaa hati iliyo mbele yao.

Usanidi unaojulikana hukata mzigo wa kiakili. Hupunguza makosa. Hufanya utiifu uweze kuthibitishwa.

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.