Privacy Policy for QRSnip: QR Code & Barcode Scanner

Effective Date: July 27, 2026

1. Information We Collect

We do not collect, process, or transmit any personal data to external servers. QRSnip operates entirely locally on your device.

2. How the Extension Works

When you activate QRSnip to scan a code:

• The extension may take a screenshot of the currently visible tab, or use an image you drop or paste.
• The image is processed locally within your browser using Chrome’s BarcodeDetector API and an offline ZXing WebAssembly decoder bundled with the extension (no network calls).
• Supported formats include QR / Micro QR / rMQR, Data Matrix, Aztec, MaxiCode, PDF417 (and Micro/Compact), EAN/UPC, Code 39/93/128, Codabar, ITF, GS1 DataBar, Telepen, plus Italian Pharmacode (Code 32) and PZN.
• Not supported: DotCode, postal barcodes (POSTNET/USPS/IMB/Planet), Microsoft Tag / HCCB, and Laetus Pharmacode.
• Decoded text never leaves your computer and is never sent to any external server.

3. Local Scan History

Recent scan results (decoded text, format, and timestamp) may be saved in chrome.storage.local on your device so you can revisit them. This history:

• Stays only on your device
• Is never synced to our servers (we have none)
• Can be cleared at any time from the History panel

4. Permissions

QRSnip requests only the minimum permissions required:

• activeTab: Temporarily access the current tab when you click the icon, use the keyboard shortcut, or choose the context menu — so a screenshot can be captured for local scanning (including PDFs opened from the web).
• storage: Temporarily hold a screenshot during scanning and store optional local scan history.
• contextMenus: Adds a “Scan with QRSnip” option when you right-click an image.
• file:// access: Lets you scan codes in local PDF files and images opened from disk. You must also enable “Allow access to file URLs” on the extension’s details page in chrome://extensions.

QRSnip does not request broad <all_urls> host access or permission to read your browsing history.

5. Third-Party Services

We do not use any third-party analytics, tracking, or advertising services. There is no tracking code inside the extension. Decoding uses the browser’s native BarcodeDetector API and a locally bundled open-source ZXing WebAssembly module — neither contacts external servers.

6. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. If we make significant changes, we will update the “Effective Date” at the top of this policy.

7. Contact Us

If you have any questions about this Privacy Policy, please contact us at dev.iproger@gmail.com or via the Chrome Web Store support tab for the extension.