Privacy.

Single-style QRs (link, WiFi, vCard, UPI, WhatsApp, etc.) are generated in your browser. We don't see the contents. There's no upload, no logging, no analytics on what you encode.

When you click Make this QR trackable, we store three things in our Redis database (Upstash): the short ID, the destination URL, and your account ID so only you can edit it. Records auto-expire after 1 year if untouched.

Each scan logs a timestamp and, where the host network provides it, the country the request originated from, the device family (iOS / Android / etc.), and the referer header. We don't log full IP addresses; the country header is set by the edge network (Vercel or Cloudflare) before the request reaches our code.

The page contents (title, tagline, avatar, theme, action list) live in our Redis store so the public landing at /m/<id> can render.

QR codes for bio and multi-action pages encode a separate /q/<id>redirect, not the /m/<id> page directly. Hits on /q count as scans; direct visits to /m/<id> (a friend pasting the link into chat, social shares, your own preview) are not logged. The scan counter you see in the dashboard reflects real QR scans only.

Sign-in is optional. When you sign in with Google, we store your email address and a user ID. Your saved brand kits and QR catalog live in our Postgres database (Supabase), gated by row-level security so only your account can read them. Sign out and we keep nothing client-side.

We don't set tracking cookies or ad pixels. We don't run third-party analytics on you. Supabase handles the OAuth handshake when you sign in; Upstash holds the Redis records for trackable + bio + multi pages. That's the lot.

Delete a trackable QR or bio / multi-action page from your dashboard and the underlying record is removed from our Redis store immediately. For local catalog entries and brand kits, clear site data for the QRDone site in your browser.