Docs

Security practices

How Sypnia protects the data it holds, in the product itself and in how Sypnia Cloud is run, who can read what, what we do not have yet, and how to report a security problem.

Applies to EngineCloud At launch

View as Markdown
On this page
  1. Built into the product
  2. Less data to protect
  3. Credentials
  4. One project cannot see another
  5. Ingest is built for hostile input
  6. Stored files stay private
  7. What the engine calls
  8. Coding agents
  9. Open code
  10. How Sypnia Cloud is run
  11. Encryption
  12. Who at Sypnia can read your data
  13. Where it goes
  14. Backups and recovery
  15. Our own secrets and code
  16. If something goes wrong
  17. What we do not have yet
  18. When you run the engine yourself
  19. Report a security problem
  20. Engine and Cloud
  21. Related

This page is for whoever reviews Sypnia before saying yes, and for whoever needs to know who can read their data. It has three parts: what is built into the product and is therefore true for the open-source engine Engine and for Sypnia Cloud Cloud alike; how we run Sypnia Cloud; and what is yours when you run the engine yourself.

Built into the product Engine Cloud

These are properties of the SDKs and the engine. They hold wherever the engine runs.

Less data to protect

The safest data is the data that was never sent.

  • What a person types never leaves the browser. Masking happens in the SDK, before anything is sent. Password, card and one-time-code fields cannot be unmasked. See Masking.
  • No request or response bodies, no cookies, no headers. No event has a field for them.
  • Secrets are dropped at the door. Span attributes whose name contains authorization, cookie, password, secret or token are removed at ingest. Sign-in tokens are removed from addresses inside recordings.
  • IP addresses are not stored with events. Ingest uses the caller’s address for the rate limit, in memory. There is no geolocation.

The whole list is in What is collected.

Credentials

CredentialWhat limits it
Ingest key, spk_…Public by design, so it is built to be harmless: it can only send. It reads nothing, changes nothing and reaches no other project. An API token used on an ingest endpoint is refused, so a secret cannot end up in a browser by mistake.
API token, sps_…Shown once. Only its SHA-256 hash is stored, so Sypnia cannot show it again and a copy of the database does not contain tokens. It belongs to one project and carries scopes: read, replay, admin. It can have an end date. A revoked token is refused within one minute.
Root token EngineLives only in the engine’s configuration, never in a table. Sypnia Cloud has none.

Secrets in the engine’s configuration, such as the storage keys, the AI key and webhook secrets, are never printed, logged or returned by the API.

One project cannot see another

Every stored object’s key starts with its project’s id, and every table has the project as the first part of its key. There is no shared table of events and no query that can be written without a project. An API token reaches the one project it belongs to. The design is in How the engine is built.

Ingest is built for hostile input

Anyone can send to a public address, so ingest trusts nothing:

  • Every event is checked against the event schema. What fails is dropped and counted; what is too long is cut.
  • Sizes are capped before and after decompression, so a small body that expands to gigabytes is stopped at the limit.
  • Each key has a rate limit per caller address, and each project can list the origins allowed to send from a browser.
  • Quotas stop a project from storing more than you decided. Nothing is dropped silently: the answer says what was refused and why.

Stored files stay private

The bucket is never public. When a browser must read a replay, or your CI must upload a source map, the engine hands out a link signed for that one object, which works for 15 minutes by default. Reading replay content needs a token with the replay scope.

What the engine calls

  • Webhooks are signed with HMAC-SHA256 and a timestamp, so your receiver can check where a delivery comes from and refuse an old one. By default they go only to HTTPS addresses on the public internet.
  • Uptime checks refuse private and loopback addresses by default, so a check cannot be used to probe a network from the inside.
  • The agent sends a problem’s context to a model: the failure, the stack with source lines, the trace, the release, the counts. It never sends replay recordings or typed input, and masked fields are not in what it reads. On the engine it is off until you set a provider; SYPNIA_AI_SEND_SOURCE=false keeps source code out. See Models and what is sent.

Coding agents

The MCP server reads, with one exception: it can mark a problem resolved, which is recorded and can be undone, and can be switched off. Text that came from your app, such as an error message, reaches your coding agent in named fields, with the instruction that it is data and must never be followed. See MCP security.

