Health and security checks for your databases, read from catalogs, statistics and settings, never from your tables. PII discovery finds the columns that hold personal data and lets you record each one's legal basis under GDPR or Georgian DPL.
PII discovery finds the columns that hold personal data from their names and types, and lets you record each one's legal basis under GDPR or Georgian DPL. It never reads a row.
Scans read catalogs, statistics views and settings, never the rows of your tables, on SaaS and on-premises alike. Some findings quote the text of recent statements from those views, values included. DBVitals sends us no telemetry, and on-premises it makes no outbound call on its own. Apart from the alerts and reports it sends you, only the AI features send data outside DBVitals, to Anthropic's Claude, and only when you use them.
What DBVitals reads, what it keeps, and what leaves it, on SaaS and on-premises.
System catalogs, statistics views and configuration parameters, never the rows of your tables. Health scans run on a read-only account with no SELECT on your tables.
Statistics views keep the text of recent statements, and some findings quote it, such as blocked and long-running statements. The values in that text stay unless the database replaced them with placeholders; PostgreSQL replaces constants, but not comments or the values in SET and DO.
Reads column names, data types and lengths from each engine's catalog, never a row. Where the account cannot see a table's columns, the result says so and names the grant that lets it see.
None. No usage data, no error reports, no licence checks: an on-premises licence is verified on the server itself.
On SaaS, DBVitals fetches public release dates of database versions from endoflife.date. On-premises it makes none: that data ships with each release.
Only when you use them, they send data to Anthropic's Claude. The Optimization Lab and Query Advisor's AI optimize send the query and its plan with their values removed, and a description of the tables they name: their columns, keys, indexes, sizes and statistics dates, with the constants in their definitions replaced by ?, and the latest scan's findings on them, never their rows. A query or plan whose values can't be removed isn't sent, and a plan you paste is kept only without them. Live Activity's Ask sends a cleaned copy of its last three snapshots with your question: sessions and users as labels, every statement with its values removed, never a client address, and a description of the tables the waiting sessions wait on. Log analysis, where it is switched on, sends the log lines. The index advisor, when a DBA asks for it on a PostgreSQL scan's result, sends that database's slowest statements with their values removed, its table statistics and a description of those tables. Nothing is sent until someone presses a feature's button, and an administrator can switch every AI feature off, which hides every AI button.
Sent only to the recipients and channels you set up. On SaaS, an alert email can carry the scan's PDF report.
SaaS runs in the EU, on AWS in Frankfurt. On-premises, DBVitals runs on your own server, and what it stores stays there.
Every issue includes the rule, evidence from system catalogs and statistics views, the compliance controls it touches, and a copy-pasteable fix. Pick one to inspect.
Same score. Same rules. Same 60-second scan.