Security Blog

Pseudonymisation and anonymisation of personal data – what is the difference?

One thing that is heavily emphasised in GDPR is the importance of Privacy by Design. Mechanisms to protect personal integrity should be built into IT systems and services. pseudomized person GDPROne of the core principles is data minimisation. This means that all products and services should be designed so that as little personal data as possible is processed. According to the Swedish Data Protection Authority you can do this in the following ways:

  • Limit data processing to information that only identifies an individual indirectly
  • Limit data gathering to data that is less sensitive
  • Replace names, e.g., with pseudonyms
  • Do not routinely have personal identity numbers as fields in databases

Two terms that have been used a lot when discussing Privacy by Design and data minimisation are anonymisation and pseudonymisation.


So what does anonymisation and pseudonymisation mean? How are they different?

Both anonymisation and pseudonymisation refer to hiding identities and personal data – but in different ways.


Pseudonym means ‘false name’ in Greek, and a famous example is the fictional character Bruce Wayne, who sometimes goes by the name Batman. Similar to Bruce Wayne and Batman, pseudonymisation in IT systems means that you mask the registered and their personal data.

In GDPR, pseudonymisation is defined as ”the processing of personal data in such a way that the data can no longer be attributed to a specific data subject without the use of additional information.” Personal data is thus exchanged with non-identifying data, and additional information is needed to recreate the original data. Further, the additional information should be kept separately.

Pseudonymisation makes the information such as personal identification numbers and personal data less accessible to unauthorized users, and is a way to comply with GDPR requirements.


Anonymised data refers to data that is made anonymous in such a way that the registered can no longer be identified. You simply remove the possibilities of identifying a person, and no additional information can restore the original information. Anonymisation is difficult. You completely lose the connection between data and the individual. Nevertheless, it can be a beneficial technique when the data is used for statistical or research purposes.

As you may gather, there is a clear distinction between the two concepts. Pseudonymisation means that an individual can still be identified through indirect or additional information. This means that pseudonymised personal data is still in scope. Anonymisation means that you cannot restore the original information, and such data is out of scope of the GDPR.


How does pseudonymisation and anonymisation work in practice?

There are different techniques you can use to pseudonymise, but also anonymise personal data.

Directory Replacement

Directory replacement means that you modify data about the registered, while there is still a link between the values. For example, you can use a customer number to identify an individual, and store information that directly identifies an individual, such as personal identification number, separately. In this way you pseudonymise the sensitive data. To anonymise, you should delete the separate sensitive information that directly identifies the registered.


In simple words, scrambling is when you mix letters, and some examples of scrambling techniques are encryption and hashing. At 24 Solutions, we offer HSM services where personal data can be encrypted.


Masking means that some of the information is hidden using random characters or other data. Masking techniques are widely used in the payment industry and card data processing, where parts of the card number are masked, not the least to comply with PCI DSS.


Related content:

5 tips when writing an IT-policy to comply with GDPR

Questions and answers about GDPR

  • 24 Solutions AB
  • Smedjegatan 2C
  • SE-13154 Nacka, Sweden
  • +46 (0)8 535 24 100