
3
Nov
Yes, UK businesses can legally outsource personal data to India. India has no UK adequacy regulations, so most arrangements need the IDTA or UK Addendum, a documented transfer risk assessment and Article 28 processor terms before an Indian team sees any personal data. Remote access counts, even when the data stays on UK servers.
Every UK business thinking about an Indian BPO partner eventually asks the same question: will this break UK data rules? It is a fair concern. The UK Government's Cyber Security Breaches Survey 2025/2026 found that 43% of UK businesses, or around 612,000 firms, identified a breach or attack in the previous year. Only 15% formally reviewed the cyber risks from their immediate suppliers, and just 6% reviewed their wider supply chain.
The money at stake is real. UK GDPR fines can reach £17.5 million or 4% of worldwide annual turnover, whichever is higher. In October 2025, the ICO fined Capita £14 million after a breach affecting 6.6 million people, and £6 million of that fell on a group company acting as a processor. This guide explains exactly what UK law requires, who owns each task and how to set up outsourcing to India step by step.
Yes. UK law does not ban outsourcing to India. It controls how personal data reaches, or becomes accessible to, organisations outside the UK.
The ICO says every restricted transfer must be covered by one of three mechanisms: adequacy regulations, appropriate safeguards or an exception.
| Transfer mechanism | Does it work for India? | What it means for you |
|---|---|---|
| Adequacy regulations | No | India is not covered, so data cannot move on this basis |
| Appropriate safeguards | Yes, this is the normal route | Use the IDTA or UK Addendum with a transfer risk assessment |
| Exceptions | Rarely | Too narrow for planned, repeated outsourcing work |
The UK-India trade agreement took effect on 15 July 2026, but it did not replace these rules. The UK Government says personal data transfers remain protected under UK data protection law.
For routine customer support, payroll or back office work, plan on using an appropriate safeguard and a transfer risk assessment.
Outsourcing to India is a restricted transfer when all three parts of the ICO's test are met. The ICO's own brief guide uses a UK business with an Indian customer service provider as an example.
Yes. The ICO's example is a UK business using an Indian IT support company through a VPN. The data stays on UK servers, but a restricted transfer takes place when the Indian company accesses it.
This is the first point we explain to UK buyers. Keeping your CRM in the UK can reduce risk, but it does not remove the transfer rules.
| Scenario | Restricted transfer? | Why |
|---|---|---|
| Indian agents answer tickets in your UK-hosted helpdesk | Yes | Remote access makes data available to a separate organisation |
| Your own employee logs in from India on holiday | No | The employee is part of the same legal entity |
| An independent contractor in India uses your systems | Yes | The contractor is a separate legal entity |
| Your Indian group company supports your UK company | Yes | Group companies are separate legal entities |
| A provider works only on truly anonymous data | No | Anonymous information is not personal data |
| Your processor works on pseudonymised data | Yes | Pseudonymised data remains personal data in this situation |
This table simplifies the ICO's examples, so check your exact data flow against its guidance. The ICO also offers an interactive transfers tool that takes about 10 minutes.
The organisation that initiates the restricted transfer is responsible for the transfer rules. If you contract directly with an Indian provider, that is normally you.
| Your setup | Who normally initiates the transfer? | What you still need to do |
|---|---|---|
| You contract directly with an Indian provider | You, as controller | Put the safeguard and transfer risk assessment in place |
| A UK provider uses its Indian team or subcontractor | The UK provider, for that transfer | Authorise the arrangement and make reasonable checks |
| You contract separately with UK and Indian providers and instruct the data flow | You, as controller | Treat the transfer as yours, even if the UK provider sends the files |
| Your Indian provider uses another overseas sub-processor | Depends on whether UK GDPR applies to the Indian provider's processing | Control sub-processors through your contract and checks |
The ICO's rule of thumb is simple: you are not initiating a transfer if you did not design its structure or choose the receiver. It also tells you to follow the contractual relationships.
No. A UK contracting entity may take responsibility for the transfer, but your wider UK GDPR duties remain. A controller must still choose a processor offering sufficient guarantees.
Yes. In the Capita case, the ICO fined the controller £8 million and the processor £6 million. A provider cannot treat data protection as only the client's problem, and a client cannot treat compliance as fully outsourced.
Use the IDTA for a UK-only arrangement if you want a standalone UK document. Use the UK Addendum if your provider already uses the EU SCCs or the contract also covers EU personal data. Neither one replaces your Article 28 contract.
| Option | Best for | Main advantage | Watch out for |
|---|---|---|---|
| IDTA | UK-only data flows | A dedicated UK document | You need another mechanism if EU GDPR also applies |
| EU SCCs with the UK Addendum | Providers handling UK and EU data | Works alongside an existing EU contract set | Both documents must be completed correctly |
| Binding corporate rules | Large corporate groups | Covers transfers inside a group | Not designed for a typical SME and third-party BPO relationship |
| Article 49 exception | Limited, specific cases | No safeguard contract | Too narrow for routine outsourcing |
For a UK-only customer support or back office contract, we would normally start with the IDTA. If you also serve EU customers, we would use the EU SCCs and UK Addendum so one contract set can cover both data flows.
EU data needs separate attention because UK and EU rules now take different approaches. A UK assessment may not be enough for EU customer records, so ask your adviser to confirm the choice against your actual data.
A transfer risk assessment (TRA) checks whether protection after the transfer will be not materially lower than in the UK. UK legislation now calls this the "data protection test", but the ICO still uses the term TRA.
The assessment looks at two main risks: access by public authorities or other third parties, and whether rights and contractual protections can be enforced. Follow these five steps.
Record the provider, location, service, systems, data types, people affected, transfer frequency and retention period. A vague description produces a weak assessment.
Give more weight to data that could cause harm if exposed. The ICO's TRA tool provides initial risk scores by data category. Basic order details and health records should not receive the same treatment.
We would review these points as a minimum:
| Indian law or rule | Why it belongs in your TRA |
|---|---|
| Section 69 of the IT Act 2000 | It allows government directions for interception, monitoring or decryption on specified grounds |
| DPDP Act Section 17(2)(a) | It lets the government exempt notified State bodies from the Act for specified purposes |
| DPDP Act Section 17(1)(d) | It disapplies many duties for foreign data processed under a foreign contract, but keeps Sections 8(1) and 8(5) |
| CERT-In directions | They require reporting of specified cyber incidents within six hours and log retention for 180 days |
Do not treat this table as your full legal review. Your answer depends on your own data, contract and service.
Record your conclusion and the reasons. Review it if the data, service, location, sub-processors or Indian law changes.
A TRA must reflect the real service, so a generic template will not be enough.
Follow these steps in order and finish them before the provider gets live access. The ICO expects your transfer mechanism to be in place at the point you make the information accessible.
List each service, system, data field and legal entity. Include CRMs, helpdesks, call recordings, shared inboxes, spreadsheets and backups.
The ICO says you must check whether you can achieve your aim without making a restricted transfer. Remove fields the team does not need, and anonymise data where you can.
Decide who is the controller, processor and sub-processor. The provider usually acts as your processor for support or back office work, but check any data it uses for its own purposes.
Record whether each flow is restricted and who initiates it. Do this per service, as payroll and customer support may use different tools and teams.
Review certificates, policies, sub-processors, access controls and incident procedures. Our guides on how to choose a BPO service provider in India and choosing a secure BPO partner cover the wider vendor checks.
Sign the IDTA or UK Addendum and record the TRA. Whoever initiates the transfer owns this step.
Complete the Article 28 terms. Update your privacy information and processing records, and complete a DPIA if the work is likely to create a high risk to people.
Start with a pilot, using limited access or test data where practical. Review access logs, staff changes, sub-processors and incidents on a schedule.
Tip: treat go-live access as your deadline. If the paperwork is not finished, the team should not have access yet.
Your contract should combine Article 28 processor terms, a transfer mechanism and service-specific security controls. An NDA protects confidentiality, but it does not provide these terms.
| Contract area | What it should say in practice |
|---|---|
| Scope | Subject matter, duration, nature and purpose of processing, data types and people affected |
| Instructions | The provider acts only on documented instructions, including for transfers |
| Confidentiality | Everyone handling the data is bound by confidentiality duties |
| Security | The provider applies appropriate Article 32 security measures |
| Sub-processors | The provider needs your authorisation and must pass on the same duties |
| Rights requests | The provider helps you answer access, deletion and other rights requests |
| Breaches and DPIAs | The provider supports your security, breach and impact assessment duties |
| End of contract | The provider deletes or returns data as you choose, unless law requires it to keep the data |
| Audit | The provider shares information and allows audits or inspections |
These are not all listed in Article 28, but we would add them to an Indian BPO contract:
If a provider offers only an NDA, the paperwork is incomplete.
The core transfer process survived, but the legal test, regulator structure and penalty risk changed. India also began phasing in its own data protection law. This is a summary as of November 2026, not legal advice.
| Date | Change | What it means for you |
|---|---|---|
| 13 November 2025 | India notified its DPDP Rules | India began a phased rollout of the DPDP Act |
| 15 January 2026 | The ICO updated its transfer guidance | The three-step test and clearer role allocation became the main reference |
| 5 February 2026 | Data (Use and Access) Act transfer provisions commenced | "Not materially lower" became the standard to apply |
| 5 February 2026 | Maximum PECR fines rose | Fines moved from £500,000 to £17.5 million or 4% of global turnover |
| 15 July 2026 | The UK-India trade deal took effect | Personal data transfers remain subject to UK data protection law |
| 30 September 2026 | The Information Commission took over | The regulator is still called the ICO, now meaning Information Commission's Office |
| 13 November 2026 | DPDP Consent Manager provisions start | This mainly affects India's consent system, not a typical UK outsourcing contract |
| 13 May 2027 | Main DPDP duties and penalties start | Providers must be ready for the Act's core rules, including those for their own Indian data |
It makes the test more practical, but it does not remove the work. You still need a safeguard, a TRA where required and any extra measures the assessment identifies.
Only partly. Section 17(1)(d) disapplies many DPDP duties when an Indian provider processes data of people outside India under a contract with a foreign company. Sections 8(1) and 8(5) continue to apply, covering data fiduciary responsibility and reasonable security safeguards.
Do not assume Indian rights such as access or erasure will protect your UK customers directly. Your UK contract must deliver what UK GDPR requires.
Risk depends on the data, not the service label. Health, payroll and HR records need more protection than routine product enquiries. These ratings are our practical starting point, not legal categories, and your TRA should set the final rating.
| Service | Typical personal data | Starting risk rating | Control to prioritise |
|---|---|---|---|
| Healthcare BPO | Health and insurance details | High | Strict need-to-know access and a DPIA check |
| HR outsourcing | Employee, absence and disciplinary records | High | Separate access for sensitive records |
| Payroll processing | Salary, bank and tax details | High | Field masking and approval checks |
| Finance and accounting | Bank details and customer or supplier records | Medium to high | Segregated duties and activity logs |
| Customer support | Contact details, orders, complaints and recordings | Medium | Recording rules and limited CRM permissions |
| Technical support | System logs and account access | Medium, or higher with admin access | Time-limited privileged access |
| Data entry and document processing | Varies by document | Low to high | Redaction and secure file handling |
| Telemarketing and lead generation | Names, phone numbers and marketing preferences | Medium, plus PECR risk | Lawful data sources and TPS screening |
UK marketing calls raise two questions: can the data go to India, and can you lawfully make the call? Transfer paperwork answers only the first question. PECR still applies, and its maximum fine now reaches £17.5 million or 4% of global turnover.
ICO registration shows that an organisation appears on the ICO's register of fee payers. It does not prove that a provider's transfers, contracts or security meet UK GDPR. We say this as a company that displays an ICO registration: it is a useful check, but never the only one.
| Ask for | A good answer | A warning sign |
|---|---|---|
| Transfer document | A completed IDTA or UK Addendum for your service, or a clear owner for it | "Our NDA covers this" |
| TRA information | Details of locations, laws, access requests and security measures | No knowledge of Indian government access rules |
| Data processing agreement | Article 28 terms before any live access | A DPA offered only after go-live |
| Sub-processor list | Named companies, locations and purposes | "We may use partners" |
| Security evidence | A current certificate and clear scope | A logo with no certificate or scope |
| Incident process | Named contacts and a stated notice period | "We will inform you as soon as possible" |
| Access controls | Role-based access, MFA and logs | Shared logins |
| Exit process | Written return, deletion and access removal steps | No end-of-contract process |
No. ISO 27001 is strong security evidence, but it does not replace your safeguard, TRA or Article 28 contract. Check that the certificate covers the service and location you are buying.
For a broader security review, read our guide on how secure data entry outsourcing is. If you are comparing support options, our UK and US customer support outsourcing guide covers costs and pricing models.
These checks also matter when you compare data entry services or finance and accounting outsourcing.
We built SkyOs BPO to serve UK businesses from Mohali, so we expect buyers to test our paperwork as well as our service. You can review our certifications and data security approach before you speak to us.
| Area | What we can show |
|---|---|
| Quality management | ISO 9001:2015, certificate no. 25-07-2016099 |
| Information security | ISO 27001:2022, certificate no. 25-07-21156582 |
| UK regulator register | ICO registration reference ZB882728 |
| People controls | NDAs covering individuals on your account |
| Access controls | Role-based access, so operators see only what their task requires |
| Data handling | Encrypted file transfer and a signed DPA for UK clients |
Before work starts, we should agree your data flows, the contracting entity, the transfer mechanism, the TRA information you need, and who can access which systems. We would rather finish the paperwork first than rush your team into a risky launch.
Outsourcing to India under UK GDPR works when you treat data protection as part of the setup, not a clause to add later. Map your data, confirm who initiates the transfer, put the right safeguard and TRA in place, and sign Article 28 terms before anyone gets access.
Choose a provider on evidence rather than badges. Ask for the documents, check the certificate scope, and start with a small pilot. The rules changed in 2026, but outsourcing to India remains workable for UK businesses that do the paperwork properly.
If you are planning to outsource, send us your process and data flow. We will tell you what can move, what should stay in the UK and which documents your team needs.
No country is "GDPR compliant" in the way this question suggests. Compliance depends on your specific arrangement. For example, a Mohali support team may have strong security, yet the UK client still needs the right safeguard and contract.
No. A UK retailer using Indian agents would therefore normally use the IDTA or UK Addendum, plus a TRA. Check the ICO's latest list before you sign, because adequacy decisions can change.
Usually, yes, or another valid safeguard. Access from India counts. Imagine an Indian agent opening your UK-hosted helpdesk to answer a refund request. The ticket stays in the UK, but that access can still create a restricted transfer.
No. A DPA covers how the processor handles data for you, but it does not replace the transfer mechanism or TRA. In a payroll contract, for example, the DPA controls the work, while the IDTA and TRA address the international transfer.
The organisation that initiates the restricted transfer. If you sign directly with an Indian provider, that is normally you, although the provider should supply the facts you need. If a UK provider subcontracts to India, the UK provider is usually responsible for that transfer.
Yes, if the transfer is lawful and access is controlled. For example, a customer may mention a medical condition during a refund call. Limit who can hear recordings, set a retention period and stop sensitive details being captured where possible.
Yes. Your privacy information should explain transfers outside the UK and the safeguards you use. A short, accurate update is better than a vague line about "trusted partners". Check whether your customer contracts also limit offshore processing.
It can. If you are subject to EU GDPR, you must check the EU transfer rules separately. A UK online shop selling into Ireland, for example, may need a contract set that works for both regimes.
Yes, but we would treat it as high risk. Start with a DPIA check, tighter access and stronger exit controls. For a UK clinic outsourcing appointment admin, we would first remove any medical detail the team does not need.

The SkyOS BPO Team is a group of outsourcing specialists delivering end-to-end solutions across customer support, healthcare BPO, finance & accounting, data entry and processing, IT services, and back-office operations. We partner with global organizations to improve efficiency, maintain compliance, and drive sustainable growth.

Leave A Comment