Security

Security, stated plainly.

We don't have a SOC 2 certificate to wave at you, so here's what we actually do — and what we don't claim.

What we do

• Authentication on non-public endpoints: API keys or admin tokens guard everything that isn't designed to be public.
• Encryption in transit: the service is deployed behind TLS (HTTPS) — we never recommend running it on plain HTTP in production.
• Input validation: every endpoint validates and size-limits its inputs; errors are structured, never stack traces.
• Structured logging: operational logs for reliability and incident response — no sensitive payloads in logs.
• Fail-closed configuration: if an auth secret isn't configured, protected endpoints refuse traffic rather than opening up.
• Admin pages and endpoints (dashboard, domain registration, CSV export) require an admin key; the service fails closed when it's unset.
• Visitor-facing endpoints (banner, config, consent logging) are public by design — they're hit by your visitors' browsers.
• All configuration is environment-driven; no secrets are hardcoded.
• Deploy behind TLS (HTTPS). Consent logs are evidentiary — back up the store and retain per your privacy policy.

What we don't claim

• No SOC 2, ISO 27001, or other certifications — yet. We'll pursue them when customer demand justifies it, and say so here when we do.
• No security practice is a guarantee. We describe controls, not outcomes.

Report a vulnerability

Email don+cookieclear@lifeofmorr.com with "security" in the subject. We'll acknowledge within 2 business days and keep you posted on the fix.