Simple, Transparent Pricing
Pay only for what you use. No hidden fees, no surprises.
Choose Your Plan
Free
Perfect for trying out
200 credits/cycle
30 days • No top-ups
Basic
For individuals
1,000 credits/cycle
31 days • Top-ups available
+250 units for €1
Pro
For professionals
4,000 credits/cycle
31 days • Top-ups available
+300 credits for €1
Business
For teams and enterprises
10,000 units/cycle
31 days • Top-ups available
+350 credits for €1
Complete Feature Comparison
| Feature | Free | Basic | Pro | Business |
|---|---|---|---|---|
| Tokens per month | 200 | 1,000 | 4,000 | 10,000 |
| Cycle length | 30 days | 31 days | 31 days | 31 days |
| Max batch size | 2 | 5 | 10 | 50 |
| Token top-ups | €1/250 | €1/300 | €1/350 | |
| API access | ||||
| MCP Server | ||||
| Public presets | ||||
| Priority support | ||||
| File Upload Limits | ||||
| Maximum file size | 1 MB | 5 MB | 10 MB | 20 MB |
| Files per batch | 2 | 5 | 10 | 20 |
| Daily uploads | 5 | 50 | Unlimited | Unlimited |
| Monthly uploads | 20 | 500 | Unlimited | Unlimited |
| Supported file types | TXT | PDF, DOCX, TXT, CSV | All types | All types |
Understanding Tokens
Think of credits like game coins. Each operation (analyzing or anonymizing text) costs units based on the text length, entities detected, and operations applied.
Typical Token Costs:
Short inputs hit a floor of ~4 tokens for analyze (base cost plus ~0.1 token per selected entity type). Above 1 000 characters at GUI defaults the cost scales at roughly 1 token per 312 characters. The exact cost is shown before every operation.
Anonymize click costs analyze + apply combined. Replace, redact, hash and mask all cost the same. Encrypt is more expensive because of the 0.8 × encryptCount term in the apply formula — roughly 3× at small inputs (~160 chars) and shrinking toward 1.2× at 50 000 chars where the per-character term dominates.
Important Notes:
• Tokens reset at the end of each cycle
• Unused credits do not accumulate
• Top-up credits expire at cycle reset
• AI Entity Creation costs 50 units per request
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.