Meta dropped the 30-day notice from its WhatsApp Business terms

Stani Mihov

Founder & CEO

·

TL;DR

What changed:

  • Meta can end the agreement at any time on notice, instead of giving 30 days' written notice plus up to three months to wind down.

  • Meta no longer promises to tell you before it changes the terms, and using the platform after an update counts as accepting it.

  • The promise to acknowledge support requests within 4 hours is gone.

  • Meta can suspend invoiced customers who get close to their credit limit, not only those who pay late.

  • If you run WhatsApp for other businesses, a breach by one of them can now cost you your own access.

What to do: If WhatsApp carries your customer support or sales, keep a fallback channel ready and your own copy of conversation records, since the agreement says Meta keeps no backups for you.

The change

On September 23, 2026, Meta replaced its Meta Terms for WhatsApp Business with a rewritten agreement, the Meta Terms for WhatsApp Business Platform. This is the contract a business accepts to send and receive WhatsApp messages or calls through Meta's business APIs, either directly or through a third-party provider that connects WhatsApp to its tools.

Meta posted a preview of the new version before it took effect, and it rewrote the related WhatsApp Business Solution Terms and Terms for Service Providers on the same date. Much of the update is restructuring. Inside it, several commitments Meta made to businesses are no longer in the text. Venpo compared the new agreement with the October 15, 2025 version clause by clause, and the full redline is on the public change page.

What changed

Six changes matter most for a business that relies on WhatsApp:

  • Ending the agreement. Meta used to promise 30 days' written notice and up to three months to wind down before ending the agreement for any reason. It can now end it "at any time for any reason upon notice to you."

  • Changes to the terms. The promise "we will notify you before we make a Change" was deleted. Using the platform after an update now counts as accepting it.

  • Support. The line saying Meta aims to acknowledge support requests within 4 hours was removed, and the new agreement does not replace it with another response target.

  • Suspension for billing. Meta could already suspend access for late payment. It can now also suspend invoiced customers who "approach, reach, or exceed" their credit limit.

  • Your clients' mistakes. Meta can suspend or end access if it determines that you "or your Clients" broke the terms, which matters for agencies and software providers that run WhatsApp for other businesses.

  • Credit checks. Meta could pull your business credit report "during the term of this Agreement." That time limit is gone.

Thirty days became "upon notice"

Under the old text, if Meta decided to stop working with a business, that business had a month of warning and then up to three more months of access to move its customer conversations elsewhere, paying for usage during that time. The new clause still requires notice but no longer says how much.

On paper, the change runs both ways: a business can now also leave with written notice instead of waiting 30 days. The companion WhatsApp Terms for WhatsApp Business Platform also keep a 30-day notice for businesses established in the EU or the UK that fall under EU platform rules, but that carve-out is limited to those two regions.

Updates now take effect through continued use

The old change clause read: "Unless otherwise required by law, we will notify you before we make a Change." The new clause drops that sentence and keeps only the consequence: "By continuing to access or use the WhatsApp Business Platform after any update, you agree to be bound by it." It also covers the policies and documentation the agreement links to, such as the WhatsApp Business Messaging Policy.

Meta did announce this particular update ahead of time, with a preview on its legal pages, but the new text no longer commits it to doing the same next time. Rate card prices keep their own rule: increases still start on the first day of the following month, and decreases can now apply right away. A document that can change under you without a fresh signature is the same shift we covered when Hotjar's DPA stopped needing your signature to change.

Billing can now cut access before a bill is late

Meta splits businesses into two billing groups. Non-invoiced customers pay by card or another payment method as they go. Invoiced customers get a credit line with a spending limit set by Meta and a monthly invoice due within 30 days.

For invoiced customers, the new suspension clause adds a trigger that does not depend on a missed payment. If spending approaches, reaches, or exceeds the credit limit, Meta may suspend all or part of the business's access "until you make payment in full." Meta says it "will endeavor to provide you with notice prior to suspension," which is a best effort rather than a guarantee. The same trigger already sat in Meta's separate Cloud API terms, and the new agreement now applies it to the platform as a whole. A similar billing trigger is behind Google Cloud's new suspension rules.

Rules that moved into the main agreement

Some of the stricter language is not new to WhatsApp businesses, but it now sits in the one agreement every platform customer accepts:

  • The platform "is not HIPAA compliant," and Meta makes no promise that it suits businesses in healthcare, financial, or legal services.

  • Meta "does not provide an archiving service, storage service, or any backup functionality," so keeping copies of conversations is the business's job.

  • Platform data cannot be used to train AI models, except to fine-tune a model used only by that business, and AI companies cannot use the platform when AI is the main product they offer, outside the countries Meta lists.

The HIPAA and backup lines already appeared in the Cloud API terms, and the AI rules were already in the WhatsApp Business Solution Terms. The support target is different: the 4-hour acknowledgment line was removed, and nothing in the new agreement takes its place.

Why this matters

