Skip to content

Agency operations

White-label AI services for Indian agencies: what goes in the contract

An agency that sells an AI chatbot, a WhatsApp assistant or AI-written content under its own name is standing between two contracts: the one with its client, and the one with whoever built the thing. Above both sit the terms of Meta and the AI model vendors, which neither the agency nor the builder can change. Many white-label disputes start where those layers do not line up. This guide is for the agency owner and the provider sitting down to agree terms. It is general information, not legal advice, and we build AI systems for agencies ourselves, so read it with that in mind.

Referral, reseller or white label: which are you?

One test lawyers use for software partner deals comes from a US firm’s summary: the questions are “who pays you, who signs the end-user contract, and who provisions the service.” Applied to an agency:

ModelWho the client contracts withWho supports the clientWhat the agency carries
ReferralThe providerThe providerLittle. The agency introduces and may earn a fee, but cannot sign contracts for the provider.
ResellerThe agency takes the order and the payment; the provider’s own terms usually still govern the serviceUsually sharedBilling and the client relationship.
White labelThe agency, under its own brandThe agency, at the front lineAlmost everything the client sees, including blame when it breaks.

Indian contract law draws a similar line. Under the Indian Contract Act, 1872, an agent acts for a principal and is not usually bound by the contracts it makes for one. In a true white label you contract with the client in your own name, so you are bound as a principal. Even if you think of yourself as the provider’s agent, section 230 presumes an agent is personally bound when it does not disclose the name of its principal, and in a white label the client usually does not know the provider exists. Price and write the contract as the principal.

What do Meta and the AI vendors allow?

The rule that saves most agencies trouble: never promise a client more than your own upstream terms allow you to give.

WhatsApp

Meta’s main partner types are Solution Partners and Tech Providers (a Tech Partner is a Tech Provider that has joined Meta’s partner programme). Solution Partners “can directly invoice their clients”, and Meta describes becoming one as “a lengthy process”. Businesses onboarded by a Tech Provider “must provide their own payment method”; Meta bills them for API use and the Tech Provider bills for its other services (Meta). If you are neither, you are working through someone who is, and their terms bind you.

Ownership follows whose business portfolio the number is set up in. If the client goes through Meta’s Embedded Signup with its own portfolio, Meta says it will “own all of their WhatsApp assets” and have full access to WhatsApp Manager, and tells partners “you cannot restrict this access in any way.” The older model of a partner holding accounts on a client’s behalf has been deprecated. So onboard each client into its own portfolio, never yours, and the client owns the number whatever brand is on your invoice. One more thing Meta decides: its account model gives each partner its own Messaging account for templates and billing, and says a Messaging account cannot be moved to another business. If the client changes provider and its templates and billing sit in the old partner’s Messaging account, they may have to be set up again; a Messaging account the client owns can be shared with up to two partners.

Meta’s terms for the WhatsApp Business Platform add three limits that matter for white label. Clause 4.1(c) says you must not “distribute, sell, resell, or rent the WhatsApp Business Platform to third parties”; you are selling a service built on it, not access to it. Clause 4.1(g) bars you from impersonating anyone or misrepresenting your affiliation (“impersonate or register on behalf of any person or entity or otherwise misrepresent your affiliation”), so the WhatsApp account should be the client’s, in the client’s own name, not the agency’s account dressed in the client’s brand. And clause 4.7 bars providers of AI technology, including “general-purpose artificial intelligence assistants”, from using the platform where the AI is “the primary (rather than incidental or ancillary) functionality”, as Meta decides. Meta allows exceptions only where it is legally required to permit AI providers, which its page for AI providers lists as Brazil, Turkiye, Italy and a group of European markets; India is not among them.

A bot that answers questions about a clinic’s timings or a shop’s orders is very likely a business using AI along the way. A general-purpose assistant is the clear target. The grey zone is a bot whose answers are the product the client’s customers come for, such as an AI tutor or an AI astrologer. Meta decides where the line falls, so keep what you sell on the incidental side and write the scope into the contract. The same clause says a business may retain an AI provider as its Solution Provider, with one condition: WhatsApp data, including anonymised, aggregated or derived forms, must not be used to build, train or improve any AI system, except to fine-tune a model used only by that business. Put that in the contract too, and make sure the model tier the provider uses does not train on what it is sent.

AI model vendors

The large model vendors let you build products for your own customers, but not resell raw access. Anthropic’s Commercial Terms allow customers to power products for “its own customers and end users” and bar reselling the services except as expressly approved, while its Usage Policy says consumer-facing chatbots “must disclose to users that they are interacting with AI rather than a human”. OpenAI’s Services Agreement lets a customer make its applications available to end users, makes the customer responsible for them, and says the customer “may not resell or lease access to its Account”. Google’s Gemini API terms say the API may not be used in services directed at, or likely to be used by, people under 18, and that content sent through unpaid tiers is used to improve Google’s products while paid tiers’ is not.

