anonym.legal

By · Last updated 2026-05-03

Tilbage til BlogGDPR & Overholdelse

MiCA og GDPR: Detektion af PII i kryptovaluta-wallets

EU's MiCA-forordning behandler kryptovaluta-wallet-adresser som finansielle identifikatorer. GDPR gælder for wallet-adresser, der er knyttet til enkeltpersoner.

May 3, 20268 min læsning
cryptocurrency PII GDPRMiCA complianceBitcoin wallet anonymizationSWIFT code detectionIBAN crypto fintech

MiCA, GDPR og kryptovaluta-wallet-adresser

En Bitcoin-adresse er 26–35 tegn i Base58Check-kodning. Den starter med "1", "3" eller "bc1". En Ethereum-adresse starter med "0x" og indeholder 40 hex-tegn. Begge er pseudonyme. Ingen af dem navngiver en person direkte.

Loven gælder alligevel.

Hvornår en wallet-adresse bliver personoplysning

Pseudonyme poster er personoplysninger, hvis de kan knyttes til en reel person. En kryptobørs har KYC-filer. Disse filer forbinder adresserne med verificerede identiteter. Adressen alene navngiver ingen uden for børsen. Inde i dens systemer identificerer den en kunde. Det gør den til en personoplysning.

Forordningen gælder i fuldt omfang.

MiCA tilføjer et ekstra lag

EU's MiCA (Markets in Crypto-Assets) trådte i kraft i december 2024. Den kræver, at udbydere af kryptoaktivtjenester — CASP'er — beskytter kunderegistre. En europæisk børs møder nu to regelsæt på én gang. MiCA sætter de finansielle rammer. Forordningen sætter databeskyttelsesreglerne. Begge gælder for den samme identifikator.

Detektionskløften i standardværktøjer

Standard PII-værktøjer er bygget til traditionel finans. De kender IBAN. De kender SWIFT/BIC. De kender routingnumre. De kender ikke kryptovaluta-adresseformater.

Send et dokument med en Bitcoin-adresse, en Ethereum-adresse og en SWIFT-kode igennem et standardværktøj. Det finder SWIFT-koden. Det overser begge on-chain-adresser.

For en CASP, der behandler KYC-filer, er dette alvorligt. Disse identifikatorer er lige så følsomme som bankkontonumre. At overse dem betyder ingen kryptering, ingen maskering og intet revisionsspor.

Artikel 32 og krypteringskløften

GDPR artikel 32(1)(a) kræver pseudonymisering og kryptering som basale kontrolforanstaltninger. 56 % af alle GDPR-bøder nævner mangelfuld kryptering som en faktor. En børs, der krypterer al detekteret PII, men overser wallet-adresser, har ikke beskyttet kernen i sit arbejde.

Detektion skal dække det fulde identifikatorsæt. For en CASP inkluderer det disse adresseformater.

Hvad en compliant pipeline ser ud som

En compliant børs tilføjer disse entitetstyper til sit detektionstrin. Bitcoin- og Ethereum-formater er inkluderet. Adresserne markeres, krypteres og logges i ROPA'en side om side med IBAN-numre og kontonumre. DPIA'en navngiver hver dækket identifikatortype. MiCA-revisionsspor er afstemt med behandlingsregistre.

Der er ikke behov for en ny politik. Kløften er teknisk. At tilføje de rette entitetstyper til detektionstrinnet lukker den.

For tekniske foranstaltninger under artikel 32, se GDPR artikel 32 og AI-værktøjer til overvågning af PII-eksponering. For hvordan pseudonymisering fungerer i praksis, se EDPB 2025-retningslinjer for pseudonymisering.

Kilder

Relaterede Artikler

GDPR & Overholdelse

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 & Overholdelse

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 & Overholdelse

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.

Klar til at beskytte dine data?

Begynd at anonymisere PII med 285+ enhedstyper på tværs af 48 sprog.

Start Gratis PrøveperiodeSe Funktioner

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.