Skip to content

Agency operations

White-label marketing from India for US and UK agencies: contracts, data, time zones and the SOW

Some US and UK agencies use a team in India for design, content, ads management or development, and keep their own name on the work. The model is lawful when it is set up properly. The risks sit in four places: client data, ownership of the work, working hours, and an SOW that leaves too much unsaid. This guide covers each from the primary texts.

The question a client eventually asks

Picture a six-person agency in Leeds. It has run a retailer’s paid social and email for two years, with an Indian team doing the builds and reports overnight. Then the retailer’s new operations director sends a data questionnaire: list every sub-processor, the countries they work from, and the transfer mechanism for each.

If the honest answer is “a team in Pune, on an email agreement”, the agency has a problem. It may be in breach of its own contract with the client, and it may not own the reports and creative it has been invoicing for. None of that is hard to fix, but it has to be fixed before the questionnaire arrives, not after.

Is your Indian partner a sub-processor?

If it touches personal data, almost certainly. Under the GDPR, your client is usually the controller of its customers’ data, your agency is its processor, and anyone you hand that work to is a sub-processor. That includes a partner who only logs into the client’s CRM, email platform, or an ad account that holds lead forms or customer lists.

Article 28(2) of the GDPR says: “The processor shall not engage another processor without prior specific or general written authorisation of the controller.” Under a general authorisation, the processor “shall inform the controller of any intended changes concerning the addition or replacement of other processors”, so the client can object. And under Article 28(4), if the sub-processor fails, “the initial processor shall remain fully liable to the controller”.

So white-label has a limit. Your brand can stay on the work, but where personal data is involved, your contract with the client must allow sub-processors and you must tell the client when you add one. Read your client contracts first. Some agency agreements already contain a general authorisation; others forbid sub-processing outright.

Is India on the safe list for data transfers?

No. The European Commission’s list of adequacy decisions does not include India, and nor does the ICO’s list of UK adequacy regulations. Without adequacy, the ICO says, a transfer must be “covered by appropriate safeguards” or rely on an exception.

Remote access counts. The ICO’s own guide to international transfers (updated 15 January 2026) uses almost exactly this situation as its example: a UK business that uses “an organisation in India” and does not send it any files, but allows it “access to the personal information you hold on your systems.” Its conclusion: “you’re making a restricted transfer.” It adds that the rules “apply to all restricted transfers, even small, infrequent ones.”

What do you sign for the transfer?

For UK GDPR

The ICO offers two sets of clauses: the International Data Transfer Agreement (IDTA), or the International Data Transfer Addendum (“in force 21 March 2022”) added to the EU’s standard clauses. The ICO is clear that “The EU SCCs are not valid on their own for restricted transfers under the UK GDPR.” It also says it plans “to update the IDTA and Addendum in the course of 2026” and that you “should continue to use the current versions”, so check that page on the day you sign.

Before relying on either, you need a transfer risk assessment. Since the Data (Use and Access) Act 2025, whose transfer provisions came into force on 5 February 2026 (SI 2026/82, Wayback copy), the ICO says UK law calls this a “data protection test”: you must decide, “acting reasonably and proportionately”, that protection is “not materially lower than in the UK” after the transfer. The ICO’s page on transfer risk assessments explains it, and an assessment done properly before the Act still counts.

For EU GDPR

The European Commission’s standard contractual clauses (Decision 2021/914) are built in modules. Module Three covers a processor passing work to another processor, and its sub-processing clause offers an option where the Indian partner may not sub-contract “without the prior specific written authorisation of the controller”, which means your client, not you. The decision says the clauses also cover the matters in Article 28(3) and (4). Clause 14 asks both sides to assess the destination country’s laws and practices before relying on the clauses.

Our understanding: Module Three fits most simply where your agency is established in the EU. A UK or US agency with an EU client usually needs its own transfer route from that client first, such as the EU’s adequacy decision for the UK, the EU-US Data Privacy Framework or the clauses themselves, and the Indian partner then comes in under that route’s onward-transfer and sub-processor rules (for a UK agency, the UK GDPR transfer rules above). This is the part to take to a lawyer.

