Self-assessment
Score yourself
Answer each question honestly. Yes = 2, Partly = 1, No = 0. Keep a running total.
Your score
0/ 24
0 of 12 answered
Not scored yet
The register
0 / 601 Is there one register of every vendor and partner holding or processing your personal data, including the ones business teams engaged directly, not only the ones procurement remembers?
02 Does each row record what data, for what purpose, where it is processed, and which sub-processors are used?
03 Is the register checked against real data flows, using your [data map](/enterprises/focus-areas/data-discovery-classification-and-mapping) as the baseline?
The contracts
0 / 604 Does every processor on the register have a valid contract?
05 Does every processor contract carry the required clauses: permitted use, safeguards, sub-processing rules, incident notification, deletion or return at the end?
06 Is there a dated remediation plan for legacy contracts, prioritised by the sensitivity of what each vendor holds?
The enforcement
0 / 607 When a customer withdraws consent, does the stop signal reach every partner who received data under that purpose?
08 Can you prove the signal arrived: a confirmation, not "we sent an email"?
09 Do vendor contracts oblige them to tell you fast when they have an incident?
The oversight
0 / 610 Is there a tiered oversight routine: deep checks for high-risk vendors, light checks for low-risk, all on a calendar?
11 Do you know, per vendor, what happens to your data when the contract ends, and is deletion or return verified?
12 Have you traced one withdrawn customer's data to every partner and produced proof that each stopped?
| Score | Where you stand | What to do next |
|---|---|---|
| 0 to 8 | Exposed | You do not know who holds your data. Build the processor register first; everything else hangs on it. |
| 9 to 16 | Halfway | The register exists but enforcement leaks. Withdrawal propagation to partners is the usual hole. |
| 17 to 21 | Strong base | Run the trace test at the end of this page and close the legacy contract backlog on its dates. |
| 22 to 24 | Leading | Watch the edges: new vendors engaged directly by business teams, and sub-processors changing underneath contracts. |
Any single "No" is a named gap, whatever the total says. Nothing leaves your browser.
What this covers
Any vendor that processes personal data for you must be bound by a valid contract. That is a legal duty. Around it sits the practice of oversight: knowing what actually moves to which vendor, making sure partners stop when consent dies, and keeping evidence that the ecosystem behaves.
This is the data-sharing dimension of vendor relationships, not general procurement reform. The third-party data exchange page covers the day-to-day discipline of sharing data safely, including why casual channels like WhatsApp do not belong in the flow. This page is about governing the relationships themselves.
The framework: four moves
Move 1: Build the processor register. Every vendor that touches personal data: who they are, what data, what purpose, under which contract, where they process it, which sub-processors they use. Build it from real flows, not only procurement records; business teams engage vendors directly.
Move 2: Fix the contracts. Every processor contract needs clauses covering permitted use, the safeguards required, sub-processing rules, incident notification, and deletion or return of data at the end. Remediate legacy contracts signed before these clauses existed; prioritise by the sensitivity of what the vendor holds, and give the plan dates.
Move 3: Monitor what moves and enforce consent. Compare real data flows to vendors against what contracts allow. When consent for a purpose dies, the stop signal must reach every partner who received data under it, technically, with confirmation. Contract alone does not do this.
Move 4: Oversee on a rhythm and keep evidence. Tiered checks matched to vendor risk: attestations, evidence requests, review meetings. Keep the contract inventory with status, partner attestations, oversight records and withdrawal-propagation test results.
Template: the processor register
One row per vendor or partner. Copy this and fill it in.
| Vendor | What data | Purpose | Contract status | Key clauses present | Sub-processors | Where processed | Tier | End-of-contract handling |
|---|---|---|---|---|---|---|---|---|
| Example: collections agency | Customer contact, loan status | Collections on overdue accounts | Signed | All | None | India, vendor DC | High | Return plus certified deletion |
The downloadable file adds the column guide and the clause checklist.
What good looks like at the end
You should have: a complete processor register, contracts brought up to standard or a dated plan to get there, a working oversight routine, and demonstrated withdrawal propagation to partners.
The live test: pick one customer who has withdrawn consent for marketing. Trace which partners ever received their data for that purpose, and produce the proof that each stopped. If the trail ends at "we sent an email", the propagation is not real.
Where enterprises go wrong
- A processor register built from procurement records only, missing the vendors business teams engaged directly.
- Legacy contracts left unremediated because there are too many. Start with the vendors holding the most sensitive data.
- Consent enforcement tested at your own systems but never at partners.
- Oversight that ends at contract signing. The contract is the starting line, not the finish.
The decisions to make
- Oversight depth per vendor tier, and the tiering criteria.
- How withdrawal propagation is implemented technically per partner.
- The order and pace of legacy contract remediation.
- Whether oversight evidence is produced for audits, and in what form.
Next step
Retention, erasure and localisation, which decides what your vendors are still holding at the end. If you need help with any of this, write to us and we will help.