Skip to content
← All articlesOutsourcing

GDPR and Outsourced Software Development: A Practical Guide

How to stay GDPR-compliant when outsourcing software development offshore: data transfers, processor agreements, test data and a checklist for buyers.

If your product handles personal data of people in the UK or EU, working with an offshore development team does not remove your obligations under the GDPR (or the UK GDPR). You remain responsible for that data. The good news is that compliance in an outsourcing relationship is mostly a matter of clear contracts, sensible access rules and disciplined engineering habits.

This guide is general information for product and engineering leaders, not legal advice. Always confirm specifics with your own counsel or data protection officer.

Who is the controller and who is the processor?

Under the GDPR, the company deciding why and how personal data is used is the controller. A development partner that touches that data on your behalf is usually a processor. That distinction drives your paperwork:

  • You need a written data processing agreement (DPA) with the vendor.
  • The vendor may only process data on your documented instructions.
  • The vendor must tell you about any sub-processors it uses and get your approval.
  • The vendor must notify you of a personal data breach without undue delay, so you can meet your own reporting duties.

If your team works inside your systems and never takes data out, the exposure is smaller. If they work from copies, exports or their own environments, the DPA matters much more.

Cross-border transfers

Sending personal data from the UK or EU to a country such as India is a restricted transfer. It is allowed when an appropriate safeguard is in place. Commonly used mechanisms include:

  • Standard Contractual Clauses (SCCs) approved by the European Commission, or the UK’s International Data Transfer Agreement or Addendum for UK data.
  • A documented transfer risk assessment describing the legal environment and the technical protections in place.
  • Supplementary technical measures such as encryption and strict access control.

Your legal adviser should decide which mechanism applies. Engineering’s job is to make sure the technical promises in those documents are actually true.

The best strategy: do not send real data at all

Most development and testing work does not need production personal data. The strongest privacy control is to keep it out of non-production environments entirely.

Approach When it works Watch out for
Synthetic data New features, UI work, load tests Needs to look realistic enough to find bugs
Anonymised copies Reproducing data-shaped bugs Weak masking can be reversed; test the masking
Masked subsets Integration and UAT testing Keep referential integrity so tests stay meaningful
Live production access Rare, time-boxed incident support Needs approval, logging and a defined end date

Truly anonymised data falls outside the GDPR, but pseudonymised data does not, so be honest about which one you have.

Engineering controls that back up the contract

A DPA is only as good as the controls behind it. Ask your partner to demonstrate the following:

  • Least-privilege access. Each developer gets only the access their task needs, through named accounts, never shared logins.
  • Single sign-on and multi-factor authentication on code hosting, cloud consoles and ticketing tools.
  • Work inside your environment. Prefer your repositories and cloud accounts over copies on vendor machines. See our post on protecting IP when outsourcing software for the same principle applied to source code.
  • Secrets management. Credentials never live in code or chat. Our secrets management guide covers the practical setup.
  • Encryption in transit and at rest for any environment holding personal data.
  • Audit logs showing who accessed what, retained long enough to investigate an incident.
  • Offboarding. Access is revoked the same day someone leaves the project, and devices or exports are deleted.

Building privacy into the product

Compliance is not only about the vendor relationship. The software itself should support your obligations. Build these into the backlog from the start:

  • Data minimisation: collect only what the feature needs.
  • A clear lawful basis and consent capture where consent is required.
  • Ways to export and delete an individual’s data when they ask.
  • Retention rules that actually delete old data.
  • A record of which systems and third-party services receive personal data.

Retrofitting these is far more expensive than designing them in, so raise them during discovery and estimation.

A buyer’s checklist

Before signing with an offshore partner, confirm that:

  1. A DPA is part of the contract, alongside the MSA and SOW.
  2. Sub-processors are listed and any change requires your approval.
  3. The transfer mechanism and any risk assessment are documented.
  4. Production data is excluded from development and test environments by default.
  5. Access is least-privilege, MFA-protected and logged.
  6. Breach notification timelines are written down and rehearsed.
  7. Data is returned or deleted at the end of the engagement, with written confirmation.
  8. Staff with data access are bound by confidentiality obligations.

Putting it into practice

Treat data protection as a normal workstream: agree the rules in the contract, enforce them with tooling, and review them each quarter. Our software development contract guide explains how a DPA fits alongside the MSA and SOW.

If you are planning an engagement and want a team that works comfortably inside your security and privacy requirements, see how our dedicated development teams operate, or contact us to talk through your compliance needs.

Let’s build what’s next.

Tell us about your platform, your product idea or the systems you want to modernise. Someone from our Chennai engineering team will get back to you personally.