Vendor privacy reviews that scale: tiering processors by data and access
A questionnaire sent to every vendor produces a pile of unread answers and no decision. A tiered review sends the long questionnaire to the dozen vendors that earn it.
Key points
- Tiering sorts vendors by how much personal data they handle and how deeply they can reach into your systems, so the deepest review goes to the few vendors where it matters and a light check goes to the rest.
- Two questions place a vendor: how sensitive and how large the personal data it handles is, and what access it has, from receiving a copy to running inside your systems.
- A tier is not permanent: a vendor moves up when it gains access to more data or a new use is added, so the review is triggered by change, not only by the calendar.
The tiers below are a working method, not a legal category. They exist to put effort where privacy risk is, and to make the choice visible.
Start with an inventory that is complete
Tiering fails when the list is short. Build it from the accounts-payable ledger, the single sign-on application list, corporate card statements and the contracts folder, and add whatever the record of processing names as a recipient. Include free tools: a free account that a department uploaded a customer list to is a processor with no contract at all.
For each vendor record the business owner, what the vendor does for you, and whether personal data goes there. Vendors that touch no personal data leave the privacy process here, though they may still matter to security, covered in the vendor risk management programme.
Two questions that place a vendor
Two questions place a vendor: how sensitive and how large the personal data it handles is, and what access it has, from receiving a copy to running inside your systems.
Data is judged by sensitivity and volume: health, financial, children’s and biometric data weigh more than business contact details, and a million records weigh more than a hundred. Access is judged by depth: a vendor that receives a monthly file is shallow; one with a standing connection to your production database, or whose staff can log in as your users, is deep.
Score each from low to high, using a few rules the whole business can apply the same way. A vendor high on both is tier one.
Three tiers, and what each is asked
Three tiers are enough for most organizations. More than that and the boundaries stop being clear.
What each tier is asked:
- Tier one. The full set: where data is hosted and supported from, sub-processors, retention and deletion, breach notice time, how requests from individuals are passed back to you, security evidence you can read, and what happens to your data at the end. Contract terms are negotiated, and the legal reading belongs to your counsel.
- Tier two. A standard questionnaire, a check that a data processing agreement is signed, and the hosting location.
- Tier three. A short form: what personal data, whose, and who owns the account. The vendor’s terms are accepted and logged.
The contract, and what to check in it
Article 28 of the GDPR requires processing by a processor to be governed by a contract or other legal act, which is why the vendor register tracks whether each processor has one signed and current. The text is on EUR-Lex. We do not recite the contents of the clauses here, because the right terms depend on the law that applies and are settled with counsel.
The review checks the contract, not the form of it: is it signed, is it the current version, does it cover the services you actually use, does it name the sub-processors or a way to learn them, and does it say where data is held? Where data crosses borders, the mechanism is checked as described in cross-border transfers in 2026.
Sub-processors and change
Ask each higher-tier vendor which other companies it passes your data to and where they operate, and require notice when that list changes.
A tier is not permanent: a vendor moves up when it gains access to more data or a new use is added, so the review is triggered by change, not only by the calendar. Events that move a vendor up include a new data category sent to it, a new integration, an acquisition of the vendor, a security incident on its side, a change of hosting country, and a new feature that involves AI. For that last case, see personal data in AI systems.
Make the register earn its place
One register line per vendor is enough: the owner, the tier, what personal data goes there, the contract status, the hosting location, the last review date and the next trigger. Residual risks that the owner accepts go into the privacy risk register with a name and a date. The structure is described on privacy risk register and vendor management.
Two controls keep the register honest. First, procurement does not pay a new vendor until it has a tier. Second, a report of vendors with no review date goes to the privacy lead monthly. Security questionnaires that work are discussed in vendor risk questionnaires that work.
How the work is bounded
The scope is agreed in writing before work starts, and the engagement is quoted in writing with it.
SecHB does not issue certifications, attestations or audit opinions: those come from accredited certification bodies, CPA firms and QSAs. The work here is what an organization does to be ready for them.
Nothing here is legal advice. Where a question turns on the law, the work is done alongside the client’s counsel, not instead of them.
Questions we are asked
What is vendor tiering?
Tiering sorts vendors by how much personal data they handle and how deeply they can reach into your systems, so the deepest review goes to the few vendors where it matters and a light check goes to the rest.
What decides a vendor’s tier?
Two questions place a vendor: how sensitive and how large the personal data it handles is, and what access it has, from receiving a copy to running inside your systems.
Why does the contract matter?
Article 28 of the GDPR requires processing by a processor to be governed by a contract or other legal act, which is why the vendor register tracks whether each processor has one signed and current.
When is a vendor re-reviewed?
A tier is not permanent: a vendor moves up when it gains access to more data or a new use is added, so the review is triggered by change, not only by the calendar.
What about sub-processors?
Ask each higher-tier vendor which other companies it passes your data to and where they operate, and require notice when that list changes.
Review fewer vendors, better
Tell us roughly how many vendors handle personal data and who owns the list today. The reply says how we would tier them. The service is privacy risk register and vendor management.