> For the complete documentation index, see [llms.txt](https://docs.askyazi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.askyazi.com/security-and-privacy/data-residency-and-hosting.md).

# Data residency and hosting

Where Yazi stores and processes study data, how WhatsApp fits in, what in-country hosting involves, and how retention and deletion work.

This page explains where your study data is stored, where each kind of processing happens, what passes through Meta because the research runs on WhatsApp, and how long data is kept. Use it to answer the "where is our data?" section of a security or privacy review.

{% hint style="info" %}
**In short:**

* Every production organisation runs on AWS in London (eu-west-2). Study data, including the photos and voice notes participants send, is stored there.
* WhatsApp messages travel through Meta's WhatsApp Business Platform. This is true of any WhatsApp research tool.
* In-country hosting (for example in South Africa or Saudi Arabia) is not offered as standard.

**Last checked:** 23 October 2026.
{% endhint %}

## Where your data is stored

Yazi is hosted on Amazon Web Services (AWS). The primary region is **London (eu-west-2)** for every organisation on production, and this is the region stated in Yazi's contracts. All stored data, including media files and backups, is held in London. No data is held in any other AWS region.

Stored data includes your studies and questions, participant records, answers, transcripts, media files (photos, voice notes, videos and documents participants send) and reports.

## Where each kind of processing happens

| What                                                           | Service                                                                                                                                                              | Where                                                                                     |
| -------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
| Study data, participant records, answers and media             | AWS databases and storage                                                                                                                                            | London (eu-west-2)                                                                        |
| Voice-note transcription                                       | AWS speech-to-text, in Yazi's AWS account                                                                                                                            | London (eu-west-2), since 5 August 2026                                                   |
| Photo and image analysis                                       | Anthropic's Claude through Amazon Bedrock                                                                                                                            | UK/EU, since 3 September 2026                                                             |
| Receipt and menu photo reading                                 | Anthropic's Claude in Yazi's AWS account                                                                                                                             | UK/EU, since 16 October 2026                                                              |
| AI interviewer, Ask Yazi, AI analysis, reports and translation | Large language models through Amazon Bedrock in Yazi's AWS account (the AI interviewer uses an OpenAI model; other features use models including Anthropic's Claude) | See [AI and your data](https://docs.askyazi.com/security-and-privacy/ai-and-your-data.md) |
| WhatsApp message delivery                                      | Meta's WhatsApp Business Platform                                                                                                                                    | Meta's infrastructure (EU and US)                                                         |

When transcription fails, nothing else is tried: the voice note stays untranscribed rather than being sent to another provider. There is no setting that sends audio outside the region.

See [AI and your data](https://docs.askyazi.com/security-and-privacy/ai-and-your-data.md) for what each AI feature does, which models run it and how to switch AI off.

### If you hold an older answer from Yazi

Several processing locations changed in 2026. If your files contain an earlier due-diligence answer, check it against this table:

* Before 5 August 2026, voice notes were transcribed by a US-hosted Google service. They are now transcribed within AWS in London.
* Before 3 September 2026, participant photos were analysed by a provider in the United States. They are now analysed in the UK/EU.
* Before 16 October 2026, receipt and menu photos were read by Google Gemini. They are now read by Claude in Yazi's AWS account.

Any answer that names a US-hosted transcription or image service is out of date.

## WhatsApp and Meta

Yazi uses the **WhatsApp Business Platform**, the business API run by Meta. It is not the consumer WhatsApp app.

* Messages between a participant and Yazi pass through Meta's infrastructure, which spans the EU and the US. This is a cross-border transfer, and it applies to any research run on WhatsApp.
* Meta acts as a processor for message delivery, under its own WhatsApp Business terms. For how long Meta keeps message content, see Meta's WhatsApp Business Platform documentation.
* WhatsApp takes part in the EU-U.S. Data Privacy Framework for WhatsApp Business Services, so transfers to Meta can rely on the European Commission's adequacy decision.
* Once a message reaches Yazi, it is stored in Yazi's AWS environment, not on Meta's servers.

## Cross-border transfers

* **South Africa (POPIA).** Yazi's systems run in London. Transfers rely on POPIA section 72: UK data protection law gives protection at least equivalent to POPIA. Yazi's POPIA DPA describes the UK hosting and WhatsApp's infrastructure and names AWS and Meta as sub-processors.
* **EU and UK (GDPR and UK GDPR).** Data is hosted in the UK, which the EU recognises as adequate. The WhatsApp delivery leg relies on the Data Privacy Framework. Standard Contractual Clauses can be added to the DPA where needed.
* A **Transfer Impact Assessment** covering EEA, UK, US and South African data flows is available on request.

## In-country hosting

The default is AWS in London. If your regulator or internal policy requires data to stay in your own country (common for banks and some large corporates), talk to Yazi before contracting:

* In-country hosting is not a setting. Any regional set-up has to be scoped and costed as a separate piece of work before it is agreed.
* Even with in-country hosting, WhatsApp messages still pass through Meta's infrastructure.

For many reviews the more useful point is separation: each organisation's data is ring-fenced from every other organisation's.

## Data that leaves Yazi because you send it

Some features send data to systems you choose. Once it arrives there, your own agreements with that provider apply, not Yazi's hosting.

| Feature                                        | Where the data goes                                         |
| ---------------------------------------------- | ----------------------------------------------------------- |
| Exports (CSV, Excel, SPSS, transcripts, media) | Your device or storage                                      |
| Google Sheets or Microsoft Excel sync          | Your Google or Microsoft account                            |
| AI assistant connectors (Claude, ChatGPT)      | Your AI provider, under your account's terms                |
| Response Push webhooks and event triggers      | The endpoint your team configures                           |
| Shared results links                           | Anyone you give the link to                                 |
| Panel recruitment (Prolific, PureSpectrum)     | The panel provider, for recruitment and completion tracking |
| Incentive payouts                              | The reward provider that delivers the reward                |

## Sub-processors

The two core sub-processors are **AWS** (hosting, AI through Bedrock, transcription) and **Meta** (WhatsApp message delivery). Other providers process data only when you use a feature that needs them, such as panel recruitment or incentives. The full list is in the sub-processor register at [askyazi.com/sub-processors](https://www.askyazi.com/sub-processors). The DPA sets the notice Yazi gives before adding a sub-processor, with a right to object.

## Retention and deletion

* **How long data is kept** is set in your contract or DPA. Agree it in writing before fieldwork.
* **The deletion date is counted from the date the project was created** in Yazi, not from a project end date. There is no end-date option today, so allow a margin (for example, ask for seven months if you need six months after fieldwork).
* **What deletion covers:** the platform and the separate media storage, primary systems and backups. Anonymised responses are deleted too if you ask.
* **Certificate of deletion:** available once deletion is complete.
* **Deletion requests** must be made in writing.
* **Deletion is done by a person, not automatically.** A monthly retention report lists data past its retention period, and the team reviews and clears it.
* **When a contract ends** you can export your data before it is deleted. The DPA sets how long you have. See [Compliance](https://docs.askyazi.com/security-and-privacy/compliance.md).

For deleting one participant's personal details, see [Participant privacy](https://docs.askyazi.com/security-and-privacy/participant-privacy.md).

## Limits and things to know

* **"Stays in the UK" excludes WhatsApp delivery.** Be precise in your own documents: storage is in London, and message transport is through Meta.
* **London is in the UK, not the EU.** Where a document says "EU residency", check whether it means UK or EU regions.
* **No automatic deletion schedule.** Deletion happens on the agreed date through a reviewed process, so put the date in writing.
* **Data you export or connect elsewhere** is outside Yazi's residency position.

## Related

* [Security overview](https://docs.askyazi.com/security-and-privacy/security-overview.md)
* [AI and your data](https://docs.askyazi.com/security-and-privacy/ai-and-your-data.md)
* [Participant privacy](https://docs.askyazi.com/security-and-privacy/participant-privacy.md)
* [Compliance](https://docs.askyazi.com/security-and-privacy/compliance.md)
* [Exports](https://docs.askyazi.com/results-and-reporting/exports.md)
* [Connect Claude or ChatGPT](https://docs.askyazi.com/integrations-and-api/connect-claude-or-chatgpt.md)
