Security

Local-first by design

Your database credentials, schema work, and query results stay on your machine. BlastRadius Cloud handles accounts and entitlements only.

Security principles

  • Customer row data stays in the customer's database
  • Secrets live in OS keychain — never in git or cloud storage
  • AI-generated SQL is untrusted until the safety layer approves it
  • Cloud stores identity and plan state — not database payloads

Practices

How we approach security

Local-first data plane

BlastRadius Desktop connects to your database from your machine. Today that is a local PostgreSQL connection. Query execution, schema discovery, and workspace code analysis do not route database payloads through BlastRadius Cloud.

SQLite on your machine holds schema metadata and history metadata (SQL text, status, row counts) — not customer row grids as a warehouse.

Credential handling

Secrets never belong in source control, workspace settings, or our cloud database.

  • Database passwords stored in OS keychain / VS Code SecretStorage
  • Cloud API tokens stored in HTTP-only session cookies on this site
  • No logging of passwords, connection strings, or API keys

SQL safety layer

AI-generated SQL is untrusted until validated. BlastRadius fails closed on parse errors and blocks writes, DDL, and multi-statement execution in the MVP read-only model.

  • SELECT and read-only WITH … SELECT only
  • Explicit user confirmation before execute
  • Parameterized queries for catalog reads — no string concatenation from user input

Cloud control plane

BlastRadius Cloud stores account identity, subscription state, entitlements, and coarse usage counters. It does not store database row data or connection strings from your desktop sessions.

  • JWT-based API authentication
  • TLS for all cloud API traffic
  • Privacy Policy and Terms describe retention and subprocessors

Security contact

If you believe you have found a security issue in BlastRadius, please report it responsibly. We acknowledge reports promptly and address confirmed issues as quickly as we can.

Report vulnerabilities: privacy@blastradius.in

Learn more

Policies and product details

Security and privacy are documented in our legal pages and reflected in the product architecture — local SQLite metadata, read-only SQL enforcement, and a separated cloud control plane.

Responsible disclosure

Please include steps to reproduce, affected components (Desktop, Cloud API, or website), and your contact preference. We aim to acknowledge reports within five business days.

Get started

Try BlastRadius on your own database

Use a read-only database role (PostgreSQL is available today) and see how local-first schema intelligence works in practice.