The short version. qrmy.app sets a single first-party cookie to keep you signed in. We don't use advertising cookies, we don't embed third-party trackers, and the QR redirect itself does not set anything on a scanner's device.
What we use
Session cookie (essential)
If you sign in through qrmy.app or dashboard.qrmy.app, our authentication provider Clerk sets a first-party session cookie so you don't have to sign in again on every page. This cookie expires when you sign out or after a period of inactivity. Without it, signing in to the product wouldn't work — that's why it's classified as essential rather than optional.
What we don't use
- No advertising cookies. No retargeting pixels.
- No Google Analytics, no Meta Pixel, no Hotjar, no Clarity.
- No third-party social embeds that drop cookies before consent.
- No "we work with 200+ partners who may store cookies on your device" mystery list.
The QR redirect
When someone scans one of your dynamic QR codes, our redirect endpoint logs the scan (timestamp, coarse device type, OS, browser, country and city when available) server-side and sends the scanner to the destination you set. It does not set a cookie on the scanner's device, and it does not set a persistent identifier of any kind. The scanner appears on your dashboard as one anonymous scan, not a person.
Site analytics
We use a privacy-preserving analytics tool on qrmy.app that does not set cookies and does not assign a persistent identifier to visitors. It records page, referrer, and country in aggregate. There is no per-visitor profile.
Your control
You can clear or block cookies at any time from your browser settings. If you block the essential session cookie, signing in to the dashboard won't work — that's the only meaningful effect of doing so.
Changes
If we ever add a new category of cookie, we'll update this page and, if it's not strictly essential, ask for your consent before setting it.
Contact
Questions: hello@qrmy.app. See also our privacy policy.