Privacy and data handling
What RDST keeps on your machine, what it sends to AI models and Readyset, what it never sends, and how to turn off usage telemetry.
RDST runs on your machine and connects directly to your database. Your monitoring history, settings and reports stay on your machine, and RDST never writes to your database. Connect it with a read-only database user: when the user you add can write, RDST warns you and gives you the SQL to create a read-only one.
This page covers what RDST keeps, what leaves your machine, and how to turn off the parts you don't want.
What RDST stores
RDST keeps its data on your own machine: the databases you've added, your saved queries, monitoring history, reports and settings. None of it is copied to Readyset.
Clear local data in Settings deletes all of it, along with the credentials RDST saved and the app's browser storage.
Database passwords
RDST saves database passwords in your operating system's secure credential store: Keychain on macOS, Credential Manager on Windows and the Secret Service on Linux. They're never written to disk in plain text and never leave your machine.
On a system without a credential store, RDST keeps passwords in memory for the session only and asks for them again next time.
The same holds when a coding agent adds a database for you. The agent sends the password only to RDST on your computer, which stores it in the credential store. Your agent's own handling of the project files it reads is covered by that agent's terms.
Your Readyset account
AI monitoring needs a Readyset sign-in, which RDST asks for when you turn monitoring on. See AI access. Your account holds your sign-in, your AI usage, and a count of the databases you monitor with AI. RDST counts each database by a fingerprint, a hash of its engine, host, port and database name salted with your account, so its address isn't sent. The name you gave the database in RDST is stored with it.
Signed out, monitoring runs locally without AI and RDST doesn't contact your account.
What is sent to the AI
Only features that need reasoning call an AI model: RDST Agent while AI monitoring is on, Analyze, Ask, schema discovery, and the written parts of reports. Everything else in the app works without an AI call.
| Sent | Never sent |
|---|---|
| SQL text. Change checks and classification send it normalized, with literals replaced by placeholders | The rows your queries return |
Execution plans from EXPLAIN and EXPLAIN ANALYZE | The contents of your tables |
| Schema metadata: table and column names and types, indexes, row estimates | Your database credentials |
| Measured numbers: calls, latency, share of database time, server settings | Your connection details |
| Descriptions you wrote in the semantic layer |
Deep analysis runs the query on your own database with real values, sampled from your app's running queries or read from the table, so the plan shows how the query actually behaves. The analysis says which source it used. The Agent activity log doesn't keep the values, and RDST deletes its local copy after 48 hours.
To stop automatic analyses from running queries with real values, turn off Deep analysis in the monitoring settings.
Agent activity lists every AI call with the model, what it was for, and the kinds of data it sent.
Where requests go
| Work | Where it goes |
|---|---|
| Change checks, query classification and ranking actions | Jev, Readyset's model for quick judgments, through your Readyset account. These calls carry normalized SQL with schema, index and timing evidence |
| Deep analysis, reports, Ask, with the included AI | Claude Haiku from Anthropic, through Readyset's AI service |
| Deep analysis, reports, Ask, with your own Anthropic key | Straight from your computer to Anthropic's API. Readyset doesn't see these requests |
Under Anthropic's API terms, Anthropic doesn't train models on API data, and it deletes API inputs and outputs within 30 days by default.
What is sent to Readyset
Your database's rows and table contents are never sent to Readyset. With the included AI, the requests described above pass through Readyset's AI service on their way to the model, and Readyset records how much AI each account uses.
When you run a comparison or the demo, Readyset runs as a container on your machine. It connects to your database locally to serve cached results, and the data stays between those two processes. Nothing is transmitted to Readyset the company, and the containers are removed when you are done with them.
Feedback and AI-output reports
Feedback sends your message, any email you add, and the context you choose to Readyset through PostHog. General feedback needs an email; AI-output reports don't. Feedback carries a one-time event identifier, not your RDST installation, trial, or provider identities.
Report AI output on Ask answers and Analyze results shows the AI output it will send, including SQL the AI generated, so you can review and redact it first.
Usage telemetry
RDST reports usage telemetry so we can see which features are used and where they fail. Signed out, it's anonymous. When you're signed in, it's linked to your Readyset account and its email.
| Collected | Never collected |
|---|---|
| A random device identifier, and your account when you're signed in | IP-derived identity |
| RDST version, operating system, Python version | Query text |
| Which commands ran, and whether they succeeded | Table, column, or database names |
| Query hashes, so repeat analyses can be counted | Connection details or credentials |
| Cumulative counts of how often features are used | Anything your queries returned |
| Your approximate location (city and country), from your IP address | Files, folders or projects RDST reads to find your databases |
| How many databases the database search found, by kind (like "2 on Docker, 1 on Supabase") | Their names, hosts or where RDST found them |
Queries appear only as hashes. The hash identifies that the same query was analyzed twice; it cannot be turned back into the query.
In RDST Desktop from the Microsoft Store, usage telemetry is off until you allow it, and so is sending database content to AI. The second time you open RDST, it asks once about diagnostics and about starting when you sign in. Both are ticked and take effect when you click Save; Skip leaves both off. RDST asks about AI when you turn on monitoring or first use a feature that needs it, and shows what the AI sees before you choose. Without AI, RDST keeps charts, history and the alerts for connections, stuck queries and locks; slow-query alerts, fixes, Ask and query analysis are off, and each says so. Change either choice in Settings: AI under AI, and the diagnostics choice under Data. Turning one off stops what it covers from then on.
Turning it off
Turn off Share diagnostics under Data in Settings, or set this environment variable before you start RDST:
export RDST_TELEMETRY=offIt turns telemetry off completely, and nothing else in RDST changes.
Working in a restricted environment
For a database that nothing outside its network may reach, run RDST next to it.
Install the CLI on a host inside the perimeter and use
rdst web over SSH port forwarding,
which puts this same interface in your browser while the database connection
stays inside the network.
Signed out and without an LLM key, RDST makes no outbound requests other than telemetry, which the setting above disables.