By · Last updated 2026-05-03

Späť na blogGDPR a Dodržiavanie

MiCA a GDPR: Detekcia osobnych udajov kryptomenovych penazeniek

Nariadenie EU MiCA traktuje adresy kryptomenovych penazeniek ako financne identifikatory. GDPR sa vztahuje na adresy penazeniek spojene s fyzickymi osobami.

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

MiCA, GDPR a adresy kryptomenovych penazeniek

Adresa Bitcoinu ma 26 az 35 znakov v kodovani Base58Check. Zacina znakmi "1", "3" alebo "bc1". Adresa Ethereum zacina "0x" a obsahuje 40 hexadecimalnych znakov. Obe su pseudonymne. Ziadna priamo neidentifikuje osobu.

Zakon sa napriek tomu vztahuje.

Kedy sa adresa penazenky stava osobnym udajom

Pseudonymne zaznamy su osobnymi zaznamami, ak su spojene so skutocnou osobou. Kryptoburza uchovava KYC subory. Tieto subory viazu tieto adresy na overene identity. Samotna adresa mimo burzy nikoho neidentifikuje. Vo vnutri jej systemov identifikuje klienta. To z nej robi osobny udaj.

Nariadenie ju plne pokryva.

MiCA pridava druhu vrstvu

EU MiCA (Markets in Crypto-Assets) nadobudla ucinnost v decembri 2024. Vyzaduje od poskytovatelov sluzieb kryptoaktiv -- CASP -- ochranu zaznamov klientov. Europska burza dnes celi dvom pravidlam naraz. MiCA stanovuje financne kontroly. Nariadenie stanovuje pravidla ochrany udajov. Obe platia pre rovnaky identifikator.

Medzera v detekcii pri standardnych nastrojoch

Standardne nastroje na ochranu osobnych udajov boli vytvorene pre tradicne financnictvo. Poznaju IBAN. Poznaju SWIFT/BIC. Poznaju smerovacie cisla. Nepoznaju formaty kryptomenovych adries.

Posielajte dokument s Bitcoinovou adresou, Ethereum adresou a SWIFT kodom cez standardny nastroj. Najde kod SWIFT. Obe adresy on-chain preskoci.

Pre CASP spracovavajuci KYC subory je tato medzera zavazna. Tieto identifikatory su rovnako citlive ako cisla bankovych uctov. Ich presklbnutie znamena ziadne sifrovanie, ziadne maskovanie a ziadny auditny zaznam.

Clanok 32 a medzera v sifrovani

GDPR Clanok 32(1)(a) vyzaduje pseudonymizaciu a sifrovanie ako zakladne kontroly. 56 % pokut GDPR uvadza zle sifrovanie ako faktor. Burza, ktora sifruje vsetky detegovane osobne udaje, ale presklbne adresy penazeniek, nechranila nic v jadre svojej cinnosti.

Detekcia musi pokryvat cely suhbor identifikatorov. Pre CASP tento subor zahrnuje tieto formaty adries.

Ako vyzera vyhovujuca pipeline

Vyhovujuca burza pridava tieto typy entit do svojho detekeneho kroku. Formaty Bitcoin a Ethereum su zahrnutie. Adresy su oznacene, zasifrovane a zaznamenane v ROPA vedla IBAN a cisel uctov. DPIA menuje kazdy pokryty typ identifikatora. Auditne stopy MiCA sa zhoduju so zaznamami o spracovani.

Ziadna nova politika nie je potrebna. Medzera je technicka. Pridanie spravnych typov entit do detekneho kroku ju zatvori.

Pre technicke opatrenia podla Clanku 32 pozrite GDPR Clanok 32 a AI nastroje monitorujuce expozicie PII. Pre fungovanie pseudonymizacie v praxi pozrite smernice EDPB 2025 pre pseudonymizaciu.

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.