- Grounds the requirement that SCC transfers be suspended or prohibited if the required EU level of protection cannot be ensured.
"suspended or prohibited"
Use this workflow before sending personal data from the EEA to a third country or international organisation without relying only on a contract label.
It keeps adequacy checks, SCC module selection, Clause 14 assessment, importer evidence, supplementary measures, and stop-transfer decisions in one auditable transfer record.
Structured answer sets in this page tree.
Cited legal and guidance references.
This workflow is for GDPR Chapter V transfer reviews where personal data leaves the EEA and the team needs to decide whether an adequacy decision is enough, whether standard contractual clauses are needed, and whether the transfer also needs supplementary measures after Schrems II.
Open one transfer record for each distinct exporter, importer, destination country, transfer tool, data set, and processing purpose. Do not group unrelated vendors or destinations into one generic TIA because the SCC assessment depends on the transfer's specific circumstances.
First decide whether the destination is covered by a current adequacy decision for the relevant recipient and sector. If it is, record the adequacy route and keep evidence that the recipient actually falls inside the decision. If it is not, move to the Article 46 transfer-tool review.
Where the transfer uses SCCs, the contract package should identify the right module and complete the appendices before the team signs off the transfer assessment. Empty annexes, generic security descriptions, or missing onward-transfer details make the assessment hard to defend.
The 2021 SCCs use a modular structure for different transfer scenarios. The workflow should therefore tie the selected module to the actual exporter/importer roles, then attach the transfer details, technical and organisational measures, sub-processor information where relevant, and competent supervisory authority details.
The TIA should answer one narrow question: in the circumstances of this transfer, can the chosen Article 46 tool work effectively in the destination country, or do local laws and practices undermine the protection promised by the SCCs?
Schrems II and the SCCs require a case-by-case assessment. The record should cover the transfer facts, the destination-country laws and practices relevant to the importer and data, the importer evidence, and any safeguards already in place.
The workflow should end in an explicit transfer decision, not a vague risk note. A transfer can proceed under SCCs only when the team can explain why the SCCs, together with any supplementary measures, ensure the required level of protection for that transfer.
If destination laws or practices prevent the importer from complying and effective supplementary measures cannot close the gap, the record should say that the transfer must not start or must be suspended or ended.
A useful transfer record lets privacy, legal, vendor-management, and security teams reconstruct the decision without searching email threads. Keep the evidence close to the vendor or system record so it is updated when the service, country, subprocessors, or data categories change.
Reopen the workflow when the transfer facts change, the importer reports an inability to comply, there is a new or changed public-authority access risk, supplementary measures stop working, SCC annexes change, or adequacy coverage changes.
Sorena can help convert SCC packages, importer evidence, TIA conclusions, and supplementary-measure controls into reusable transfer records for GDPR work.
Ask source-linked questions about adequacy, SCCs, TIA evidence, and supplementary measures using the cited sources on this page.
Review your transfer route, SCC annexes, importer evidence, and supplementary-measure gaps with Sorena.
"suspended or prohibited"
"document any request for disclosure"
"make such documentation available"
"maintain, amend or withdraw"
"companies in the United States that participate"
"Standard Contractual Clauses"
"transfers of personal data to third countries"