anonym.legal

By · Last updated 2026-05-03

Povratak na blogGDPR i usklađenost

MiCA i GDPR: Detekcija PII kripto novcanika

EU MiCA regulativa tretira adrese kriptovalutnih novcanika kao finansijske identifikatore. GDPR se primenjuje na adrese novcanika koje su povezane s pojedincima. Standardni alati za zastitu podataka ne prepoznaju ove formate.

May 3, 20268 min čitanja
cryptocurrency PII GDPRMiCA complianceBitcoin wallet anonymizationSWIFT code detectionIBAN crypto fintech

MiCA, GDPR i adrese kripto novcanika

Bitcoin adresa ima 26-35 karaktera u Base58Check kodiranju. Pocinje s "1", "3" ili "bc1". Ethereum adresa pocinje s "0x" i sadrzi 40 hex karaktera. Obe su pseudonimne. Nijedna direktno imenuje osobu.

Zakon se i dalje primenjuje.

Kada adresa novcanika postaje licni podatak

Pseudonimni zapisi su licni zapisi ako se mogu povezati s pravom osobom. Kripto berza poseduje KYC dokumenta. Ta dokumenta povezuju ove adrese s verifikovanim identitetima. Sama adresa ne imenuje nikoga van berze. Unutar njenih sistema, imenuje korisnika. To je cini licnim podatkom.

Regulativa je pokriva u potpunosti.

MiCA dodaje drugi sloj

EU MiCA (Markets in Crypto-Assets) stupila je na snagu u decembru 2024. Zahteva od pruzalaca usluga kriptovalutnih aktiva - CASP-ova - da stite evidenciju o korisnicima. Evropska berza sada istovremeno suocava s dva pravila. MiCA postavlja finansijske kontrole. Regulativa postavlja pravila zastite podataka. Oba se primenjuju na isti identifikator.

Detekcijski jaz u standardnim alatima

Standardni alati za zastitu podataka razvijeni su za tradicionalne finansije. Poznaju IBAN. Poznaju SWIFT/BIC. Poznaju sifre za medjubankarski prenos. Ne poznaju formate kripto adresa.

Posaljite dokument s Bitcoin adresom, Ethereum adresom i SWIFT kodom kroz standardni alat. Pronadje SWIFT kod. Propusti obe blockchain adrese.

Za CASP koji obradjuje KYC datoteke, ovaj jaz je ozbiljan. Ovi identifikatori su jednako osetljivi kao brojevi bankovnih racuna. Propustanje ih znaci nema enkripcije, nema maskiranja i nema revizijskog traga.

Clan 32 i enkripcijski jaz

GDPR clan 32(1)(a) zahteva pseudonimizaciju i enkripciju kao bazicne kontrole. 56% kazni po GDPR-u navodi losу enkripciju kao faktor. Berza koja enkriptuje sve detektovane licne podatke ali propusti adrese novcanika nije zastitila nista u srzi svog poslovanja.

Detekcija mora pokriti kompletan skup identifikatora. Za CASP, taj skup ukljucuje ove formate adresa.

Kako izgleda uskladjen pipeline

Uskladjena berza dodaje ove tipove entiteta u svoj korak detekcije. Bitcoin i Ethereum formati su ukljuceni. Adrese su oznacene, enkriptovane i evidentirane u ROPA-i pored IBAN-ova i brojeva naloga. DPIA imenuje svaki tip identifikatora koji je pokriven. Revizijski tragovi prema MiCA uskladjeni su s evidencijama obrade.

Nema potrebe za novim politikama. Jaz je tehnicki. Dodavanje pravih tipova entiteta u korak detekcije ga zatvara.

Za tehnicke mere prema clanu 32, pogledajte GDPR clan 32 i AI alati koji prate izlozenost PII. Za prakticno funkcionisanje pseudonimizacije, pogledajte EDPB 2025 smernice za pseudonimizaciju.

Izvori

Povezani članci

GDPR i usklađenost

Japan My Number: Verhoeff & APPI

63% of generic tools fail My Number detection in Japanese documents. My Number uses Verhoeff algorithm — the most complex national ID checksum in Asia.

GDPR i usklađenost

HDPA Greece: AFM & AMKA Detection

Greek AFM detected with 52% accuracy by generic tools. HDPA issued 89 decisions in 2024 — up 162% from 2022. Tourism and maritime sectors face distinct.

GDPR i usklađenost

NAIH Hungary: TAJ-Szám and Adóazonosító Jel

Hungarian NER accuracy is 67% vs. EU average 82% — NAIH's 2024 assessment. TAJ-szám weighted checksum and adóazonosító jel detection gaps.

Spremni da zaštitite svoje podatke?

Počnite sa anonimizacijom PII sa 285+ tipova entiteta na 48 jezika.

Započnite besplatnu probuPogledajte funkcije

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.