Vendor profiles · AI customer-service agent on WhatsApp

Before a UK firm switches on Meta Business Agent

Reviewed by Michael K. Onyekwere, CIPP/ELast reviewed 15 October 2026

Independent compliance research from Janus Compliance. Not legal advice.

This note is for UK firms deciding whether to switch on Meta Business Agent, if and when it reaches them. It answers customers on WhatsApp, and it can hand a chat over to the business. WhatsApp's help centre says "This feature is currently only available in limited countries to select businesses."

A business that switches it on chooses to put its customers' messages through Meta's AI, and it chooses what those customers are told. Under the UK GDPR those look like controller decisions for the business, whatever role Meta takes.

These are the questions a UK firm should be able to answer before the agent goes live (none of them is a finding that anyone is in breach):

1. What role does Meta play, and for which processing?

The Addendum to Meta's Business Agents and Platform Terms (last updated 16 July 2026) names Meta as the business's "Processor/Service Provider" for listed processing. One listed instruction is to "create and maintain Customer profiles for Company for customer relationship management based on Interface Data". Interface Data covers the chats themselves. The same Addendum lets Meta use "Designated Interface Data" (broadly, chats on Meta's own apps, and on other channels where Meta's user terms apply) as "Content", and the terms say Meta "has independently obtained rights to use that content from such consumer end-users under separate terms".

The terms and the Addendum do not use the word "controller" themselves. The Addendum, however, incorporates Meta's Global Processor Terms as its Data Processor Terms, and their European Region Terms say that, for UK personal data Meta processes as the business's processor, "Company is the Controller and Meta UK Processor is the Processor for the purposes of the UK GDPR". Meta UK Processor is defined as "Meta Platforms, Inc. or where applicable the Meta Affiliate that is party to the Applicable Terms".

None of these documents states Meta's role for the chats it uses as Content. For that use the terms point elsewhere: "Meta may use Content and related information as described in the Meta Terms of Service and Meta Privacy Policy". The Privacy Policy served in the UK says "The data controller responsible for your information is Meta Platforms, Inc.", but it does not mention Meta Business Agent.

So the same customer chats fall under two sets of terms (some processing on the business's instructions, some under rights Meta says it holds itself). A firm should map which processing falls on which side, as its records and its privacy notice both depend on that map. It should also record which Meta company acts as its processor and how the processor data reaches it. The European Region Terms say that transfers of that data from the business to Meta UK Processor "shall be governed by the UK Addendum" (the ICO's International Data Transfer Addendum to the EU standard contractual clauses), except where the destination is treated as adequate. That clause does not cover the chats Meta uses as Content.

2. Will customer chats train Meta's models, and can the business stop it?

The terms let Meta use Content "to improve our artificial intelligence models and algorithms, including Business Agents", and say it may do so "through automated or manual (i.e. human) review and through third-party vendors in some instances". WhatsApp's help centre says "Messages sent or received in chats that have connected Meta Business Agent will still be collected by Meta when you are chatting with the business, even when you mute Meta Business Agent."

The reply settings treat replies and collection separately. One setting is described as "Paused for new chats but learning", and the help centre says "While paused, it will continue to collect data from new chats to learn how to respond to customers." A separate "Pause AI replies" control "will stop Meta Business Agent from responding to customers in subsequent new chats", and the help page that describes it does not say whether collection continues. These pages describe the agent learning how to respond to the business's own customers. Meta's permission to use Content "to improve our artificial intelligence models and algorithms" comes from the terms, and the help pages do not say whether any of these settings affects it.

The "Ignore past chats" choice covers past chats only. Next to that choice, the setup page notes that "When Meta Business Agent doesn't have enough information to begin responding to customers, it will go into learning mode. In learning mode, it collects data from new chats to learn how to respond to customers." Deleting the agent ends the sharing ("When you delete Meta Business Agent, you will no longer be sharing your messages with Meta."), although the help pages do not say what happens to chats Meta has already used as Content. No business-side opt-out from Meta's use of Content to improve its models appears in the terms and help pages read for this note (the logged-in settings were not inspected).

Customers see a notice in the chat, but the help centre gives it two different wordings. The page for customers says "This message will appear in your chat with the business: AI from Meta receives chats to improve AI quality and generate messages for this business." The page for businesses says customers "will see the following message if you're using Meta Business Agent in a chat: AI from Meta receives and generates messages for this business." This note has not established which wording UK customers see. Meta's Privacy Policy relies on legitimate interests to "Develop and improve AI at Meta for Meta Products and for third parties", and tells users who want to object to "visit the Facebook settings and the Help Centre and Instagram settings". It names no WhatsApp route, and this note has not read WhatsApp's own privacy policy, so it does not say whether a customer can object to the use of their chat. What will the firm say to a customer who asks whether their chat trained Meta's AI?

3. Should past chats be shared at onboarding?

Setup offers two choices: "Use past chats: Teach Meta Business Agent how to respond to customers using your chats from the past six months." and "Ignore past chats: Do not use past chats to teach Meta Business Agent." The Addendum treats historic chats shared at onboarding as Business System Data. For a business located in the UK, that definition also covers "prior chat history on other Meta Company Products (including Instagram and Messenger)". The Addendum instructs Meta, as the business's processor, to use Business System Data "for the purposes of assisting, developing and maintaining Business Agents". The customers in those chats wrote to the business for their own reasons (usually an order or a booking), and the firm has to decide whether sharing them serves its own purpose or Meta's product.

