Privacy

Privacy Policy

This page describes the intended data handling of the current Quick QR website.

Last updated: October 27, 2026

QR generation

QR codes are generated in your browser. The current generator is not designed to send the QR text, URL, email details, SMS text, or Wi-Fi credentials to a Quick QR application server.

History and browser storage

If “Save to History” is enabled, supported QR content may be saved in your browser's local storage so it can be shown again on the same browser and device. History is limited to a small number of recent items and is not synced to an account.

Wi-Fi QR payloads are excluded from the history feature because they may contain network passwords. Your browser may still retain data according to its own settings, extensions, or developer tools. Clearing site data may remove saved history and theme preferences.

Camera and image scanning

When you scan with the camera or upload an image, QR decoding is designed to happen in your browser. The site does not intentionally upload camera frames or the selected image for decoding. The decoded result is displayed to you and is not opened automatically.

The scanner may load the jsQR decoding library from a third-party content delivery network (jsDelivr). That provider may receive standard technical information associated with the browser's request for the library, such as your IP address and request metadata. The QR image and decoded result are not included in that library request by the scanner code.

External links and hosting

If you choose to open a link contained in a QR code, that destination's own privacy policy and practices apply. The website's hosting provider may also process routine server and security logs when you visit the site.

Children and sensitive information

Do not encode passwords, confidential data, or personal information in QR codes unless you understand the risks of sharing and storing that information. A QR code is not a secure container for a secret.

Changes and contact

This policy should be reviewed whenever analytics, advertising, forms, external services, or server-side features are added. A public contact method should be configured on the Contact page before launch.