QR Snap privacy policy

Last updated: 17 September 2026

QR Snap ("the extension") decodes QR codes that are visible in your browser. It collects nothing and transmits nothing.

What the extension collects

Nothing. The extension has no server, no account and no analytics. No data is sent anywhere, to us or to any third party. We do not sell or share user data.

What happens locally

• When you start a scan or a snip, the extension takes a screenshot of the visible area of the current tab, decodes it in your browser's memory and then discards the image. The screenshot is never written to disk and never uploaded.
• If the local history option is on (it is on by default), the decoded text, the page title and the page URL of the last 50 codes are stored on your computer using Chrome's local extension storage. This never leaves your machine and is not synced between devices.
• You can switch the history off in the extension settings, clear it with one click in the popup, or remove everything by uninstalling the extension.

Permissions

The extension requests activeTab, scripting, contextMenus, storage and clipboardWrite. They are used only to capture the current tab when you ask for a scan, to draw the selection rectangle and the result panel in the page, to provide the right-click menu entries, to store your settings and optional history locally, and to copy a decoded value to your clipboard.

The extension requests no host permissions and loads no remote code. The QR decoding library (jsQR, Apache-2.0) is bundled inside the extension package.

Children

The extension is not directed at children and collects no data from anyone, regardless of age.

Changes

If this policy changes, the updated version is published on this page with a new "last updated" date, and the change is recorded in the project's changelog.

Contact

Questions or concerns: open an issue on GitHub.