Alex is Sprintlaw’s co-founder and principal lawyer. Alex previously worked at a top-tier firm as a lawyer specialising in technology and media contracts, and founded a digital agency which he sold in 2015.
How To Use The IDTA In Practice: A Step-By-Step Checklist
- 1) Identify Whether You’re Making An International Transfer
- 2) Confirm Roles: Controller vs Processor
- 3) Choose The Correct Transfer Approach
- 4) Complete And Sign The IDTA (Properly)
- 5) Carry Out A Transfer Risk Assessment (And Add Safeguards If Needed)
- 6) Update Your Customer-Facing Documents And Internal Policies
- 7) Prepare For Incidents (Because They Happen)
- 8) Keep Records And Review Regularly
- Key Takeaways
If your business uses cloud software, outsources customer support, runs marketing campaigns, or stores data in online tools, there’s a good chance you’re transferring personal data outside the UK - even if you never “send” anything manually.
Under UK GDPR, international data transfers are tightly regulated. One of the most common legal tools UK businesses use to make those transfers lawful is the UK International Data Transfer Agreement (IDTA) - but it’s not the only option.
Below, we’ll break down what the UK IDTA is, when you need it, how to use it in real life, and the practical steps to stay compliant without drowning in legal jargon.
What Is The UK International Data Transfer Agreement (IDTA)?
The UK International Data Transfer Agreement (IDTA) is a standard form contract designed for UK organisations that transfer personal data to recipients outside the UK.
In plain English: if your business is exporting personal data internationally (for example, customer contact details, employee records, user analytics, or marketing lists), the IDTA is one way to make that transfer lawful under UK GDPR and the Data Protection Act 2018.
Why Does The IDTA Exist?
UK GDPR says you can’t transfer personal data outside the UK unless the transfer is protected in a legally recognised way.
That’s because when data leaves the UK, it may be exposed to:
- different privacy laws (some stronger, some weaker);
- different enforcement standards;
- government access rules that don’t align with UK standards; and
- increased security risks depending on how the data is stored and accessed.
The IDTA is intended to help you contractually require the overseas recipient to protect the data to standards similar to those required in the UK.
Is The IDTA The Only Option?
No. Depending on your transfer, there may be other “transfer mechanisms” available. A very common alternative is using the EU Standard Contractual Clauses (EU SCCs) together with the UK Addendum (issued by the ICO). But the IDTA is often a direct option for UK small businesses because it’s specifically designed for UK GDPR compliance.
In practice, your choice often depends on:
- where the data is going (which country);
- whether the recipient is a supplier/processor or another controller;
- the type of data (regular personal data vs special category data); and
- the risk profile of the transfer.
When Do UK Businesses Need An IDTA?
You generally need a transfer mechanism like the UK International Data Transfer Agreement when:
- your business is subject to UK GDPR; and
- you’re transferring personal data to a recipient outside the UK; and
- the destination country isn’t covered by a UK “adequacy” decision (more on that below).
Importantly, “transfer” can happen in ways that aren’t obvious. It’s not just emailing spreadsheets overseas.
Common Triggers (Even For Small Businesses)
You might need an IDTA if you:
- use a non-UK based CRM or email marketing platform;
- host your website or app on servers located outside the UK;
- outsource payroll, bookkeeping, or HR admin to an overseas provider;
- use an overseas call centre or virtual assistants;
- have a development team outside the UK who can access production data;
- share customer or employee data with a parent company or group company abroad.
What If The Data Just “Passes Through” Another Country?
International transfer rules can still be relevant where personal data is accessible from outside the UK - for example, if your supplier’s support team is based overseas and can remotely access your account containing personal data.
This is why it’s worth mapping your data flows, even at a high level. If you don’t know where your personal data is going, it’s very hard to be compliant (and even harder to respond confidently if a customer asks questions).
What About “Adequate” Countries?
UK GDPR allows international transfers to certain countries without needing an IDTA, if the UK has decided that the destination provides “adequate” protection.
Think of adequacy as the UK saying: “this country’s privacy framework is broadly comparable, so the risk is lower.”
But adequacy doesn’t apply everywhere - and adequacy decisions can change over time - so you shouldn’t assume you’re safe without checking.
What Does The IDTA Cover (And What It Doesn’t)?
The UK IDTA is a contract that imposes privacy and security obligations on the overseas recipient of the data.
It’s a key legal building block - but it’s not a magic shield that fixes everything.
What The IDTA Helps You Do
Used properly, the IDTA can help you:
- create enforceable contractual obligations on the overseas recipient;
- set baseline security and governance expectations;
- put a recognised UK GDPR transfer mechanism in place;
- clarify the parties’ roles (controller/processor) and responsibilities; and
- reduce the risk of unlawful transfers (which can trigger regulatory action, complaints, and contractual disputes).
What The IDTA Does Not Do On Its Own
The IDTA generally won’t be enough if you don’t also handle the operational side of compliance. For example, the IDTA won’t:
- map your data flows for you (you still need to understand what’s being transferred);
- replace your need for a proper Privacy Policy (your users still need to be informed);
- replace mandatory UK GDPR Article 28 processor terms in your supplier contract where a vendor processes personal data for you (you may still need a proper Data Processing Agreement alongside the IDTA);
- remove your obligation to assess transfer risk and consider additional safeguards; or
- fix an underlying problem if you’re collecting more personal data than you need in the first place.
In other words: the IDTA is part of your compliance setup, not the whole setup.
How To Use The IDTA In Practice: A Step-By-Step Checklist
If you’re a small business, you typically want a clear process you can apply again and again as you add new tools and suppliers.
Here’s a practical checklist you can work through.
1) Identify Whether You’re Making An International Transfer
Start with the basics:
- What personal data is involved (customers, users, employees, suppliers)?
- Who is receiving it (a vendor, group company, contractor)?
- Where are they located, and where is the data hosted?
- Can the data be accessed from outside the UK (including by support teams)?
A quick reality check: if you use modern cloud services, you’re probably dealing with international transfers somewhere in your stack.
2) Confirm Roles: Controller vs Processor
Before you sign anything, get clear on whether:
- you are acting as a controller (deciding why and how personal data is used);
- the overseas provider is acting as a processor (processing on your instructions); or
- you and the overseas party are both controllers (each making decisions about the data).
This matters because your contract structure may need more than just the IDTA. If you’re using a vendor to process data for you, you’ll typically also need processor-specific terms required by UK GDPR (often handled through a Data Processing Agreement or equivalent clauses in the main contract).
3) Choose The Correct Transfer Approach
Depending on the country and the relationship, you may be able to rely on:
- adequacy (no IDTA needed);
- the UK IDTA;
- the EU SCCs plus the UK Addendum; and/or
- other recognised transfer arrangements.
If you’re not sure which route applies, it’s worth getting advice early - because signing the wrong thing (or nothing at all) is one of the most common compliance gaps we see in growing businesses.
4) Complete And Sign The IDTA (Properly)
Even though the IDTA is a “standard” document, it still needs to be completed correctly.
Common details you’ll need to populate include:
- who the parties are (legal entity names, addresses, signatories);
- what data is being transferred (categories of data and data subjects);
- why the transfer is happening (purpose);
- security measures (technical and organisational);
- how long the data will be retained; and
- any onward transfers (sub-processors and downstream recipients).
This is where small businesses can accidentally trip up. If the description of the transfer is vague, incomplete, or doesn’t match reality, the contract may not provide the protection you think it does.
5) Carry Out A Transfer Risk Assessment (And Add Safeguards If Needed)
UK GDPR expects you to consider whether the transfer is actually safe in practice, not just “paper compliant”.
So you may need to consider:
- local laws and government access risks in the destination country;
- the nature of the data (for example, health data vs basic contact details);
- how the recipient will store, access, encrypt, and restrict data; and
- whether extra safeguards are needed (like encryption, pseudonymisation, access controls, or storing certain datasets only in the UK).
This step is especially important if you’re transferring sensitive personal data or doing anything high-risk (like profiling, extensive tracking, or processing at scale).
6) Update Your Customer-Facing Documents And Internal Policies
International transfers shouldn’t come as a surprise to the people whose data you’re handling.
That usually means making sure your Privacy Policy accurately explains:
- that international transfers occur;
- which countries data may be transferred to (where appropriate);
- why the transfers happen; and
- what safeguards you rely on (for example, the UK IDTA or the UK Addendum).
If you run an online business, you may also need to align your Cookie Policy with your analytics and advertising tools - because many tracking tools involve overseas transfers in the background.
And if your team accesses personal data as part of their roles, having clear internal rules around devices, access, storage, and secure handling can help (for example, through an Acceptable Use Policy).
7) Prepare For Incidents (Because They Happen)
Even with great suppliers and strong contracts, data incidents can still occur. A simple example: a staff member accidentally shares a file externally, or a vendor account gets compromised.
Having a Data Breach Response Plan means you’re not scrambling under pressure, and you can respond quickly with a clear chain of responsibility.
8) Keep Records And Review Regularly
International transfer compliance isn’t a one-off box tick.
As your business grows, you’ll likely add new software, new contractors, new markets, and new data processing activities. Each of those changes can affect your transfer position.
It’s smart to review international transfers when you:
- sign a new supplier contract;
- start storing a new type of data (for example, ID documents);
- expand into new territories;
- change hosting arrangements; or
- receive complaints or questions about data handling.
Common International Transfer Scenarios For Small Businesses
To make this more concrete, here are a few everyday examples where an IDTA (or similar safeguard) often becomes relevant.
Using Overseas SaaS Tools (CRM, Email Marketing, Analytics, Support)
This is probably the most common scenario. Many popular tools are run by overseas companies or host data across multiple regions.
If personal data is stored or accessed outside the UK, you’ll likely need:
- processor terms (where the provider is processing on your instructions);
- a compliant international transfer mechanism (often the IDTA or the UK Addendum); and
- website terms that match how your service actually operates.
If you provide software yourself, getting your SaaS Terms right can also be part of protecting your business - especially where your product touches personal data or uses overseas infrastructure.
Outsourcing Contractors Or Teams Abroad
Hiring developers, designers, virtual assistants, or support staff outside the UK can be a great way to grow efficiently.
But if those contractors can access personal data (for example, customer tickets, CRM records, or user accounts), you should treat that access like an international transfer.
In many cases, you’ll need a written agreement that covers:
- confidentiality and permitted use;
- security obligations;
- subcontracting restrictions; and
- international transfer safeguards (potentially including the IDTA).
Group Companies And International Expansion
If you have a UK company and a related company overseas (or you’re expanding internationally), it’s common to share personal data for finance, HR, or customer management purposes.
That kind of “intra-group” sharing can still be a regulated international transfer, and you may need a structured set of agreements and policies to make it lawful and manageable.
Ecommerce And Cross-Border Fulfilment
If you sell products online and use fulfilment partners outside the UK, you may be sharing customer data such as:
- names and delivery addresses;
- phone numbers and email addresses;
- order history and preferences; and
- returns or complaint information.
That can trigger both contract and privacy obligations - so it’s worth checking that your customer-facing documents, vendor terms, and internal processes are all aligned.
For many businesses, a solid starting point is putting an overall compliance framework in place (often through a GDPR package) and then layering in the right agreements for higher-risk suppliers and transfers.
Key Takeaways
- The UK International Data Transfer Agreement (IDTA) is a key legal tool for making overseas transfers of personal data lawful under UK GDPR.
- You may be making international transfers without realising it - especially if you use cloud tools, outsource overseas, or allow remote access to systems containing personal data.
- The IDTA doesn’t replace other UK GDPR requirements: where a supplier processes personal data for you, you’ll still need compliant Article 28 processor terms (often in a Data Processing Agreement), and you should explain transfers in your Privacy Policy.
- International transfers often require a practical risk assessment and, in some cases, additional safeguards like encryption, access controls, and strict onward-transfer rules.
- Keep your documents and processes up to date as your suppliers and systems change, and make sure you have an incident plan (such as a Data Breach Response Plan) so you can respond quickly if something goes wrong.
This article is general information only and not legal advice. If you’d like help reviewing your international data transfers, putting the right IDTA arrangements in place, or tightening up your UK GDPR compliance more broadly, you can reach us at 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.


