Tarification Simple et Transparente
Payez uniquement pour ce que vous utilisez. Pas de frais cachés, pas de surprises.
Choose Your Plan
Gratuit
Parfait pour essayer
200 tokens/cycle
30 jours • Pas de recharges
Basique
Pour les particuliers
1 000 tokens/cycle
31 jours • Recharges disponibles
+250 tokens pour 1 €
Pro
Pour les professionnels
4 000 tokens/cycle
31 jours • Recharges disponibles
+300 tokens pour 1 €
Entreprise
Pour les équipes et les entreprises
10 000 tokens/cycle
31 jours • Recharges disponibles
+350 tokens pour 1 €
Comparaison Complète des Fonctionnalités
| Feature | Free | Basic | Pro | Business |
|---|---|---|---|---|
| Tokens par mois | 200 | 1,000 | 4,000 | 10,000 |
| Durée du cycle | 30 days | 31 days | 31 days | 31 days |
| Taille maximale du lot | 2 | 5 | 10 | 50 |
| Recharges de tokens | €1/250 | €1/300 | €1/350 | |
| Accès API | ||||
| Serveur MCP | ||||
| Préréglages publics | ||||
| Support prioritaire | ||||
| Limites de Téléchargement de Fichiers | ||||
| Taille maximale de fichier | 1 MB | 5 MB | 10 MB | 20 MB |
| Fichiers par lot | 2 | 5 | 10 | 20 |
| Téléchargements quotidiens | 5 | 50 | Unlimited | Unlimited |
| Téléchargements mensuels | 20 | 500 | Unlimited | Unlimited |
| Types de fichiers pris en charge | TXT | PDF, DOCX, TXT, CSV | All types | All types |
Comprendre les Tokens
Considérez les tokens comme des pièces de jeu. Chaque opération (analyser ou anonymiser du texte) coûte des tokens en fonction de la longueur du texte, des entités détectées et des opérations appliquées.
Coûts Typiques en Tokens :
Texte court : 1-3 tokens, texte moyen : 3-5 tokens, texte long : 5-15 tokens
L'anonymisation coûte légèrement plus cher que l'analyse en raison d'opérations supplémentaires
Notes Importantes :
• Les tokens se réinitialisent à la fin de chaque cycle
• Les tokens non utilisés ne s'accumulent pas
• Les tokens de recharge expirent lors de la réinitialisation du cycle
• La création d'entités IA coûte 50 tokens par demande
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.