Activities / What code does

Processes de-identified data

processes_deidentified_data

Your app strips or replaces the identifiers in personal data so it no longer points to a person, or receives, shares or links data that has been through that.

  • scope code
  • in the registry since 1.19
  • 15 laws in 10 jurisdictions name it

What triggers it

The lint's definition. It strips or replaces the identifiers in personal data to de-identify, pseudonymize or anonymize it, or receives, shares or links data that has been through that with other datasets. Encryption alone is not this.

This covers a step that tokenizes, masks or removes names and ids before analytics or sharing, a pseudonymization or anonymization pipeline, a dataset your app receives or licenses that is described as de-identified, and joining such a dataset with another.

What does not

Encryption alone does not count.

Pseudonymized data usually stays personal data, so an app that does this also declares processes_personal_data.

Often confused with Processes personal data.

The law it brings into scope

The kinds of law that name this activity in the LexLint law library, with the number of laws and jurisdictions in each, as of . The examples are chosen by rule, laws in force first and the widest jurisdiction first; each section's page lists every law.

Area of lawLawsJurisdictions
Privacy law

Have a legal basis for personal data, honor people's rights over it, and report a breach.

15 10

Counterparties that usually come with it

  • the people the data came from
  • a partner, vendor or researcher the data is shared with

A component that cannot run as documented without one of these names it in its ACTIVITIES.md under talks_to, with required: true. That party's jurisdiction then joins the run of every product that uses the component, and the finding says why it is there. A default the deployer can change is asked about, never added. Talking to a party never makes a product that party.

In a declaration

A library or framework that makes this possible enables it; an application whose shipped code does it performs it.

For a library

activities: - id: processes_deidentified_data mentioned: enables enabled: requires_configuration where: [<the module that carries it>] note: <one sentence>

For an application

activities: - id: processes_deidentified_data mentioned: performs enabled: by_default where: [<the module that carries it>] note: <one sentence: what it does, and the kind of law it attracts>