Describe the actual processing
Record the service, duration, purposes, categories of information and people concerned. Identify which party determines the purposes and means and which activities, if any, are performed on documented instructions.
Separate customer workload processing from the provider’s own account, billing, security and support records. A generic label should not hide different purposes or responsibilities.
Agree the duties and safeguards
Review confidentiality, authorised access, security measures, assistance with relevant rights or regulatory duties and the handling of incidents. Establish how instructions, material changes and requests for information will be managed.
The safeguards should reflect the actual service. For example, customer-managed guest systems and applications may require controls that are outside the infrastructure provider’s operational scope.
Document locations and supporting providers
Identify relevant infrastructure and service providers, their roles and the applicable authorisation or notification arrangements. Review where data is stored and accessed and whether transfer safeguards are required.
Ask for service-specific supplier information and assurance evidence. This public website is not an exhaustive processor register for every possible infrastructure configuration.
Plan retention, return and deletion
Agree how data is returned or removed at service end, the available export formats, the customer’s retrieval responsibilities and any applicable retention exceptions. Address backup copies and logs explicitly rather than assuming that deleting a running server removes every record.
Confirm the final processing terms before placing an order. Raise any mandatory organisational clauses early so they can be assessed against the proposed delivery model.