For a lot of SaaS companies, WhatsApp is a customer channel for support conversations, onboarding messages, payment reminders, and sales follow-ups. The old agreement gave those teams a few fixed points to plan around: a month's warning before Meta could walk away, time to move customers to another channel, a heads-up before the rules changed, and a response target when something broke.

Those are the details a continuity plan or a vendor review leans on, and they are no longer written into the contract. None of it shows up in the product itself, which is why a change like this is easy to miss in a vendor's document. It follows the pattern we saw when Perplexity moved three protections out of its privacy policy: the product looked the same, but the written commitment did not.

Potential impact

For a SaaS company using the WhatsApp Business Platform, directly or through a provider, the update raises five practical questions:

  • If WhatsApp access stopped with little warning, which customer conversations would break, and is a fallback channel ready?

  • Where are conversation records kept, given that Meta keeps no backups for you?

  • Who on the team checks Meta's legal pages, now that using the platform after an update counts as accepting it?

  • For invoiced accounts, how close does spending usually run to the credit limit Meta has set?

  • If you run WhatsApp for clients, how would one client's breach affect the rest of your account?

Teams in healthcare and other regulated fields also have a clear line to check against, since the agreement states the platform is not HIPAA compliant. Keeping answers like these current across every vendor is where continuous vendor contract monitoring earns its place.

How Venpo detected it

Venpo monitors the Meta Terms for WhatsApp Business as part of its continuous vendor risk monitoring. On September 24, the day after the new version took effect, Venpo flagged the rewrite, marked every inserted and deleted clause, and rated 21 changes as negative for the business, separate from the renumbering and boilerplate around them. The same day, it caught related updates to the WhatsApp Business Solution Terms, the Terms for Service Providers, and the Business Messaging Policy. The full redline is on the WhatsApp change page, and every monitored document is listed on the WhatsApp vendor profile.

Business outcome

Teams that rely on WhatsApp for customer conversations got a plain-English list of what moved the day after the new terms took effect, with each point tied to the inserted or deleted text. That leaves time to line up a fallback channel, set up backups, and check credit limits while nothing is urgent. The alternative is learning about the new termination wording from a notice that the relationship is ending.

Key takeaway

Meta's rewrite took four protections out of the contract behind WhatsApp Business: the 30-day notice, the three-month wind-down, the promise of notice before changes, and the 4-hour support target. Those protections existed only on the page, so the page is where their removal shows up, which is exactly what monitoring vendor terms of service is for.

The change

On September 23, 2026, Meta replaced its Meta Terms for WhatsApp Business with a rewritten agreement, the Meta Terms for WhatsApp Business Platform. This is the contract a business accepts to send and receive WhatsApp messages or calls through Meta's business APIs, either directly or through a third-party provider that connects WhatsApp to its tools.

Meta posted a preview of the new version before it took effect, and it rewrote the related WhatsApp Business Solution Terms and Terms for Service Providers on the same date. Much of the update is restructuring. Inside it, several commitments Meta made to businesses are no longer in the text. Venpo compared the new agreement with the October 15, 2025 version clause by clause, and the full redline is on the public change page.

What changed

Six changes matter most for a business that relies on WhatsApp:

  • Ending the agreement. Meta used to promise 30 days' written notice and up to three months to wind down before ending the agreement for any reason. It can now end it "at any time for any reason upon notice to you."

  • Changes to the terms. The promise "we will notify you before we make a Change" was deleted. Using the platform after an update now counts as accepting it.

  • Support. The line saying Meta aims to acknowledge support requests within 4 hours was removed, and the new agreement does not replace it with another response target.

  • Suspension for billing. Meta could already suspend access for late payment. It can now also suspend invoiced customers who "approach, reach, or exceed" their credit limit.

  • Your clients' mistakes. Meta can suspend or end access if it determines that you "or your Clients" broke the terms, which matters for agencies and software providers that run WhatsApp for other businesses.

  • Credit checks. Meta could pull your business credit report "during the term of this Agreement." That time limit is gone.

Thirty days became "upon notice"

Under the old text, if Meta decided to stop working with a business, that business had a month of warning and then up to three more months of access to move its customer conversations elsewhere, paying for usage during that time. The new clause still requires notice but no longer says how much.

On paper, the change runs both ways: a business can now also leave with written notice instead of waiting 30 days. The companion WhatsApp Terms for WhatsApp Business Platform also keep a 30-day notice for businesses established in the EU or the UK that fall under EU platform rules, but that carve-out is limited to those two regions.

Updates now take effect through continued use

The old change clause read: "Unless otherwise required by law, we will notify you before we make a Change." The new clause drops that sentence and keeps only the consequence: "By continuing to access or use the WhatsApp Business Platform after any update, you agree to be bound by it." It also covers the policies and documentation the agreement links to, such as the WhatsApp Business Messaging Policy.

Meta did announce this particular update ahead of time, with a preview on its legal pages, but the new text no longer commits it to doing the same next time. Rate card prices keep their own rule: increases still start on the first day of the following month, and decreases can now apply right away. A document that can change under you without a fresh signature is the same shift we covered when Hotjar's DPA stopped needing your signature to change.

Billing can now cut access before a bill is late

