Can't sign in.

Sign-in failures fall into a small number of buckets. Try these in order.

**1. Wrong password.** The most common. Click "Forgot your password?" on the sign-in page. LADLE sends a reset link to your email (via Supabase auth). Check spam if it doesn't arrive in 2 minutes.

**2. Wrong email.** If you signed up with a work email and are trying with a personal one, or vice versa. Try both. Passwords are per-email — one account per email.

**3. Not confirmed.** New accounts need an email confirmation click before the first sign-in. Check the inbox of the address you signed up with. The link expires after 24 hours; if it's expired, sign up again (same email is fine — the confirmation gets re-sent).

**4. Third-party cookies blocked.** Some browser privacy settings block the Supabase session cookie. Symptoms: sign-in appears to succeed (no error), then you're bounced back to /login. Fix: allow cookies for our domain, or try a different browser (Chrome / Safari default settings work).

**5. VPN or corporate proxy interfering.** Rare but possible. Some corporate networks strip auth cookies or block Supabase's auth endpoint. Try turning off the VPN or a mobile hotspot as a test.

**6. Session expired.** If you were signed in yesterday and are getting bounced today, your refresh token may have expired. Sign in again with your password. If you had used "Sign out everywhere" from another device, your session was invalidated globally — that's a feature, not a bug.

**7. Account deleted.** If you clicked "Delete account" in the past, the account is gone. There's no recovery. Sign up again with the same email to start fresh.

**8. Something's actually broken.** If none of the above apply, email help@ladle.chat with (a) your email, (b) the browser you're using, (c) what you're seeing. Include a screenshot if it helps. We can pull the server logs to see what auth returned.