Video anonymization and privacy law: GDPR, CCPA and de-identification

More than faces. A licence plate can be tied to a keeper; a name on a monitor, a badge, a letter, or a spoken address all identify a person; and in context even a distinctive tattoo or gait can. Under GDPR, any footage from which a living individual can be identified — directly or indirectly — is personal data, which is why a serious anonymization pass covers the whole set, not just the obvious faces.

• Faces and heads of un-consented people
• Licence plates linkable to a registered keeper
• Legible screens, documents, forms, badges, and mail
• Names, addresses, and numbers spoken in the audio
• On request, distinctive identifying marks

The line is reversibility. Pseudonymization replaces or hides an identifier in a way that can still be undone with additional information — a mask layer you can toggle off, or an un-blurred master kept alongside. Pseudonymized data is still personal data and stays in scope. Anonymization means the identifier cannot be recovered by any reasonably likely means; only then does the data fall outside the regime. That is why the redaction has to be baked into the pixels and any un-redacted source destroyed or controlled.

If a regulator, a customer, or your own counsel asks whether a batch was anonymized, "we ran a blur tool" is not an answer. An auditable record shows, per file: which identifier classes were in scope, the detector version and settings, the recall measured on a labelled sample, who reviewed it, and what happened to the source footage. That record is what turns a privacy claim into something you can defend.

Firsthand delivers this record with every anonymization job and a data-processing summary suitable for a DPIA. This guide is general information, not legal advice — your counsel makes the determination for your jurisdiction and use.