Security & trust
We sell security.
Of course we use it on ourselves.
Every customer asks: "How do you protect MY data?" Here's the full picture — controls, sub-processors, residency, and how to report a vulnerability.
Six pillars of our posture
AES-256-GCM at rest
Every customer credential we store (Cloudflare tokens, GitHub OAuth, Slack webhook URLs) is encrypted with AES-256-GCM via a versioned `ENCRYPTION_KEY`. Database backups inherit the same encryption.
TLS 1.3 in transit
All API endpoints enforce TLS 1.3; SSL Labs A+ rating with HSTS preload. We probe our own outbound TLS posture daily and alert if the score regresses.
Hardware-backed MFA
Owner accounts must enrol TOTP MFA within 2 days of signup; aal2 enforcement across the dashboard. WebAuthn/Passkeys land Q3.
SOC 2 aligned controls
We run 20 of the SOC 2 Trust Services Criteria controls continuously against our own platform. Evidence collection is automated.
Continuous self-monitoring
Our own scanner runs against our own domains. We eat our own dog food — every check we sell, we run on ourselves daily.
Our live score badge is activating — check back soon for the real-time number.
Regional residency — on the roadmap
Per-tenant data-residency pinning (EU / US / APAC) is architected in our schema and codebase, but not yet live — every organisation is stored in the same single-region Supabase project today. See the Trust Centre for current status.
Sub-processors
Every third-party service in our data path — 21 today, updated whenever we add or remove a vendor. The canonical list with DPAs lives on the sub-processors page (SOC 2 control CC9.1).
| Sub-processor | Purpose | Region |
|---|---|---|
| Supabase | Postgres + auth + object storage | Single region |
| Cloudflare | Edge/CDN + DDoS in front of our app; WAF automation for customer domains | Global |
| Stripe | Subscription billing + tax + checkout | US/EU |
| Brevo | Transactional email delivery | EU |
| Kapso.ai | WhatsApp Business message routing | US |
| WorkOS | Enterprise SSO (SAML/OIDC) + SCIM provisioning | US |
| OpenAI | LLM — primary (triage, plain-language rewrite, chat) | US |
| Anthropic | LLM — fallback provider | US |
| OpenRouter | LLM router — catch-all fallback | US |
| MiniMax | LLM — APAC-region fallback | APAC |
| HIBP | Breach + credential-leak data | US |
| Google Safe Browsing | URL reputation classification | US |
| VirusTotal | URL + file reputation enrichment | US |
| MXToolbox | Email blacklist lookup | US |
| URLScan.io | Phishing-page sandbox + screenshot | EU |
| OSV.dev | Open-source vulnerability database | US |
| NVD | National Vulnerability Database (CVSS metadata) | US |
| EPSS | Exploit Prediction Scoring System | US |
| GitHub | GitHub App — repo scanning (installing customers only) | US |
| Sentry | Error tracking + performance monitoring | US |
| Namecheap | Domain availability lookup (brand protection) | US |
Where our visibility ends
This page covers how we protect OUR platform. See what the product does — and does not — catch for YOUR business.
See the boundaryStatus page
Live uptime + per-service heartbeat. Subscribe to incident notifications.
View statusResponsible disclosure
Found a vulnerability? Email [email protected] — we don't run a paid bounty yet, but we credit researchers publicly on request.
Read policyAligned with industry standards