anonym.legal

By · Last updated 2026-05-03

Tagasi BlogisseGDPR ja Vastavus

MiCA ja GDPR: Krüptorahakoti isikuandmete tuvastamine

EL-i MiCA maarustik kasitleb kruptoraha rahakoti aadresse finantsidentifikaatoritena. GDPR kehtib rahakoti aadressidele, mis on seotud isikutega.

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

MiCA, GDPR ja kruptoraha rahakoti aadressid

Bitcoini aadress on 26-35 tahaht Base58Check kodeeringus. See algab '1', '3' voi 'bc1' ga. Ethereumi aadress algab '0x'-iga ja sisaldab 40 heksadetsimaalset tahaht. Moimad on pseudonuumsed. Kumbki ei nimeta isikut otseselt.

Seadus kehtib endiselt.

Millal muutub rahakoti aadress isikuandmeteks

Psuedonymiseeritud kirjed on isikuandmed, kui need seovad reaalse isikuga. Kruptobors haldab KYC-faile. Need failid seovad need aadressid kinnitatud identiteetidega. Aadress ise ei nimeta kedagi valisusel borsi. Borsi sustoomides nimetab see klienti. See teeb sellest isikuandmed.

Maarustik katab seda taises mahus.

MiCA lisab teise kihi

EL-i MiCA (Kruptovarade turud) joustus 2024. aasta detsembris. See kohustab kruptovarade teenusepakkujaid - CASP-e - kaitsma kliendi kirjeid. Euroopa bors seisab praegu kahe reegli ees korraga. MiCA kehtestab finantskontrollid. Maarustik kehtestab andmekaitsreeglid. Moimad kohalduvad samale identifikaatorile.

Tuvastamise lünk standardtoriistades

Standard isikuandmete toritsad on loodud traditsioonilise rahanduse jaoks. Need teavad IBAN-i. Need teavad SWIFT/BIC-i. Need teavad suunakoode. Need ei tea kruptoraha aadresside vorminguid.

Saatke dokument Bitcoini aadressiga, Ethereumi aadressiga ja SWIFT-koodiga labi standardse toriista. See leiab SWIFT-koodi. See jatab molemad ahelasisesed aadressid vahele.

CASP-i jaoks, kes tootleb KYC-faile, on see lünk tostlik. Need identifikaatorid on sama tundlikud kui pangakonto numbrid. Nende vahele jatamine tahendab, et puudub krupteemine, maskeerimine ega auditijalgede.

Artikkel 32 ja krupteerimise lünk

GDPR-i artikkel 32(1)(a) nab pseudonymiseerimist ja krupteerimist baaskontrollidena. 56% GDPR-i trahvidest mainib halba krupteerimist tegurina. Bors, mis krupteerib koik tuvastatud isikuandmed, kuid jatab rahakoti aadressid vahele, ei ole kaitsnud midagi oma too tuumas.

Tuvastamine peab katma koik identifikaatorite kogumi. CASP-i jaoks sisaldab see kogum neid aadresivorminguid.

Mis nabb vastaev toruliins valja

Vastaev bors lisab need uiksuse tuped oma tuvastamise etappi. Bitcoini ja Ethereumi vormingud on lisatud. Aadressid markstatakse, krupteritakse ja logitakse ROPA-sse koos IBAN-ide ja kontonumbritega. DPIA nimetab iga kaetud identifikaatorityyp. MiCA auditijalgede on kooskolas tootlemiskirjetega.

Uut poliitikat pole vaja. Lünk on tehniline. Oigete uiksuse tuupide lisamine tuvastamise etappi sulgeb selle.

Tehniliste meetmete kohta artikli 32 alusel vaadake GDPR artikkel 32 ja tehisintellekti toritsad isikuandmete kokkupuute seireks. Pseudonymiseerimise toimimise kohta praktikas vaadake EDPB 2025 pseudonymiseerimise juhised.

Allikad

Seotud Artiklid

GDPR ja Vastavus

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 ja Vastavus

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 ja Vastavus

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.

Kas olete valmis oma andmeid kaitsma?

Alustage PII anonüümitamist 285+ üksustüübi abil 48 keeles.

Alusta Tasuta KatsetVaata Funktsioone

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.