Privacy
Last updated: May 2026. This is a side project; keep expectations modest.
What we collect
If you sign in, Supabase Auth stores account identifiers (for example email) and session data as configured in your Supabase project. We do not sell personal data.
Scans
When you run a scan, we store the target URL metadata, scores, and per-check results in Supabase Postgres under your user id so you can reopen reports. Opt-in share links use a random token; public viewers do not see your account details.
Optional OpenAI (“Generate fix”)
If enabled on the server, clicking Generate fix sends a small JSON payload (check id and platform hint) to OpenAI—not your full site HTML. We do not train third-party models on your behalf; refer to OpenAI’s policies for their retention.
Cookies
We use cookies for Supabase session management where required by the auth integration.
Retention
Old scans may be deleted on a schedule you configure (see deployment docs for optional cron). You can revoke a share link from the scan page at any time.
Contact
This project may not provide a support inbox. For hosting-specific issues, check your Railway and Supabase dashboards.