What must the processing terms say?

Article 28(3) lists the terms a processor contract must contain, and the ICO’s contract guidance restates them for the UK. The same terms should flow down from your agency to the Indian partner:

TermWhat it means in a white-label deal
Processing only on documented instructionsThe partner acts only on your written instructions. The ICO says “any written form, including email” works, if it can be saved.
Duty of confidenceEveryone at the partner who sees client data is bound to confidentiality.
Appropriate security measuresArticle 32 security. In practice, name the controls: individual logins, two-factor authentication, no shared passwords, client data off personal devices.
Using sub-processorsNo freelancers or new tools without your prior written authorisation, with the same terms passed down.
Data subjects’ rightsThe partner helps you answer access and deletion requests.
Assisting the controllerHelp with security, breach notification and impact assessments.
End-of-contract provisionsAt your choice, delete or return all data, and delete copies.
Audits and inspectionsThe partner gives you the information to show compliance and allows audits.

The ICO notes that the current contracts guidance is “under review” because of the Data (Use and Access) Act. It also says the Danish data protection authority’s standard clauses for processors, approved by the European Data Protection Board, should meet the requirements if used “without amendment”. Article 28(10) carries a warning for both sides: a processor that starts deciding the purposes and means of processing “shall be considered to be a controller” for that processing.

What changes if your clients are in the US?

As we understand it, there is no general federal equivalent of Article 28; outside a few regulated sectors, the rules depend on the state. California is the example most agencies meet. Its consumer privacy law says that a business disclosing personal information to a service provider “shall enter into an agreement” that, among other things, specifies that the data is disclosed “only for limited and specified purposes” (Civil Code 1798.100(d)). A “service provider” must work under a written contract that bars selling or sharing the data, using it for other purposes, or combining it with data from elsewhere (1798.140(ag)). If the service provider brings in someone else, it must notify the business and bind that person by written contract.

The California Privacy Protection Agency’s regulations (effective 1 January 2026) add detail in section 7051. The business purpose “shall not be described in generic terms”; the contract must require the provider to say when it “can no longer meet its obligations”; and the business’s checks may include assessments or audits “at least once every 12 months”. These rules bite when your client is a covered business under the law. Your agency is then usually its service provider, and the duty to notify the client and bind your Indian partner by written contract applies to you. Ask a US lawyer whether your clients are covered; the contract terms are good practice either way.

What does Indian law add?

Less than many agencies fear, but not nothing. India’s Digital Personal Data Protection Act, 2023 has a specific exemption in section 17(1)(d) for personal data “of Data Principals not within the territory of India” processed under a contract “with any person outside the territory of India by any person based in India”. Once the Act’s main duties commence, that will cover your clients’ customer data, about people outside India, handled by an Indian partner under its contract with you.

The exemption is partial. Section 8(1), which makes the Data Fiduciary (the party that decides why and how the data is processed) responsible for processing done on its behalf “irrespective of any agreement to the contrary”, and section 8(5), on “reasonable security safeguards”, are not lifted by it. In a white-label chain the Data Fiduciary is usually your client, so in practice these duties reach your Indian partner through the security and processor terms in your contract. The exemption also covers only people outside India: a campaign aimed at Indian customers is outside it. The Act’s main duties become enforceable on 13 May 2027, according to PIB, in line with the government’s commencement notification of 13 November 2025, which brings the Act’s core duties, sections 3 to 17 apart from section 6(9), into force eighteen months after that date, and the DPDP Rules.

Separately, CERT-In’s directions of 28 April 2022 require service providers and body corporates in India to report listed cyber incidents, including data breaches, “within 6 hours of noticing such incidents”, and to keep logs of their ICT systems for “a rolling period of 180 days” within India. Write your own notification clause so that your partner tells you at the same time it tells CERT-In, not after.