In practice: either the provider runs the model accounts in its own name, or the client owns them and adds the provider as a member of its organisation or project. API keys are never passed between companies. Use paid tiers for client data, and pass the vendors’ usage rules down the chain in writing.

Which clauses should the contract cover?

Picture a Pune agency running a WhatsApp assistant for a dental clinic, built by a provider in another city. One Monday the clinic’s number is restricted after patients complain about messages. The clinic rings the agency, the agency rings the provider, and the provider points at Meta. Who pays for the lost week, who files the appeal, who reports the incident and who owns the number are all decided by paperwork that is easier to write before that Monday than after it.

The same list works whether you are the agency signing with a provider or the agency signing with its client; only the direction changes.

ClauseWhy it mattersWhat to agree
Who owns the accountsIf the client is onboarded into its own business portfolio, Meta makes it the owner of its WhatsApp assets.Client owns the number, its WhatsApp account, its Meta business portfolio and any ad accounts. Provider and agency hold access, not ownership.
Platform and AI rulesA breach by any party can get the client’s number restricted.Each party follows Meta’s and the model vendor’s policies, which are attached or linked. The bot tells users it is AI.
Billing upstreamMeta bills either the partner or the client directly, depending on the partner type.Whose payment method or credit line pays Meta and the model vendors, how it is passed on, and what happens if a payment fails.
Opt-in and noticesMeta makes the business responsible for opt-in.Who collects and records WhatsApp opt-in, who drafts the privacy notice, and who keeps it up to date.
Data rolesUnder the DPDP Act, the client will usually be the Data Fiduciary.Agency and provider act as Data Processors, only on instructions, under a written contract with a security clause.
Training on client chatsWhere an AI provider is retained as Solution Provider, Meta’s clause 4.7 forbids using WhatsApp data to train or improve AI, except a model used only by that business.No training on client WhatsApp data, including anonymised, aggregated or derived forms; model tiers that do not train on inputs; the same promise from every sub-processor.
Sub-processorsFrom May 2027, a customer can ask the client which processors their data went to.A list of every company that touches the data (model vendor, hosting, WhatsApp partner), with countries, and notice before any change.
IncidentsEvery party that notices an incident has its own CERT-In duty, which cannot be passed on.Each party tells the others within a fixed number of hours (agree the number) of noticing an incident, in both directions.
Intellectual propertyCopyright assignments in India need writing and detail.Who owns the prompts, workflows, knowledge base and outputs; what is licensed rather than assigned; for how long and where.
Liability and indemnityThe agency faces the client; the provider faces the vendors.The agency’s cap to its client should not exceed what it can recover from the provider plus what it is willing to carry itself; indemnities for each party’s own policy or data breaches.
Service levelsSome failures are Meta’s, not yours.Response and fix times for what the provider controls. Template approvals, quality ratings and account bans excluded as outcomes.
ExitClients leave, and providers stop trading.Export of conversation data, knowledge base and template wording in usable form; erasure after the legal retention period; help sharing the client’s WhatsApp account with the new partner and unsharing it from the old one, knowing templates and billing may need to be set up again if they sat in the old partner’s Messaging account.
Upstream changesMeta and the vendors change terms and prices.A right to reprice or exit on notice when an upstream change makes the service unworkable.

What does the DPDP Act change for white-label deals?

Once its main duties commence on 13 May 2027, the DPDP Act makes the business that decides why and how data is used, usually your client, responsible for processing done on its behalf “irrespective of any agreement to the contrary”, and lets it use a processor “only under a valid contract”. The DPDP Rules require that contract to include a provision for reasonable security safeguards. After a breach, the client must tell the Data Protection Board and each affected person without delay, and send the Board a detailed report within seventy-two hours of becoming aware of it. The Act does not use the word “sub-processor”, but from May 2027 a person who gave consent can ask the client for the identities of every processor their data was shared with, so the list has to exist.

Two things to settle now. First, roles: if your agency decides what the bot does with customer data for its own purposes, such as reusing leads across clients (which Meta’s terms separately forbid for WhatsApp data), it may be a Data Fiduciary in its own right, with all the duties that brings. Second, erasure: from May 2027 the Rules will require the client, as Data Fiduciary, to keep personal data and processing logs, including its processors’ copies, for at least a year, so “delete everything the day the contract ends” and “keep logs for a year” have to be reconciled in writing. Our DPDP guide for small businesses covers the duties in detail.

Who must report a security incident?

Every party that notices it. The CERT-In Directions of April 2022 require service providers and body corporates to report listed cyber incidents, including data breaches and data leaks, “within 6 hours of noticing”. CERT-In’s FAQ says “Any entity which notices the cyber security incident, shall report to CERT-In” and that the obligation “is neither transferrable nor indemnified or dispense with”. It also says “body corporate” includes a sole proprietorship. The same Directions ask these businesses to keep logs of their systems for a rolling 180 days. A clause saying the provider handles all incident reporting does not take the duty off the agency. Each party’s six hours run from when it notices the incident or is told of it, so a contract cannot make anyone late or early under CERT-In. What it can do is make sure the client hears fast enough to file its own report, and, once the DPDP duties commence, to tell the Data Protection Board without delay.

