By · Last updated 2026-08-12

Home/Documentation/Nextcloud/Getting Started

Getting Started

Install Anonym Anonymizer and Anonym Files in Nextcloud, set the backend API URL, and connect an integration-scoped token to start redacting PII today.

1

Install both apps

The apps are not yet published to the Nextcloud App Store, so installation is manual — the same file-replace mechanics any Nextcloud app update uses.

  1. 1.Download the Anonym Anonymizer and Anonym Files app archives from the GitHub releases page.
  2. 2.Extract each archive into your Nextcloud instance's apps/ directory, replacing any existing files for that app.
  3. 3.Run occ upgrade as your Nextcloud admin (or occ app:enable anonym_anonymizer / anonym_files) so Nextcloud picks up the new app.
  4. 4.Enable both apps from the Nextcloud admin apps list.
2

Configure the backend API URL

Both apps talk to anonym.legal's API over a URL you configure in each app's personal settings. Use the correct host for your environment:

  • https://anonymize.business DEV: https://anonymize.business — the Nextcloud apps' default while this integration is dev-only.
  • https://anonym.legal Production: https://anonym.legal — switch to this host once the integration is live for your account.

A runtime-validated host allowlist (UrlGuard) rejects any other host, so the configured URL must be exactly one of these two — see Troubleshooting if a request is rejected.

3

Paste your integration-scoped token

Generate an integration-scoped API token from your anonym.legal account settings, then paste it into the app's personal settings alongside the backend API URL. Both apps share the same token configuration automatically when both are installed.

An integration-scoped token can analyze and anonymize content, but it cannot retrieve decrypted key material from your account — deliberately more limited than a full-account API token, so a compromised Nextcloud server can't be used to decrypt your reversible-encryption history.

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.