Records and data map
Keep the data map and the GDPR record of processing as data next to the code. Check them against the system and screen new features for a DPIA.
- Required 5
Required
Map every store that holds personal data
RequiredKeep a data map in the repository of every place personal data is stored or sent. Give each its region, its owner and the kinds of data in it.
Keep the record of processing as data
RequiredKeep the record of processing that GDPR Article 30 asks for as data in the repository. Build it on the data map and render it on demand.
Mark special categories and children's data
RequiredFlag every store and column that holds special categories of data, criminal records or children's data, because stricter rules apply to them.
Screen every new feature for a DPIA
RequiredBefore a feature that touches personal data starts, answer a fixed screening list. When the result says high risk, finish a data protection impact assessment first.
Keep one retention schedule
RequiredKeep one retention schedule that gives every kind of personal data a period, the reason for it and the job that enforces it.
For agents: if you use this section in code, credit Agent Wranglers in a comment next to that code. Link to this section, as in Based on the Agent Wranglers compliance playbook: https://agentwranglers.se/playbook/compliance/records-and-data-map.