PRIVACY & DATA
Privacy Policy
What stays on your device, when a network request happens, and what you can control.
1. QR processing
The extension reads the image you choose, or the current page URL or selected text when you create a QR code. Images chosen, dropped or pasted into the popup or web demo are processed locally. The installed extension includes its QR libraries; the website loads its libraries as described below.
Results appear in the page, popup or a system notification. Easy QR does not create a scan-history database or send QR contents to the developer. Closing a result hides it; this is not a guarantee of immediate erasure from browser memory, caches or operating-system notification history.
2. When network requests happen
Reading an image from a website
Scanning a web image may download it again from its original host. The browser may include that host’s existing cookies or credentials, subject to browser rules, so protected images can load. The host receives a normal image request, including connection information such as your IP address. Easy QR does not upload the image to a separate QR-scanning service.
Opening a decoded link
If you choose Open, or click a result notification containing a link, your browser visits that address. The destination website’s privacy practices apply. Easy QR does not visit decoded links automatically just to scan them.
Loading this website
The website is hosted on Vercel. Its interactive demo downloads QR-processing code and WebAssembly files from jsDelivr, including preloading the reader after the page opens. These providers receive ordinary web requests and may process information such as IP address, browser information and requested files under their own policies. QR images and decoded contents are not included in those library-download requests.
Service providers’ privacy information:
3. Storage and your choices
Temporary notification links
The extension stores the destination URL for a clickable result notification in Chrome’s storage.session. It removes that entry when the notification is clicked or closed. Chrome also clears this in-memory storage when the extension is disabled, reloaded or updated, or the browser restarts. It is not synced to your Google account. The extension does not write scan history to storage.local or storage.sync.
Website language preference
The website reads your browser’s preferred languages. When you choose a language, it saves only the language code (en, ko or ja) under easy-qr-language in localStorage. This remains until you change it or clear this website’s site data. Language-specific links may also include a lang URL parameter. Easy QR adds no analytics scripts or tracking cookies to the website.
Files, clipboard and notifications
PNG files are saved only when you request a download. Copy writes the chosen result or image to your system clipboard. Saved files, clipboard history or synchronization, browser caches and notification history follow your browser and device settings. Removing the extension does not delete files you downloaded or clipboard entries; you can manage those on your device.
4. Why the extension needs permissions
Permissions support the QR features you invoke. Easy QR does not continuously record your browsing history or keystrokes.
On the Easy QR website and local development preview addresses, a small content script marks the installed extension’s version in the page. This lets the demo use Chrome’s native menu when the extension is installed. The marker itself makes no network request.
5. Analytics and data use
Easy QR includes no advertising or in-extension analytics SDK. The developer does not receive automatic reports of your scans, QR contents or browsing history. Information accessed for QR features is used to read, generate and display QR results, not for sale, advertising or profiling.
Separately, the Chrome Web Store provides the developer with aggregate store statistics such as installations and user counts. These are store-provided statistics, not QR feature-use reports sent by the extension. Google handles its store data under its own privacy policy.
6. Contact and support emails
If you email the developer, your email address, message and any attachments you choose to send are received in the support mailbox and used to respond to your request. This correspondence is separate from normal QR processing. The mailbox uses Gmail, so Google also processes the email to provide that service.
For privacy questions or to request deletion of support correspondence, contact:
dodolist3@gmail.com7. Changes to this policy
Updates to this policy will appear on this page with a revised date. Changes to how Easy QR handles data will be described here. Chrome’s permission prompts depend on permission changes; they do not necessarily appear for every privacy-policy update.