PRIVACY

Your code stays on your screen.

ScreenCode is deliberately built so the sensitive part of the job happens on your device, not ours.

THE SHORT VERSION

Does ScreenCode upload images or decoded QR data?

No. Screenshots and photos are decoded inside your browser. Generated QR codes are also created and exported there. ScreenCode does not upload those images, decoded values, contact details, Wi-Fi credentials, authenticator secrets, or generated files to a server.

Browser extensions

The ScreenCode extensions for Chrome, Edge, Firefox, and Safari run only after you choose Select a QR code. ScreenCode temporarily freezes the visible area of the active tab in extension memory before showing the selection tool, displays that frozen image in a private closed interface, crops it to the rectangle you selected, and reads that crop locally on your device. This keeps the result tied to the pixels you saw even if a page changes afterward. The visible-tab capture, crop, decoded values, and payload classifications are not uploaded, transmitted to ScreenCode or a third party, logged, or saved.

The background copy of the full visible-tab capture is deleted as soon as the review screen retrieves it, or within 60 seconds if the scan is abandoned. The reader clears the full image after making the crop and clears the crop after decoding. The extension does not use analytics, remote decoding, remote code, or persistent storage. It never performs a decoded action without your explicit approval.

Embedded demonstration video

The browser extensions page includes a YouTube video using YouTube's privacy-enhanced embed. Loading or playing the video may send your IP address, browser details, and interaction information to YouTube or Google under their own privacy terms. No QR code, screenshot, or decoded value is included in that request.

Scan history

Scan history is off by default. If you turn it on, eligible decoded values are stored only in that browser's local storage. Images are never saved. Authenticator setup values and Wi-Fi credentials are excluded from history even when the feature is enabled.

Creation history

Creation history is also off by default and saved only on the device. It stores a reusable setup after export. Uploaded logos and Wi-Fi passwords are deliberately excluded from saved creation history.

Accounts and limited site analytics

ScreenCode requires no account. We use Google Analytics 4 for limited, on-site measurement of page views, sessions, traffic sources, broad device categories, and scroll activity. We do not enable Google Signals, advertising personalization, User-ID, cross-site advertising tracking, outbound-click tracking, form tracking, site-search tracking, file-download tracking, or video tracking.

ScreenCode does not send Google Analytics any uploaded image, decoded QR or barcode value, opened destination, contact detail, Wi-Fi credential, authenticator secret, or generated file. Basic hosting infrastructure may still process ordinary connection data needed to deliver the site, such as an IP address and browser request headers.

Opening external links

ScreenCode shows a decoded destination before opening it and flags several common warning signs. Once you choose to visit another website, call a number, open a payment app, or use another external service, that destination controls its own data practices. ScreenCode cannot make the rest of the internet behave itself.

Offline use

After the web app has been installed and cached, supported scanning and generation features can continue to run offline. Link destinations and other external actions still require the relevant network or app.

Chrome Web Store Limited Use

ScreenCode's use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Last updated September 2, 2026. ScreenCode is a SquarePi LLC product.