Resources
Practical guides, examples and checklists for anonymising documents and complying with the General Data Protection Regulation.
Artificial intelligence increases the risk of re-identification. Anonymising before publishing, handing over or uploading a document to AI is the practical way to apply GDPR data minimisation.
A clear definition of anonymising and anonymised data, with examples, techniques and the mistakes that turn anonymisation into mere pseudonymisation.
Metadata exposes the author, the machine and the file history. How to check and strip it before you publish a PDF.
A black rectangle redacts nothing — the text stays underneath and can be copied. Here is how to truly redact a PDF before publishing it.
The question is not whether to anonymize everything, but whether you need to know the identity for the intended use. A guide by document type plus a checklist.
Pseudonymisation reduces re-identification risk but does not remove the personal-data status. Learn how to apply it correctly and when to move to full anonymisation.
Anonymizing is irreversible and removes the document from GDPR scope. Pseudonymizing is reversible and remains personal data. A practical guide.
Fines of thousands of euros, warnings and corrective measures: how the AEPD acts when documents are published without anonymization and the real cases that show it.
Cover with a rectangle, forget the metadata, publish the original in the same folder… The 10 most common mistakes when anonymizing and how to avoid them.
Publishing council minutes with names, IDs or addresses can end in a DPA case. A practical guide to anonymizing them properly.
Fines, warnings and corrective measures: four real AEPD cases showing what happens when a document is published or shared without being anonymised.
Name and ID are only the start. Here's the full list of personal data you must remove before publishing any document.
An internal notice board isn't a security measure. We analyse decision PS/00447/2023 and the recurring mistakes when publishing labour documentation without anonymisation.
A .docx stores much more than you see: tracked changes, comments, authors, versions. A guide to anonymizing Word with no trace left behind.
Municipal transparency doesn't authorise publishing any personal data. The Los Alcázares case shows why every set of minutes must be reviewed before disclosure.
A black rectangle isn't enough. Learn how to anonymize a PDF by also stripping the text layer, metadata and images that leak personal data.
A public ruling doesn't turn the national ID into freely disclosable data. We analyse decision A/00040/2011 and how to prepare a ruling before publishing it.
An unreviewed attachment can turn an internal communication into a disclosure of specially sensitive data. Decision PA/00041/2025 shows why.
A public authority can breach the GDPR without receiving a financial fine. We analyse the regime under article 77 of the LOPDGDD and the measures the AEPD can still impose.
Proper anonymisation isn't a black marker. We cover what the GDPR requires, how it differs from pseudonymisation and which techniques actually eliminate re-identification risk.
Drawing black rectangles isn't anonymising. We show how to anonymise a PDF by removing text, metadata and images, and how to verify it before publishing.
Choosing software to anonymize documents isn't just about price. We cover the criteria DPOs and compliance teams use to get it right in 2026.
Pseudonymisation protects but doesn't exempt you from the GDPR. We explain the differences with anonymisation with clear examples and real use cases.
Publishing rulings or open data without proper anonymisation is a fast track to a fine. Here's what the public sector must anonymise and how.
