StrokeStroke

Security

A database client holds the keys to production. This page describes how Stroke handles that, where its responsibility ends, and how to tell me about a problem.

Last updated

  • Direct connections

    Stroke talks to your database from your machine. Nothing is proxied.

  • Secrets in the keychain

    Passwords and tokens go to the OS keychain, not a file.

  • Encrypted sync

    End-to-end encrypted. Our servers hold ciphertext only.

  • Local-only MCP

    The agent server listens on 127.0.0.1 and needs a token.

On this page
  1. 01Your databases and credentials
  2. 02Sync
  3. 03AI and the MCP server
  4. 04Licenses and updates
  5. 05Report a vulnerability

01

Your databases and credentials

In short: Direct connections from your device; secrets in the OS keychain.

  • Stroke connects to your databases directly from your computer. Queries and results never pass through our servers.
  • Passwords, tokens and API keys are stored in the operating system's keychain (Keychain on macOS, Credential Manager on Windows, the Secret Service on Linux).
  • TLS is available for every engine that supports it, and SSH tunnels for reaching databases on private networks.
  • Any connection can be opened read-only, which blocks writes in the editor, the grid and the AI.

02

Sync

In short: End-to-end encrypted with a passphrase only you know.

When you turn on sync, each record (a connection, a workspace, your settings) is encrypted on your device with XChaCha20-Poly1305 before upload. The key is wrapped with a key derived from your sync passphrase using Argon2id. Our servers store only ciphertext and the wrapped key, so they cannot read your data, and a lost passphrase cannot be recovered by us.

03

AI and the MCP server

In short: Agents get what you allow, and only from your machine.

  • The MCP server binds to 127.0.0.1, requires a token, and refuses requests from other origins, which blocks DNS-rebinding attacks from web pages.
  • You choose what an agent may run: read only, read and write, schema changes, or full access. Each statement is checked before it runs.
  • The built-in AI asks before running anything destructive.
  • When you use your own AI provider, data goes from your machine to that provider under its terms.

04

Licenses and updates

In short: Signed licenses, signed updates.

  • License entitlements are signed with Ed25519 and bound to the device they were issued to, so a copied file doesn't grant Pro elsewhere.
  • Updates are signed, and the app verifies the signature before installing anything.

05

Report a vulnerability

In short: Email me privately; please don't open a public issue.

Send details to support@stroke.click with “Security report” in the subject: what you found, how to reproduce it, and the version you tested. I'll confirm I got it, keep you posted while I fix it, and credit you in the changelog if you'd like. Please give me a reasonable chance to ship a fix before publishing.

Questions about any of this?

Email us and a person reads it. For privacy requests, say what you need (a copy of your data, a correction, or deletion) and we'll take it from there.