Security
How a delivered Analytics Dashboard instance is built to fail closed, not open.
API-key authentication
Every control endpoint (add a source, update metrics, read the dashboard) requires an X-API-Key header. No key configured means every request is rejected — the system fails closed, never open.
Encryption in transit
All traffic to and from a delivered instance runs over TLS, including calls to every connected source API.
Your data stays yours
Aggregated metrics are delivered directly to the destination you configure — your dashboard, your infrastructure. We don't retain a copy or route your data through a third-party store.
Bring your own credentials
Every source-API key the build uses is yours. You control the account, the spend, and can revoke access at any time. We don't hold a standing copy of your keys after delivery.
Read-only by default
Unless a write-back capability is explicitly part of your agreed scope, the dashboard only reads from your connected sources — it never modifies data at the origin.
Credential handling during support
If a support task requires access to your environment, access is scoped to that specific task and time-boxed. We do not request or hold standing admin credentials as a condition of delivery.
Incident response
If a security issue affecting a delivered build is identified, we notify the affected party without undue delay, describe the exposure plainly, and ship a fix on a priority track.
Responsible disclosure
If you believe you've found a vulnerability in a delivered build or on this site, contact us through the channel you used to place your order. Describe the issue and, if possible, steps to reproduce it. We take reports seriously, do not pursue legal action against good-faith researchers who report responsibly, and will confirm receipt and a fix timeline directly.