Personal data
For: tenant admins and governance reviewers.
Associate people with jobs before relying on the platform to find their records. Use the task pages below to export data, restrict processing, handle a contest, erase records or set retention. Each task states what it reaches and what remains outside it.
GDPR gives people the right to see their data, to have its processing restricted or stopped for a purpose, to contest an automated decision about them, and to have their data erased. A job about a person (a support ticket, an application, a customer's order) carries their data in its input, in every step's input and output, and in its answer; Temporal keeps all of it in the job's history, and backups keep copies. Deleting rows does not reach the copies.
So a job about people is encrypted with a key of its own, which only the keys of those people open, and erasing a person destroys the keys. What that means for backups is said below, with what holds until a restore.
Related tasks and reference
- Associate people and purposes with jobs
- Find and export personal data
- Restrict processing and record contests
- Erase personal data
- Retain records and restore backups
- Personal data held by plugins
Previous section links
backups: Read the section.
decision records and contests: Read the section.
erase: Read the section.
exports: Read the section.
find what you hold: Read the section.
give a person their data: Read the section.
keep what a law asks you to keep: Read the section.
memory about people: Read the section.
one job id one set of people: Read the section.
people from triggers: Read the section.
purposes and legal bases: Read the section.
restrict and object: Read the section.
several people in one job: Read the section.
start a job for a person: Read the section.
the erasure policy: Read the section.
what it does not reach: Read the section.
what plugins keep: Read the section.