By George Curta · Last updated 2026-07-24
LibreOffice 扩展入门指南
安装 anonym.legal 扩展,登录账户,并在 LibreOffice Writer、Calc 或 Impress 中运行首次 PII 匿名化。
快速安装(推荐)
- 1.点击上方下载按钮获取 .oxt 文件。
- 2.双击已下载的 .oxt 文件。
- 3.LibreOffice 将自动打开并提示安装。
- 4.出现提示时重启 LibreOffice。
手动安装
- 1.在 LibreOffice 中,前往「工具」→「扩展管理器」。
- 2.点击「添加」并选择已下载的 .oxt 文件。
安装后重启 LibreOffice 以激活扩展。
打开侧边栏
安装后,打开 anonym.legal 侧边栏面板。
前往「视图」→「侧边栏」,然后点击 anonym.legal 面板图标。
侧边栏面板显示在文档右侧。您可以拖动边缘调整其大小。
登录您的账户
输入您的 anonym.legal 凭据进行身份验证。
启用零知识身份验证以获得最大保护。您的密码永远不会发送到服务器——仅发送使用 Argon2id 派生的加密证明(64 MB 内存,3 次迭代,并行度=1)。
还没有账户? 创建免费账户 并获得 200 个免费额度以开始使用。
您的会话持续 60 分钟。凭据在本地缓存 7 天,以便快速重新验证。
分析您的文档
选择范围并对文档运行 PII 检测。
- 选择范围:整个文档或当前所选内容
- 自动检测 267 种以上实体类型
- 支持 48 种语言并自动检测
在 Calc 中,分析将单元格内容处理为制表符分隔的文本。在 Impress 中,处理来自所有幻灯片对象的文本。
选择匿名化方法
根据您的使用场景从 5 种匿名化方法中选择一种。
将 PII 替换为类型化标记,如 <PERSON_1>、<EMAIL_ADDRESS_1>。在文档中保持一致。
用星号替换字符同时保留格式。适用于显示部分数据,如最后 4 位数字。
完全删除 PII 并替换为 [REDACTED]。不可逆——原始数据无法恢复。
对 PII 生成加密哈希值。相同输入始终产生相同哈希值,便于跨文档关联。
使用 AES-256-GCM 加密 PII。凭借正确的密钥,可以解密并还原原始数据。
预览与应用
在应用更改前,在预览对话框中检查检测到的实体。
- 预览对话框以表格形式显示最多 50 个检测到的实体
- 应用前可选择或取消选择单个实体
- 使用实体级运算符为每种实体类型选择不同的方法
点击「应用」对文档进行匿名化。如需撤销,请使用 Ctrl+Z(macOS 上为 Cmd+Z)。
使用技巧与最佳实践
- 在应用前,请务必使用预览对话框检查检测结果。您可以取消选择误报。
- 应用匿名化后,可立即使用 Ctrl+Z(macOS 上为 Cmd+Z)撤销。
- 将常用配置保存为预设,以便在文档间快速复用。
- 格式保留仅在 Writer 中有效——将保留粗体、斜体、下划线、字体大小、字体名称、颜色和高亮。
- 对于大型文档,请使用选择模式分段处理以保证准确性。
- 文档以每块 8,000 个字符、400 个字符重叠的方式分块处理,确保不遗漏边界处的实体。
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.
- 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
We run a full check suite on every release.
Each surface gets its own sweep script and report.
Human reviewers spot-check the output each week.
We track recall and precision on a labelled set.
Bad runs block the deploy.
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.
You can top up at any time.
Unused credits roll over each month.
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.