Complete this form before customer personal information (PII) is transferred to, stored in, or made accessible from a cloud region outside the jurisdiction where it was collected. Answer each question as accurately as possible and attach supporting evidence where requested.
This template is a neutral record-keeping and review aid. It does not constitute legal advice, does not guarantee any particular outcome, and is not a statement of compliance with any particular law, regulation, or contractual scheme. Requirements vary between jurisdictions and change over time; consult qualified specialists in the relevant jurisdictions before relying on any conclusion recorded here.
Internal reference or case number
Date this form was opened
Requesting reviewer or analyst
Overall urgency of this clearance request
Routine
Elevated
Expedited
Emergency retrospective review
Identify every party in the transfer chain and describe the destination jurisdiction and cloud region. Where a party's role is unclear, record the role as understood by your organisation and flag the uncertainty for the reviewing officer.
Data exporter legal entity name
Data exporter trading name or brand (if different)
Exporter country or territory of establishment
Exporter role in relation to the personal information
Controller or equivalent decision-maker
Processor or service provider acting on instructions
Joint or shared decision-maker
Sub-processor engaged by another processor
Other or not yet determined
Exporter privacy or data protection contact person
Exporter contact email address
Exporter contact telephone (include country code)
Data importer legal entity name
Importer role in relation to the personal information
Processor or service provider acting on instructions
Controller or equivalent decision-maker
Joint or shared decision-maker
Sub-processor
Affiliate providing shared infrastructure
Other or not yet determined
Destination country or territory of the cloud region
Cloud region or availability zone identifier
Physical location of primary data centres (city or area, if known)
Cloud service model used for the transfer
Infrastructure service (rented compute and storage)
Platform service (managed runtime and databases)
Software service (vendor-operated application)
Hybrid or multi-model deployment
Private or self-hosted cloud in the destination region
Other
Deployment model
Public shared region
Dedicated or single-tenant region
Community region shared by a defined group
Hybrid spanning on-premises and cloud
Other
Is the destination jurisdiction the same as the jurisdiction where the personal information was originally collected?
Status of any formal recognition, adequacy finding, or comparable arrangement between the exporter's jurisdiction and the destination jurisdiction (as understood by your organisation)
Recognition or comparable arrangement reported to be in place
No recognition or comparable arrangement identified
Status under review or subject to change
Not known
Will the personal information be accessible from, or transferred onward to, any jurisdiction other than the destination jurisdiction?
Purposes of the transfer (select all that apply)
Cloud storage and backup
Application hosting and delivery
Analytics, reporting, or business intelligence
Customer support and service operations
Fraud detection and security monitoring
Software development, testing, or staging
Disaster recovery and business continuity
Shared internal systems or group-wide platforms
Artificial intelligence or machine learning processing
Other:
Transfer frequency
One-time transfer
Recurring scheduled transfers
Continuous or near real-time replication
Ad hoc or on-demand access only
Not yet determined
Anticipated start date of the transfer
Anticipated duration or review horizon
Sponsoring business unit or department
Business owner or accountable manager
Transfer chain register — list every entity that will handle the personal information
Entity name | Role in the chain | Jurisdiction of establishment | Service or function provided | Contract in place? | Evidence reference | |
|---|---|---|---|---|---|---|
Has a record-of-processing or equivalent internal inventory entry been created for this transfer?
Classify the personal information proposed for transfer, estimate volumes, and record the minimisation steps applied. Where a category is sensitive or subject to additional restrictions in any relevant jurisdiction, describe it plainly and flag it for the reviewing officers.
Categories of personal information included in the transfer (select all that apply)
Identity and contact details
Account credentials or authentication data
Transaction and payment history
Device, network, and technical identifiers
Location or geolocation data
Communications content (messages, call recordings, support transcripts)
Browsing behaviour and product usage telemetry
Employment or professional information
Financial standing or credit-related information
Health, biometric, or other sensitive personal information
Information about children or young people
Information inferred or derived about the individual
Other:
Approximate number of individuals whose personal information is in scope
Approximate number of records or objects to be transferred
Estimated data volume per transfer cycle (gigabytes)
Groups of individuals represented in the data set (select all that apply)
Existing customers
Prospective or former customers
Employees or contractors of the exporter
Minors or young people
Individuals in vulnerable circumstances
Representatives or contacts of organisations
Members of the public with no established relationship
Other
Source of the personal information
Collected directly from the individual
Received from a partner or service provider
Observed or generated through use of a service
Derived or inferred internally
Publicly available sources
Mixed sources
Purpose limitation statement — describe the specific, defined purposes the transferred data will serve in the destination region
Is every data element proposed for transfer strictly necessary for at least one stated purpose?
Data minimisation measures applied (select all that apply)
Field-level removal of unnecessary attributes
Aggregation or summarisation instead of record-level transfer
Pseudonymisation or tokenisation of direct identifiers
Anonymisation or irreversible de-identification
Sampling or subset extraction instead of full data set
Truncation, rounding, or generalisation of values
Retention limits applied at the destination
None applied yet
Data elements deliberately excluded from the transfer
Is unstructured or free-text content included?
No
Yes, with automated screening or redaction
Yes, without automated screening
Will the transferred data be combined with other data sets in the destination region?
PII inventory and minimisation worksheet
Data element or field | Category | Sensitivity tier | Data subject group | Approximate records | Percent retained after minimisation | Records retained | Strictly necessary? | |
|---|---|---|---|---|---|---|---|---|
Customer email address | Identity and contact | Standard | Existing customers | 1250000 | 100.0 | 1250000 | ||
Full date of birth | Identity | Elevated | Existing customers | 1250000 | 20.0 | 250000 | ||
Support call transcripts | Communications content | Elevated | Existing customers | 84000 | 5.0 | 4200 | ||
0 | ||||||||
0 | ||||||||
0 | ||||||||
0 | ||||||||
0 | ||||||||
0 | ||||||||
0 |
Please rate the following statements about data quality and minimisation for this transfer
Strongly disagree | Disagree | Neutral | Agree | Strongly agree | Not assessed | |
|---|---|---|---|---|---|---|
The data set contains only fields with a documented purpose | ||||||
The volume transferred is the smallest workable amount | ||||||
Records of individuals no longer in scope have been removed | ||||||
Sensitive or elevated-tier fields have additional handling controls | ||||||
The data set has been reviewed for accidental inclusion of unrelated personal information |
Are deletion, return, or secure destruction procedures defined for the transferred data at the end of its retention period?
Record the transfer mechanism relied upon, the state of any contractual safeguards, and the outcome of the documented impact assessment for the destination jurisdiction. References to standard contractual clauses or similar instruments describe widely used template wording; whether a given instrument is appropriate or sufficient is a matter for qualified advisers in the relevant jurisdictions.
Transfer mechanism(s) relied upon (select all that apply)
Standard contractual clauses or equivalent template clauses
Binding corporate rules or equivalent internal group rules
Certification, code of conduct, or comparable scheme
Explicit consent of the individual where appropriate
Contractual necessity for performance of an agreement
Derogation for occasional or limited transfers
Internal policy or instruction set with documented safeguards
Not yet determined
Date the governing transfer agreement or clauses were signed
Contract or agreement reference number
Have the clauses been signed by all parties in the transfer chain, including any sub-processors?
Have any optional or annexed terms been modified, disclaimed, or limited by any party?
Has a documented transfer impact assessment (TIA) or equivalent risk assessment been completed for this transfer?
Assessment methodology, framework, or internal standard applied
Assessor name and role
Factors considered when assessing the destination jurisdiction (select all that apply)
Relevant laws and practices on access to data by public authorities
Independence and powers of any supervisory or oversight bodies
Availability of redress or remedy for affected individuals
Rule of law, due process, and judicial oversight generally
Sector-specific rules affecting the data or industry
Practical experience or reported incidents involving similar transfers
Publicly available transparency reports or disclosures
Advice from qualified local counsel
None of the above considered yet
Summary of findings regarding the destination jurisdiction
In your assessment, how likely is it that authorities in the destination jurisdiction could obtain access to the transferred personal information in ways that conflict with the exporter's stated obligations?
Very unlikely
Unlikely
Uncertain
Likely
Very likely
Unable to assess
Supplementary or compensating measures identified (select all that apply)
Strong encryption with keys held outside the destination jurisdiction
Pseudonymisation or tokenisation before transfer
Split or multi-region storage so no single region holds complete records
Strict access controls and least-privilege administration
Contractual commitments to challenge or notify requests where lawful
Enhanced logging, monitoring, and independent audit rights
Reduced data scope or shortened retention
None identified
Does the agreement include controls over onward transfers by the importer to third parties?
Is there an approved process for adding or replacing sub-processors?
Has any supervisory authority, court, or other body previously been engaged on this transfer arrangement or a materially similar one?
Has input been sought from qualified legal counsel in the exporter's and destination jurisdictions?
Transfer safeguard audit checklist
Safeguard or clause area | Documented | Evidence reference | Gap severity (1 = none, 5 = critical) | Reviewer notes | |
|---|---|---|---|---|---|
Obligation to process only on documented instructions | CLAUSE-4.1 | Aligned with internal processing policy | |||
Confidentiality commitments for personnel | CLAUSE-5.2 | Signed acknowledgements on file | |||
Security measures annex completed | ANNEX-II | Annex lists controls; encryption detail to be refreshed | |||
Assistance with individual rights requests | Process not yet documented for the destination region | ||||
Notice or challenge process for authority requests | Awaiting importer position and local counsel input | ||||
Audit and inspection rights | CLAUSE-7.4 | Remote audit accepted; on-site rights limited | |||
Return or deletion at end of service | CLAUSE-8.5 | Deletion certificate required within 30 days | |||
Please upload the signed transfer agreement or clauses (with annexes)
Please upload the transfer impact assessment or equivalent risk assessment report
Please upload any legal adviser memoranda or jurisdiction summaries relied upon
Please upload supporting evidence such as certifications, audit reports, or transparency disclosures
Overall documentation completeness for this section (1 = incomplete, 10 = fully evidenced)
Outstanding gaps, open questions, or assumptions to be resolved before clearance
Describe the technical and organisational measures applied to the transferred personal information, with particular attention to encryption, key custody, access control, and the handling of requests from public authorities. Record only measures that are actually in place or formally committed; do not record aspirational controls as implemented.
Is the personal information encrypted while stored in the destination region?
Is the personal information encrypted while in transit to and within the destination region?
Who controls the encryption keys?
Exporter retains and manages its own keys
Keys held by the importer or cloud provider
Independent key management or custody service
Split control between exporter and provider
Not yet determined
Are keys held in a hardware security module or equivalent hardened key store?
Can the exporter revoke or rotate keys independently of the destination region operator?
Additional protective techniques applied (select all that apply)
Tokenisation of direct identifiers
Format-preserving obfuscation
Data splitting across regions or providers
Confidential computing or isolated execution environments
Differential privacy or noise injection for analytics
Secure multi-party computation
None applied
Access control measures in place (select all that apply)
Role-based or attribute-based access control
Multi-factor authentication for administrative access
Least-privilege and just-in-time elevation
Segregation of duties for key and data administration
Named administrator list with periodic recertification
Network segmentation and private connectivity
Session recording or privileged activity logging
Restriction on administrative access from certain jurisdictions
None documented
Is there a documented policy or contractual commitment describing how requests from public authorities in the destination jurisdiction are handled?
Does the importer publish transparency reporting or equivalent disclosures about authority requests?
Are there contractual or policy commitments to notify the exporter of any unauthorised access, disclosure, or security incident affecting the transferred data?
Is continuous monitoring, logging, or independent audit of access to the transferred data in place?
Encryption and protective control inventory
Control or measure | Applies to (data state or scope) | Standard, algorithm, or method | Key or secret custodian | Verified in place | Last verified | Evidence reference | |
|---|---|---|---|---|---|---|---|
Please rate the effectiveness of the following mitigation areas as currently implemented
Not effective | Slightly effective | Moderately effective | Very effective | Fully effective | Not yet assessed | |
|---|---|---|---|---|---|---|
Protection of data at rest in the destination region | ||||||
Protection of data in transit and between services | ||||||
Control over who can access plaintext personal information | ||||||
Ability to detect and respond to unauthorised access | ||||||
Ability to respond to requests from public authorities in a controlled way | ||||||
Ability to withdraw, delete, or render the data unusable on short notice |
Residual technical risks, known limitations, and compensating measures
Please upload security architecture diagrams or control descriptions relevant to this transfer
Please upload the most recent independent audit, attestation, or assurance report for the destination environment
This section records the review conclusions and decisions of the privacy function and the legal function. A recorded decision reflects the reviewer's assessment on the basis of the information available at the time; it is not a guarantee of any regulatory or legal outcome.
Data protection officer or senior privacy reviewer name
Data protection officer contact email
Organisational unit of the privacy function
Privacy function review — please rate each area
Not satisfactory | Needs improvement | Acceptable with conditions | Satisfactory | Strong | Not assessed | |
|---|---|---|---|---|---|---|
Completeness and accuracy of the party and jurisdiction information | ||||||
Adequacy of data minimisation and purpose limitation | ||||||
Suitability of the stated transfer mechanism | ||||||
Quality of the transfer impact assessment | ||||||
Adequacy of encryption, key management, and access controls | ||||||
Clarity of the handling approach for authority requests | ||||||
Overall readiness to proceed with the transfer |
Privacy function clearance decision
Cleared to proceed
Cleared subject to conditions
Deferred pending further information
Not cleared
Escalated for further review
Privacy function summary, observations, and recommended safeguards
Date of privacy function review
Data protection officer or senior privacy reviewer signature
Chief legal officer or senior legal reviewer name
Chief legal officer contact email
Has the legal function reviewed the governing transfer agreement and any annexes?
Has the legal function considered the transfer impact assessment and its conclusions?
Are there any ongoing disputes, investigations, or claims that could bear on this transfer?
Legal function review — please rate each area
Very high concern | High concern | Moderate concern | Low concern | Minimal concern | Not assessed | |
|---|---|---|---|---|---|---|
Enforceability of the transfer mechanism as documented | ||||||
Adequacy of contractual protections against onward disclosure | ||||||
Exposure arising from the laws and practices of the destination jurisdiction | ||||||
Allocation of liability and indemnity between the parties | ||||||
Clarity of termination, suspension, and exit rights | ||||||
Overall legal risk of proceeding as proposed |
Legal function clearance decision
Approved to proceed
Approved subject to conditions
Deferred pending further information
Not approved
Escalated to a wider review body
Legal function summary, risk allocation notes, and required contract amendments
Date of legal function review
Chief legal officer or senior legal reviewer signature
Combined clearance status recorded for this transfer
Cleared to proceed
Cleared subject to conditions
Pending further review
Not cleared
Withdrawn by the requesting unit
Review cycle for this clearance record
Reviewed on every material change
Every 6 months
Annually
Every 24 months
At the end of the stated transfer period
Next scheduled review date
Is a periodic re-assessment trigger defined for material changes such as a change of region, sub-processor, or applicable rules?
I confirm that the information recorded in this form is accurate to the best of my knowledge and that supporting evidence has been attached where requested
I understand that this record documents a review process and does not by itself establish compliance with any particular legal requirement
Final notes, dissenting opinions, or matters reserved for a later decision