Updated: 22 November 2026
Where your data lives
The service runs on a server in Europe. The database can only be reached from that server, never from the internet. Backup copies leave encrypted for a storage in France (Scaleway, Paris region). The full list of providers, with what each one receives, is in the list of sub-processors.
Encryption
- In transit: everything goes over HTTPS, with a Let's Encrypt certificate renewed automatically. The browser is asked never to come back over HTTP (HSTS).
- At rest: your screens, your designed back end, your scenarios, your comments and the state of co-editing are encrypted (AES-256-GCM) with a key of your organization's own. That key is itself encrypted by a master key that is never in the database: a stolen database or backup, on its own, gives nothing readable.
- The secrets you entrust to the studio (Jira token, webhooks) are encrypted separately.
Walls between organizations
Every row of the database belongs to an organization, and the database itself refuses to return a row of another organization (PostgreSQL row-level security), whatever the query. Automated tests check these walls on every change of the code.
Kits (the components of your app) run in an isolated frame, on an origin of their own: their code can neither read the editor nor act with your session.
Accounts and access
- Sign-in with Google. The studio knows no password.
- A session is a random token in a cookie scripts cannot read; the database only keeps its fingerprint. You see your open sessions and can close one remotely.
- Four roles (administrator, editor, reviewer, guest), checked by the server on every request.
- Personal tokens (scripts, agents) can be limited to a project, to reading, until a date. They are shown only once.
- After ten refused sign-ins in a row, the address and the account are blocked for 15 minutes. The number of requests per minute is limited.
Nobody at Conflo reads your content without you
For Conflo's support to see your screens (to help you), an administrator of your organization must open a support access: for 1 to 72 hours, read-only if they wish. While it is open, a banner tells all your members. The opening, the closing and every screen read by support go to your audit log. Without an open access, entry is refused.
Audit log
Sign-ins (successful or refused), invitations, role changes, tokens, settings, support access, reads and writes of AI agents: who, what, when and from where. Your administrators read and export it. Nobody can change or erase it from the tool.
Artificial intelligence
Your content trains no model. An AI agent only reaches it if your organization has allowed it and issued it a token; your administrators can forbid all agents. What an agent reads and writes goes to the audit log.
Backups
- A copy of the database every night, kept 14 days on the server.
- An encrypted copy off the server every night: 7 nights, 4 weeks and 6 months are kept.
- Every week, the latest copy is restored into a test database to check that it reads back.
- A missed backup, a full disk or a burst of errors raises an alert.
- Availability is watched from outside: status page.
Your data belongs to you
You export a project or the whole organization as one file, at any time. A deletion takes effect after 30 days (it can be cancelled until then); the backups that still hold the data then expire on their own.
How it is checked
- Dependencies are audited (
npm audit, Trivy) and the code analysed (Semgrep). - An internal security review attacked a local instance in November 2026: walls between organizations, kit upload, isolated frame, sessions and tokens, then an OWASP ZAP scan. The flaws found were fixed.
- The server updates itself automatically for the system's security fixes.
Reporting a flaw
Write to security@conflostudio.com. Please leave time for a fix before making a flaw public. Answer within 5 working days (acknowledgement).