Local Storage | Developer Documentation

Check a country-of-storage requirement for your WhatsApp connection

You cannot choose Meta's country of storage through ChatArchitect. Meta's Local Storage feature is a separate setting in its messaging infrastructure; the developer instructions for that setting are not a customer setup procedure offered by ChatArchitect.

ChatArchitect does not store customer message texts or attachments. This describes ChatArchitect's handling of that content. To assess a storage-location requirement, also check Meta's service and any CRM, help desk or other tool that keeps a copy. See the message content and storage guide for those separate parts of the connection.

Understand the scope of Meta Local Storage

Meta describes Local Storage as a phone-number setting for the location of message content at rest. Its documentation also describes an earlier processing period during which content can be handled in Meta data centers internationally. A selected storage region therefore does not by itself describe every place where processing occurs.

Read the official Meta Local Storage reference when interpreting a requirement. The presence of that feature in Meta documentation does not make country selection available through ChatArchitect.

Describe the requirement before evaluating the service

1. Name the data. Specify whether the requirement concerns message texts, attachments, contact details, delivery records or another category.
2. Name the operation. Separate storage at rest, processing, backups and access by staff. A requirement limited to stored content differs from one covering all processing.
3. Name the location. State the exact country or region required by your company, rather than describing it only as “local”.
4. Identify the systems. Include Meta, your connected CRM or help desk, and systems where your team exports or downloads copies.
5. Confirm the fit. Ask the provider of each relevant system to explain its handling of the named data and operation. Share the requirement with ChatArchitect support before relying on the connection for that purpose.

For example, “store exported conversation files in our company system in country X” and “process all message content only in country X” describe different requirements. This is an illustrative distinction, not a claim that ChatArchitect offers either configuration.

Keep the number connection on the supported route

Use the ChatArchitect number connection guide for the standard customer setup. Selecting a Meta storage country is not a step in that route. If your requirement needs a different service configuration, establish its availability with support before changing the connected number.

Meta registration parameters and de-registration instructions from the former imported article are not a supported self-service way to add country selection to ChatArchitect. No migration duration or interruption-free change is promised here.