By · Last updated 2026-06-05

Rudi kwa BlogGDPR & Ufuatiliaji

ANSPDCP Romania: Utambuzi wa CNP na Ukaguzi

ANSPDCP iligundua 78% ya zana zinakosa CNP ya Kiromania na uthibitishaji sahihi. CNP inasimba jinsia, tarehe ya kuzaliwa, na kaunti ya kuzaliwa — athari za aina maalum ya GDPR.

June 5, 20267 dakika kusoma
Romania ANSPDCPCNP checksum validationRomanian GDPRBPO complianceRomanian identifiers

ANSPDCP Romania: Utambuzi wa CNP na Ukaguzi wa GDPR

Imesasishwa kwa 2026

Taasisi ya data ya Romania ni ANSPDCP. Tathmini yake ya 2024 iligundua 78% ya zana za PII hazitambui Cod Numeric Personal (CNP). Wengi wanakimbia hatua ya jedwali la ukaguzi. Pengo hilo huunda hatari halisi ya uzingativu. Romania inashughulikia data ya EU kwa wateja wengi wa Magharibi. Mfiduo ni mpana.

Kitambulisho cha Taifa Chenye Data Nyingi Zaidi cha Romania

CNP ni kitambulisho cha taifa chenye tarakimu 13. Kila kundi la tarakimu kina data ya kibinafsi:

  • Tarakimu 1: Msimbo wa jinsia na karne. Kiume kilichozaliwa 1900–1999 = 1. Kike kilichozaliwa 1900–1999 = 2. Kiume kilichozaliwa 2000+ = 5. Kike kilichozaliwa 2000+ = 6. Mkazi wa kigeni wa kiume = 7. Mkazi wa kigeni wa kike = 8. Mkazi mwingine = 9.
  • Tarakimu 2–3: Tarakimu mbili za mwisho za mwaka wa kuzaliwa.
  • Tarakimu 4–5: Mwezi wa kuzaliwa (01–12).
  • Tarakimu 6–7: Siku ya kuzaliwa (01–31).
  • Tarakimu 8–9: Msimbo wa kaunti. Unafunika kaunti 41 na sekta sita za Bucharest (misimbo 01–52).
  • Tarakimu 10–12: Mpangilio wa kuzaliwa ndani ya siku hiyo na kaunti.
  • Tarakimu 13: Tarakimu ya ukaguzi.

Tarakimu 1 peke yake inafunua jinsia ya kibiolojia. Chini ya Kifungu cha 9 cha GDPR, hiyo inafanya nambari hii kuwa kipengele cha data ya aina maalum. Inahitaji ulinzi mkubwa zaidi kuliko data ya kawaida ya kibinafsi.

Jinsi tarakimu ya ukaguzi inavyofanya kazi: Chukua tarakimu 12 za kwanza. Zidisha kila moja kwa uzito wake (2, 7, 9, 1, 4, 6, 3, 5, 8, 2, 7, 9). Jumla ya matokeo. Gawanya na 11 na chukua mabaki. Mabaki ya 10 hutoa tarakimu ya ukaguzi 1. Mabaki ya 11 inamaanisha msimbo si halali. Mabaki nyingine yoyote ndiyo tarakimu ya ukaguzi.

Zana zinazoruka mtihani huu zina njia mbili za kushindwa. Kwanza, kila mfuatano wa tarakimu 13 unabandikwa bendera kama mechi (matokeo mazuri ya uongo). Pili, nambari iliyoharibika inapita ukaguzi wa muundo lakini ina data mbaya. Data hiyo inahitaji ukaguzi na inakosekana (matokeo mabaya ya uongo).

Matatizo ya NER katika Nyaraka za Lugha ya Kiromania

Kupata vitambulisho ni sehemu tu ya kazi. Maandishi ya Kiromania yanaongeza vikwazo zaidi vya utambuzi.

Diacriti: Kiromania inatumia ș, ț, ă, â, na î. Zana zilizofunzwa kwa lugha nyingine mara nyingi hukosa majina yenye herufi hizi. Nyaraka za zamani katika usimbaji wa Latin-2 zinaongeza kushindwa zaidi.

Miundo ya anwani: Aina za mitaa zinatumia fomu fupi — Str., Bd., Al., Cal. Majina ya mji na kata yanafuata sheria za ndani. Wakagua waliojengwa kwa anwani za Kifaransa au Kijerumani hufanya vibaya hapa.

Uinamishaji wa majina: Majina hubadilika umbo kwa kesi ya kisarufi katika Kiromania. Jina la mtu mmoja linaonekana tofauti katika sehemu tofauti za sentensi. Mifano ya NER lazima yashughulikie hili ili kuunganisha majina katika nyaraka.

Angalia mwongozo wetu wa utambuzi wa PII wa APAC jinsi mapengo ya lugha yanavyoathiri utambuzi katika hati zisizo za Magharibi.

Jinsi Kesi za ANSPDCP Zinavyokua

Kesi za ANSPDCP zinaonyesha mifumo mitatu.

Kesi za uvunjaji wa BPO: Faili zilizoshirikiwa zina nambari za kitambulisho cha wafanyakazi na data ya wateja wa EU bila usimbuaji. Kumbukumbu duni zinamaanisha kampuni haiwezi kujua rekodi zipi zilipatikana. Hiyo hurefusha uchunguzi na kuongeza faini.

Mfiduo wa huduma za afya: Faili za mgonjwa — kitambulisho cha taifa, kitambulisho cha kadi ya afya, na utambuzi — zinafikia mtu asiyestahili. Zana ya PII haikuwa na usaidizi wa muundo huu. Data ilisalia bila kufunikwa.

Kushindwa kwa uhamishaji wa kimataifa: Kampuni ya nje ya kazi inatuma rekodi zilizounganishwa na vitambulisho kwa upande wa tatu usio wa EEA. Hakuna Tathmini ya Athari ya Uhamishaji. Hakuna Vifungu vya Kimkataba vya Kawaida. Hali ya Kifungu cha 9 ya data inabadilisha pengo la kawaida kuwa ukiukwaji wa kuzidi.

Udhibiti Matatu kwa Uzingativu wa ANSPDCP

Hizi tatu zinaunda kiwango cha chini cha kiufundi:

  1. Utambuzi wa CNP na uthibitishaji wa modulo-11 — ulinganifu wa muundo peke yake haitoshi.
  2. NER inayojua diacriti — funika ș, ț, ă, â, na î katika vyanzo vya UTF-8 na Latin-2.
  3. Utambuzi wa kadi ya kitambulisho — kadi ya taifa inaonekana pamoja na CNP katika aina nyingi za nyaraka.

Kwa mtazamo mpana wa jinsi vitambulisho vya taifa vinavyosababisha hatari ya GDPR, angalia mwongozo wetu wa utambuzi wa kitambulisho cha kodi cha taifa cha EU.

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.