By · Last updated 2026-03-10

Back to BlogGDPR & Compliance

Open-Source Anonymization: LibreOffice

How public sector organizations use LibreOffice with anonym.legal's extension for GDPR-compliant document anonymization.

March 10, 20269 min read
LibreOffice extensiongovernment anonymizationpublic sector GDPRopen source complianceuniversity data protection

The Public Sector LibreOffice Mandate

Across the European Union, government agencies are increasingly mandating open-source software. Italy, France, Germany, and Spain have formal policies favoring open-source alternatives. The European Commission's Open Source Software Strategy 2020-2023 explicitly promotes open-source adoption. Germany's Schleswig-Holstein announced migration of 25,000 government PCs to LibreOffice in 2024. The French Gendarmerie deployed GendBuntu (Ubuntu with LibreOffice) on over 77,000 workstations.

These organizations need GDPR-compliant document anonymization — but most PII redaction tools only support Microsoft Office.

anonym.legal's LibreOffice Extension fills this gap: the same 285+ entity type detection available in Writer, Calc, and Impress, on Windows, macOS, and Linux.

Why Open Source Matters for Data Protection

No vendor lock-in

Microsoft Office requires ongoing licensing (Microsoft 365 subscriptions). LibreOffice is free. For government agencies with thousands of desktops, this represents significant budget savings — but the decision often goes beyond cost.

Open-source software provides transparency: the source code is auditable. For agencies processing citizen data, the ability to inspect the tools they use is a governance requirement, not a preference.

Data sovereignty

Government agencies handling citizen data face strict data residency requirements. anonym.legal's infrastructure runs on Hetzner servers in Germany — data never leaves EU jurisdiction. Combined with LibreOffice (no Microsoft cloud dependencies), the entire document workflow stays within controlled environments.

GDPR Article 25: Data protection by design

GDPR Article 25 requires data protection by design and by default. Using PII anonymization tools integrated directly into the document editing workflow — rather than external copy-paste processes — is a stronger "by design" implementation. The anonymization step is part of the document lifecycle, not an afterthought.

Real-World Use Cases

Government DSAR Responses

When citizens submit Data Subject Access Requests (DSARs), agencies must provide copies of all personal data held — but must redact third-party PII (other citizens, staff names, case officers).

With the LibreOffice Extension:

  1. Open the response document in Writer
  2. Click Analyze to detect all PII
  3. Review in the preview dialog — accept third-party entities, reject the requester's data
  4. Apply anonymization
  5. Export and send

The preview dialog is critical here: DSARs require selective redaction (remove staff names, keep the requester's data), not blanket anonymization.

University Research Data

Research institutions processing study participant data must anonymize before publication or data sharing. The typical workflow:

  1. Collected data in spreadsheets (Calc) with participant names, IDs, contact information
  2. Interview transcripts in Writer with participant quotes containing identifying details
  3. Presentation slides (Impress) for conferences with case study data

The LibreOffice Extension handles all three document types with the same detection engine. Presets ensure consistent anonymization across the entire research dataset.

Court Document Redaction

Courts publishing decisions must redact party names, addresses, and identifying information. The LibreOffice Extension supports:

  • Replace: Party names to PERSON_1, PERSON_2 (maintaining referential consistency within the document)
  • Redact: Complete removal of addresses and contact details
  • Mask: Partial masking of dates or case numbers where context must be preserved

Format preservation in Writer ensures that court document formatting — headers, footers, numbered paragraphs, indentation — remains intact after redaction.

Deployment in Public Sector Environments

Individual installation

For small teams or individual users:

  1. Download .oxt from anonym.legal/api/download/libreoffice
  2. Double-click to install
  3. Restart LibreOffice

Centralized deployment

For IT departments managing multiple workstations:

  • Distribute the .oxt file via network share, SCCM, Ansible, or similar
  • LibreOffice accepts silent extension installation via command line
  • Presets can be standardized across the organization via shared anonym.legal accounts

Authentication

The extension supports zero-knowledge authentication — passwords are derived locally using Argon2id and never transmitted. For organizations requiring SSO integration, the web app provides an alternative access point with the same detection capabilities.

Compliance Mapping

RequirementHow It's Met
GDPR Article 5(1)(c) — Data minimizationOnly detected PII is modified; non-PII text unchanged
GDPR Article 25 — Data protection by designAnonymization integrated into document editing workflow
GDPR Article 32 — Security of processingAES-256-GCM encryption, ZK auth, ISO 27001 infrastructure
GDPR Recital 26 — Anonymization scopeReplace/Redact/Mask remove data from GDPR scope
GDPR Article 4(5) — PseudonymizationEncrypt method provides reversible pseudonymization
BDSG Section 22 — Special categoriesEntity type detection covers health, biometric, and ethnic data

Getting Started for Public Sector

  1. Download the extension — free, no licensing
  2. Create an anonym.legal account — free tier includes 200 tokens/month
  3. Review full documentation — installation, features, troubleshooting

For organizations requiring higher volumes, paid plans start at EUR 3/month for 1,000 tokens.

Sources:

  • European Commission Open Source Software Strategy 2020-2023
  • Schleswig-Holstein, Germany — 25,000 government PC migration to LibreOffice (2024 announcement)
  • French Gendarmerie — 77,000+ GendBuntu (Ubuntu/LibreOffice) workstations deployed by 2019
  • GDPR Articles 4(5), 25, 32, Recital 26 — compliance framework
  • BDSG Section 22 — German Federal Data Protection Act special categories

Ready to protect your data?

Start anonymizing PII with 285+ 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.

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

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.