Who owns the bot, the prompts and the content?

Under the Copyright Act, 1957, the author is the first owner of a work. An employer owns what an employee makes in the course of employment. For most work an outside firm makes, such as code, prompts and written content, the firm is the first owner, and the client gets ownership only through a written assignment. (Commissioned photographs, paintings, portraits, engravings and films are an exception: the person who commissions and pays for them owns them unless agreed otherwise.) For computer-generated work, the Act names as author “the person who causes the work to be created”. Whether purely AI-generated output is protected at all is not settled in India, which is another reason to deal with outputs by contract. Section 19 requires an assignment to be in writing, signed by the assignor or their authorised agent, and to identify the work, the rights, the duration and the territory, and the royalty or other consideration payable (in practice, the fee is usually stated). Where an assignment leaves out the duration, the law treats it as five years; where it leaves out the territory, India; and rights not used within a year of the assignment can lapse unless the assignment says otherwise.

For a white-label AI service, list each piece separately: the provider’s underlying platform and code (usually licensed, not assigned), the client-specific workflows and prompts, the knowledge base built from the client’s documents, and the outputs the system produces. The model vendors’ terms generally give their customer the outputs; pass that down so the client ends up owning what was made for it.

Can you stop a provider or client from working with each other?

Not with a broad non-compete. Section 27 of the Contract Act makes an agreement void to the extent it restrains someone from exercising a lawful profession, trade or business, with a narrow exception for the sale of goodwill. Clauses that stop a provider approaching your clients after the contract ends are often unenforceable in India. Restrictions that apply only while the contract runs, such as the provider not dealing directly with your clients during the term, are generally on firmer ground. Confidentiality clauses, and a clear description of what each side brings and keeps, protect an agency better still. Take legal advice on any restraint you want to rely on.

What should an agency never promise its client?

  • Outcomes Meta controls: template approval, a verified badge, messaging limits, or that a number will never be restricted.
  • That the AI will never make a mistake. Promise the review, the handoff to a person and the fix time instead.
  • That the client’s data never leaves India, unless every processor in the chain has confirmed it in writing.
  • Ownership of anything you only hold a licence to.

A checklist before you sign

  1. Write down which model you are in: referral, reseller or white label.
  2. Confirm the provider’s Meta status (Solution Partner, Tech Provider or working through one) and the model vendors it uses.
  3. Onboard the client into its own Meta business portfolio, so it owns its WhatsApp number and account.
  4. Attach or link the Meta and AI vendor policies, and agree that the bot discloses it is AI.
  5. Name the data roles, get the sub-processor list with countries, and rule out training on client WhatsApp data in any form.
  6. Agree a fixed incident notice time, in hours, in both directions.
  7. List the IP: platform, workflows, prompts, knowledge base, outputs. Assign or license each in writing.
  8. Line up liability caps and indemnities between the two contracts.
  9. Agree service levels that exclude what Meta decides.
  10. Agree the exit: export, erasure after the retention period, and the handover of the WhatsApp account to a new partner.
  11. Ask your accountant how GST applies to the way you bill.

QUESTIONS

Common questions

Can an agency white-label a WhatsApp chatbot in India?

Yes, through a Meta Solution Partner or Tech Provider. If the client is onboarded into its own business portfolio, it owns its WhatsApp number and account and keeps full access to WhatsApp Manager. Meta’s terms bar reselling the platform itself, impersonating another business, and offering AI on WhatsApp where the AI is the main product rather than part of a business’s own service.

Can I resell access to an AI model under my agency’s brand?

Not raw access. Anthropic’s and OpenAI’s terms allow building applications for your own customers but bar reselling the service or access to the account (Anthropic allows it only with express approval), and Google’s APIs terms bar sublicensing an API to third parties. Sell the finished service, run the accounts properly, and never hand out API keys.

Who is responsible for client data in a white-label AI service?

From 13 May 2027, under the DPDP Act, usually the client, as Data Fiduciary, whatever the contract says. The agency and provider act as processors and should do so only under a written contract with security safeguards.

Can a contract make the provider responsible for reporting cyber incidents?

It can make the provider tell you quickly, but it cannot take away your own duty. CERT-In says its six-hour reporting obligation is neither transferable nor indemnified.

Is a non-compete clause with a white-label provider enforceable in India?

Usually not, if it restrains the provider’s trade after the contract ends. Section 27 of the Indian Contract Act makes such restraints void, with a narrow exception for the sale of goodwill. Rely on confidentiality and clear ownership instead, and take legal advice.

REFERENCES

Sources and further reading

Each link was opened and checked on .

← All field notes