Pull requests Cloud are opened on a branch Sypnia creates. Sypnia never merges, never pushes to your default branch and never force-pushes over someone else’s commits. See Pull requests.

Open code

The engine, the Console, the SDKs, the MCP package and the skills are open source. You can read what runs in your users’ browsers and what the engine does with it, and so can anyone you ask to review it. The browser SDK sets no cookies and loads nothing from other companies. See Licensing.

How Sypnia Cloud is run Cloud

Sypnia Cloud is the same engine, deployed by us on Amazon Web Services in us-east-1, with a private part around it: accounts, billing, the app and the GitHub App. Sypnia is run by a small team; this is what that team does.

Encryption

  • In transit: every address of Sypnia Cloud is HTTPS only, and connections between its parts are encrypted.
  • At rest: the bucket and the database are encrypted with keys managed by AWS.
  • Passwords are stored as salted hashes, never as text. You can also sign in with GitHub and use GitHub’s own two-step sign-in.

Who at Sypnia can read your data

  • Access to production is limited to the people who operate the service. Each has their own sign-in, with two steps.
  • Staff look at a customer’s project for three reasons only: you asked for help and the answer needs it, we are investigating a failure or an incident, or we are investigating abuse of the service. We look at what that needs and no more.
  • A replay shows what your users saw. Staff open one only when you point at that session, or when an incident cannot be understood without it.
  • Your data is not sold, not used for advertising and not used to train models.

Where it goes

The companies that touch your data, and what each receives, are listed in Data location and retention: Amazon Web Services, OpenRouter and the model provider behind it, and GitHub and Stripe when you use them. Card numbers go to Stripe and never reach Sypnia.

Backups and recovery

The database is backed up every day and each backup is kept 7 days. Stored files rely on the durability of Amazon S3, which keeps several copies of every object. Backups are restored only to recover from a failure of ours, never to bring back something you deleted.

Our own secrets and code

  • Keys and passwords of the service are kept in a secret store, not in the code repository.
  • The dependencies of the engine and the SDKs are checked for known vulnerabilities, and fixes are released as new versions listed in the changelog.

If something goes wrong

If we learn that someone read or changed data they should not have, we tell the owners of the affected organizations by e-mail as soon as we know what was affected: what happened, which data, what we did and what you should do. There is no public status page at launch.

What we do not have yet

These docs only promise what is true. At launch Sypnia Cloud does not have:

  • A certification or an independent audit report.
  • Single sign-on. It is planned.
  • Two-step sign-in of its own. Sign in with GitHub to use GitHub’s.
  • A choice of region. Everything is in the United States. To keep data elsewhere, self-host.
  • Encryption keys that you manage.
  • A paid bug bounty.
  • A public status page, or a service level agreement.

When you run the engine yourself Engine

Everything in the first part of this page still holds. Everything in the second part becomes yours: where the data lives, who can read it, encryption, backups and upgrades. Sypnia, the company, has no access to a self-hosted engine and receives nothing from it: no telemetry, no licence check, no usage report.

The security checklist is the list to go through before real traffic.

Report a security problem

If you find a way to read or change data that is not yours, or to make Sypnia do something these pages say it cannot, tell us before anyone else. This holds for Sypnia Cloud, for the engine and for the SDKs.

  • Write to support@sypnia.com with «Security» in the subject. Do not open a public report in the repository.
  • Say what you did, what happened, and how to repeat it. Do not include other people’s data; a description is enough.
  • Do not send secrets. If a token was exposed, revoke it first.

What we do: a person reads every report, tells you whether we could reproduce it, and tells you when it is fixed. Fixes in the engine and the SDKs are marked in the changelog. We ask you to give us time to fix a problem before you publish it. We do not promise a response time, and we pay no rewards at launch.

Engine and Cloud

The Sypnia engine and Sypnia Cloud compared
Sypnia engineOpen source, self-hostedSypnia CloudPaid service, with a free tier
Protections in the SDKs and the engineAll of them.The same.
Who operates itYou.Sypnia.
Who can read the dataWhoever holds a token, and whoever administers your infrastructure.The members of your organization, and Sypnia staff under the rules above.
Encryption at rest, backups, upgradesYours to set up. See the security checklist.Done by us.
The model the agent usesThe provider you configure, or none.A model reached through OpenRouter.

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