Pseudonymisation

Data & Tracking

Also: Pseudonymization · Data Tokenisation

What it doesSwaps names for codes

Still linkableWith a separate key

Not the same asAnonymisation

Used forAnalytics, CRM exports, testing

Quick definition

Pseudonymisation is a data protection technique that replaces identifying details like name or email with an artificial code. The original identity can still be recovered using a separate key kept apart from the dataset, which is what makes it different from true anonymisation.

How it varies across Australia

Pseudonymisation adoption in Australian marketing stacks is uneven. Larger organisations with dedicated data teams use it routinely for customer relationship management (CRM) exports and analytics sandboxes. Smaller businesses tend to skip it entirely or confuse it with deleting the customer's name, which isn't the same thing.

See data and tracking maturity across Australian industries →

What it actually means

Think of a cloakroom ticket. The ticket itself doesn't say your name. Hand someone the ticket and they can't identify you from it alone. But the cloakroom keeps a log linking ticket numbers to names, and anyone with access to both the ticket and the log can work out exactly whose coat it is. That's pseudonymisation. The identifying field is swapped for a code, and the code can be reversed if you hold the separate key.

This matters because pseudonymised data is still considered personal information under most privacy frameworks, including the Australian Privacy Act. Swapping an email for a token doesn't take the data out of scope. It reduces the damage if the dataset leaks, because whoever finds it still needs the key to reattach identities.

Marketing teams use pseudonymisation constantly without naming it. Hashing an email before sending it to an ad platform, replacing customer IDs with tokens in a data warehouse, running analytics on a customer segment using account numbers instead of names. All pseudonymisation. The technique sits quietly underneath attribution, segmentation and most first-party-data pipelines.

Pseudonymisation doesn't remove the risk. It moves the risk into a smaller, better-guarded box.

How it shows up

It shows up in the data layer as hashed emails feeding conversion application programming interfaces (APIs), in CRM exports where customer names are swapped for account numbers before a vendor sees the file, and in analytics platforms where user identifiers replace raw personal details. It also shows up in consent records, where a person's preferences are stored against a token rather than their name, so marketing systems can respect a choice without every system needing to know exactly who made it.

The Australian context

The Privacy Act 1988 and the Office of the Australian Information Commissioner (OAIC) treat pseudonymised data as personal information, not anonymous information. Australian Privacy Principle 11 requires organisations to take reasonable steps to protect personal information from misuse, and pseudonymisation is one of the accepted reasonable steps, not a substitute for the obligation itself.

With Privacy Act reform progressing, the OAIC has signalled that pseudonymisation will keep being recommended as a practical safeguard for marketing databases, particularly where data is shared with agencies, platforms or third-party vendors for testing or analysis.

Where people get this wrong

Calling pseudonymised data anonymous.If a key exists anywhere that can reverse the code back to a real person, the data is still personal information under Australian privacy law regardless of what the field is labelled.

Storing the key next to the pseudonymised dataset.Keeping the lookup table in the same database or accessible to the same staff defeats the purpose. The protection only works if the key is genuinely separated.

Assuming pseudonymisation removes consent obligations.You still need a lawful basis and, where required, opt-in consent to collect and use the underlying data. Pseudonymising it afterwards doesn't retroactively fix a consent gap.

Common questions

Is pseudonymised data still covered by privacy law?

Yes. Under the Australian Privacy Act, pseudonymised data is still personal information because it can be reattached to an identity using the separate key. Only true anonymisation, where reattachment is genuinely impossible, takes data outside privacy obligations.

What's the difference between pseudonymisation and encryption?

Encryption scrambles data so it's unreadable without a decryption key, but the structure often stays intact. Pseudonymisation specifically replaces identifying fields with artificial codes. The two are often used together, but encryption protects data in transit or storage while pseudonymisation protects identity.

Why would a marketing team bother pseudonymising customer data?

It reduces the damage from a data breach, satisfies reasonable-steps obligations under privacy law, and lets teams share data with vendors, agencies or ad platforms for analysis without exposing raw identities. It's a practical middle ground between full access and full lockdown.

Can pseudonymised data be used for personalised marketing?

Yes, as long as the system that sends the actual message still holds the key to reverse the token back to a contactable identity. Many customer data platforms run analytics and segmentation on pseudonymised records, then reattach identity only at the point of sending.

Debrief

Get the next one

No spam. No fluff. Just the next article, straight to your inbox.

Keep exploring

About New Rebellion

New Rebellion is a marketing intelligence consultancy. We build tools, score Australian businesses on how their marketing actually performs, and publish Debrief every day. This dictionary is part of how we work in the open.

How we think →