Transfer Impact Assessment (TIA)
Version: 1.0 · 30 June 2026 Classification: Internal (Operational Use)
The Transfer Impact Assessment (TIA) module of EterShield allows organisations to document, assess and approve transfers of personal data to countries outside the European Economic Area (EEA), in compliance with GDPR Art. 46, the Schrems II case law (CJEU, C-311/18) and the EDPB guidance (Recommendations 01/2020 on supplementary measures).
1. Definitions
| Term | Definition |
|---|---|
| International transfer | Any operation of sending, making available or accessing personal data by a recipient established outside the EEA |
| Third country | A country that is not part of the EEA and has no applicable European Commission adequacy decision |
| Transfer mechanism | The legal ground that legitimises the transfer: adequacy decision, SCCs, BCR or Art. 49 derogation |
| TIA | Transfer Impact Assessment: a legal and factual analysis that determines whether the chosen mechanism offers protection equivalent to that of the GDPR |
| Schrems II | CJEU judgment (16/07/2020) that invalidated the Privacy Shield and imposed the obligation to carry out a TIA before any transfer to the US under SCCs |
| DPF | EU-US Data Privacy Framework: the EU-US adequacy mechanism; subject to high legal risk following a court decision in 2026 |
| Supplementary measures | Additional technical (encryption, pseudonymisation) or contractual measures applied to close protection gaps in the destination country |
| DPF Watch | Automatic EterShield feature that identifies DPF/adequacy→US transfers without an associated TIA |
2. Subject Matter and Scope
2.1 Subject matter
The TIA module supports compliance with GDPR Art. 46 by EterShield's customer organisations, allowing them to:
- Catalogue all international transfers of personal data
- Assess the legal framework of the destination country (surveillance risk, available legal remedies, access by authorities)
- Select and document the appropriate transfer mechanism
- Define and record supplementary measures
- Approve or reject transfers on the basis of documented analysis
- Monitor the continued validity of the mechanisms in force
2.2 Legal basis
| Ground | Reference |
|---|---|
| Obligation to ensure adequate protection | GDPR Art. 44 |
| Transfer mechanisms | GDPR Art. 46 (SCCs, BCR) and Art. 45 (adequacy) |
| Specific derogations | GDPR Art. 49 |
| Obligation to carry out a TIA | CJEU C-311/18 (Schrems II) + EDPB Recommendations 01/2020 |
| Supplementary measures | EDPB Recommendations 01/2020 (updated 2021) |
2.3 Scope of application
The module is applicable to any EterShield customer organisation that:
- Uses services from providers established outside the EEA
- Transfers personal data to subsidiaries, partners or customers in third countries
- Uses cloud, analytics or AI tools with processing outside the EEA
2.4 Availability
In production since 30 June 2026. Access it from Transfer Impact Assessment (TIA).
3. Data Model
3.1 Main fields
| Field | Type | Description |
|---|---|---|
destinationCountry |
Text | Destination country of the transfer (e.g. USA, India, Brazil) |
mechanism |
Enumeration | Legal ground for the transfer; see the table of values |
surveillanceRiskAssessment |
Free text | Assessment of the legal framework of the destination country: surveillance legislation, access by authorities, data subjects' legal remedies |
supplementaryMeasures |
Free text | Additional technical and organisational measures applied (e.g. end-to-end encryption, pseudonymisation, reinforced contractual clauses) |
residualRisk |
Enumeration | Risk level after measures: LOW / MEDIUM / HIGH / CRITICAL |
decision |
Text | Final decision on the transfer |
decisionRationale |
Free text | Legal and factual grounds for the decision |
reviewDate |
Date | Deadline for reassessment |
status |
Enumeration | Life cycle status; see §4 |
3.2 Values of the mechanism field
| Value | Name | Description |
|---|---|---|
ADEQUACY |
Adequacy decision | The European Commission has recognised the country as adequate: free transfer |
SCC |
Standard Contractual Clauses | SCCs approved by the EC (Decision 2021/914): the standard mechanism |
BCR |
Binding Corporate Rules | For multinational groups with BCR approved by the supervisory authority |
DPF |
EU-US Data Privacy Framework | EU-US mechanism: subject to legal risk; verify validity before using |
DEROGATION |
Art. 49 derogation | Specific and exceptional cases: explicit consent, performance of a contract, vital public interest |
3.3 Optional links
A TIA can be associated with:
| Module | Field | Purpose |
|---|---|---|
| Data Flow | dataFlowId |
Identify the technical data flow that supports the transfer |
| RoPA (ProcessingActivity) | processingActivityId |
Link to the GDPR Art. 30 processing activity |
| Supplier (Vendor) | vendorId |
Associate with the supplier receiving the data |
| DPA | dpaId |
Link to the Data Processing Agreement entered into |
4. Usage Flow
4.1 Life cycle (statuses)
| Status | Description | Who acts |
|---|---|---|
DRAFT |
In preparation: no legal effect; data can be edited freely | MANAGER |
UNDER_REVIEW |
Submitted for review: awaiting decision by the GDPR officer | ADMIN / MANAGER |
APPROVED |
Approved: the transfer has a valid documentary basis | ADMIN / SUPER_ADMIN |
REJECTED |
Rejected: the transfer cannot proceed | ADMIN / SUPER_ADMIN |
NEEDS_REVISION |
Requires changes before resubmission | ADMIN / SUPER_ADMIN |
4.2 Recommended process
Step 1: Identify the transfer Determine the destination country, the recipient, the categories of personal data transferred and the approximate volume. Check the registered Data Flows to confirm whether the transfer is already documented.
Step 2: Select the mechanism Check whether an adequacy decision exists for the country concerned. If not, use SCCs as the standard mechanism. BCR apply only to groups with prior approval. Avoid the DPF as the sole mechanism while legal uncertainty persists.
Step 3: Assess the surveillance risk
Analyse the legal framework of the destination country: is there legislation that requires the recipient to share data with authorities? Do data subjects have effective legal remedies? This analysis must be documented in the surveillanceRiskAssessment field.
Step 4: Define supplementary measures If the legal framework of the destination country has gaps (governmental access without guarantees equivalent to those of the EU), define supplementary measures. Examples: end-to-end encryption with a key controlled by the Controller, pseudonymisation before the transfer, additional contractual non-disclosure clauses.
Step 5: Determine the residual risk and decide With the supplementary measures in place, assess the residual risk. If it is LOW or MEDIUM, the transfer may be approved. If it is HIGH or CRITICAL, the transfer must be rejected or suspended until additional measures are implemented.
Step 6: Submit for approval
Change the status to UNDER_REVIEW and notify the GDPR officer. After review, the status becomes APPROVED, REJECTED or NEEDS_REVISION.
Step 7: Monitor and review The review date must be set (maximum 12 months). The system generates an automatic alert when the date approaches. Review immediately in the event of a legislative change, a change of supplier or invalidation of the mechanism.
5. Integration with Other Modules
5.1 Data Flows
The Data Flows module documents the technical flows of personal data. Each flow with the "International transfer" field filled in must have an associated TIA. The link creates GDPR traceability from Art. 30 to Art. 46.
5.2 RoPA
The RoPA module records the processing activities under GDPR Art. 30. An activity that includes international transfers must be linked to the corresponding TIA, making the record of activities auditable in its entirety.
5.3 Suppliers (TPRM)
The Suppliers module records the details of the recipients. Associating the TIA with the supplier makes it possible to quickly identify all transfers to a given recipient and their approval status.
5.4 DPA (Data Processing Agreement)
The DPA module records the Data Processing Agreements entered into with sub-processors. The TIA complements the DPA: while the DPA governs the contractual obligations, the TIA documents the prior legal assessment that justifies entering into the agreement.
5.5 DPF Watch
DPF Watch is an automatic monitoring feature integrated into the Privacy dashboard. Without any manual configuration, the system:
- Identifies all Data Flows and DPAs with an international transfer whose mechanism is
DPForADEQUACYwith the US as destination - Checks whether each has an associated TIA with status
APPROVED - If there are transfers without coverage, displays a red alert on the DPF Watch card with the number of uncovered flows
- On click, redirects to Transfer Impact Assessment (TIA) with the filtered list, where the missing assessments can be created
DPF Watch does not replace the TIA: it is a control mechanism that ensures no transfer is left unassessed.
6. Good Practices and FAQ
I have signed SCCs with the supplier. Is that enough to transfer? SCCs are necessary but not sufficient after Schrems II. A prior TIA is mandatory to confirm that the SCCs offer adequate protection in the specific context of the destination country.
The supplier is DPF-certified. Do I need a TIA? Given the current legal risk of the DPF (challenged in court since 2026), it is recommended to keep SCCs as a parallel mechanism and to document a TIA regardless of the supplier's DPF certification.
How often should I review the TIA? At least every 12 months, or immediately after: a legislative change in the destination country, a change of supplier or data location, a judicial invalidation of the transfer mechanism, or a security incident affecting the transfer.
The residual risk is HIGH. Can I approve the transfer? It is not recommended. HIGH or CRITICAL residual risk indicates that the supplementary measures are insufficient. The transfer must be suspended until additional measures are implemented, or an alternative must be explored (EU-based supplier, data processed locally).
What do I record in the "Surveillance risk assessment" field? Document: (a) the existence of mass surveillance legislation in the country (e.g. FISA 702, EO 12333 in the US); (b) whether the authorities can access data without notifying the data subject; (c) whether the data subject has effective means of judicial redress; (d) references to the EDPB reports or legal analyses used.
How do I document effective supplementary measures? Describe concretely: the type of encryption and who controls the keys; pseudonymisation applied before the transfer and the correspondence table kept in the EU; additional contractual clauses that prevent the recipient from handing over data to authorities without prior notification.