Now · pairs to your phone over WebRTC Issue 04 · 2026 Free to design · from €9.99 one-time to ship
Screenshotify
Help · Accounts

Cloud sync and signing in.

TL;DR. Optional. Sign in if you want projects to follow you across devices and browsers, or to buy an export or AI credits. Free-tier editor works without an account. Delete your account anytime from the editor — cascades wipe everything.

What you can do without an account

  • Full editor with every device frame, template, AI translation and a watermarked preview — everything except watermark-free export
  • Auto-save to browser localStorage
  • JSON export and import of projects
  • Phone-to-desktop screenshot pairing (no account needed for the WebRTC connection)

What signing in adds

  • Cloud sync — projects save to Supabase keyed to your user-id; same projects available on any browser you sign in on
  • Project history — switch between multiple cloud projects via the project picker
  • Feedback board — post and vote on the in-app feature requests
  • Purchases — required to buy an export or AI credits (we need a stable identity to track entitlement)

The signin flow

Click 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.

Deleting your account

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.

Privacy

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.

Common questions

Can I migrate from anonymous to signed-in without losing my work?

Yes. The browser localStorage project loads on first sign-in and saves to the cloud automatically. Don't clear browser data before signing in.

How is auth handled — Supabase, Auth0, magic link?

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.

Can I sign in via Google / Apple / GitHub?

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.

Open the editor →