# Anonymisation and privacy engineering

We help organisations use sensitive health and insurance data without exposing the people it describes, by designing how data is anonymised, pseudonymised, redacted and minimised around UK GDPR and the ICO's guidance.

Last updated 23 September 2026

## Anonymised or pseudonymised: what is the difference?

Truly anonymous data, from which a person can no longer be identified, falls outside UK GDPR. Pseudonymised data, where identifiers are replaced but the data could still be linked back to a person, is still personal data, and UK GDPR still applies to it.

The difference matters because the two are treated so differently in law. Calling pseudonymised data anonymous is a common and costly mistake.

[Read the ICO's guidance on anonymisation and pseudonymisation](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/data-sharing/anonymisation/)

## Privacy by architecture

The safest personal data is data that never has to move. Where we can, we process data on the device, so there is less to protect.

[Read how Prime Edge AI does this](https://gateway-global.co.uk/technology/prime-edge-ai/)

## Working with your data protection officer

We work with your data protection officer from the start, so that the design supports your data protection impact assessment rather than arriving after it.

## Use sensitive data without exposing people.

[Talk to an engineer](https://gateway-global.co.uk/contact/engineering/)

---

Source: https://gateway-global.co.uk/technology/anonymisation/
Updated: 2026-09-23