Security and telemetry
How to report a vulnerability, what's in scope, the guarantees the code is built around, and what OpenDash sends home (nothing).
Report a vulnerability
Please report it privately, never in a public issue or discussion:
- on GitHub, open the repository's Security tab and choose Report a vulnerability, or
- email hello@sureshkumar.dev.
Include what you found, how to reproduce it, and what it affects. We'll acknowledge the report as soon as we can, work on a fix, and credit you in the release notes if you'd like.
Supported versions. OpenDash is pre-1.0. Security fixes go into main and the latest release.
In scope
The code in the repository and the images built from it: tenant isolation, authentication and API keys, the query gateway and its read-only guarantees, the answer gate, stored secrets, and the Slack and email integrations.
Guarantees the code is built around
| Guarantee | How it's enforced |
|---|---|
| Workspaces can't see each other's data | Every tenant table is keyed by (org_id, id) with row-level security. The application role can't bypass it, and code reaches tenant data only through withTenant. A test suite checks every table has its policies and that cross-workspace access is denied. |
| Your databases are never written to | Only workers connect, through read-only sessions with server-side time limits, as the read-only user you created. |
| Numbers can't be made up | The model cites query cells; deterministic code recomputes every one. |
| Secrets stay secret | Connection passwords and model keys are encrypted with your key (OPENDASH_KEK), never logged, never put in prompts, never returned to the browser. |
| Closed by default | Self-hosted instances are invite-only, and sign-in requires HTTPS. |
| No SSRF through tools | Outbound calls go through an SSRF guard; inbound webhooks are verified by signature. |
| Personal data stays out of answers | Personal-data columns can be counted and filtered, but their values are never returned. |
For the settings you control as an operator, see Networking and security.
Telemetry
Self-hosted builds send no telemetry. If anonymous usage statistics are ever added, they will be opt-in, documented, and easy to turn off.
- Tracing to your own OpenTelemetry collector is opt-in (
OTEL_EXPORTER_OTLP_ENDPOINT), and spans never carry a question, its SQL or an answer. - Telemetry in third-party dependencies is audited and disabled.