Sharing personal data outside Europe: what to check first

A sister company, a supplier or an IT provider outside the European Economic Area, or simply a cloud app: each can be an international transfer. Here is how to tell, and what to put in place.

Checked against the sources on 2 November 2026 6 min read

IN SHORT

  • Sending data to, or giving remote access to, an organisation outside the EEA is a transfer, including a company in your own group.
  • Without an adequacy decision you need a safeguard, usually the Commission’s 2021 standard contractual clauses in the right module, plus a documented transfer impact assessment.
  • The Article 49 exceptions are for occasional situations; a regular flow of data to a partner or supplier needs a proper transfer tool and a processor agreement where relevant.

Many Belgian companies work with someone outside Europe. It might be a sister company that handles orders, a supplier that needs customer addresses, an accountant or IT provider abroad, or a family partner who helps run the business from another country. Staff also use cloud tools and messaging apps hosted all over the world. Each of these can be an international transfer of personal data, and the GDPR sets conditions before data may leave.

The rules are not meant to stop international business. They make sure the protection travels with the data. Here is how to tell whether they apply to you, and what to check.

What counts as a transfer

The European Data Protection Board (EDPB) treats something as a transfer when three conditions are met:

  1. your company is subject to the GDPR for the processing in question;
  2. you send personal data to another organisation, or otherwise make it available to it;
  3. that organisation is in a country outside the European Economic Area (the EU plus Iceland, Liechtenstein and Norway), even if it is itself subject to the GDPR.

“Making available” includes remote access. If a provider abroad can log in to your system and see customer or staff data, that is a transfer even if the data never moves. The same goes for a sister company: a group of companies is not one organisation for these rules, so sharing within the group can be a transfer too.

Countries with an adequacy decision

The simplest case is a country that the European Commission has recognised as offering an essentially equivalent level of protection (Article 45). Data can flow to these countries as it does within the EEA, although every other GDPR rule still applies. The Commission keeps the current list of adequacy decisions on its website; check it rather than relying on memory, because it changes.

For the United States, the adequacy decision covers only organisations certified under the EU–US Data Privacy Framework. On 3 September 2025 the EU General Court dismissed a challenge to that decision (Latombe v Commission, T-553/23). An appeal to the Court of Justice is pending, so it is sensible to know which of your US providers rely on the framework, and what their contract says if it falls.

Countries without an adequacy decision

For a country without an adequacy decision, you need an appropriate safeguard under Article 46. For most small and medium-sized companies, that means the European Commission’s standard contractual clauses (SCCs), adopted in 2021 (Implementing Decision (EU) 2021/914).

The clauses come in four modules. You pick the one that matches the roles:

ModuleYou areThe recipient abroad isTypical example
1ControllerControllerA sister company or partner using the data for its own purposes
2ControllerProcessorAn IT provider, call centre or bookkeeper working on your instructions
3ProcessorSub-processorYou process data for a client and use a provider abroad
4ProcessorControllerYou return data to a client outside the EEA

The text of the clauses may not be changed. You choose the module and options, complete the annexes (what data, for what purpose, which security measures), and may add protections, but you cannot water them down. The 2021 clauses are also not designed for a recipient that is itself directly subject to the GDPR; that case needs specific advice.

Signing the clauses is the start of the work, not the end of it.

The transfer impact assessment

In Schrems II (C-311/18, 16 July 2020) the Court of Justice held that standard clauses are valid, but that the exporter must check whether the law and practice of the destination country allow the recipient to keep its promises. Clause 14 of the 2021 SCCs turns this into an obligation: before the transfer, both parties assess the situation and document it.

The EDPB’s Recommendations 01/2020 set out the steps:

  • know your transfers, including onward transfers;
  • identify the transfer tool you rely on;
  • assess whether anything in the law or practice of the destination country, such as broad access by public authorities, could undermine the clauses for this transfer;
  • where it could, add supplementary measures, for example strong encryption where the recipient does not hold the key, or pseudonymisation;
  • if no measure is enough, do not transfer, or stop.

For a small company this does not need to be a thesis. It needs to be honest, specific to the data and the recipient, and on file.

Why the exceptions rarely help

Article 49 lists derogations for specific situations, among them explicit consent after being told of the risks, transfers necessary for a contract with the person, important reasons of public interest, legal claims and vital interests. The EDPB reads them strictly. They are meant for occasional situations, not for a regular flow of data to a sister company or supplier.

A one-off booking for a customer’s trip abroad may fit. A monthly export of your customer database to a partner does not. If the transfer is part of how your business runs, you need adequacy or a safeguard such as the SCCs.

Contracts with providers

When a provider processes data on your behalf, Article 28 requires a processor agreement, wherever the provider is. Large cloud and messaging providers usually include a data processing addendum, often with SCCs built in. Read it, keep a copy, and check:

  • where the data is stored and from where support staff can access it;
  • which sub-processors are used, in which countries;
  • which transfer tool covers each of them;
  • how you are told about changes.

Free consumer versions of apps often come without such terms. If staff use them for customer or employee data, you may have transfers and processing with no contract at all.

Where to start

  1. List who sees your data abroad. Group companies, partners, suppliers, IT and software providers, and the apps your staff actually use.
  2. Find the tool for each. Adequacy decision, Data Privacy Framework certification, SCCs (and which module), or nothing yet.
  3. Document the assessment. For each transfer without adequacy, a short, specific transfer impact assessment and any extra measures.
  4. Put it in your records. Add transfers and their safeguards to your record of processing and privacy notice, and review them when a supplier or the law changes.

Sources

  1. Regulation (EU) 2016/679 (GDPR), Articles 28 and 44 to 49
  2. EDPB Guidelines 05/2021 on the interplay between Article 3 and Chapter V, version 2.0 (2023), what counts as a transfer
  3. European Commission, adequacy decisions, current list
  4. Commission Implementing Decision (EU) 2023/1795, EU–US Data Privacy Framework
  5. General Court, judgment of 3 September 2025, Latombe v Commission, T-553/23; appeal pending before the Court of Justice
  6. Commission Implementing Decision (EU) 2021/914, standard contractual clauses
  7. European Commission, questions and answers on the standard contractual clauses
  8. Court of Justice, judgment of 16 July 2020, Facebook Ireland and Schrems, C-311/18
  9. EDPB Recommendations 01/2020 on supplementary measures
  10. EDPB Guidelines 2/2018 on derogations of Article 49

General information, checked on 2 November 2026. Rules and decisions change, and every situation is different: this is not advice on your own case.

The information in this article is current as of 16/11/2026.

NEXT STEP

Put your transfers and supplier contracts in order

As part of a compliance programme we map who sees your data abroad, choose the right transfer tool, draft or review the processor agreements and clauses, and document the assessments. Privacy maintenance keeps them current when suppliers or the law change.