Docs

Privacy and security

What 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.

Applies to EngineCloud At launch

View as Markdown

Sypnia records what people do in your app. That is useful and it is a responsibility, yours and ours. This section says exactly what is collected, what is never collected, how to hide more, how to delete, and how the data is protected.

It is written for three readers: the person installing Sypnia, the person who must explain it to their own users, and the person reviewing it before saying yes.

Most of this section applies to the open-source engine and to Sypnia Cloud alike, because collection and masking happen in the SDKs, which are the same. Where the two differ, mainly in who stores the data and who can read it, each page says so.

  • What is collected

    Every kind of data Sypnia receives, which of it is personal, and what it never receives.
  • Masking

    What is hidden always, what you can hide, and how to check it.
  • Deleting data

    What «delete» removes, how fast, and what stays.
  • Security practices

    How access, storage and staff access work, and what we do not have yet.

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