By George Curta · Last updated 2026-08-12
Iniziare
Installa Anonym Anonymizer e Anonym Files in Nextcloud, imposta l'URL API del backend e collega un token di integrazione per redigere i PII oggi stesso.
Installa entrambe le app
Le app non sono ancora pubblicate sul Nextcloud App Store, quindi l'installazione è manuale — la stessa meccanica di sostituzione file usata per qualsiasi aggiornamento di un'app Nextcloud.
- 1.Scarica gli archivi delle app Anonym Anonymizer e Anonym Files dalla pagina delle release GitHub.
- 2.Estrai ogni archivio nella directory apps/ della tua istanza Nextcloud, sostituendo eventuali file esistenti per quell'app.
- 3.Esegui occ upgrade come amministratore Nextcloud (oppure occ app:enable anonym_anonymizer / anonym_files) così Nextcloud rileva la nuova app.
- 4.Abilita entrambe le app dall'elenco delle app dell'amministratore Nextcloud.
Configura l'URL API del backend
Entrambe le app comunicano con l'API di anonym.legal tramite un URL che configuri nelle impostazioni personali di ciascuna app. Usa l'host corretto per il tuo ambiente:
https://anonymize.businessDEV: https://anonymize.business — l'impostazione predefinita delle app Nextcloud finché questa integrazione è solo per sviluppo.https://anonym.legalProduzione: https://anonym.legal — passa a questo host una volta che l'integrazione è live per il tuo account.
Una lista consentita di host validata a runtime (UrlGuard) rifiuta qualsiasi altro host, quindi l'URL configurato deve essere esattamente uno di questi due — vedi Risoluzione dei Problemi se una richiesta viene rifiutata.
Incolla il tuo token con ambito di integrazione
Genera un token API con ambito di integrazione dalle impostazioni del tuo account anonym.legal, quindi incollalo nelle impostazioni personali dell'app insieme all'URL API del backend. Entrambe le app condividono automaticamente la stessa configurazione del token quando sono entrambe installate.
Un token con ambito di integrazione può analizzare e anonimizzare contenuti, ma non può recuperare materiale chiave decrittato dal tuo account — deliberatamente più limitato di un token API dell'intero account, così un server Nextcloud compromesso non può essere usato per decrittare la tua cronologia di crittografia reversibile.
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.