When a development project becomes a data transfer
Hiring a developer abroad is not a data transfer in itself. It becomes one when the team can see or handle personal data: logging into a live store with real customer accounts, receiving a database export, or reading support tickets that contain names and emails.
That distinction matters, because many projects never need real data. A new website, a Shopify theme or a custom application can be designed, built and tested with dummy data, then connected to the real system at launch by someone on your side. If the team never touches personal data, there is no transfer to justify.
Where a project does need real data, such as migrating a customer database or fixing a bug that only shows up in production, GDPR's rules on international transfers apply, and you need one of the legal routes below.
Route one: an adequacy decision
The European Commission can decide that a country protects personal data to a standard essentially equivalent to the EU's. Data can then flow there without extra safeguards. The Commission's list currently covers Andorra, Argentina, Brazil, Canada (commercial organisations), the Faroe Islands, Guernsey, Israel, the Isle of Man, Japan, Jersey, New Zealand, the Republic of Korea, Switzerland, the United Kingdom, the United States (for organisations in the EU-US Data Privacy Framework) and Uruguay.
If your developers work from one of those places, the transfer route is simple. Most offshore development markets are not on the list, Pakistan included, so for them you need the next route.
Route two: Standard Contractual Clauses
Standard Contractual Clauses are model contract terms, pre-approved by the Commission, that oblige the receiving party to protect the data to EU standards. The current set was adopted on 4 June 2021 in Implementing Decision (EU) 2021/914, and it replaced the older clauses.
The clauses come in modules for different relationships. For a development agency working on your systems, you are usually the controller and the agency is the processor, so the controller-to-processor module applies. You sign them alongside your normal data processing terms.
Signing is not quite the end of it. Since the Schrems II judgment, exporters are expected to check whether anything in the destination country's law would stop the clauses working in practice, and to add measures if needed. This is usually called a transfer impact assessment. For a development project, sensible measures are short, specific access, encryption, and keeping data in your own systems rather than copying it out.
Route three: derogations, and why they rarely fit
GDPR also allows transfers in specific situations without adequacy or clauses, for example with someone's explicit consent or where a transfer is necessary for a contract with them. These derogations are meant for occasional cases. They do not suit an ongoing development project where a team works with your data week after week, so do not rely on them for this.
How to set up the project so the risk stays small
The best approach is to make the question smaller. Most of the risk disappears if you decide early which parts of the project really need personal data.
Build and test with dummy or anonymised data by default. Give real access only for the tasks that need it, for as long as they need it, through accounts you control and can switch off. Keep the data in your own systems: let the team work in your Shopify admin or your cloud account rather than sending them exports. And keep the code in a repository you own, so access is easy to review.
If you are a UK business rather than an EU one, the structure is the same but the paperwork differs. The UK uses its own International Data Transfer Agreement or the UK Addendum to the EU clauses, and our offshore vs UK agency guide covers that side.
This is general information, not legal advice. Your data protection adviser should confirm the setup for your business.
Sources
Frequently asked
Quick answers
Is Pakistan covered by an EU adequacy decision?
No. Pakistan is not on the European Commission's list of countries with an adequacy decision, so transfers of personal data to a team there normally rely on Standard Contractual Clauses.
Do I need Standard Contractual Clauses if the developers never see customer data?
Not for the transfer itself, because no personal data is transferred. That is why building and testing with dummy data is the simplest protection. Once real data is involved, for example in a migration, the clauses are needed.
Which SCC module applies to a development agency?
Usually controller-to-processor, because you decide what happens to the data and the agency handles it on your instructions. If the agency used a subcontractor, the processor-to-processor module could also come into play.
Does the same apply to UK businesses?
The principles are the same, but the UK has its own documents: the International Data Transfer Agreement or the UK Addendum to the EU clauses. A UK business working with a team outside the UK should use those.



