anonym.legal

By · Last updated 2026-05-03

Nazaj na blogGDPR in skladnost

MiCA in GDPR: zaznavanje osebnih podatkov kripto denarnic

Uredba EU MiCA obravnava naslove kriptovalutnih denarnic kot financne identifikatorje. GDPR se uporablja za naslove denarnic, povezane s posamezniki.

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

MiCA, GDPR in naslovi kripto denarnic

Bitcoinov naslov je 26-35 znakov v kodiranju Base58Check. Zacne se z "1", "3" ali "bc1". Ethereumov naslov se zacne z "0x" in vsebuje 40 heksadecimalnih znakov. Oba sta psevdonimna. Nobeden neposredno ne imenuje osebe.

Zakon se vseeno uporablja.

Ko naslov denarnice postane osebni podatek

Psevdonimni zapisi so osebni zapisi, ce se navezujejo na resnicno osebo. Kripto menjalnica hrani datoteke KYC. Te datoteke vezejo te naslove na preverjene identitete. Naslov sam zunaj menjalnice ne imenuje nikogar. Znotraj njenih sistemov imenuje stranko. To ga naredi za osebni podatek.

Uredba ga v celoti pokriva.

MiCA doda drugo plast

EU MiCA (Markets in Crypto-Assets) je stopila v veljavo decembra 2024. Zahteva, da ponudniki storitev s kriptopremozenjem - CASP - varujejo zapise strank. Evropska menjalnica zdaj soci dvema praviloma hkrati. MiCA doloca financne nadzore. Uredba doloca pravila varstva podatkov. Oba se nanasata na isti identifikator.

Vrzel zaznavanja v standardnih orodjih

Standardna orodja za osebne podatke so bila zgrajena za tradicionalne finance. Poznajo IBAN. Poznajo SWIFT/BIC. Poznajo smernestevilke. Ne poznajo formatov kripto naslovov.

Poslite dokument z Bitcoinovim naslovom, Ethereumovim naslovom in kodo SWIFT skozi standardno orodje. Najde kodo SWIFT. Oba naslova veriznih transakcij zamudi.

Za CASP, ki obdeluje datoteke KYC, je ta vrzel resna. Ti identifikatorji so enako obcutljivi kot stevilke bancnih racunov. Njihovo zamujanje pomeni brez sifriranja, brez maskiranja in brez revizijske sledi.

Clen 32 in vrzel sifriranja

Clen 32(1)(a) GDPR zahteva psevdonimizacijo in sifriranje kot temeljne kontrole. 56% glob GDPR navaja slabo sifriranje kot dejavnik. Menjalnica, ki sifrira vse zaznane osebne podatke, a zamudi naslove denarnic, ni zascitila nicesar v jedru svojega dela.

Zaznavanje mora pokrivati celoten nabor identifikatorjev. Za CASP ta nabor vkljucuje te formate naslovov.

Kako izgleda skladna cevovod

Skladna menjalnica doda te vrste entitet v korak zaznavanja. Formati Bitcoin in Ethereum so vkljuceni. Naslovi so oznaceni, sifrirani in zabelezeni v ROPA poleg IBAN-ov in stevilk racunov. DPIA imenuje vsako vrsto identifikatorja, ki je pokrita. Revizijske sledi MiCA se ujemajo z evidencami obdelave.

Nova politika ni potrebna. Vrzel je tehnicna. Dodajanje pravilnih vrst entitet v korak zaznavanja jo zapre.

Za tehnicne ukrepe po clenu 32 glejte GDPR clen 32 in orodja AI za spremljanje izpostavljenosti osebnih podatkov. Za delovanje psevdonimizacije v praksi glejte smernice psevdonimizacije EDPB 2025.

Viri

Ste pripravljeni zaščititi svoje podatke?

Začnite z anonimizacijo PII z več kot 285 tipi entitet v 48 jezikih.

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.