Local-First & Zero Query / Schema Telemetry
SQLStudio is a local-first native Rust + GPUI desktop workbench. By architectural design, your database operations stay strictly on your machine:
- We NEVER collect, log, or upload your SQL queries, result rows, table schemas, DDL, index stats, or orphan audit outputs.
- SQLStudio contains zero analytics trackers, ad SDKs, or background telemetry beacons.
- Community Edition, the 7-day local trial, and imported `SQLS1.` offline tokens verify 100% locally with zero outbound network requests.
Encrypted Local Credential Vault (.credentials.vault.json)
Database passwords, SSH passphrases, MCP HTTP Bearer secrets, and BYOK API keys are NEVER written in plain text. Secrets are encrypted locally inside `.credentials.vault.json` (and OS keychain integration where configured) ONLY when you explicitly opt in to remember them; otherwise they stay in volatile memory for the active session only.
All new connections default to `read_only = true` to prevent accidental mutations by users or connected MCP agents.
Direct BYOK Model Calls & Outbound PII Shield
When using AI Copilot, requests go directly from your machine to your selected provider among our 20 BYOK integrations (such as OpenAI, Anthropic, Gemini, DeepSeek, or 100% local Ollama / llama.cpp)—never proxied through SQLStudio servers.
Outbound payloads and MCP responses pass through SQLStudio’s local PII shield (masking emails, phones, IDs, and cards while exempting numeric aggregates) and your configured column `deny`/`mask` rules.
Licensing & Machine Fingerprint Hash (Online Activation Only)
Only when you explicitly run online activation (`sqlstudio license activate`), periodic license validation, or slot deactivation (`sqlstudio license deactivate`) does SQLStudio contact our stateless Cloudflare Worker gateway (`https://license.sqlstudio.dev`) and Creem:
- Transmitted fields are strictly limited to: your Creem license key / `license_id`, `instance_name` (device label), `instance_id`, and a one-way SHA-256 machine fingerprint hash (`sqlstudio-machine-fp-v1` derived from OS, arch, hostname, username, and OS machine UUID seed—never raw files or unhashed secrets).
- When Cloudflare KV caching is enabled on the gateway, it retains only minimal license metadata (`license_id`, `key`, `product_id`, buyer email, and `status`) to process Creem webhooks and device validation.
Billing & Payment Privacy (Creem MoR)
Payment card details, billing addresses, and tax identification numbers are collected and processed solely by Creem as Merchant of Record under PCI-DSS and applicable privacy laws (including GDPR). SQLStudio never receives or stores your payment card numbers.
Your Rights, Deletion & Contact
You can delete `.credentials.vault.json` and local workspace configs anytime on your device, or run `sqlstudio license deactivate` to unbind your instance slot. To request access to or deletion of gateway license metadata tied to your email, contact us via GitHub or your Creem receipt support channel.
Download v0.6.5 and run sqlstudio license start-trial to test all 7 FeatureGates with zero commitment.