シンプルで透明な価格設定
使用した分だけお支払いください。隠れた手数料や驚きはありません。
Choose Your Plan
無料
試用に最適
200トークン/サイクル
30日 • トップアップなし
ベーシック
個人向け
1,000トークン/サイクル
31日 • トップアップ可能
+250トークンで€1
プロ
プロフェッショナル向け
4,000トークン/サイクル
31日 • トップアップ可能
+300トークンで€1
ビジネス
チームおよび企業向け
10,000トークン/サイクル
31日 • トップアップ可能
+350トークンで€1
完全な機能比較
| Feature | Free | Basic | Pro | Business |
|---|---|---|---|---|
| 月あたりのトークン | 200 | 1,000 | 4,000 | 10,000 |
| サイクルの長さ | 30 days | 31 days | 31 days | 31 days |
| 最大バッチサイズ | 2 | 5 | 10 | 50 |
| トークンのトップアップ | €1/250 | €1/300 | €1/350 | |
| APIアクセス | ||||
| MCPサーバー | ||||
| 公開プリセット | ||||
| 優先サポート | ||||
| ファイルアップロード制限 | ||||
| 最大ファイルサイズ | 1 MB | 5 MB | 10 MB | 20 MB |
| バッチあたりのファイル数 | 2 | 5 | 10 | 20 |
| 1日のアップロード | 5 | 50 | Unlimited | Unlimited |
| 月間アップロード | 20 | 500 | Unlimited | Unlimited |
| サポートされているファイルタイプ | TXT | PDF, DOCX, TXT, CSV | All types | All types |
トークンの理解
トークンはゲームコインのように考えてください。各操作(テキストの分析または匿名化)は、テキストの長さ、検出されたエンティティ、および適用された操作に基づいてトークンが必要です。
典型的なトークンコスト:
短いテキスト: 1-3トークン、中程度のテキスト: 3-5トークン、長いテキスト: 5-15トークン
匿名化は追加の操作により分析よりも若干高くなります
重要な注意事項:
• トークンは各サイクルの終了時にリセットされます
• 未使用のトークンは蓄積されません
• トップアップされたトークンはサイクルリセット時に失効します
• AIエンティティ作成はリクエストごとに50トークンが必要です
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.