> For the complete documentation index, see [llms.txt](https://docs.360dialog.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.360dialog.com/docs/hub/local-storage.md).
# Local Storage
This page describes how local storage offers an additional layer of data management control for message data at rest.
Local storage provides an additional layer of data management control by allowing the selection of where message data is stored at rest. This is particularly relevant for businesses in regulated industries such as finance, government, or healthcare that must adhere to specific regional data residency policies.
### How Local Storage Works
Local storage is a setting enabled at the WhatsApp business phone number level. It is supported by both the Cloud API and MM Lite API. **It is not supported for COEX numbers.**
When local storage is enabled, the following constraints apply to message content:
* Data-in-use – While being processed, message content may be stored on Meta data centres internationally.
* Data-at-rest – After the processing period, message content is deleted from Meta data centres outside of the specified region and persisted only within the selected local storage region.
### Processing Durations
Local storage applies to both text and media content sent or received via the platform. The following items are included:
* Text messages – The text payload and message body.
* Media messages – Media payloads including audio, documents, images, and videos.
* Template messages – Static templates and the parameters passed at the time of sending (text or media).
A limited set of metadata attributes is also included to associate the encrypted payload with the original message. This metadata is protected via tokenization and encryption.
### Available data storage regions
The following regions are currently supported:
* [x] **APAC**: India, Singapore, Indonesia, South Korea, Japan, Australia
* [x] **LATAM**: Brazil
* [x] **MEA**: South Africa, Bahrain
* [x] **Europe**: EU (Germany), UK, Switzerland
* [x] **NORAM**: Canada
### Limitations
* Media files uploaded by a business phone number with local storage enabled are restricted to that specific phone number. These files cannot be shared with other phone numbers associated with the business portfolio.
* This feature is not available for COEX numbers
### Enabling Local Storage
{% stepper %}
{% step %}
[Log in](https://app.360dialog.com/) to the 360Dialog Hub.
{% endstep %}
{% step %}
In the **channel section**, choose the particular channel you want to update.
{% endstep %}
{% step %}
Go to the **API Settings** section and click on the pencil icon or three dots.
{% endstep %}
{% step %}
Select the preferred data storage region and then **save.**
{% endstep %}
{% endstepper %}
{% hint style="info" %}
**Default storage region**
The default storage region is the United States.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.360dialog.com/docs/hub/local-storage.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
