By · Last updated 2026-06-05

Rudi kwa BlogGDPR & Ufuatiliaji

PII ya Maandishi Huru ya CSV: Zaidi ya Kufuta Safu

CSV za uchunguzi zina PII si tu katika safu zilizopangwa bali pia katika majibu ya maandishi huru. Kufuta safu za kawaida kunakosa PII inayovunja kanuni ya Rekebisho la 26 la GDPR ya kutopatikana.

June 5, 20267 dakika kusoma
research dataCSV anonymizationGDPR Article 89survey datadata sharing

Pengo Ambalo Kufuta Safu Kunakosa

Imesasishwa kwa mwaka 2026

Seti za data za utafiti zinahamia kati ya vyuo vikuu kama faili za CSV. Timu zinapotayarisha CSV kwa kushiriki, kazi inategemea safu. Tafuta habari za kibinafsi. Futa au ibadilishe.

Njia hiyo inafanya kazi kwa sehemu zilizowekwa. Safu inayoitwa "barua pepe" inashikilia anwani za barua pepe — ifute. Safu inayoitwa "simu" inashikilia nambari za simu — ifute. Safu inayoitwa "jina_la_mshiriki" inashikilia majina — ibadilishe kwa nambari ya msimbo.

Lakini safu za jibu la maandishi huru ni eneo la kipofu. Kuondoa safu zilizotajwa hakuzigusi.

Uchunguzi wenye mistari 5,000 unaweza kuwa na safu tano za PII zilizopangwa na safu kumi na tano za majibu ya maandishi huru. Zilizopangwa zinashikilia majina, barua pepe, nambari za simu, vitambulisho, na miaka ya kuzaliwa. Maandishi huru zinashikilia maoni, maelezo, na mapendekezo.

Safu zilizopangwa zinasafishwa. Safu za maandishi huru zinabaki zikiwa za kawaida. Lakini watu wanaandika mambo kama mifano hii mitatu.

Kwanza: "Daktari wangu katika Boston Medical Center, Dk. Maria Santos, alisema matibabu yalikuwa mapya." Pili: "Nimekuwa nikishughulikia hili tangu ajali yangu ya 2019." Tatu: "Unaweza kuwasiliana na mlezi wangu kwa margaret.wells@gmail.com kwa maelezo."

Kila ingizo linataja mtu halisi. Baadhi zinajumuisha ukweli wa afya au mawasiliano. Hakuna hata moja inayoonekana katika kichwa cha safu. Hakuna inayopatikana na kufuta safu.

Kwa Nini Hii Inashindwa Kiwango cha GDPR

Rekebisho la 26 la GDPR linafafanua rekodi za kisiriana kama rekodi ambazo haziwezi kuunganishwa na mtu yeyote. Kiwango ni cha juu. Rekodi ni za kweli kisiriana tu wakati utambulisho upya hauwezekani kwa akili.

CSV yenye safu safi zilizowekwa lakini watu waliotajwa katika maandishi huru haipiti mtihani huo. Majina hayo yanaweza kutambuliwa. Seti ya data bado ni ya kibinafsi. Kanuni za Kifungu cha 89 cha GDPR bado zinatumika. Kwa hivyo hatari hizi tatu zinatokea.

Msamaha wa utafiti wa Kifungu cha 89: Kifungu cha 89 kinaruhusu watafiti kushughulikia habari za kibinafsi kwa sayansi na wajibu wachache. Lakini tu pale "dhamana zinazofaa" zinapowepo. Kushiriki faili yenye PII ya maandishi huru huku ukidai ulinzi wa Kifungu cha 89 ni kushindwa kwa kisheria.

Idhini ya maadili: IRB na bodi nyingi za maadili zinahitaji kufuta majina kamili kwa seti za data zilizoshirikiwa. Kazi ya sehemu — safu zilizowekwa zikisafishwa, maandishi huru yakiacha bila kushughulikiwa — kwa kawaida inashindwa. Bodi inaweza kukataa uwasilishaji.

Makubaliano ya kushiriki data: DSA kati ya taasisi huweka kiwango kinachohitajika cha kufuta majina. Kazi ya sehemu inayoshindwa Rekebisho la 26 la GDPR inaweza kukiuka DSA. Angalia muhtasari wetu wa Uzingatiaji wa Kisheria jinsi hii inavyoendana na programu pana.

Kwa Nini Maandishi Huru Ni Magumu Sana Kusafisha

