Architecture and privacy
QR code privacy: Offline QR and Smart QR explained
A technical Fair-QR architecture overview: what stays local in Offline QR, which normal website data exists, and how Smart QR is processed separately.
Short answer
In the public Offline QR generator, the QR payload is produced in the browser and is not sent to a Fair-QR API for QR generation. An optional logo is processed locally as a data URL. On download, the QR configuration may be stored in local browser history. A normal website visit still creates technical connection and analytics metadata. Smart QR is a separate, server-managed product.
The essential separation
- Offline QR: the final payload is embedded directly in the QR code.
- Offline QR: no account or server-side QR generator is required.
- Smart QR: the code contains a managed Fair-QR short link.
- Smart QR: destination, routing, and analytics require server storage.
- Visiting a website is not the same as a completely network-free application.
Data flow compared directly
| Question | Offline QR | Smart QR |
|---|---|---|
| What is in the code? | Final URL, text, WiFi, or contact payload | Managed Fair-QR short link |
| Where is it generated? | In the user's browser | Code and destination are managed in the dashboard |
| Account required? | No | Yes |
| Editable later? | No; create a new code | Yes; the printed code remains unchanged |
| Scan analytics? | No Fair-QR scan analytics | Yes, according to configuration and plan |
What technically happens in the Offline generator
- Inputs update local React state in the browser.
- The QR graphic is rendered client-side from that payload.
- Logo files are checked in the browser and converted to a local data URL.
- PNG, JPEG, and SVG downloads are produced from the rendered browser element.
- On download, a local history entry may be saved in the current browser profile's Local Storage.
- Analytics events describe actions such as export format or logo file type; the QR payload is not used as an event property.
“Offline QR” describes local QR generation and the directly embedded payload. The website and its assets still need to load on the initial visit.
Data that can still exist during local generation
When any website is requested, hosting and security systems receive technically necessary connection data such as IP address, time, requested URL, and browser information. Fair-QR also uses data-minimised website and product analytics to understand errors and usage patterns. This metadata is separate from the QR payload itself.
Users can remove local QR history inside Fair-QR or by clearing browser data. A downloaded static QR code then works independently of a Fair-QR account as long as its embedded content remains valid.
Why Smart QR requires server-side processing
Smart QR is designed to change a destination after printing. The code therefore contains a managed short link instead of the final payload. On scan, Fair-QR must resolve that link, apply routing rules, and—when enabled—record a minimised scan event.
This architecture is functionally necessary but intentionally separate from the public Offline generator. Smart QR requirements must not change the local generation behavior of the free Offline flow.
How the claim can be checked
- Open browser network tools and watch requests while editing QR content.
- Confirm that no QR payload is sent to a QR-generation endpoint.
- Compare Local Storage before and after a download.
- Test Offline QR and Smart QR separately because their data flows intentionally differ.
- Read the current privacy policy for hosting, analytics, and retention details.
Documentation and basis
This page documents the Fair-QR implementation; the current privacy policy remains legally authoritative.
Related resources
Print guide
How to print QR codes: size, contrast, and quiet zone
A technical QR code print guide covering the quiet zone, module size, error correction, logo rules, and a verifiable preflight checklist.
Open technical resourceTest methodology
QR code scan testing: a reproducible test method
A reproducible QR scan protocol for devices, distances, lighting, surfaces, logos, and success rates without invented benchmark results.
Open technical resourceCreate a QR code locally in your browser
For fixed content, the public generator produces the payload directly on your device.