Start with the actual relationship
A controller decides why and how personal information is used. A processor handles it on a controller’s behalf. Your business will commonly be the controller for its customer database, with a hosting or CRM provider processing that information under instructions. But the same supplier may act as a controller for separate purposes, such as administering its own customer accounts.
Do not classify the whole relationship from a single label in the terms. Ask what happens to each data flow. If a vendor uses your customer records for an independent purpose, a standard processor agreement does not by itself make that activity acceptable. The ICO stresses that responsibility follows the reality of the processing.
Read the data agreement, not just the sales page
The required controller–processor contract should describe the processing and include the protections specified by Article 28. These cover documented instructions, confidentiality, security, sub-processors, help with individual rights and assistance with relevant compliance obligations. They also address return or deletion at the end and information needed to demonstrate compliance.
A practical procurement file should contain the applicable version of the agreement, not merely a link which can change. Check which legal entity contracts with you and whether the terms apply to the product tier you are buying. A security brochure, encryption claim or certification can inform due diligence, but none replaces the required agreement.
Make supplier checks proportionate to the consequences
A mailing list of business contacts and a file containing workers’ medical information present different risks. Start with what could happen to the people concerned if information were disclosed, altered or unavailable. Use that to decide how much assurance you need.
Useful questions include who can access records, whether administrators can require multi-factor authentication, how restoration works, how incidents are reported and whether audit logs are available. For a critical service, ask for evidence rather than accepting a generic answer. Testing an export with invented records is often more revealing than reading a long list of product features.
Configuration is part of the purchase
Supplier security and your own account settings are separate layers. A well-protected platform can still expose information through an unrestricted sharing link or an employee account that was never closed. Decide who approves access, who reviews it and who removes it when responsibilities change.
Our practical recommendation is to assign a named owner to each service and record the approved purpose, information categories and permitted users. Avoid placing additional sensitive information into convenient free-text fields without review. When introducing a new integration, check what it copies and where: connecting two approved services creates another data flow that may need its own assessment.
Look beyond the advertised hosting location
The location of a primary server does not answer every international-transfer question. Overseas support, affiliated organisations and sub-processors may be relevant. Map the organisations receiving information and obtain the applicable transfer information from the supplier.
The business also needs a workable incident contact. Agree how urgent notifications reach you and who will evaluate them. A supplier’s statement that it is investigating is not a reason to ignore your own assessment or reporting responsibilities. Keep escalation details somewhere accessible if the affected platform itself becomes unavailable.
Plan how the relationship ends
Exit should be considered before signing. Ask whether you can obtain a usable export, what happens to attachments and audit records, how account closure affects backups and which information the supplier retains under separate obligations. Distinguish an export from a proven ability to move to another system.
For implementation, keep a short supplier register with an owner, contract location, review trigger and exit plan. Revisit it after significant changes, not only at renewal. This turns due diligence into an operating practice rather than a one-off questionnaire. Outsourcing can improve capability, but it works best when responsibilities remain explicit on both sides. Make those responsibilities visible to the colleagues using the service.
Sources and further reading
Primary guidance behind this briefing. Requirements depend on the facts; check the current guidance before making a decision.
This is general guidance, not a legal opinion on your circumstances or a guarantee of compliance. An individual assessment may be needed, particularly where sensitive information, disputed rights or regulatory action is involved.