localStorageClick the user icon in the header → enter your email → optionally set a display name → click Submit. We use Supabase Auth with password sign-in. You can also use the magic-link option if your Supabase setup is configured for that.
Confirmation email check is optional — by default Supabase's email-confirmation flow is on, so you'll get a verification mail. Click the link, you're signed in. No password reset hoops for the initial signup.
Open the account modal (user icon → Account) → "Danger" tab → "Delete account". Confirms once,
then runs a Supabase RPC that cascades-deletes your auth.users row. Foreign keys on
the screenshotify schema cascade from there: profile, projects, feedback items, votes — all gone.
We don't keep backups beyond 30 days. After that the deletion is irreversible. Local browser
localStorage is separate — clear browser data if you want to wipe local copies too.
The full privacy story is at /legal/privacy. Short version: stored on Supabase (EU region), no third-party tracking, no advertising pixels, no cookie banner because we don't set tracking cookies.
Yes. The browser localStorage project loads on first sign-in and saves to the cloud automatically. Don't clear browser data before signing in.
Supabase Auth with email + password as the primary flow. The deadlock-fix we have around onAuthStateChange means signin shouldn't ever hang — if it does, hard-refresh and try again.
Not yet. Supabase supports it; we haven't wired the UI. Email/password covers the use case until we hear there's real demand for social auth.