Who owns the work your partner produces?

Not you, unless the contract says so in the right form. The default in all three countries is that the author owns the copyright, and paying for the work does not move it to you. India has one exception worth knowing: a photograph, painting, portrait, engraving or film made for payment at someone’s request belongs to that person unless agreed otherwise (section 17(b)). Who that person is depends on the chain: it can be your agency, if you briefed and paid for the shoot, or your Indian partner, if it hired a freelancer. The rule gives way to any agreement, so do not rely on it: take the signed assignment either way.

CountryThe defaultWhat makes the transfer work
United Kingdom“The author of a work is the first owner” (CDPA 1988, section 11); an employer owns an employee’s work“An assignment of copyright is not effective unless it is in writing signed by or on behalf of the assignor” (section 90(3))
United StatesA commissioned work is “made for hire” only in nine listed categories, and only with a written instrument signed by both parties (17 USC 101)Any transfer must be “in writing and signed” (17 USC 204(a)), so pair a work-for-hire clause with a backup assignment
IndiaThe author is the first owner; an employer owns work made under a “contract of service”, and a photograph or film made for payment at someone’s request belongs to that person unless agreed otherwise (Copyright Act 1957, section 17)A signed written assignment that names the work, the rights, the duration, the territory and the royalty or other consideration (section 19)

Sources: CDPA section 11 and section 90 (Wayback copies of legislation.gov.uk), 17 USC 101, 17 USC 201 and 204, and the Copyright Act, 1957.

The Indian rule holds two traps for a foreign agency. Section 19(5): “If the period of assignment is not stated, it shall be deemed to be five years from the date of assignment.” Section 19(6): if the territory is not stated, “it shall be presumed to extend within India.” And under section 19(4), rights the assignee does not exercise within a year may lapse “unless otherwise specified”. An assignment clause should therefore say worldwide, for the full term of copyright, and that non-use does not cause a lapse. Our view: if your contract is governed by UK or US law, still make the assignment meet section 19, since the work is made in India.

Ask how your partner’s own people are engaged. In our reading, a freelancer is not an employee under a contract of service, so their work needs its own signed assignment to the partner before the partner can assign it to you.

How many working hours will you actually share?

India Standard Time is UTC plus 5:30, maintained by CSIR-NPL. The UK and the US move their clocks, on different dates. The UK moves forward on the last Sunday in March and back on the last Sunday in October; the US, per NIST, on the second Sunday of March and the first Sunday of November. Our arithmetic from those rules:

PeriodLondonNew YorkLos Angeles
Winter (UK from the last Sunday in October, US from the first Sunday in November)India 5.5 hours ahead10.5 hours ahead13.5 hours ahead
Summer (US from the second Sunday in March, UK from the last Sunday in March)4.5 hours ahead9.5 hours ahead12.5 hours ahead
Mismatch weeks (14 to 27 March 2027; 31 October to 6 November 2027)5.5 hours ahead9.5 hours ahead12.5 hours ahead

With an Indian day of 10:00 to 18:00 and a UK day of 09:00 to 17:00, you share about 4.5 hours in British Summer Time and 3.5 hours in winter. With New York there is no overlap at all on those hours; the Indian team has to work a later shift. A 14:00 to 22:00 IST shift shares about 3.5 hours of the New York morning in US summer and 2.5 hours in winter, and almost nothing with the West Coast, where work with a team in India runs as a next-morning handover. Agree the shift in writing, and agree what “end of day” means: whose day, in which time zone.

The gap can work in your favour: briefs sent in the afternoon come back as drafts the next morning. That only works if the brief is complete when it leaves. A half-written brief costs a full day.

What should the SOW say?

