The personal-data report

jadpo check writes build/report/personal-data.md and a .json twin, in the same form as its other reports (The report). For each person entity it lists:

• every marked field, with its category, entity, store and caches;
• who may read it, from policy;
• its retention, or "kept until erased";
• what erasure does to each record that belongs to the person;
• every connection a marked field is sent to, and whether its copy is erased by the provider's erasure: or kept for an accepted reason;
• keys copied into the outbox for erasure at providers, while they wait;
• the step records of actions with several changing calls, which hold providers' answers, encrypted, until the action commits (an answer over 1 MB is a fault);
• connections holding OAuth grants, and whose grants they are;
• sensitive fields, flagged.

That is most of a record of processing activities (Article 30). Your team adds what the compiler can't know: the purpose of each use, the lawful basis, and the organisation's details.

Changes to the report appear in the approval review, the summary of a change a person signs off before it ships (Review and sign-off). So a pull request that starts sending email addresses to a new provider is seen by a person before it ships.