> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.flowella.io/llms.txt
> Use this file to discover all available pages before exploring further.

# WhatsApp data privacy, retention and residency

> How Meta's Cloud API encrypts, stores and keeps WhatsApp message data, local storage and No Storage options, and where Flowella holds its own copy.

Every WhatsApp message to or from your business passes through Meta's Cloud API. WhatsApp encrypts it between the customer's phone and the Cloud API, which decrypts it and passes it to your provider, and encrypts your replies the same way. Meta acts as your data processor, keeps message content for at most 30 days, and doesn't use it to choose the ads people see. Two optional settings change where and how long Meta stores it.

> [!NOTE]
>
> **In Flowella.** Partly supported. Numbers connected through Flowella use Meta's standard storage. Flowella doesn't turn on local storage or No Storage. Flowella keeps its own copy of conversations, contacts and Flow answers in Microsoft Azure's UK South region, until they're deleted. See [Data security](https://knowledge.flowella.io/security/data-security.md).

## What Meta keeps

| Data | How long Meta keeps it | Why |
| - | - | - |
| Message content | Up to 30 days | To retry delivery and provide the service |
| Customer identifiers (phone numbers and IDs on each message) | Deleted within 30 days of a message's last status update | To route messages |
| Business details (numbers, address, profile) | Under Meta's terms of service | To run your account |
| Media you upload | Until the media expires. See [Media formats and sizes](https://knowledge.flowella.io/whatsapp/messaging/media-specs.md). | To deliver it |

Messages are encrypted at rest. The Cloud API holds the encryption keys on your behalf, which is how it can decrypt messages for your provider.

## Meta's role under data protection law

* **Processor.** For the Cloud API, Meta acts as a data processor or service provider on behalf of your business. It only uses the messages to provide the service, on your instructions.
* **Your obligations stay with you.** You're responsible for meeting GDPR, UK GDPR and other laws for the data you collect, including opt-in. See [Opt-in and opt-out](https://knowledge.flowella.io/whatsapp/messaging/opt-in-and-opt-out.md).
* **Transfers.** Meta relies on GDPR-compliant transfer mechanisms when data moves from the EU or UK to the US, with data transfer addendums for European and UK customers.
* **Certifications.** Meta holds SOC 2 Type II and ISO 27001 reports for the Cloud API, published in its Business Messaging Compliance Center.
* **Ads.** The Cloud API doesn't automatically use your WhatsApp messages to inform the ads people see.

## Local storage and No Storage

| Option | What it does | Set when | Trade-offs |
| - | - | - | - |
| **Standard** | Messages processed and stored in Meta's data centres for up to 30 days | Default | None |
| **Local storage** | Message data stored at rest in a chosen country, such as the UK, Germany for the EU, or Switzerland | When the number is registered | Only the countries Meta offers |
| **No Storage** | Messages and media kept for at most 1 hour, never stored at rest | Before the number is registered | Failed deliveries can only be retried for 1 hour. Missed webhooks are lost after 1 hour instead of 7 days. Incoming media can only be downloaded for 1 hour. |

With No Storage, a message that can't be decrypted on the customer's phone after an hour fails with error `131036`, and an incoming message whose webhook can't be delivered within the hour is dropped with error `131035`.

> [!NOTE]
>
> **In Flowella.** Flowella registers numbers with Meta's standard storage. If your organisation needs local storage or No Storage, [contact Flowella support](https://flowella.io/support) before you connect the number, because the setting is chosen at registration.

## Where Flowella's copy lives

| | Meta (Cloud API) | Flowella |
| - | - | - |
| Region | Meta's data centres, or your local storage country | Microsoft Azure UK South, with files copied to UK West |
| Message retention | Up to 30 days | Until deleted |

HubSpot holds its own copy of anything Flowella sends to it, such as form submissions and timeline events. Deleting data in Flowella doesn't remove it from Meta or HubSpot.

## Related

> [card] [Data security](https://knowledge.flowella.io/security/data-security.md)
>
> How Flowella stores and protects your data.

> [card] [Phone numbers](https://knowledge.flowella.io/whatsapp/accounts/phone-numbers.md#local-storage)
>
> Local storage at registration.

> [card] [User identifiers](https://knowledge.flowella.io/whatsapp/messaging/user-identifiers.md)
>
> Phone numbers, BSUIDs and the contact book.

> [card] [Opt-in and opt-out](https://knowledge.flowella.io/whatsapp/messaging/opt-in-and-opt-out.md)
>
> Consent rules for WhatsApp.

Checked against Meta's documentation on 18 November 2026: [Data privacy and security](https://developers.facebook.com/documentation/business-messaging/whatsapp/data-privacy-and-security), [Local storage](https://developers.facebook.com/documentation/business-messaging/whatsapp/local-storage) and [No Storage](https://developers.facebook.com/documentation/business-messaging/whatsapp/no-storage).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.