By · Last updated 2026-03-28

Späť na blogGDPR a Dodržiavanie

KYC vo velkej mierke: Naklady na falzive pozitivne vysledky

Digitalna banka spracuvajuca 5 000 KYC ziadosti denne v 15 krajinach EU zistila, ze jej krok skenovania PII sposobuje 2-denné nahromadenie vo fronte.

March 28, 20267 min čítania
KYC PII automationfintech complianceAML data protectionPII false positive costdigital banking GDPR

Konkurujuce pravidla KYC

Pravidla Poznaite svojho zakaznika (KYC) vytvaraju skutocne napatie pre fintech firmy. Regulatori chcu dokladne kontroly totoZnosci. Vyzaduju od firm zber a overenie osobnych dokumentov. Ale zakony o ochrane udajov tlacia opacnym smerom. Vyzaduju od firm minimalizaciu tychto udajov po ich zhromazdeni.

Banka otváraza novy ucet zhromazduje vela dokumentov. Tieto zahrnaju narodne preukazy, pasy a ridicske preukazy. Tiez zbiera doklady o adrese a financne doklady. Tieto subory obsahuju husté osobne udaje. GDPR, pravidla AML a bankove dozorne organy vyzaduju prisne zaobchadzanie.

Ked tieto udaje prechadzaju do systemov odhalovani podvodov alebo analyzy, platia dalsie pravidla. Aktivuju sa datove pravidla GDPR. Osobne udaje musia byt maskované alebo de-identifikovane pred akymmkolvek druhym pouzitim.

Problem 2-denneho nahromadenia

Digitalna banka spracovavala 5 000 KYC ziadosti denne v 15 krajinach EU. Ich krok skenovania PII sposobil vazny problem. Miera falzivych pozitivnych vysledkov bola prilis vysoka. Fronty na preskumanie rástly, az dosiahli 2-denné nahromadenie.

Pricina bola jasna. Ich nastroj zalozeny na ML oznacoval priblizne 8 % textu bez PII ako osobne udaje. Kazdy subor mal vela stran. Denný objem falzivych pozitivnych vysledkov bol prilis velky na to, aby ho tym stihol zvladnut v jeden den. Neustale zaostávali.

Falzive pozitivne vysledky spadali do troch skupin:

  • Nazvy spolocnosti oznacene ako mena osob (model zamienal vlastne podstatne mena)
  • Referencne kody oznacene ako ID cisla (nebol pouzity ziadny kontrolny sucet)
  • Bezne krstne mena ako "Chase" v názvoch bank oznacene ako PII mena osoby

Kazdy falzivý pozitivny vysledok vyzadoval ludsky prezkum. Pri 8 % z 5 000 dennÿch suborov to produkuje tisice dennÿch uloh. Ziadnu nebolo mozne automatizovat.

Co ukazuje vyskum ACL

Vyskum ACL 2024 testoval viacjazycne modely NLP na zistovanie PII. Zistenie bolo markantne. Iba 5 % viacjazycnych modelov NLP dosiahne lepsie ako 85 % F1-skore pre PII mimo anglictiny napriec vseytkymi 24 jazykmi EU.

F1-skore kombinuje presnost a navratnost. Nizka presnost znamena vela falzivych pozitivnych vysledkov. Nizka navratnost znamena vela vynechanych poloziek. Oba vysledky su ohodnotene slabo. Miera 95 % neuspesnych pri dosiahnutí 85 % F1 ukazuje, ako narocne je v praxi medzijazyckove skenovanie PII.

Naproti tomu XLM-RoBERTa dosahuje 91,4 % medzijazyckove F1 pre ulohy PII. Tato cifra pochadza z benchmarkingu HuggingFace 2024. Medzera medzi 91,4 % a medianom modelu vysvetluje, preco krabicove nastroje zlyhavaju v medzijazykovom KYC.

Hybridny dizajn pre KYC s vysokym objemom

Problem falzivych pozitivnych vysledkov je riesitelny. Tri konstrukčne volby ho opravuju.

Regex s kontrolou kontrolneho suctu: Narodni ID cisla maju pevne pravidla. Nemecke Steuer-ID, holandske BSN a polske PESEL pouzivaju matematiku kontrolneho suctu. Ak cislo kontrolny sucet nesplna, nie je to narodni ID. Format plus kontrolny sucet produkuje takmer nulove falzive pozitivne vysledky pre tieto ID.

Kontextovo uvazomajuce NLP pre mena: Mena osob v KYC suboroch sa objavuju na znamych miestach. Tieto zahrnaju polia "Meno:", "Priezvisko:" a nastavene polia formularov. Vyzadovanie kontextoveho slova pred oznacenim mena znizuje falzive pozitivne vysledky. Zastavuje nazvy firm od spustenia upozorneni na mena osob.

Ladiaci prah podla typu suboru: KYC subory sa lisia od e-mailov podpory alebo zdravotnych zaznamov. Kazdy typ ma iny mix PII. Nastavenie prahov podla typu suboru umoznuje tymu ladit podla potrieb. Velky objem KYC dostane vyssu presnost. Zdravotna de-identifikacia dostane vyssu navratnost.

2-denné nahromadenie nie je nevyhnutnym nakladom skenovania PII. Je to naklad za pouzivanie generickeho nastroja v specifickom pracovnom postupe. Riesenim je nastavenie, nie vacsi tym.

Nas pruvodca zhodou GDPR pokryva pravidla minimalizacie udajov. Nas prehlad bezpecnosti a zhody vysvetluje technicke kontroly podporujuce pracovne toky KYC v sulade s predpismi.

Zdroje

Pripravení chrániť vaše údaje?

Začnite anonymizovať PII s 285+ typmi entít v 48 jazykoch.

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.