Privacy

DB Access Receipts is local-first. The CLI has no telemetry and sends no queries, credentials, results, receipts, or usage events to us.

What stays on your device

Database URLs and signing keys are stored in your operating system keychain. Receipt JSON is written only to the directory in your policy. Receipts omit result cells, raw SQL, database URLs, and raw parameter values by default.

The interactive site demo stores up to ten illustrative receipts in local storage under db-receipts:demo-receipts, plus an optional theme choice. You can clear demo history on the home page or through browser settings.

Licenses and purchases

If you paste or return with a license, the token and a daily verification verdict are stored in local storage under sb_license:db-access-receipts. The token is sent only to Sociobot's verification endpoint. Checkout is hosted by Sociobot/Dodo, the merchant of record; their policies govern purchase information.

Network activity

This site uses no analytics, advertising, third-party fonts, or tracking scripts. Same-origin assets may be cached by a service worker for offline use. A license verification request occurs only after a license is supplied.

Your control

Remove local data through the demo's clear control and your browser's site-storage settings. Remove CLI secrets with db-receipts secret clear. Delete receipt files using your normal retention policy.

Contact

For privacy questions, open an issue in the project repository. Do not include credentials, license tokens, query text, or database data.