By George Curta · Last updated 2026-04-07
置換
検出されたPIIを文書の可読性を維持する現実的な偽データに置き換えます。
最適な用途：
- テスト環境
- デモデータ生成
- トレーニングデータセット
- 文書共有
例
削除
文書からPIIを完全に削除し、[REDACTED]のようなプレースホルダーに置き換えます。
最適な用途：
- 法的文書
- FOIAリクエスト
- 公共記録
- 裁判所の提出書類
例
ハッシュ（SHA-256）
文書間で一貫した擬似化を可能にする一方向の暗号ハッシュです。
最適な用途：
- 研究データ
- 分析
- 文書間リンク
- 擬似化
例
暗号化（AES-256-GCM）
認可されたユーザーが正しいキーで元のデータを復元できる可逆暗号化です。
最適な用途：
- 一時的な匿名化
- データ復元のニーズ
- 監査要件
- 可逆ワークフロー
例
マスク
PIIを部分的に隠しながら、参照のために一部の文字を可視化します。
最適な用途：
- カスタマーサポート
- 検証表示
- 部分的な可視性のニーズ
- ユーザーインターフェース
例
方法の比較
| 方法 | 可逆 | リンク可能 | 可読性 | 最適な用途 |
|---|---|---|---|---|
| 置換 | いいえ | いいえ | はい | テスト、デモ |
| 削除 | いいえ | いいえ | 部分的 | 法的、公共記録 |
| ハッシュ（SHA-256） | いいえ | はい | いいえ | 研究、分析 |
| 暗号化（AES-256-GCM） | はい | いいえ | いいえ | 一時的、監査 |
| マスク | 部分的 | いいえ | 部分的 | サポート、UI表示 |
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
- Common questions
- Glossary
- How tokens work
- Security posture
- Where we comply
- What we detect
- Case studies
- Release notes
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
- Open the web app and try a sample file.
- Learn how credits get counted.
- See current plans and limits.
- Meet the team behind the product.
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.