Privacy Policy

Last updated: October 2026

This is a straightforward privacy policy because there's not much to say. We don't want your data.

QR code generation

All QR codes are generated entirely in your browser using client-side JavaScript. The text, URLs, or data you enter are never sent to any server. We couldn't see what you're encoding even if we wanted to.

The optional API is the one exception. A request to /api/generate carries the text you put in its URL to a Cloudflare server, which builds the image and does not store the text. Cloudflare, which hosts the site, may keep its own request logs. The web generator never calls the API.

Cookies

qrmake.dev does not set any cookies. If you access the site through Cloudflare's network, Cloudflare may set essential security cookies—this is standard for any site behind their CDN and is not something we control.

Local storage

The site uses your browser's localStorage to save your QR code history and preferences. This data lives only on your device and is never transmitted anywhere. You can clear it at any time through your browser settings.

Analytics

We use Umami, a privacy-friendly, open-source analytics tool. Umami does not use cookies and does not collect personal data. It tells us things like how many people visited the site and which pages are popular. It does not track individual users or build profiles.

We also count download starts by file format and successful share-link copies in the main generator. These action counts do not include your QR content, share-link contents, history, or settings. Download starts do not tell us whether a file was saved to disk.

Personal data

We do not collect, store, or process any personal data. There are no accounts, no email forms, no contact databases.

Third-party trackers

There are none. No Google Analytics, no Facebook pixels, no advertising networks, no tracking scripts of any kind beyond the privacy-respecting Umami instance mentioned above.

Changes to this policy

If this policy ever changes, it will be updated here with a new date. Given the nature of this site, meaningful changes are unlikely.

Contact

If you have questions about this policy, reach out via the channels listed on our About page.