UK payments · July 2026
[email protected]
+44 7563 115980 (phone and WhatsApp)
For data owners and data brokers.
Data de-identification is the removal or replacement of everything in a dataset that identifies a person, so the data can be shared, licensed or sold.
We work across the whole market, for any company that holds data and any company that buys it.
We handle structured data, such as spreadsheets, databases, transaction tables and logs, and unstructured data, such as emails, chat messages, documents, call transcripts and tickets. Unstructured data means free text written by people. It carries the most hidden identifiers, so it receives the most attention.
We work in the formats the owner already uses, and deliver in the formats the buyer needs, such as CSV, JSON Lines (one record per line) or Parquet (a compressed table format).
Every release carries the records that both the owner and the buyer need to approve it.
| Deliverable | What it contains | Who relies on it |
|---|---|---|
| Clearance record | Ownership, authority, contracts, confidentiality, copyright and database right, earlier licences and the permitted uses | Owner and buyer legal teams |
| Privacy assessment | The lawful basis for the de-identification work, the exclusions and the analysis under each law that applies | Privacy teams on both sides |
| De-identification report | Methods used, where processing ran, how the key was handled, test results and remaining risk | Security, privacy and data teams |
| Exclusion record | Each category removed, why and in what volume | Buyer privacy and data teams |
| Data sheet | What the dataset contains, its source, date range, structure, volumes and known limits | Buyers and their governance teams |
| Licence terms | Scope of use, term, exclusivity, onward rights, retention, deletion and the ban on re-identification | Both parties |
| Release approval | Owner sign-off for each data package | The owner's board and the buyer |
See also: Data broker registration · How to sell data to AI companies · Anonymisation vs pseudonymisation · HIPAA de-identification · AI data licensing deals · AI data licensing agreement
Tell us where you are and where you want to be.
[email protected]
+44 7563 115980 (phone and WhatsApp)
We run it on the data owner's own premises, so raw records never leave its systems, and we clear the rights and the privacy position at the same time. Each release comes with a clearance record, a de-identification report and test results that a buyer's legal and privacy teams can rely on.
On this page
We clear the rights and the privacy position, de-identify datasets on the owner's own premises and test the result before anything is released. We also source and supply cleared datasets from companies that want to sell their data.
Rights clearance confirms that the owner is entitled to license the data for the buyer's intended use. The buyer's legal team needs it in writing before a deal can close.
Where a restriction applies, the material is removed, consent is obtained or the permitted use is narrowed. The clearance record lists each check, its result and the uses the owner can grant.
De-identification is itself a use of personal data. UK guidance confirms that anonymising personal data counts as processing, so the owner needs a lawful basis (a legal ground the law allows for using personal data), a defined purpose and notice to people. We document all three before work starts.
We then set what must be excluded altogether: special category data (information revealing racial or ethnic origin, political opinions, religious or philosophical beliefs or trade union membership, genetic data, biometric data used to identify a person, health, and sex life or sexual orientation), criminal offence data, identity numbers, account credentials and precise location.
In the US, under the California Consumer Privacy Act (CCPA), information is deidentified only if the business takes reasonable measures to stop it being linked to a consumer, publicly commits not to re-identify it, and binds every recipient by contract to do the same. Health information covered by HIPAA (the US federal health privacy law) is de-identified by one of two methods: removing 18 listed types of identifier with no actual knowledge that the rest could identify anyone, or a documented expert finding that the risk is very small.
On-premises (on-prem) means the work runs on the owner's own servers or inside its own cloud account. Our process is set up there, and only approved, de-identified output is released.
UK guidance sets the motivated intruder test: could a reasonably competent person, using the internet, public records and ordinary investigative methods, identify someone if they set out to?
Data is released only when the risk of identification is sufficiently remote. Results and the remaining risk are written up in the de-identification report.
These words are often used loosely. In law they have precise and different effects.
| Term | What it means | Legal effect |
|---|---|---|
| Anonymous (UK and EU) | No one can be identified by any means reasonably likely to be used (GDPR Recital 26) | Data protection law does not apply to it |
| Pseudonymised (UK and EU) | Identifiers are replaced, but people could be identified using additional information kept separately (GDPR Article 4(5)) | It remains personal data, and the law applies in full |
| Pseudonymised data held by a recipient (EU) | In September 2025 the EU Court of Justice held that pseudonymised data is not necessarily personal data for a recipient who cannot re-identify anyone | Status is judged in the hands of each holder, and the original owner's duties continue |
| De-identified (UK offence) | Re-identifying it without the consent of the organisation that de-identified it is an offence (Data Protection Act 2018, section 171) | A licence's ban on re-identification is backed by the criminal law |
| Deidentified (California) | Cannot reasonably be linked to a consumer, backed by a public commitment and contracts with recipients (CCPA section 1798.140(m)) | It falls outside the CCPA's definition of personal information |
| De-identified (US health) | Either 18 types of identifier removed with no actual knowledge of identifiability, or an expert finding that the risk is very small (HIPAA Privacy Rule, 45 CFR 164.514(b)) | It is no longer protected by the HIPAA Privacy Rule |
Each engagement follows the same six steps, scaled to the size of the dataset.
| Step | What happens | Output |
|---|---|---|
| 1. Scope | The dataset, the intended buyer or use, and the owner's systems and obligations | Written scope |
| 2. Clear | Rights and privacy reviewed, restrictions resolved and permitted uses agreed | Clearance record and privacy assessment |
| 3. Set up | De-identification set up inside the owner's environment and run on a pilot set of records | Pilot output for review |
| 4. Test | Sample review, uniqueness and linkage tests, with adjustments until the data passes | De-identification report |
| 5. Release | The owner approves each package, and data moves to the buyer in the agreed formats | Release approval, data sheet and exclusion record |
| 6. Maintain | New records processed on a schedule, with tests repeated when anything material changes | Versioned releases with change notes |
We also source and supply datasets. Companies that want to sell or license their data engage us to prepare it and bring it to buyers. Data brokers and AI teams engage us to find data that matches a specification, from companies that have chosen to license it.
For a data owner, this means one team handles clearance, de-identification and the sale. For a buyer, it means every dataset arrives with the same records, whichever company it came from.
The removal or replacement of everything in a dataset that identifies a person, so the data can be shared, licensed or sold while staying useful.
It depends on how well it is done. Data that no one can reasonably use to identify a person is anonymous and outside UK and EU data protection law. Data that could be re-linked using separately held information remains personal data.
Anonymisation removes the link between the data and the person. Pseudonymisation replaces identifiers with codes, but the link can be restored with information held separately. UK guidance describes anonymisation as reducing the personal data you hold, and pseudonymisation as reducing the risks of the personal data you hold.
No. De-identification runs on your own servers or in your own cloud account. Only output that has passed testing, and that you have approved, is released.
We apply the motivated intruder test, review samples, look for records that stand out, try to link records to public information and assess the risk in the buyer's hands.
Yes, where it is truly anonymous and the owner has the rights to license it. Contracts and copyright still apply to anonymous data, so we clear the rights as well as the privacy position.
Either, agreed for each engagement. The clearance record and the de-identification report are prepared so that both sides can rely on them.
Yes. We test an existing dataset against the same standards, report the remaining risk and set out what needs to change before release.
Yes. We source and supply company datasets to a buyer's specification, each from a company that has chosen to license its own data, cleared to the same standard.
Existing licences, exclusivity and earlier sales are checked during rights clearance, so that a new licence never conflicts with one already granted.
Each point of law on this page was checked against these official sources on 26 October 2026. This page is general information, not legal advice.
UK payments · July 2026
AI governance · July 2026
AI governance · February 2026