# Data location and retention

> Where Sypnia Cloud stores your data, which other companies touch it, how long each kind of data is kept on each plan, and when it is deleted.

Applies to: Sypnia Cloud (paid service). Status: at launch.  
Source: https://docs.sypnia.com/cloud/data-location-and-retention/

**\[Cloud]** This page is for anyone who must answer «where is our data, and for how long?». It describes Sypnia Cloud. On a self-hosted engine the answer is yours: the data is in the bucket and the database you chose, for as long as you set.

## Where your data is stored

Sypnia Cloud runs on Amazon Web Services, in the region **us-east-1** (Northern Virginia, United States). All of it is there:

| Data                                                                              | Where               |
| --------------------------------------------------------------------------------- | ------------------- |
| Raw events, replay recordings, page snapshots and source maps                     | Amazon S3           |
| Results: problems, the index of sessions, performance numbers, settings, accounts | A Postgres database |

There is no choice of region at launch. If your data must stay in another country, or must never leave your own infrastructure, self-host the engine: it is the same software. See [Self-hosting](https://docs.sypnia.com/self-hosting).

## Who else touches your data

Sypnia Cloud uses other companies to do specific jobs. Each receives only what its job needs.

| Company                                      | Job                                                      | What it receives                                                                                                                                                                                                                                                                                                    |
| -------------------------------------------- | -------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Amazon Web Services                          | Hosting, storage, and sending e-mail (Amazon SES)        | Everything Sypnia Cloud stores. For e-mail: the address, and the text of the alert or summary.                                                                                                                                                                                                                      |
| OpenRouter, and the model provider behind it | Running the model for the agent's analysis               | What the agent reads about a problem, with masked fields left out. Never replay recordings or typed input. Requests are sent with the settings that forbid providers from keeping the data or training on it. The full list is in [Models and what is sent](https://docs.sypnia.com/agent/models-and-what-is-sent). |
| GitHub                                       | Pull requests, only if you install the Sypnia GitHub App | The branch and the pull request Sypnia writes. See [The GitHub App](https://docs.sypnia.com/cloud/github-app).                                                                                                                                                                                                      |
| Stripe                                       | Payments, only on paid plans                             | Your card and billing details. Sypnia does not receive the card number.                                                                                                                                                                                                                                             |

Sypnia does not sell your data, does not use it for advertising, and does not use it to train models. It is used to show you your own app.

## How long data is kept

A plan keeps data for a number of days. The number of each plan is in the table of [Plans and limits](https://docs.sypnia.com/cloud/plans-and-limits). This table says exactly what that number applies to.

| Data                                                                                                          | Kept                                                                                                                                                                                                                                                                              |
| ------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Events, sessions and their timelines, traces                                                                  | The plan's days                                                                                                                                                                                                                                                                   |
| Replay recordings                                                                                             | The plan's days, and never more than 30                                                                                                                                                                                                                                           |
| Page snapshots                                                                                                | The plan's days                                                                                                                                                                                                                                                                   |
| Activity of people and accounts                                                                               | The plan's days                                                                                                                                                                                                                                                                   |
| Hourly and daily numbers: performance, click counts, usage                                                    | 400 days, on every plan. They are totals, and hold nothing about people.                                                                                                                                                                                                          |
| Alerts                                                                                                        | The plan's days                                                                                                                                                                                                                                                                   |
| Uptime                                                                                                        | Single results for 7 days, and the numbers of each hour for 400 days, on every plan. They hold nothing about people.                                                                                                                                                              |
| Source maps                                                                                                   | 90 days after their release was last seen                                                                                                                                                                                                                                         |
| **Problems**: the sentence, the analysis, the status, the counts for each day, and one example of the failure | As long as the project exists, or until you delete the problem, in the app or through the [API](https://docs.sypnia.com/api/problems). This is what lets Sypnia say «came back» months later. The sessions, replays and traces linked from a problem expire with the plan's days. |
| Releases, project settings, keys, tokens, uptime checks                                                       | As long as the project exists                                                                                                                                                                                                                                                     |
| Usage counters for each month                                                                                 | As long as the organization exists                                                                                                                                                                                                                                                |
| Your account and your organization                                                                            | Until you delete them                                                                                                                                                                                                                                                             |
| Invoices and payment records                                                                                  | As long as accounting rules require us to keep them, even after you delete the organization                                                                                                                                                                                       |
| Request logs of our servers, which include IP addresses                                                       | 30 days                                                                                                                                                                                                                                                                           |
| Backups of the database                                                                                       | 7 days                                                                                                                                                                                                                                                                            |

### When deletion happens

- Age is counted from the moment the data was recorded. A session's age is counted from its last event.
- A cleanup runs once a day. Data is deleted within 24 hours of passing its age.
- Deleted data stays in database backups until the backup itself expires, at most 7 days later, and is not restored from there except to recover from a failure of ours.
- Asking for something older than the plan keeps gives a clear answer that it expired, not an empty result.

### When the plan changes

- **To a larger plan:** data is kept longer from that day on. What was already deleted does not come back.
- **To a smaller plan:** data older than the new number of days is deleted the day the change takes effect. The app says so before you confirm.

## Deleting sooner

You do not have to wait for data to expire. You can delete one person's data, a session, a problem, a project or the whole organization at any time. Deleting one person removes them from every list at once, and everything stored about them, the raw event files included, is gone within 24 hours. A problem can be deleted in the app or through the [API](https://docs.sypnia.com/api/problems). See [Deleting data](https://docs.sypnia.com/privacy/deleting-data).

## Taking your data out

Everything Sypnia keeps about your project can be read through the [API](https://docs.sypnia.com/api) while it is kept, with an API token. There is no one-click export at launch.

## Engine and Cloud

|                     | Sypnia engine (open source, self-hosted)                                     | Sypnia Cloud (paid service, with a free tier)                                             |
| ------------------- | ---------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
| Where data lives    | In the bucket and the Postgres database you chose, in the country you chose. | On Amazon Web Services, region us-east-1, United States.                                  |
| How long it is kept | As long as you set, for each kind of data.                                   | The plan's days. Problems are kept while the project exists.                              |
| Who else touches it | Your own providers, and the AI provider you configure, if any.               | Amazon Web Services, OpenRouter, and GitHub and Stripe when you use them.                 |
| Who can read it     | Whoever holds a token, and whoever administers your infrastructure.          | The members of your organization, and Sypnia staff under the rules in Security practices. |

How to set retention on your own engine is in the [configuration reference](https://docs.sypnia.com/self-hosting/configuration). What Sypnia collects in the first place is in [What is collected](https://docs.sypnia.com/privacy/what-is-collected), and how we protect it in [Security practices](https://docs.sypnia.com/privacy/security-practices).

## Example: the shop on Builder

On 12 March three people could not pay. The shop is on Builder, which keeps data for 30 days.

- Until 11 April, the three sessions can be opened and their replays watched.
- On 12 April the cleanup deletes those sessions, replays and traces.
- The problem itself stays: its sentence, that it hit 3 people on 12 March, that it was resolved that afternoon. If the same failure returns in June, Sypnia still knows it and marks it «came back».
