Security and privacy
No analytics.
Your data stays yours.
What SQLAtlas does, what it refuses to do, and exactly what leaves your computer.
What SQLAtlas never does
- Collect usage data, SQL text, rows or connection details. There is no telemetry code.
- Ask you to create an account.
- Store a password anywhere but your system keychain. If the keychain can't be used, it refuses to save rather than write a file.
- Downgrade a connection's encryption by itself.
- Change your server's date format, language or time-zone settings.
- Run AI answers, or send anything to an AI without showing you first.
What leaves your computer, and when
| What | Where to | When |
|---|---|---|
| Your queries and edits | Your database server | When you run them |
| SSH traffic | Your SSH server | When a connection uses a tunnel |
| Microsoft Entra sign-in | Microsoft, in your browser | Only if you choose Entra sign-in for a SQL Server connection |
| An AI request (your SQL with literal values replaced, table and column names, your question) | A model on your own computer, or Anthropic with your own API key | Only if you turned the assistant on and approved that exact request |
| App Store purchase | Apple | When you buy Pro on a Mac |
| Licence activation: the licence key, a salted hash of a random installation id, and the app version | The SQLAtlas licensing service | Windows and Linux only: when you activate or deactivate a licence, and for an optional weekly check that is off unless you turn it on |
Security model
- TLS with certificate and host name verification is the default; optional certificate pinning (PostgreSQL) and client certificates.
- SSH host-key fingerprint required and checked during key exchange, before authentication. A profile with a tunnel never connects directly.
- Production connections are read-only until you unlock them for a limited time; every write is shown for review first.
- Optional Touch ID on the Mac: saved passwords can be used only after Touch ID or your Mac password.
- Every file the app reads or writes is one you chose in a system dialog.
- A strict Content Security Policy inside the app; the app window cannot reach any network host.
How it's tested
Automated tests run against real PostgreSQL, MySQL, MariaDB and SQL Server servers in eight versions, plus a recorded security audit of the app. CI builds and tests it on Linux, Windows and macOS.
Report a vulnerability
Please email security@sqlatlas.eu. I reply within three working days. Please give me 90 days before publishing, and don't test against servers or accounts that aren't yours. See also security.txt.
This website has no cookies, no analytics and no third-party requests, and sends a strict Content Security Policy.