Privacy statement
Privacy notice ============== Version 1.0, 1 November 2026. Who is responsible. Sun AI and Data LLC, Concord, California, USA is responsible for the personal data described here. Questions and requests: support@dbsheriff.ai. What we collect, why and for how long What: Your e-mail address How it is handled: Sent once, through Amazon SES, so we can e-mail you a sign-in link. We keep only a keyed hash (HMAC-SHA-256 with a secret key), not the address. Why: To send the link and to allow one live account per address How long: The hash is cleared when your account is deleted, at the latest after the 24-hour limit plus clean-up What: Your network address (IP) How it is handled: Seen by the web server and by Cloudflare Turnstile. We keep keyed hashes of the address and of its network block (/24). Why: To limit abuse and block bad actors How long: Hashes cleared with your account, but kept in a block list while a lock holds (up to 24 hours). Raw addresses can appear only in error and security logs (see the last row). What: Sign-in link, session and API token How it is handled: Stored only as hashes. The link works once for 15 minutes. Why: To sign you in How long: Revoked at logout, expiry or 24 hours What: Your login name (a pseudonym such as dv...) How it is handled: Generated by the demo. On its own it does not name you. Why: To tell visitors apart in the demo How long: 400 days in the demo; permanently in DBSheriff's append-only audit trail What: The SQL you run How it is handled: Shown publicly on the monitor with your login name and kept in the audit trail. The demo portal itself keeps no SQL text. Your browser keeps your last 30 statements until you log out. Why: It is what DBSheriff watches; showing it is the point of the demo How long: Statements that touch a sensitive table, or that DBSheriff rates risky, go into the permanent audit trail: kept indefinitely, archived, and never deleted by the product. All other statements are deleted after 7 days. Per-statement monitoring records: up to 400 days. What: What DBSheriff decided How it is handled: Alerts, risk scores, blocked or ended statements and locks tied to your login name Why: To show how the product responds How long: Same as the audit trail What: Technical logs How it is handled: Web server and host logs: time, address, page, result Why: Security and operation How long: We keep no general access log. The error and security logs rotate by size, so old lines are overwritten as new ones arrive (50 MB, 5 files). Public by design. Your login name and your statements appear on a public page. Do not type personal data. The audit trail cannot delete an entry once written. Who receives data on our behalf. Cloudflare (Turnstile bot check; sees your address and browser signals), Amazon Web Services (e-mail delivery through SES), Google Cloud (hosting and storage). No analytics service is used: the demo's pages load no analytics script. The company that hosts the domain's DNS records (Wix) sees no visitor data. Cloudflare acts as our processor when it blocks bots, and as an independent controller of the signals it uses to improve Turnstile. We do not sell personal data and show no advertising. Where. United States. Your data is processed and stored there. If you use the demo from outside the United States, you are sending your data to the United States, and by signing up you agree to that. Your rights. Depending on where you live, you may have the right to access, correct or delete your personal data, to object to how we use it, and to complain to your data protection authority. California residents have the rights to know, delete and correct under the CCPA/CPRA, and we do not treat anyone differently for using them. We do not sell or share personal data for advertising. We use your data because it is necessary to give you the demo you asked for and for our legitimate interest in keeping the demo safe from abuse. To make a request, write to support@dbsheriff.ai from the address you signed up with: we can find your record from the keyed hash. Deleting it removes the hashes and ends your access. It cannot take your login name or your statements out of the audit trail or off the public monitor, because that record is append-only. After the hashes are gone, we can no longer link that name to you. Today we can end your access and block your address, but we cannot erase a single line from the audit trail or the public monitor. Children. The demo is not for people under 21. Security. Secrets and keys stay on the server, addresses and e-mails are stored only as keyed hashes, and the sign-in and API use HTTPS. No system is perfectly secure. Changes. We will post changes here with a new version date.