By · Last updated 2026-08-12

直接在 Nextcloud 中匿名化 PII

两款配套应用将 anonym.legal 的 PII 检测与匿名化功能带入您的 Nextcloud 实例:一个用于文本与文件分析的整页编辑器,以及一个用于右键匿名化的文件侧边栏标签页。需要 Basic 或更高级别的 anonym.legal 账户。

两款配套应用

根据您的工作方式,安装其中一款或两款均可。

Anonym Anonymizer

一款独立应用,提供整页界面用于文本与文件分析。使用文件选择器从 Nextcloud 中选取任意文本文件,在保存前预览匿名化内容,并可从 6 种匿名化方法(替换、掩码、删除、哈希、保留、加密)中进行选择。

Anonym Files

直接在 Nextcloud Files 中添加右键菜单的“使用 anonym.legal 匿名化”操作和一个侧边栏标签页,提供完整的分析 / 匿名化 / 去匿名化工作流程。如果同时安装了 Anonym Anonymizer,Anonym Files 会自动共享其 API 密钥配置。

安装

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

  1. 1从 GitHub releases 页面下载您需要的应用压缩包。
  2. 2将压缩包解压到您 Nextcloud 实例的 apps/ 目录中。
  3. 3以 Nextcloud 管理员身份运行 occ upgrade(或 occ app:enable anonym_anonymizer / anonym_files),让 Nextcloud 识别新应用。
  4. 4在 Nextcloud 管理员应用列表中启用该应用,然后在应用的个人设置中配置您的 anonym.legal API 令牌。

集成范围的 API 令牌——设计上更安全

两款应用都使用集成范围的 API 令牌向 anonym.legal 进行身份验证,而不是您的完整账户令牌。集成令牌可以分析和匿名化文本与文件,但无法获取解密后的密钥材料——因此,即使其所在的 Nextcloud 服务器被攻破,攻击者也无法用该令牌解密您的可逆加密历史记录。可从您的 anonym.legal 账户设置中生成该令牌。

管理 API 令牌

需要 Basic 或更高级别的计划

两款 Nextcloud 应用都需要 Basic 或更高级别的 anonym.legal 账户。免费计划不包含这些应用所依赖的 API 访问权限。

查看价格

兼容性

  • Nextcloud 28 至 31
  • PHP 8.1 或更高版本

手动升级提醒,而非自动更新

两款应用都会定期检查新版本,如有新版本会显示一条简单的管理员提醒,并附带更新日志链接。不会自动安装任何内容——升级始终采用本页所述的手动文件替换和 occ upgrade 步骤,由您的 Nextcloud 管理员按您自己的计划执行。

常见问题

是否需要同时安装两款应用?

不需要。您可以安装 Anonym Anonymizer 以使用整页编辑器,安装 Anonym Files 以在 Nextcloud Files 中使用右键/侧边栏匿名化功能,或者两款都安装——同时安装时,它们会自动共享您的 API 令牌配置。

这些应用是否在 Nextcloud App Store 中?

尚未上架。请从 GitHub releases 页面手动安装,使用标准的 Nextcloud 文件替换和 occ upgrade 步骤,与任何非 App Store 的 Nextcloud 应用的安装和更新方式相同。

这些应用会自动更新吗?

不会。当有新版本可用时,应用会显示手动升级提醒,并附带更新日志链接。何时安装由您的 Nextcloud 管理员决定,安装步骤与初次安装相同,均为手动操作。

这些应用使用的 API 令牌存储在共享的 Nextcloud 服务器上是否安全?

这是一个集成范围的令牌,其权限被有意限制得比您的完整账户 API 令牌更小:它可以分析和匿名化内容,但无法像完整账户令牌那样从您的账户中获取解密后的密钥材料。

支持哪些 Nextcloud 版本?

Nextcloud 28 至 31,需要 PHP 8.1 或更高版本。

准备好在 Nextcloud 中匿名化 PII 了吗?

下载应用,安装到您的实例上,并连接您的 anonym.legal 账户。

从 GitHub Releases 下载

Limitations / Important note

  • These apps are not distributed through the Nextcloud App Store; install and upgrade them manually via the GitHub releases page and occ upgrade.
  • The version-check notice is manual-upgrade only — nothing installs automatically on your Nextcloud instance.
  • This page is informational and is not legal advice.

How we measure — our methodology

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.