入门指南

在您的 Nextcloud 环境中安装 Anonym Anonymizer 和 Anonym Files 这两款官方应用程序，设置好后端服务的 API URL 地址，并连接一个仅限本次集成使用的范围令牌，完成以上全部步骤后即可立即开始对文档中的 PII 个人身份信息进行有效匿名化处理，保障企业合规要求。

安装两款应用

这些应用尚未发布到 Nextcloud App Store，因此需要手动安装——采用与任何 Nextcloud 应用更新相同的文件替换方式。

1.从 GitHub releases 页面下载 Anonym Anonymizer 和 Anonym Files 的应用压缩包。
2.将每个压缩包解压到您 Nextcloud 实例的 apps/ 目录中，替换该应用已有的所有文件。
3.以 Nextcloud 管理员身份运行 occ upgrade（或 occ app:enable anonym_anonymizer / anonym_files），让 Nextcloud 识别新应用。
4.在 Nextcloud 管理员应用列表中启用这两款应用。

Download Anonymizer app Download Files app

配置后端 API URL

两款应用都通过您在各自个人设置中配置的 URL 与 anonym.legal 的 API 通信。请根据您的环境使用正确的主机：

https://anonymize.business DEV：https://anonymize.business ——在此集成仍处于仅限开发阶段时，是 Nextcloud 应用的默认地址。
https://anonym.legal 生产环境：https://anonym.legal ——一旦该集成对您的账户正式上线，请切换到此主机。

运行时校验的主机允许列表（UrlGuard）会拒绝任何其他主机，因此配置的 URL 必须恰好是以上两者之一——如果请求被拒绝，请参阅“故障排除”。

粘贴您的集成范围令牌

在您的 anonym.legal 账户设置中生成一个集成范围的 API 令牌，然后将其粘贴到应用的个人设置中，与后端 API URL 一起配置。两款应用同时安装时，会自动共享同一份令牌配置。

集成范围的令牌可以分析和匿名化内容，但无法从您的账户中获取解密后的密钥材料——其权限被有意限制得比完整账户 API 令牌更小，因此即便 Nextcloud 服务器被攻破，也无法用它解密您的可逆加密历史记录。

Manage API tokens

返回 Nextcloud 文档

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.