Mapajibu ya uchunguzi wa maandishi huru ni miongoni mwa malengo magumu zaidi ya PII. Hapa ni kwa nini.

Majina katika muktadha: "Dk. Maria Santos katika Boston Medical Center" inahitaji utambuzi wa enti zilizotajwa (NER) kutambua mtu na shirika. Orodha za maneno muhimu haziwezi kupata hii.

Majina katika hadithi: "Gari la John Henderson liligonga langu" linaweka jina halisi ndani ya hadithi. Ni mtu aliyetajwa kwa njia ya kupita. NER tu inaweza kuipata.

Miundo isiyo ya kawaida: Mawasiliano yanaweza kusomwa "niwasiliane nami kwa margaret dot wells katika gmail." Zana rahisi za regex hukosa hizi.

Maneno maalum ya utafiti: Uchunguzi wa kimatibabu mara nyingi una vitambulisho vya hospitali, misimbo ya tovuti, na majina ya mahali. Hizi zinaweza kutambua mtu hata zinapoonyesha kawaida.

Kwa hivyo ufananisho wa mfumo peke yake hautoshi. Zana zinazotegemea NLP zinahitajika kwa kufuta kweli kwa uchunguzi. Angalia Usalama na Uzingatiaji kwa chaguo za kiufundi.

Mfano Halisi Kutoka Vyuo Vikuu Vitatu

Timu ya utafiti katika vyuo vikuu vitatu vya Ulaya ilifanya uchunguzi wa uzoefu wa wagonjwa. Seti ya data ilikuwa na wajibu 5,000, safu 3 za PII zilizowekwa, na safu 8 za maandishi huru. Mpango ulikuwa kushiriki faili katika tovuti chini ya DSA na Kifungu cha 89 cha GDPR.

Kwa kufuta safu tu:

  • Safu za PII zilizowekwa: ziliondolewa
  • Safu za maandishi huru: zimebaki za kawaida
  • Dai: "Safu za PII zimefutwa"
  • PII iliyobaki: watu 47 waliotajwa, anwani 23 za barua pepe katika maoni, majina 18 ya mahali yanayoweza kutambua wajibu

Kwa ugunduzi unaotegemea NLP:

  • Safu za PII zilizowekwa: zimebadilishwa na tokeni thabiti
  • Safu za maandishi huru: majina 47 yamebadilishwa, barua pepe 23 zimefunikwa, majina 18 ya mahali yamefanywa ya jumla ("Boston Medical Center" → "[Taasisi ya Huduma za Afya]")
  • Matokeo: faili inayopita Rekebisho la 26 la GDPR
  • Bodi ya maadili iliidhinisha njia
  • DPO ilithibitisha uzingatiaji wa DSA

Pengo ni la kweli. Matokeo ya kwanza yanaonekana safi. Matokeo ya pili ni safi.

Itifaki ya Hatua Tano Kabla ya Kushiriki

Tumia hatua hizi kabla ya kushiriki faili yoyote ya uchunguzi au mahojiano.

Hatua ya 1: Taja kila safu Alama kila safu kama PII iliyowekwa, isiyokuwa ya PII iliyowekwa, au maandishi huru. Iandike.

Hatua ya 2: Shughulikia PII iliyowekwa Futa ingizo ambazo hazihitajiki kwa uchambuzi. Badilisha ingizo zinazohitajika kwa kuunganisha rekodi. Rekodi misimbo iliyotumika.

Hatua ya 3: Skani safu za maandishi huru Endesha ugunduzi wa NLP katika safu zote za maandishi huru. Kagua kila matokeo. Thibitisha ni zipi za kweli za PII.

Hatua ya 4: Tumia mabadilisho Badilisha PII iliyothibitishwa katika matokeo ya maandishi huru. Tumia lebo wazi kama `[MTU]`, `[BARUA PEPE]`, au `[ENEO]`.

Hatua ya 5: Thibitisha na ufafanue Sampuli mistari 50–100 kutoka matokeo. Kagua ingizo za maandishi huru kwa mkono. Andika muhtasari mfupi: zana zilizotumika, aina za enti zilizopatikana, safu zilizoshughulikiwa. Kishirikiane na faili kwa ukaguzi wa maadili.

Hii inabadilisha "tulifuta safu ya jina" kuwa mchakato wazi, ulioandikwa. Inakidhi Kifungu cha 89 cha GDPR na viwango vya kufuta majina ambavyo bodi nyingi za maadili zinahitaji. Tembelea kituo chetu cha nyaraka kwa miongozo inayohusiana.

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.