Honest about what's protected.

Encryption

All traffic to the API and dashboard is served over TLS. Data at rest — your datasets, run artifacts, and labels — is encrypted by the underlying storage layer.

Tenant isolation

Every dataset, run, and label is owned by a tenant and scoped by tenant on read. The two cookie-auth surfaces (customer dashboard and operator admin) use separate cookie names and signing salts on purpose — logging into one does not grant the other. The customer API is a third, independent surface authenticated by bearer token.

Credentials & API keys

API keys are gn_live_-prefixed and stored hashed; lookups use a constant-time compare. A bad or revoked key returns an indistinguishable 401 so a probing attacker cannot tell which it is. We never log keys or password hashes.

Network & input defenses

• SSRF allowlist — customer-supplied LLM hosts are checked against a per-provider allowlist; requests to loopback, private, link-local, or cloud-metadata addresses are rejected.
• No customer code execution — the hosted path never runs customer-supplied Python. Specs carrying a code field are rejected at the API boundary.
• Strict response headers — HSTS, a per-request CSP nonce, X-Content-Type-Options, X-Frame-Options: DENY, and a referrer policy on every response.
• Untrusted uploads — dataset bytes are parsed through a shape-validating pipeline that rejects pickles.

Verifiability

Security here is not only about keeping data out — it's about being able to prove a result. Every governed run seals and hashes its estimand, metric, gold snapshot, and model pins, and emits a reproducibility manifest. You can confirm a certified number was computed against the locked plan and recompute it yourself. The system is designed to decline to certify when the data can't support a trustworthy number rather than overclaim.

Data residency & private deployment

Today the service is hosted, with the isolation and deletion controls above; see data residency for specifics. A VPC / on-prem deployment — where you hold the data and the gold and we provide the estimator, so safety- or fraud-sensitive data never leaves your environment — is on the roadmap. Until it ships, residency is procedural (encrypted, isolated, deletable, pre-registered, reproducible), and we will say so plainly to any reviewer who asks.

Reporting a vulnerability

If you believe you've found a security issue, email kodycoppock@gmail.com. We'll acknowledge and work with you on a fix.