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

# Data and privacy

> Where teacher and school data is stored, what leaves the EEA, and what consent controls.

This page summarises what a school needs in order to answer its own data
protection questions. The binding statements are the
[privacy policy](https://www.mesolab.ai/privacy) and
[cookie policy](https://www.mesolab.ai/cookies).

## Where things are processed

The distinction that matters is between **where your work is stored** and
**where AI generation happens**. They are not the same place.

| | Location | Leaves the EEA? |
| - | - | - |
| Your database records — units, lessons, assessments, resources | Ireland (`europe-west1`) | No |
| Uploaded documents | Ireland (`europe-west1`) | No |
| Curriculum data and search | EU (`europe-west1`, `eu-west-1`) | No |
| Product analytics | EU | No |
| **AI generation** — units, lessons, rubrics, assessments, resources, slides | United States | **Yes** |
| **MESO Assist** chat | United States | **Yes** |
| **Image generation** | United States | **Yes** |
| **Voice transcription** | United States | **Yes** |
| Error monitoring | United States | **Yes**, only with consent |

> [!NOTE]
>
> In short: **your data rests in Ireland; generation happens in the United
> States.** When a teacher generates a unit plan, the prompt and the curriculum
> context needed to build it are sent to a US region, and the result is stored back
> in Ireland.

## What this means for free-text entry

Anything a teacher types into a planning field or into MESO Assist may be sent
for generation. Teachers should be told not to enter pupil names, or anything
about an individual pupil's health, background or circumstances, in free-text
fields.

This is worth saying explicitly in staff briefings — it is the single most
useful piece of guidance a school can give.

## Two commitments worth quoting to staff

Both are stated to every teacher during setup, so they are safe to repeat in a
briefing:

* **Nothing a teacher writes is used to train third-party models.**
* **Everything can be exported or deleted** by the teacher, from Settings.

US processing is carried out under standard contractual clauses.

## Consent

Teachers control two things themselves, under **Settings → Workspace →
Privacy**:

* **Analytics** — product analytics, processed in the EU
* **Error monitoring** — diagnostic reports, processed in the United States

Both can be withdrawn at any time, and withdrawal takes effect immediately.
Neither is required to use MESO.

## Questions a school should ask us

We would rather answer these directly than have you infer them:

* your data processing agreement and its terms
* retention periods, and what happens to a teacher's work when they leave
* anything a data protection officer needs for a school-side assessment

Write to [contact@mesolab.ai](mailto:contact@mesolab.ai). If a fact is not
stated on this page or in the published policies, ask rather than assume it.


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