By · Last updated 2026-08-12

Komdu í gang

Settu upp Anonym Anonymizer og Anonym Files í Nextcloud, stilltu vefslóð bakenda API-sins, og tengdu nýtt tákn til að byrja að ritskoða PII strax í dag.

1

Settu upp bæði forritin

Forritin eru ekki enn birt í Nextcloud App Store, svo uppsetning er handvirk — sömu skráaskiptaaðferðir og allar Nextcloud forritauppfærslur nota.

  1. 1.Sæktu Anonym Anonymizer og Anonym Files forritaskjalasöfnin af GitHub releases síðunni.
  2. 2.Pakkaðu hvoru skjalasafni út í apps/ möppu Nextcloud-uppsetningarinnar þinnar, og skiptu út öllum núverandi skrám fyrir það forrit.
  3. 3.Keyrðu occ upgrade sem Nextcloud stjórnandi (eða occ app:enable anonym_anonymizer / anonym_files) svo Nextcloud taki nýja forritið í notkun.
  4. 4.Virkjaðu bæði forritin úr stjórnendalista Nextcloud.
2

Stilltu bakenda API vefslóðina

Bæði forritin tala við API anonym.legal í gegnum vefslóð sem þú stillir í persónulegum stillingum hvors forrits. Notaðu rétta hýsilinn fyrir umhverfið þitt:

  • https://anonymize.business DEV: https://anonymize.business — sjálfgefið hjá Nextcloud forritunum meðan þessi samþætting er aðeins fyrir þróun.
  • https://anonym.legal Framleiðsla: https://anonym.legal — skiptu yfir í þennan hýsil þegar samþættingin er komin í notkun fyrir reikninginn þinn.

Keyrslutíma-staðfestur hýsingarleyfilisti (UrlGuard) hafnar öllum öðrum hýslum, svo stillta vefslóðin verður að vera nákvæmlega annar þessara tveggja — sjá Vandamál og algengar spurningar ef beiðni er hafnað.

3

Límdu inn samþættingartáknið þitt

Búðu til API-tákn með samþættingarumfangi í stillingum anonym.legal reikningsins þíns, og límdu það svo inn í persónulegum stillingum forritsins ásamt bakenda API vefslóðinni. Bæði forritin deila sömu táknstillingunni sjálfkrafa þegar bæði eru uppsett.

Samþættingartákn getur greint og nafnleynt efni, en getur ekki sótt dulkóðuð lykilgögn úr reikningnum þínum — vísvitandi takmarkaðra en fullt reikningstákn, svo Nextcloud þjónn í hættu er ekki hægt að nota til að afkóða afturkræfu dulkóðunarsöguna þína.

Manage API tokens

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.

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

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.