Security and privacy
quadrille is built to keep your data with you. This page explains, with as little jargon as possible, what the app does to protect it and what you can verify yourself. The full technical document is SECURITY.md in the repository.
How the app is protected
Browser and installable app
- Strict Content Security Policy: scripts only from the app's own origin, no inline scripts, no plugins, the app cannot be embedded by other sites (only quadrille.it, for the demo). The same security headers (
X-Content-Type-Options,Referrer-Policy,Permissions-Policy, HSTS) are sent by the server. - All user content is escaped before it reaches the page; the sheet's SVG is built from escaped strings only.
- Only
http(s)links open;javascript:and other schemes are rejected. The PDF preview runs in a sandbox with no referrer. External requests are limited to the configured Supabase project and, only with previews on, to the preview service. - The service worker caches same-origin files only. No secrets live in the client: the Supabase public key is public by design and every access is enforced by the server.
Cloud and collaboration (Supabase)
- Row-level security on every table: you only see boards you are a member of; editors write, viewers read. Share links go through a controlled function, so a token never grants access to anything else; the owner can turn them off or rotate them.
- Rows are size-limited, batch uploads are capped, conflicts are resolved by the server. Uploaded files live under unguessable paths and uploading requires edit rights.
- Signing in with Google, Apple or GitHub gives the app only your e-mail and name; nothing is ever written back to those accounts.
Desktop and phone
- Desktop (Electron): isolated, sandboxed renderer, no Node access, navigation away from the app blocked, external links in the system browser, permissions denied except camera and microphone, hardened runtime on macOS.
- Phone (Capacitor): HTTPS scheme on Android, mixed content disabled, the same policy as the web app, minimal permissions (camera and microphone only when you use them), builds signed with a key that never lives in the code.
Checks on every version
Before every build an automated test (npm run test:compliance) fails if the policy is weakened, an inline script appears, a secret-looking string lands in a shipped file, a permission is added on Android, an iOS usage description or the privacy manifest goes missing, the legal pages are unlinked or the version numbers drift apart. Dependencies are checked with npm audit for web, desktop and mobile.
Reporting a vulnerability
Write privately to info@quadrille.it or use GitHub's private reporting (Security → Report a vulnerability). We answer within 3 working days and credit reporters, if they wish, in the release notes. Please do not open a public issue.
Documents: privacy policy · terms of use · third-party licences.