Short answer: Your practice is the controller and the provider is your processor, so you need a written Article 28 contract. Giving a team in India access to client data is a restricted transfer, and India has no UK adequacy regulations, so you also need a safeguard such as the ICO's IDTA and a transfer risk assessment.

Controller and processor

You decide why and how client data is used, so you are the controller. The provider works only on your instructions, so it is a processor. UK GDPR requires a written contract that limits the processor to your documented instructions, commits its people to confidentiality, requires appropriate security, bars sub-processors without your written authorisation, and covers deleting or returning data at the end (ICO guidance on processor contracts).

Remote access still counts as a transfer

Practices sometimes assume nothing is transferred if the data stays in their own Xero or IRIS. The ICO says otherwise. Making personal information accessible to a separate organisation outside the UK is a restricted transfer, and its own example is a UK business giving an organisation in India access to data on its systems. Because your practice initiates that transfer, you are responsible for complying with the transfer rules, and the rules apply to all restricted transfers, even small, infrequent ones (ICO brief guide to international transfers). One login to one client's file is enough.

Adequacy, safeguards and the risk assessment

UK adequacy regulations cover the EEA and a short list of other countries. India is not on it (ICO adequacy list). Without adequacy, the transfer needs an appropriate safeguard, such as the ICO's International Data Transfer Agreement or the UK Addendum to the EU standard contractual clauses, and you must complete a transfer risk assessment (ICO). Keep the signed documents and the assessment on file.

Your privacy notice also has to mention the transfer. See do I have to tell my clients?

What EarthOne signs

We sign a GDPR-aligned Data Processing Agreement before any work begins. It covers sub-processor restrictions, breach notification and the return or deletion of data at the end. Our privacy policy sets out the transfer safeguards we rely on. We sign the ICO's International Data Transfer Agreement (IDTA) with our clients, and we use encrypted transfer and role-based access. To review our standard DPA before you speak to us, email [email protected].

Related service: Our Data Processing Agreement. All other questions are in the UK practice outsourcing FAQ.

Ask us about your practice

Tell us the work you want to outsource, your software and roughly how many clients. Ketul replies within one business day with the model that fits and the cost. Or email [email protected].

Book a free 30-minute consultation

Related questions

Does working in our own software avoid a restricted transfer?
No. The ICO treats making personal information accessible to a separate organisation outside the UK as a restricted transfer, even when the data stays on your systems. Working in your own software still helps, because you control and can remove access.
What must a controller and processor contract include?
Processing only on your documented instructions, confidentiality commitments, appropriate security, no sub-processors without your written authorisation, help with data subject rights and breaches, deletion or return of data at the end, and audit rights.