Privacy Policy
Last updated 6 August 2026
This describes what SchemaDrift Guardian collects and why. It is written to be read, not to be defensible — where something is a limitation rather than a promise, it says so.
What we never receive
Your data. The service compares schema structure — table names, column names, types, nullability, constraints, enum variants. Row contents are never read, transmitted, or stored. The introspection query runs in your CI and returns metadata only.
Your production database. The GitHub Action introspects a throwaway database that CI creates and destroys. Nothing here ever opens a connection to your live systems.
What we store
- Account: your GitHub user ID, login, display name, avatar URL, and primary verified email address, received when you sign in with GitHub.
- Workspace: a workspace created for you on first sign-in, and the GitHub App installation ID once you install it.
- Schema metadata: the structural snapshots described above, plus the computed differences between them.
- CI run records: repository name, pull request number, commit SHA, verdict, and timing.
- API keys: stored as SHA-256 hashes. The plaintext is shown once at creation and cannot be recovered afterwards — not by you, and not by us.
- Session cookies: an
httpOnlysession cookie scoped to this domain, holding a random token. Session tokens are stored hashed.
Credentials for connected sources
If you register a data source with connection credentials, they are encrypted at rest with AES-256-GCM before being written to the database, and are never returned by any read endpoint.
Analytics and error monitoring
We use PostHog on the website and dashboard to understand feature usage, record sessions, and diagnose application errors. PostHog receives usage events and account properties such as your GitHub user ID, email address, display name, and workspace role.
What we do not do
- No advertising, and no sale or sharing of personal data for advertising.
- No profiling, and no automated decisions with legal effects.
Third parties that necessarily see something
- GitHub — authentication, and the Check Runs and pull request comments the service posts on your behalf.
- PostHog — product analytics, session recordings, and application error monitoring.
- Our hosting and network providers — they process traffic to run the service. Providers may change; this page will be updated when they do.
There is no payment processor, because the service is free and collects no payment details.
Retention
Schema snapshots and CI run history are retained while your workspace exists, because a baseline is only useful in comparison to history. Sessions expire after 14 days. Ask us to delete your workspace and we will remove the account, its snapshots, and its run history.
Your rights
You can request access to, correction of, export of, or deletion of your data by emailing hello@schemadrift.dev. Depending on where you live you may have additional rights under the GDPR, the UK GDPR, or the CCPA; we honour those requests regardless of where you live.
Security, stated honestly
Traffic is served over TLS. Secrets are encrypted at rest. API keys and session tokens are stored hashed. What this service does not have is a completed third-party security audit, a SOC 2 report, or a formal bug bounty. It is early-access software run by one person. That is a reason to weigh what you connect to it, and we would rather say so than let a certification-shaped silence imply otherwise.
Changes
Material changes will be reflected here with a new date at the top. Since this is early access, the shape of the service may change; this page changes with it.