Docs

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 Cloud At launch

View as Markdown
On this page
  1. Where your data is stored
  2. Who else touches your data
  3. How long data is kept
  4. When deletion happens
  5. When the plan changes
  6. Deleting sooner
  7. Taking your data out
  8. Engine and Cloud
  9. Example: the shop on Builder

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:

DataWhere
Raw events, replay recordings, page snapshots and source mapsAmazon S3
Results: problems, the index of sessions, performance numbers, settings, accountsA 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.

Who else touches your data

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

CompanyJobWhat it receives
Amazon Web ServicesHosting, 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 itRunning the model for the agent’s analysisWhat 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.
GitHubPull requests, only if you install the Sypnia GitHub AppThe branch and the pull request Sypnia writes. See The GitHub App.
StripePayments, only on paid plansYour 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. This table says exactly what that number applies to.

DataKept
Events, sessions and their timelines, tracesThe plan’s days
Replay recordingsThe plan’s days, and never more than 30
Page snapshotsThe plan’s days
Activity of people and accountsThe plan’s days
Hourly and daily numbers: performance, click counts, usage400 days, on every plan. They are totals, and hold nothing about people.
AlertsThe plan’s days
UptimeSingle results for 7 days, and the numbers of each hour for 400 days, on every plan. They hold nothing about people.
Source maps90 days after their release was last seen
Problems: the sentence, the analysis, the status, the counts for each day, and one example of the failureAs long as the project exists, or until you delete the problem, in the app or through the API. 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 checksAs long as the project exists
Usage counters for each monthAs long as the organization exists
Your account and your organizationUntil you delete them
Invoices and payment recordsAs long as accounting rules require us to keep them, even after you delete the organization
Request logs of our servers, which include IP addresses30 days
Backups of the database7 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. See Deleting data.

Taking your data out

Everything Sypnia keeps about your project can be read through the API while it is kept, with an API token. There is no one-click export at launch.

Engine and Cloud

The Sypnia engine and Sypnia Cloud compared
Sypnia engineOpen source, self-hostedSypnia CloudPaid service, with a free tier
Where data livesIn 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 keptAs long as you set, for each kind of data.The plan's days. Problems are kept while the project exists.
Who else touches itYour 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 itWhoever 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. What Sypnia collects in the first place is in What is collected, and how we protect it in 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».

Sections

Start hereWhat Sypnia is, how it works, what is open source and what is the paid cloud, and the two ways to get your first problem in plain words.ConceptsThe ten ideas Sypnia is made of, each defined precisely, from a project and its keys to problems, traces and alerts.SDKsHow your app sends data to Sypnia. One SDK for the browser, one for Node, one for Next.js, and the OpenTelemetry intake for every other backend.The agentHow Sypnia analyses a problem, what it writes, what it sends to a model and what it never does.MCP and skillsConnect your coding agent to Sypnia so it can ask what is failing in production, read what it needs to fix it, and set Sypnia up for you.API referenceThe Sypnia HTTP API: one API for the open-source engine and for Sypnia Cloud, with every endpoint, parameter, response and error.CLI referenceThe sypnia command: how to install it, the variables it reads, what its exit codes mean, and where each command is documented.Self-hostingWhat you run when you host the Sypnia engine yourself, what you need, what it costs, and what you do not get compared with Sypnia Cloud.How the engine is builtThe whole Sypnia engine on one page, from a click in your app to the sentence your coding agent reads, with the design rules and the code that holds them.Sypnia CloudHow the paid service works, from organizations and roles to plans, limits, billing, where your data lives, the GitHub App and support.Privacy and securityWhat Sypnia collects from your app and its users, what it never collects, how masking works, how to delete data, and how the service is protected.LicensingWhich licence covers each part of Sypnia, what you may do with it, how the name may be used, and the terms of a contribution.GuidesStep-by-step recipes for the common ways to use Sypnia, from apps made with AI builders and Next.js on Vercel to Supabase, source maps in CI, alert e-mails from your own engine, and moving from Sentry.ReferenceThe pages you look things up in, from the event schema and the glossary to what is planned, the changelog and the common questions.
↑↓ to move↵ to openEsc to close