Security and privacy
Where your connection details, queries and AI requests go, and what Tamery stores.
Connection details
Connection strings are encrypted on your device. On desktop, the device key uses the system keychain where available.
You choose what reaches Tamery's cloud when you create a connection:
| Sync type | Stored in the cloud |
|---|---|
| Full | The complete connection string, encrypted. |
| No password | Connection details without the password, SSH secrets, SSL key secrets, or access token. |
| Metadata only | Name, engine, label, and color. No connection string. |
Synced connection strings are encrypted with a workspace key. They are decrypted on Tamery's server when another device retrieves them, then sent over HTTPS. This is not end-to-end encryption.
Where queries run
- Desktop: your computer connects to the database directly.
- Web with
tamery proxy: the computer running the proxy connects to the database. - Web without a local proxy: Tamery's cloud proxy connects to public database servers and handles the query and its results.
The cloud proxy cannot reach private addresses or open SQLite and certificate files on your computer. Use desktop or the local proxy for those. Connections whose secrets stay on your device also need desktop or the local proxy.
Cloud proxy IP addresses
If your database only accepts allowlisted IP addresses, add these so the cloud proxy can reach it:
208.77.244.241
152.55.184.240
152.55.185.189
Add all three. The proxy can connect from any of them. Desktop and tamery proxy connect from your own network, so allow that address instead.
Other services at our hosting provider share these addresses. An allowlist narrows who can reach your database, but the database password still protects it.
Encryption between Tamery and your database depends on the connection's SSL settings.
SSH tunnels
SSH tunnels run on desktop only. Tamery checks the server's host key and asks before trusting an unknown one. A changed key is refused.
You can use your SSH agent, a key file, a pasted private key, or a password. ~/.ssh/config is supported; ProxyJump and ProxyCommand are not.
What else we store
Saved queries and AI chats are stored on our servers, so they follow you to every device. They are kept per database and go away when you remove the connection.
Query history and the query logger stay on the device that ran the queries. So do your Navigator, tab, and table layout.
AI and your data
AI requests go through our servers to external model providers. The chat sends your messages. Editor and filter features also send the schema context they need.
The built-in chat does not execute SQL. Coding agents connected through MCP can read data and make changes according to the access you grant; their results become part of the agent's context.
AI help with a failed test
Explain with AI sends connection diagnostics when you click it. Tamery removes connection identifiers and secrets from the error, and sends details such as the engine, port, SSL options, and whether the host is local or public.
Agent access
MCP clients use a local access token. Keep it out of shared config files. If it leaks, regenerate it in Settings → MCP.
Tamery's read-only checks cannot stop every side effect of a database function. For a hard limit, connect with a database user that has only the permissions you need.
Tamery is open source under AGPL-3.0.