Back to BlogTechnical

LibreOffice PII Anonymization Extension

Step-by-step guide to anonymizing PII in LibreOffice Writer, Calc, and Impress with the anonym.legal extension—267+ entity types, formatting preserved.

March 10, 202610 minute read
LibreOffice extensiondocument anonymizationPII redactionopen source officeWriter anonymizationformat preservation

LibreOffice PII Anonymization Extension

LibreOffice has an estimated 200 million users worldwide. Governments, schools, and businesses all rely on it. Many use it to avoid costly software licenses. But until now, users had no built-in tool to find and remove personal data from their files.

The old fix was painful. Copy text into a web app. Anonymize it. Paste it back. This kills formatting. It breaks tables, styles, and layout. For complex Writer documents, this does not work.

The anonym.legal extension solves this. It works inside the app. It detects 267+ entity types in Writer, Calc, and Impress.

Install in Under Two Minutes

The extension ships as an .oxt file. This is the standard format for all extensions.

Quick Install:

  1. Download the .oxt from anonym.legal/api/download/libreoffice
  2. Double-click the file
  3. Confirm the prompt
  4. Restart

Manual Install:

  1. Open the application
  2. Go to Tools, then Extension Manager
  3. Click Add, then pick the .oxt file
  4. Restart

After restart, the anonym.legal sidebar shows under View, then Sidebar. Sign in to begin.

How Detection Works

Two engines run together to find PII.

EngineFindsConfidence
RegexEmails, SSNs, IBANs, credit cards, phone numbers1.0
spaCy NLPNames, organizations, locations0.85+

Detection runs on the anonym.legal API. Text goes to certified servers in Germany. The servers hold ISO 27001 status. Results return to the extension. No document files are sent. Only text is transmitted.

What each app does:

  • Writer: Extracts full text or selection only
  • Calc: Reads cells as tab-separated values across all sheets
  • Impress: Reads text objects from all slides

Five Anonymization Methods

MethodExampleCan reverse?GDPR class
ReplaceJohn Smith → PERSONNoAnonymization (Recital 26)
Maskjohn@example.com → j***@e***.comNoAnonymization
Redact555-0123 → [REDACTED]NoAnonymization
Hash (SHA-256/512)SSN → a1b2c3d4...NoPseudonymization (WP29)
Encrypt (AES-256-GCM)Name → ENC:xyz...YesPseudonymization (Art. 4(5))

You can mix methods in one pass. Replace names, but encrypt emails. Each entity type gets its own rule.

Format Stays Intact in Writer

This is the key win over copy-paste. The extension keeps all formatting when it replaces text.

Seven font properties preserved:

  • Family, size, bold, italic, color, underline, strikethrough

Four paragraph properties preserved:

  • Alignment, first-line indent, left margin, right margin

"John Smith" in bold 14pt Times New Roman becomes "PERSON" in the same style. Tables, headers, and footers all stay intact. The extension works inside the document model. It does not export and reimport text.

Note: Format tracking only applies to Writer. Calc and Impress do text-level replacement only.

Review Before You Apply

The preview shows up to 50 found entities. Each row shows:

  • Entity type (PERSON, EMAIL_ADDRESS, PHONE_NUMBER, etc.)
  • Original text
  • Proposed replacement
  • Confidence score

Accept or reject each entity one by one. Select all or clear all with one click. Nothing changes until you click Apply. In Writer, Ctrl+Z undoes the last operation.

Presets Sync Across Devices

Save your settings as a preset. Pick entity types, methods, and thresholds. Reuse it across all your documents. It saves time.

On paid plans, presets sync across all anonym.legal products. Set one up in the web app. It appears in the desktop app and the Office Add-in within five minutes. Encryption keys use zero-knowledge wrapping. Only your password can decrypt them.

For more on how the Office Add-in handles the same workflow in Word, see Word Add-in Redaction for Law Firms.

LibreOffice vs. Microsoft Office

