Skip to content
Docs home

SECURITY · UPDATED AUGUST 2026

Security Controls

The actual controls in place: origin checks, webhook signatures, redaction, secret boundaries, and monitored boundaries.

Boundary controls

Requests are validated at the edge of every surface. The origin check gates POST endpoints so cross-origin requests from unapproved contexts are refused; the Stripe inbound endpoint verifies the signature header before applying any payment update; the Alertmanager sink is fail-closed and refuses anything without the exact configured secret. Protected headers — authorization, content-length, content-type, host, user-agent, and the signature headers — cannot be injected through webhook configuration.

The forbidden key set

A closed set of keys is refused from release evidence, redacted from error contexts, and must never reach public artifacts: auth tokens, access tokens, service role keys, passwords, secrets, API keys, Supabase keys, and customer identity (email, phone, name, address, booking customer identity). The redactor walks payloads recursively under a depth budget and replaces values with [REDACTED] — it never throws on pathological input.

Secret boundaries

The browser bundle carries only the publishable anon key; the service role key lives server-side and is gitignored in deployment. Cron, metrics, and webhook secrets are environment configuration, rotated through the documented rotation procedure, and logged only as presence. TLS for self-hosted deployments terminates at the OpenResty edge with automated certificate management; the application itself never handles private keys.

Business trust lives on the Security page

The /security page carries the business-facing trust narrative. This page carries the technical inventory — controls, boundaries, and behaviors — because the two audiences need different evidence.

STILL READING

Something here still feels worth checking together.

This documentation describes the product exactly as it is implemented. If a behavior you expected is not here — or is here and does not match your deployment — tell the team. Implementation questions start on the contact page.