By George Curta · Last updated 2026-08-12
Kom Igång
Installera Anonym Anonymizer och Anonym Files i Nextcloud, ange backend-API-URL:en och anslut en integrationsavgränsad token för att maskera PII idag.
Installera båda apparna
Apparna är ännu inte publicerade i Nextcloud App Store, så installationen sker manuellt — samma filutbytesmekanik som varje Nextcloud-appuppdatering använder.
- 1.Ladda ned apparkiven för Anonym Anonymizer och Anonym Files från GitHub releases-sidan.
- 2.Extrahera varje arkiv till din Nextcloud-instans apps/-katalog, och ersätt eventuella befintliga filer för den appen.
- 3.Kör occ upgrade som din Nextcloud-administratör (eller occ app:enable anonym_anonymizer / anonym_files) så att Nextcloud upptäcker den nya appen.
- 4.Aktivera båda apparna från Nextclouds admin-applista.
Konfigurera backend-API-URL:en
Båda apparna talar med anonym.legals API över en URL du konfigurerar i varje apps personliga inställningar. Använd rätt värd för din miljö:
https://anonymize.businessDEV: https://anonymize.business — Nextcloud-apparnas standard medan denna integration bara är för utveckling.https://anonym.legalProduktion: https://anonym.legal — växla till denna värd när integrationen är aktiv för ditt konto.
En körningsvaliderad tillåtelselista för värdar (UrlGuard) avvisar alla andra värdar, så den konfigurerade URL:en måste vara exakt en av dessa två — se Felsökning om en förfrågan avvisas.
Klistra in din integrationsavgränsade token
Skapa en integrationsavgränsad API-token i dina anonym.legal-kontoinställningar, och klistra sedan in den i appens personliga inställningar tillsammans med backend-API-URL:en. Båda apparna delar samma tokenkonfiguration automatiskt när båda är installerade.
En integrationsavgränsad token kan analysera och anonymisera innehåll, men kan inte hämta dekrypterat nyckelmaterial från ditt konto — medvetet mer begränsad än en fullständig kontotoken för API:et, så en komprometterad Nextcloud-server kan inte användas för att dekryptera din historik för reversibel kryptering.
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, held by our hosting provider.
- 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 company HQ is in Saarbrücken, Germany. Our servers run in Hetzner's Falkenstein datacenter.
Hetzner holds 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
Automated checks run on every release.
Each surface gets its own sweep script and report.
Human reviewers spot-check the output each week.
We test detection against sample documents before each release.
A failing unit or integration run stops the release.
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.
Paid plans can buy top-up credits.
Credits reset at the end of each cycle.
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.