By George Curta · Last updated 2026-04-27
在 LibreOffice Writer、Calc 和 Impress 中匿名化
开源办公套件，企业级隐私。我们的原生 LibreOffice 扩展为 Writer、Calc 和 Impress 带来 PII 检测和匿名化功能。
在整个 LibreOffice 中工作
一个扩展用于 Writer 文档、Calc 电子表格和 Impress 演示文稿。完整的侧边栏集成，支持格式保留。
LibreOffice Writer
Documents, contracts, reports — with full format preservation
LibreOffice Calc
Spreadsheets, data tables — cell-based processing
LibreOffice Impress
Presentations, slides — text object extraction
主要优势
原位工作
无需复制粘贴。直接在 LibreOffice 中通过集成的侧边栏面板进行匿名化。
格式保留
Writer 文档保留所有格式 - 粗体、斜体、字体、颜色、段落样式。仅文本内容更改。
安全处理
文档保留在您的机器上。仅文本被发送到我们的加密 API 进行实体检测和匿名化。
核心功能
PII 检测
- 检测 285+ 种实体类型（名称、电子邮件、SSN、IBAN、信用卡等）
- 混合检测：正则表达式模式 + NLP 实现最大准确性
- 多语言支持（48 种语言，包括 RTL）
- 自定义实体识别，支持正则表达式或拒绝列表
匿名化方法
- 5 种方法：替换、掩蔽、编辑、哈希 (SHA-256)、加密 (AES-256-GCM)
- 使用 ZK 包装的个人密钥进行可逆加密
- 按实体运算符配置（每种实体类型使用不同方法）
- 分块处理（8,000 字符块）用于大型文档
高级功能
预览对话框
在匿名化之前查看最多 50 个检测到的实体。选择、取消选择或为每个实体更改方法后再提交。
预设
保存并重复使用匿名化设置。预设在所有设备之间同步，包括实体类型、方法和分数阈值。
可逆加密
使用 AES-256-GCM 加密 PII 并稍后解密。ZK 包装的密钥从您的帐户自动加载，具有会话持久性。
按实体运算符
为每种实体类型配置不同的匿名化方法。哈希名称、加密电子邮件、掩蔽电话号码 - 一次完成。
跨设备同步
预设、自定义实体和加密密钥通过您的帐户每 5 分钟在所有设备间同步。
48 种语言
完整的多语言支持，包括阿拉伯语、希伯来语、中文、日语和韩语。完全支持 RTL 语言。
文档支持
Writer
完整的文本提取、基于选择的处理和格式保留（7 个字体 + 4 个段落属性）。
Calc
基于单元格的处理，制表符分隔的文本提取。处理整个工作表或选定范围。
Impress
幻灯片文本对象处理。从所有幻灯片中的所有形状和文本框提取和匿名化文本。
系统要求
在 Windows、macOS 和 Linux 上与 LibreOffice 3.0 或更高版本兼容。
支持的平台
- • LibreOffice Writer 3.0+ (Windows, macOS, Linux)
- • LibreOffice Calc 3.0+ (Windows, macOS, Linux)
- • LibreOffice Impress 3.0+ (Windows, macOS, Linux)
您需要什么
- • Python 3.10+（在大多数平台上与 LibreOffice 一起打包）
- • anonym.legal 帐户（免费或付费）
- • 用于 API 访问的互联网连接
- • PyNaCl（可选，用于 ZK 身份验证和加密方法）
常见问题
支持哪些 LibreOffice 应用程序？
Writer、Calc 和 Impress。Writer 具有完整的功能支持，包括格式保留。Calc 将单元格作为制表符分隔的文本进行处理。Impress 从幻灯片对象中提取文本。
如何安装扩展程序？
下载 .oxt 文件，双击它，或在 LibreOffice 中转到「工具」>「扩展管理器」>「添加」。或者，从源目录运行 python3 build.py --install。
它保留文档格式吗？
可以，在 Writer 文档中。该扩展保留 7 个字体属性（粗体、斜体、下划线、删除线、字体名称、大小、颜色）和 4 个段落属性（对齐、首行缩进、左边距、右边距）。
什么是零知识身份验证？
ZK 身份验证意味着您的密码永远不会离开您的设备。相反，使用 XChaCha20-Poly1305 加密和 Argon2id 密钥派生向我们的服务器发送密码学证明。可选 - 也支持标准电子邮件/密码登录。
我可以离线使用它吗？
不行。扩展程序需要互联网连接以与 anonym.legal API 通信进行实体检测和匿名化。要离线使用，请参阅 anonym.plus。
From the Blog
View all articlesMixed Format E-Discovery: Compliance Gap
E-discovery productions and GDPR DSARs span PDFs, Word docs, Excel, and JSON exports. Using different tools for each format creates consistency gaps that.
The PDF Redaction Trap: Data Exposed
The DOJ Epstein files, the Manafort case, and NSA leaks all share the same failure: cosmetic redaction that leaves underlying text extractable.
Legal PII: Privilege Detection
Case reference numbers, bar admission numbers, court docket numbers, and client matter IDs are legally sensitive identifiers that standard PII tools miss.
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
- Common questions
- Glossary
- How tokens work
- Security posture
- Where we comply
- What we detect
- Case studies
- Release notes
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 servers live in Falkenstein, Germany.
We use Hetzner. They hold 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.