Both extensions share the same backend. The same text gives the same results in Writer and in Word. The engine is one and the same.

FeatureLibreOffice ExtensionOffice Add-in
Entity types267+267+
Languages4848
Methods55
Format trackingWriter onlyWord only
PreviewUp to 50 entitiesUp to 50 entities
ZK authYesYes
Preset syncYes (paid plans)Yes (paid plans)
PlatformsWindows, macOS, LinuxWindows, Mac, Web, iPad

For a broader look at PII compliance across operating systems, see Cross-Platform PII Compliance: Mac, Linux, Windows.

System Requirements

  • LibreOffice 3.0 or later
  • Python 3 (bundled with most installs)
  • Internet access (for the PII detection API)
  • anonym.legal account (free tier: 200 tokens/month)

Get Started

  1. Download the extension
  2. Double-click to install, then restart
  3. Open View → Sidebar → anonym.legal panel
  4. Sign in
  5. Open a document, click Analyze, review, click Apply

Full docs: LibreOffice Extension Docs

When This Approach Has Limits

Working inside the document model to preserve formatting is what makes this extension better than copy-paste, and that design is sound, but limits remain worth stating plainly.

Detection accuracy bounds the result. The two engines find what they are trained to find. Regex catches structured patterns like emails and IBANs with high confidence, but spaCy NLP scores names, organizations, and locations at 0.85 and above, which means borderline cases fall below threshold and slip through. A name written in an unusual form, a misspelled location, or a free-text note can be missed entirely. The preview shows up to 50 entities, so longer documents with more matches still require you to verify that nothing was overlooked before you apply changes.

Format preservation is Writer-only. The seven font and four paragraph properties are tracked in Writer through the UNO model, but Calc and Impress do plain text-level replacement. A spreadsheet anonymized through this extension keeps no record of cell styling decisions, and quasi-identifiers spread across columns, such as postcode plus birthdate plus role, can re-identify a person even after direct identifiers are gone. The output may be pseudonymized rather than truly anonymized, which carries legal consequences worth understanding before sharing.

Encrypt mode keeps data in legal scope. The Hash and Encrypt methods are pseudonymization under GDPR Article 4(5), not anonymization. Encrypted values remain reversible with your key, so the data stays inside GDPR scope and the burden simply shifts to protecting that key custody. The extension supports your compliance workflow but does not constitute compliance on its own. A human still has to choose the right method per entity type, confirm the preview, and judge whether the shared copy meets the legal standard the situation demands.

Sources

  • The Document Foundation — estimated 200M+ LibreOffice users worldwide
  • anonym.legal PII Detection Testing — 95.5% accuracy, 42/44 independent tests
  • GDPR Recital 26 — anonymization removes data from GDPR scope; Article 4(5) — pseudonymization definition

Limitations / When this doesn't apply

Working inside the document model preserves formatting, but detection accuracy bounds the result. Regex catches structured patterns like emails and IBANs with high confidence; spaCy NLP scores names, organizations, and locations at 0.85 and above, so borderline cases fall below threshold and slip through. A name in an unusual form, a misspelled location, or a free-text note can be missed entirely, and the preview shows up to 50 entities, so longer documents still need verification before you apply changes.

Format preservation is Writer-only. Calc and Impress do plain text-level replacement, and clearing direct identifiers from cells leaves quasi-identifiers — postcode plus birthdate plus role — that can re-identify a person, so spreadsheet output is often pseudonymized rather than truly anonymized.

The Hash and Encrypt methods are pseudonymization under GDPR Article 4(5): encrypted values stay reversible with your key, so the data remains in legal scope and the burden shifts to key custody. The extension supports your workflow but does not constitute compliance; a human still chooses the method per entity, confirms the preview, and judges whether the shared copy meets the legal standard. This is general guidance, not legal advice.

Ready to protect your data?

Start anonymizing PII with 267+ entity types across 48 languages.

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.
  • 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

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.