Meta splits businesses into two billing groups. Non-invoiced customers pay by card or another payment method as they go. Invoiced customers get a credit line with a spending limit set by Meta and a monthly invoice due within 30 days.

For invoiced customers, the new suspension clause adds a trigger that does not depend on a missed payment. If spending approaches, reaches, or exceeds the credit limit, Meta may suspend all or part of the business's access "until you make payment in full." Meta says it "will endeavor to provide you with notice prior to suspension," which is a best effort rather than a guarantee. The same trigger already sat in Meta's separate Cloud API terms, and the new agreement now applies it to the platform as a whole. A similar billing trigger is behind Google Cloud's new suspension rules.

Rules that moved into the main agreement

Some of the stricter language is not new to WhatsApp businesses, but it now sits in the one agreement every platform customer accepts:

  • The platform "is not HIPAA compliant," and Meta makes no promise that it suits businesses in healthcare, financial, or legal services.

  • Meta "does not provide an archiving service, storage service, or any backup functionality," so keeping copies of conversations is the business's job.

  • Platform data cannot be used to train AI models, except to fine-tune a model used only by that business, and AI companies cannot use the platform when AI is the main product they offer, outside the countries Meta lists.

The HIPAA and backup lines already appeared in the Cloud API terms, and the AI rules were already in the WhatsApp Business Solution Terms. The support target is different: the 4-hour acknowledgment line was removed, and nothing in the new agreement takes its place.

Why this matters

For a lot of SaaS companies, WhatsApp is a customer channel for support conversations, onboarding messages, payment reminders, and sales follow-ups. The old agreement gave those teams a few fixed points to plan around: a month's warning before Meta could walk away, time to move customers to another channel, a heads-up before the rules changed, and a response target when something broke.

Those are the details a continuity plan or a vendor review leans on, and they are no longer written into the contract. None of it shows up in the product itself, which is why a change like this is easy to miss in a vendor's document. It follows the pattern we saw when Perplexity moved three protections out of its privacy policy: the product looked the same, but the written commitment did not.

Potential impact

For a SaaS company using the WhatsApp Business Platform, directly or through a provider, the update raises five practical questions:

  • If WhatsApp access stopped with little warning, which customer conversations would break, and is a fallback channel ready?

  • Where are conversation records kept, given that Meta keeps no backups for you?

  • Who on the team checks Meta's legal pages, now that using the platform after an update counts as accepting it?

  • For invoiced accounts, how close does spending usually run to the credit limit Meta has set?

  • If you run WhatsApp for clients, how would one client's breach affect the rest of your account?

Teams in healthcare and other regulated fields also have a clear line to check against, since the agreement states the platform is not HIPAA compliant. Keeping answers like these current across every vendor is where continuous vendor contract monitoring earns its place.

How Venpo detected it

Venpo monitors the Meta Terms for WhatsApp Business as part of its continuous vendor risk monitoring. On September 24, the day after the new version took effect, Venpo flagged the rewrite, marked every inserted and deleted clause, and rated 21 changes as negative for the business, separate from the renumbering and boilerplate around them. The same day, it caught related updates to the WhatsApp Business Solution Terms, the Terms for Service Providers, and the Business Messaging Policy. The full redline is on the WhatsApp change page, and every monitored document is listed on the WhatsApp vendor profile.

Business outcome

Teams that rely on WhatsApp for customer conversations got a plain-English list of what moved the day after the new terms took effect, with each point tied to the inserted or deleted text. That leaves time to line up a fallback channel, set up backups, and check credit limits while nothing is urgent. The alternative is learning about the new termination wording from a notice that the relationship is ending.

Key takeaway

Meta's rewrite took four protections out of the contract behind WhatsApp Business: the 30-day notice, the three-month wind-down, the promise of notice before changes, and the 4-hour support target. Those protections existed only on the page, so the page is where their removal shows up, which is exactly what monitoring vendor terms of service is for.

Real-time change notifications

Stay ahead of every legal change

Get updates, product news and expert tips on navigating legal changes

Stripe updated Terms of Service

Dispute resolution clause now requires mandatory arbitration in all regions

High Impact2 hours ago
AWS modified Privacy Policy

Data retention period extended from 2 years to 5 years for all services

Medium Impact5 hours ago
Shopify revised Acceptable Use Policy

New restrictions on AI-generated content in product descriptions

Review1 day ago
Slack changed Data Processing Agreement

Third-party data sharing expanded to include analytics partners

High Impact1 day ago

Real-time change notifications

Stay ahead of every legal change

Get updates, product news and expert tips on navigating legal changes

Stripe updated Terms of Service

Dispute resolution clause now requires mandatory arbitration in all regions

High Impact2 hours ago
AWS modified Privacy Policy

Data retention period extended from 2 years to 5 years for all services

Medium Impact5 hours ago
Shopify revised Acceptable Use Policy

New restrictions on AI-generated content in product descriptions

Review1 day ago
Slack changed Data Processing Agreement

Third-party data sharing expanded to include analytics partners

High Impact1 day ago