Accounts
- Passwords are stored as scrypt hashes; sign in is rate limited and takes the same time whether or not an account exists.
- Two factor authentication with an authenticator app, with ten single use recovery codes stored as hashes. The authenticator secret is encrypted at rest.
- Sessions use httpOnly cookies; every change request needs a CSRF token and a same origin request.
Isolation and permissions
- Every request is checked on the server against the workspace role: owner, admin, editor, client or viewer.
- Workspaces and sites are isolated; API keys are scoped to one workspace and to specific permissions.
Published sites
- Published sites are static files: no customer server code runs on our servers.
- Site content is validated against a strict schema; styles and rich text pass through allowlists, so pages cannot contain injected scripts.
- Third party embeds and custom code run in sandboxed frames without access to the site or its visitors.
- Every published page is sent with a strict Content Security Policy, and previews are served from a separate origin with no app cookies.
Uploads
File types are detected from their content, images are re-encoded (removing metadata and anything hidden in the file), and SVG files with scripts or external references are refused.
AI
The AI can only act through validated tools on a copy of your site; every tool call is checked and logged, and nothing is saved or published without your approval.
Infrastructure
Data is encrypted in transit (TLS) and stored in managed databases and object storage with backups. Background jobs retry safely and are idempotent. Outgoing requests to addresses you provide (webhooks, link checks) are blocked from reaching private networks.
Reporting a vulnerability
Please email [email protected] with details. We will acknowledge within three business days and keep you updated. Please do not access other people's data or disrupt the service while testing.