Privacy Policy

Static QR Codes

When you generate a static QR code, all processing happens entirely in your web browser. The content you enter — URLs, text, WiFi passwords, contact info — is never sent to or stored on our servers. We never see it. This is a technical architecture choice, not just a policy promise. You can verify this by reading our source code or by using the tool with your internet connection disabled.

Dynamic QR Codes

If you create a dynamic QR code (one where you can change the destination after printing), we store the following:

• The destination URL
• A bcrypt hash of your passphrase (not the passphrase itself)
• An optional label you provide
• A scan counter (a simple number — nothing about who scanned it)

We do not store: your actual passphrase, any personally identifiable information, IP addresses of people who scan your codes, geolocation data, or device information.

Analytics

We use Cloudflare Web Analytics, which is privacy-respecting: no cookies, no personal data collection, no tracking individual users. We do not use Google Analytics, tracking pixels, or any other third-party analytics scripts.

Cookies

We don't use cookies. Period.

Third Parties

We use Cloudflare for hosting, CDN, and dynamic QR code redirects. Cloudflare's privacy policy applies to infrastructure-level data they process. We don't use any other third-party services.

Data Retention

Dynamic QR code data is retained until you deactivate it using your passphrase. We don't collect your email or any contact information, so we have no way to reach out to you about your data.

Open Source

You can verify every claim on this page by reading our source code on GitHub.

Changes

If we change this policy, the change will be visible in our Git history.

Contact

Questions or concerns? Open an issue on GitHub.