Privacy Policy
Published June 20, 2026
Qrogo is built to collect as little as possible. This page explains what we do and don't do with your data.
The data controller is Qrogo, Valencia, Spain. For any data question or request, email support@qrogo.com.
Static QR codes are generated in your browser
When you create a static QR code (URL, Wi-Fi, vCard, text and similar), the encoding and rendering happen on your device. The content you enter — including Wi-Fi passwords and contact details — is not transmitted to or stored on our servers.
Accounts
If you create an account, we store your email and a securely hashed password to authenticate you. We do not sell or share account data. You can request deletion by emailing support@qrogo.com.
Hosted pages and uploads
Hosted pages (menus, link-in-bio, etc.) and any files you upload are stored on our own server to serve those pages. Uploads are limited to images and PDFs. Don't upload anything you wouldn't want publicly accessible via its link.
Scan analytics
For dynamic codes and hosted pages we record basic scan counts with country-level location and coarse device type. We do not capture precise location, and we do not use third-party advertising or analytics trackers.
Site analytics
We count page views and daily unique visitors so we know whether the site is useful. This is done without storing anything on your device — no analytics cookie, no identifier in your browser's storage.
Instead, our server derives a temporary hash from your IP address and browser user-agent, combined with a random value that we regenerate every 24 hours and never write down. That hash lets us avoid counting the same person twice in a day. Because the random value changes daily and is never stored, the hash cannot be reversed to your IP address and today's cannot be matched to tomorrow's — which is why we can report how many people visited, but genuinely cannot tell whether you have been here before.
Cookies
We use a first-party session cookie to keep you logged in, a short-lived cookie during Google sign-in, and — if you open a password-protected page — one that remembers you entered the password. That's all of them. Every one is strictly necessary for something you asked for.
There are no advertising cookies, no cross-site tracking cookies and no analytics cookies. That is also why you aren't reading this through a cookie consent banner.
Changes
We'll update this page if our practices change, and revise the "Updated" date above.