The master agreement carries the legal terms; the statement of work is where most white-label arrangements actually go wrong. A workable SOW covers:

  • Deliverables and acceptance: what counts as done, who signs it off, and how many revision rounds are included.
  • Response windows in a named time zone: for example, a reply within four working hours, UK time, during the overlap.
  • Access: which client systems the partner may log into, with individual logins under the client’s or your account, never shared passwords. Accounts stay in the client’s name.
  • White-label rules: no partner branding, no direct contact with your client, and what happens if the client contacts the partner directly.
  • Named sub-processors and tools: the partner’s freelancers, software and AI tools that will see client data, with a change notice period.
  • Incidents: notify you within a stated number of hours, and before or alongside any report to CERT-In.
  • Exit: return or deletion of all client data and copies, with written confirmation.
  • Ownership: signed assignment, worldwide, full term, including drafts and source files, flowing down from any freelancer.
  • Payment and tax: currency, invoicing schedule and who bears bank charges. Your partner can tell you whether it supplies as an export of services under a Letter of Undertaking; under India’s IGST Act, section 16, exports of services are zero rated.

Indian agencies on the other side of this arrangement face their own contract questions, especially when AI services are involved. Our guide to white-label AI contracts covers that side, and our checklist for choosing an agency lists what to ask any partner about account ownership and reporting.

A checklist before the first client file is shared

  1. Read each client contract: does it allow sub-processors, and what notice does it require?
  2. Sign a processing agreement with the partner that carries every Article 28(3) term, flowed down from your client contract.
  3. Sign the transfer safeguard: the IDTA or the UK Addendum for UK GDPR, and for EU GDPR the route that fits where your agency is established (see above); record your transfer risk assessment.
  4. For US clients, add California-style service provider terms: specific purpose, no selling or sharing, notice if the partner can no longer comply, audit rights.
  5. Put a signed copyright assignment in place: worldwide, full term, no lapse, and backed by assignments from the partner’s freelancers.
  6. Agree the shared hours, the shift and the response windows, in writing, with the mismatch weeks marked.
  7. Write the SOW: deliverables, acceptance, access, white-label rules, incidents, exit and payment.
  8. Diary a review of the ICO pages: its contracts guidance says it is “under review”, and it plans to update the IDTA and Addendum in 2026.

QUESTIONS

Common questions

Can a UK agency use a white-label team in India under UK GDPR?

Yes, with the right paperwork. India has no UK adequacy regulations, so the agency needs the IDTA or the UK Addendum to the EU clauses and a transfer risk assessment. The ICO treats remote access to UK data from India as a restricted transfer, even if no file is sent. A processor contract with the Article 28 terms is also required.

Do I have to tell my client I use an Indian white-label partner?

If the partner handles personal data, usually yes. Article 28(2) of the GDPR bars a processor from engaging another processor without the controller’s prior written authorisation, and under a general authorisation the processor must inform the controller of new sub-processors. Your brand can stay on the work; the data relationship cannot be hidden.

Who owns the creative made by an Indian contractor?

Generally the author owns it first under Indian, UK and US law, and payment does not transfer it to you. India has an exception for photographs and films made for payment at someone’s request, but who that person is depends on the chain, so take a signed written assignment either way. Under India’s Copyright Act, an assignment that does not state its duration is deemed to last five years, and one that does not state territory is presumed to cover only India, so state worldwide and the full term.

Does India’s DPDP Act apply to UK or US customer data processed in India?

Mostly not, once the Act’s main duties commence on 13 May 2027. Section 17(1)(d) will exempt personal data of people outside India processed in India under a contract with a person outside India. Sections 8(1) and 8(5), on the Data Fiduciary’s responsibility for processors and on reasonable security safeguards, will still apply. CERT-In’s six-hour incident reporting already applies to service providers in India.

How many working hours overlap between India and the UK or US?

India is 4.5 hours ahead of the UK in British Summer Time and 5.5 hours ahead in winter, so a normal Indian day shares about three and a half to four and a half hours with a UK day. With US Eastern time, India is 9.5 or 10.5 hours ahead, so overlap needs a later shift in India.

REFERENCES

Sources and further reading

Each link was opened and checked on .

← All field notes