Processors and transfers
List every vendor that touches your data with its contract, region and transfer basis, publish your subprocessors, and check AI providers' terms on training.
- Required 7
- Recommended 1
Required
Keep one register of vendors
RequiredKeep one register of every vendor that handles personal data or reaches production. Fail the build when the code uses a vendor not in it.
Check each agreement covers Article 28
RequiredCheck every data processing agreement against the list in GDPR Article 28(3), and record the result and the breach notice deadline in the vendor register.
Publish your subprocessors
RequiredIf you process personal data for business customers, publish your subprocessor list at a stable address and tell customers before you add one.
Record a legal basis for every transfer
RequiredFor every store or vendor outside the European Economic Area, record the transfer basis under GDPR Chapter V. Contract clauses also need a transfer impact assessment.
Check the Data Privacy Framework status of US vendors
RequiredRely on the EU-US Data Privacy Framework only for US vendors on its active list. Check the list monthly and keep signed contract clauses as a fallback.
Rank vendors and check their evidence
RequiredRank every vendor by the data and access it has, and require current security evidence for the top tier.
Record the data terms of every AI provider
RequiredGive every AI model provider a vendor register entry with its plan, its training setting, its retention and its region. Allow only plans that do not train on your data.
Recommended
Confirm deletion when a vendor leaves
RecommendedWhen you stop using a vendor, get written confirmation that it deleted or returned your data, before you remove it from the register.
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/processors-and-transfers.