By · Last updated 2026-05-03

返回博客GDPR 与合规

MiCA与GDPR:加密钱包地址的个人信息检测

欧盟MiCA法规将加密货币钱包地址视为金融标识符。与个人关联的钱包地址适用GDPR,而标准个人信息工具完全无法识别这类地址格式。

May 3, 20268 分钟阅读
cryptocurrency PII GDPRMiCA complianceBitcoin wallet anonymizationSWIFT code detectionIBAN crypto fintech

MiCA、GDPR与加密货币钱包地址

比特币地址采用Base58Check编码,长度为26至35个字符,以「1」、「3」或「bc1」开头。以太坊地址以「0x」开头,后接40个十六进制字符。两者均具有假名性质,均不直接指向任何人。

但法律依然适用。

钱包地址何时成为个人数据

假名化记录一旦与真实人员关联,即构成个人数据。加密货币交易所持有KYC文件,将这些地址与已核实身份绑定。在交易所系统之外,该地址无从指向任何人;在系统内部,它对应着一位客户。这使其成为个人数据。

相关法规对其完整适用。

MiCA增加了第二层监管

欧盟MiCA法规(加密资产市场监管)于2024年12月正式生效,要求加密资产服务提供商(CASP)保护客户记录。欧洲交易所现在同时面临两套规则:MiCA设定金融控制要求,GDPR设定数据保护要求,两者均适用于同一标识符。

标准工具的检测缺口

标准个人信息工具为传统金融设计,了解IBAN、SWIFT/BIC代码和银行路由号码,却不了解加密货币地址格式。

将一份同时包含比特币地址、以太坊地址和SWIFT代码的文件通过标准工具处理,结果是:SWIFT代码被找到,两个链上地址均被遗漏。

对于处理KYC文件的CASP而言,这一缺口相当严重——这些标识符与银行账号同等敏感,遗漏意味着无加密、无脱敏、无审计日志。

第32条与加密缺口

GDPR第32条第1款(a)项要求将假名化和加密作为基础控制措施。56%的GDPR罚款将加密不足列为影响因素。如果一家交易所对所有检测到的个人信息进行了加密,却遗漏了钱包地址,等于在自身核心业务中没有任何实质性保护。

检测必须覆盖完整的标识符集合,对CASP而言,这个集合必须包含上述地址格式。

合规管道的构建方式

合规交易所将上述实体类型添加至检测步骤,涵盖比特币和以太坊格式。这些地址随即被标记、加密,并与IBAN和账号一同记录在ROPA中,DPIA列明每种受覆盖的标识类型,MiCA审计日志与处理记录保持一致。

无需调整任何政策,缺口属于技术层面,在检测步骤中添加正确的实体类型即可填补。

第32条技术措施详情请参阅GDPR第32条与AI工具监控个人信息暴露;假名化实践方法请参阅EDPB 2025假名化指南合规

参考资料

准备好保护您的数据了吗?

开始使用 285 种实体类型在 48 种语言中匿名化 PII。

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.