Documentation Index
Fetch the complete documentation index at: https://meta-preview.mintlify.io/llms.txt
Use this file to discover all available pages before exploring further.
Message Flows
When a user sends a message to one of these businesses, the message travels end-to-end encrypted between the user and the Cloud API. As per the Signal protocol, the user and the Cloud API, on behalf of the business, negotiate encryption keys and establish a secure communication channel. WhatsApp cannot access any message content exchanged between users and businesses. Once a message is received by the Cloud API, it gets decrypted and forwarded to the Business. Messages are only temporarily stored by the Cloud API as required to provide the base API functionality. Messages from a business to a user flow on the reverse path. Businesses send messages to Cloud API. The Cloud API service stores the messages temporarily and takes on the task to send the message to the WhatsApp platform. Messages are stored for any necessary retransmissions. All messages are encrypted by the Cloud API before being sent to WhatsApp using the Signal protocol with keys negotiated with the user (recipient). WhatsApp acts as the transport service. It provides the message forwarding software; both client and server. It has no visibility into the message content being sent. It protects the users by detecting unusual messaging patterns (like a business trying to message all users) or collecting spam reports from users. Cloud API, operated by Meta, acts as the intermediary between WhatsApp and the Cloud API businesses. In other words, those businesses have given Cloud API the power to operate on their behalf. Because of this, WhatsApp forwards all messages destined for those businesses to Cloud API. WhatsApp also expects to receive from Cloud API all messages from those businesses. This is the same client behavior that the On-Premise client has. Meta, in providing the Cloud API service, acts as a Data Processor on behalf of the business. As such, the businesses have requested Meta to provide programmatic access to the WhatsApp Business Platform. Cloud API receives from WhatsApp the messages destined for the businesses that use Cloud API. Cloud API also sends to WhatsApp the messages sent by those businesses. Other parts of Meta (other than Cloud API) do not have access to the Cloud API business communications, including message content. Meta does not use any Cloud API data for advertising.Stored and Collected Data
All data collected, stored and accessed by Cloud API is controlled and monitored to ensure proper usage and maintain the high level of privacy expected from a WhatsApp client. Information about the businesses, including their business phone numbers, business address, etc. is maintained by Meta and the Business Manager product and is subject to the terms of service set by Meta. Cloud API relies on Business Manager and other Meta systems to identify any access to Cloud API on behalf of the business. Messages sent or received via Cloud API are only accessed by Cloud API, no other part of Meta can use this information. Messages have a maximum retention period of 30 days in order to provide the base features and functionality of the Cloud API service; for example, retransmissions. After 30 days, these features and functionality are no longer available. Cloud API does not rely on any information about the user (customer/consumer) the business is communicating with other than the phone number used to identify the account. This information is only used to deliver the messages via the WhatsApp client code. User phone numbers are used as sources or destinations of individual messages; as such they are deleted when messages are deleted. No other part of Meta other than Cloud API has access to this information. No message content is shared or sent to WhatsApp at any time and no WhatsApp employee has access to any message content.| Cloud API Data | System | Available to the rest of Meta? | Available to WhatsApp? |
|---|---|---|---|
| Message content | Cloud API | No | No |
| Consumer phone number | Cloud API | No | Yes |
| Non-identifiable statistics | Cloud API | Yes | Yes |
| Integrity signals - per business | WhatsApp Client | No | Yes |
| Business information | Business Manager | Yes | Yes |
| Billing - per business | Yes | Yes |
FAQs
Does Meta use the WhatsApp messages that are shared with it by a business for advertising?
Does Meta use the WhatsApp messages that are shared with it by a business for advertising?
Where are the servers for the Cloud API?
Where are the servers for the Cloud API?
Is the Cloud API end-to-end encrypted? What is the encryption model?
Is the Cloud API end-to-end encrypted? What is the encryption model?
What happens to message data at rest? How long is it stored?
What happens to message data at rest? How long is it stored?
Does Meta have access to encryption keys?
Does Meta have access to encryption keys?
What is the security model? Which certifications does the Cloud API have?
What is the security model? Which certifications does the Cloud API have?
How does the Cloud API comply with regional data protection laws (such as GDPR, LGPD, and PDPB)?
How does the Cloud API comply with regional data protection laws (such as GDPR, LGPD, and PDPB)?
What does Meta and WhatsApp do to make sure the transfer of data from the E.U. to the US is compliant?
What does Meta and WhatsApp do to make sure the transfer of data from the E.U. to the US is compliant?
- For customers in the European Region, see the WhatsApp Business Data Transfer Addendum.
- For customers in the UK, see the WhatsApp Business UK Data Transfer Addendum.