The incorporated processor terms say "Company agrees that Meta may de-identify and anonymize Applicable Personal Data received from Company under the Applicable Terms and Process such data as permitted by Applicable Law." They also require the business not to share with Meta personal data that it "knows or reasonably should know" includes "health related data, financial data, other categories of sensitive data". That bar covers new chats Meta processes as the business's processor as well as past ones. Six months of customer chats may include such details, and setup offers only the two choices above, so a firm that cannot rule this out would choose "Ignore past chats".

Meta's Commercial Terms add a wider rule: a business may not use Meta Products to "collect from people" information that "includes health, financial, biometrics or other categories of similarly sensitive information", except where the terms for the product specifically allow it or financial information is sent to complete a financial transaction. A firm whose customers routinely send health or financial details should consider whether it can give these commitments at all.

4. What must customers be told?

In the clause headed "Warning Regarding Outputs", the terms include the words "You also recognize and agree that you - not Meta - are responsible to users". The incorporated processor terms make the business warrant that it will "Provide notice to individuals and obtain all consents, rights, and authorizations, or other lawful basis, regarding Company's disclosure of Applicable Personal Data to Meta and Meta's Processing of Applicable Personal Data". That commitment covers the personal data Meta processes as the business's processor. For Meta's own use of chats as Content, the help centre says "We will let customers know the first time they start chatting with a business that has AI connected" (the two wordings of that notice are in question 2).

WhatsApp's help centre, however, points customers two ways. It sends them to Meta ("Since these AI chats are a Meta service, you'll need to approach Meta to request data access or deletion.") and to the business ("Users who want to access or delete information that businesses have collected about them should contact the business for more information."). A firm should check whether its privacy notice covers any of this, and whether a customer could tell which of the two to ask.

5. Who carries the loss?

Meta's liability to the business under these terms is capped: "Our aggregate liability arising out of or relating to any access or use of Business Agents, will not exceed the greater of one hundred dollars ($100) or the amount you have paid us in the past twelve months." The business, in turn, indemnifies Meta against "any claims, losses, and expenses (including attorneys' fees) arising from or relating to your: (i) use of the Business Agents, including any subsequent use of any Content, or (ii) breach of these Terms." The terms' limitation clauses apply only to Meta's liability, and they set no limit on this indemnity. The firm needs to know who pays if an Information Commission inquiry or a customer claim starts with something the agent said (and whether its insurance responds).

6. Who handles a data protection complaint that arrives through the agent?

Section 164A of the Data Protection Act 2018, in force from 19 June 2026, lets a data subject complain to the controller if they consider there is an infringement of the UK GDPR in connection with their personal data. The controller has to facilitate such complaints and acknowledge each one within 30 days of receiving it. It must also, without undue delay, take appropriate steps to respond to the complaint and inform the complainant of the outcome. If a customer makes that complaint to the agent, has the business received it? After the agent hands the chat over, the terms say it "may continue to observe the content being shared in the chat" and that "This content shall be deemed Content under these Terms." Where is the complaint logged, and who answers it?

Sources

  • Meta, Business Agents Terms and Addendum - last updated 16 July 2026. Primary for Meta's processor role, the processing instructions, the definitions of Business System Data, Interface Data and Designated Interface Data, the use of Content to improve Meta's AI, the handover clause, the indemnity and the liability cap - checked 15 October 2026
  • Meta Global Processor Terms and their European Region Terms, last updated 20 March 2026, incorporated by the Addendum as its Data Processor Terms - checked 15 October 2026
  • Meta Privacy Policy, effective from 23 July 2026, as served in the UK - checked 15 October 2026
  • Meta, Commercial Terms - read alongside the Addendum; primary for the sensitive-information rule. Meta has published an updated version, effective 30 October 2026, which lists the Business Agents terms among the supplemental terms it incorporates - checked 15 October 2026
  • WhatsApp Help Centre, Meta Business Agent pages: setting up (Android and iPhone versions), using, pausing or deleting and customer questions - checked 15 October 2026
  • Data Protection Act 2018, section 164A, in force from 19 June 2026 (Data (Use and Access) Act 2025 (Commencement No. 6 and Transitional and Saving Provisions) Regulations 2026, S.I. 2026/82, reg 3(a), with reg 7) - checked 15 October 2026

Based on Meta's published terms as checked on 15 October 2026, which Meta can change. Janus Compliance is not a law firm and this page is general information, not legal advice.

ShareXBluesky

Talk to Michael

About Meta Business Agent, or your AI vendor governance more broadly.

CompanyScope's public profiles cover the general picture. Michael runs Janus DPO-as-a-Service for businesses that need ongoing AI vendor governance, and writes one-off CIPP/E-reviewed Vendor Risk Notes for specific procurement decisions. Tell him what you're actually trying to clear.

A sentence or two is plenty.

Your context goes only to Michael. We don't share with the vendor or anyone else. Privacy notice.

Each new entry, by email

Every new Register entry delivered with the legal analysis: the incident, the duty engaged, who is liable across the chain, and what governance would have prevented it. Written by Michael K. Onyekwere, CIPP/E. Free.

Subscribe

Delivered through Compliance Engineering on Substack, which handles your subscription and consent. Unsubscribe any time. Privacy notice.

For ongoing AI compliance support, work with Janus DPO-as-a-Service. For other vendors, browse the full index, or see real agent failures analysed legally in the AI Agent Incident Register.