Privacy Policy
Last updated: 20 November 2026. This policy describes, in plain language, what MyQRFree collects, what it deliberately does not collect, and what you can ask us to delete.
1. The short version
Static QR codes are generated entirely in your browser. The text, URL, Wi-Fi password, contact details, or logo you type into the generator are never uploaded to our servers, never stored, and never shared. If you only use the free static generator, the scanner, or the bulk generator, we hold no record of what you generated.
Only two features touch our servers: signed-in accounts with dynamic QR codes, and the scan counts those codes produce. For those, we collect the minimum needed to run the feature, hash identifying values before storing them, and never sell data to anyone.
2. What we collect — and what we do not
Static QR codes, scanner, bulk generator (no account needed)
- Nothing is uploaded. Payload building, QR rendering, logo compositing, and PNG/SVG/PDF downloads all run locally on your device.
- Saved codes and design presets in “My Codes” for static codes live in your browser’s local storage, on your device only. Clearing browser data removes them.
- We do not see, log, or store the content of any static QR code you create.
Accounts and dynamic QR codes (signed in) — coming later
- Your email address, used only for sign-in (magic link) and account security.
- The destination URL, label, and active/inactive state of each dynamic code you create, so the short link can redirect and so only you can edit it.
- Your design presets, if you save any, so they are available on your next visit.
Scan analytics (dynamic codes only)
When someone scans a dynamic code, we record an anonymous scan event: the time of the scan, an estimated country (from the hosting provider’s country header, where available), a coarse device type (mobile, tablet, or desktop), and the referring page where available. We do not store raw IP addresses or raw user-agent strings. Both are passed through a one-way SHA-256 hash with a server-side salt before storage, and only the hash is kept — it is used to estimate unique visits and to rate-limit abuse. Automated bot requests are redirected so the scan still works, but they are not counted as scans.
We never collect the content of a scanned code beyond the destination it points to, never fingerprint devices, and never combine scan data with data from other services to identify an individual scanner.
3. Cookies
We use a session cookie to keep you signed in (database session, NextAuth). We do not set advertising cookies ourselves.
If advertising is enabled on this site, Google AdSense and its partners may set cookies — including the DoubleClick cookie — to serve ads, limit how often you see the same ad, and, where you have consented, to show ads based on your interests. You can opt out of personalised advertising at any time at Google Ads Settings or at aboutads.info/choices. The cookie banner on this site lets you dismiss the notice; your choice is stored in your browser only.
Third-party vendors, including Google, may use cookies to serve ads based on a user’s prior visits to this or other websites. Google’s use of advertising cookies enables it and its partners to serve ads to users based on their visit to this site and/or other sites on the Internet. You may opt out of personalised advertising by visiting Google Ads Settings.
4. How long we keep data
- Scan events: up to 365 days, then deleted automatically by a scheduled cleanup job.
- Dynamic codes and presets: until you deactivate, delete, or delete your account.
- Uploaded restaurant menu PDFs: up to 90 days, then deleted.
- Sign-in emails and security logs: only as long as needed for account security.
5. Your rights: export and deletion
While signed in, you can download all of your data (your dynamic codes, their scans, and your presets as JSON) from My Codes or via GET /api/account/export, and you can delete your entire account — codes, scans, presets, sessions, and your user record — via DELETE /api/account (the My Codes page asks you to confirm twice first; deletion cannot be undone). If you cannot sign in, email us at support@myqrfree.com from the email address on the account and we will verify and process the request.
6. Who we share data with
We do not sell personal data. Data is processed only by the services needed to run the site: our hosting provider (Vercel), our database provider (Postgres — Neon or Supabase), our email provider for magic-link sign-in, and, when ads are enabled, Google AdSense. Each processes data only to provide its service. We disclose data to authorities only where legally required.
7. Children
This service is not directed at children under 13, and we do not knowingly collect personal data from them. Accounts are for users aged 13 or older (or the age of digital consent in your country).
8. Changes to this policy
If we change what we collect or how long we keep it, we will update the date at the top of this page and, for material changes, note it on the home page. Continued use of the site after a change means you accept the updated policy.
9. Contact
Questions about this policy, or a deletion request: support@myqrfree.com — see also our contact page.