Security & privacy
What we read
Checkups read only PostgreSQL statistics and catalog views (for example pg_stat_activity, pg_stat_user_tables, pg_stat_statements, pg_replication_slots, pg_policies). A checkup never reads the contents of your tables.
Setting values whose names suggest secrets (for example archive_command, primary_conninfo, anything containing password, secret, token or key) are shown as (hidden), and string literals in running-query text are masked. We never display an archive command, only which tool it uses.
Findings can include object names (tables, indexes, roles) and normalized query text from pg_stat_statements, which may reveal schema details.
Encryption in transit
Remote checkups require TLS with certificate verification by default. Invalid certificates and servers without TLS stop the connection; there is no automatic downgrade. For a private provider CA, use sslrootcert in the connection URL or set PGSSLROOTCERT when running locally. Explicit sslmode=no-verify disables certificate verification; sslmode=disable disables encryption.
If you'd rather not send credentials
Run npx pg-checkup scan on your own machine. It reads the same statistics, writes them to a file you can read, and uploads the file only if you say so. The connection string and password never reach us, and the collector refuses to run with a role that can read your tables. See Run it on your machine.
Read-only guarantee
Each scan session runs SET default_transaction_read_only = on. Combined with a pg_monitor-only role, the scan cannot modify data.
What we store
- Connection string: used to run one scan, held in memory, never written to disk or logs. Errors are redacted before display.
- Scan results (findings and evidence): a free report opens only for the person who ran it, for 7 days without an account and 30 days with one. A Workspace report can be opened by anyone with its link, until you delete it.
- Accounts: email, an optional name, and either a salted password hash (scrypt) or your GitHub/Google id. Sessions are stored hashed. You can delete your account, reports and sign-in details from the Account page.
- Payments: handled by Paystack. We never see card details.
- Waitlist: your email, only if you join.
Recommendations
- Create a dedicated role and rotate its password after use.
- Restrict the role to specific databases where you can.
Reporting a vulnerability
Email [email protected]. Please do not test against databases you do not own.