Privacy
Privacy policy
Last updated: October 5, 2026
What the QR tools process
QR Toolbox is designed so QR payload generation, local logo processing, camera scanning, and QR image decoding happen in your browser. The QR tools do not require an account or a server-side database.
Files, camera, and permissions
When you choose a local logo or QR image, your browser reads the selected file for processing on your device. The scanner can request camera permission when you start a camera scan. The QR Toolbox application does not provide a feature that uploads those selected files or camera frames to its own server.
Links you choose to open
A decoded QR result may contain a web address or another type of payload. The site only offers its one-click “Open link” action for HTTP and HTTPS URLs. You are responsible for deciding whether an external destination is trustworthy.
Hosting and technical data
Like most websites, the hosting and delivery infrastructure used to serve this site may process technical request information needed to deliver pages, protect the service, and maintain reliability. QR Toolbox does not use that infrastructure to store QR payloads or uploaded QR images as an application feature.
Analytics and cookies
QR Toolbox uses Google Analytics 4 to understand aggregate site usage, such as which pages and QR tools are used, how visitors navigate the site, and which QR actions are completed. Google Analytics may use cookies, device information, and other identifiers to provide measurement and reporting. QR Toolbox does not send the actual QR payload, Wi-Fi credentials, contact details, message text, or uploaded QR image contents to Google Analytics.
Where required by applicable law, consent choices will be presented before relevant analytics or advertising processing occurs. You can also control certain Google data and advertising settings through Google Ads Settings. More information about how Google handles information from sites and apps that use its services is available at Google’s Business Data Responsibility site.
Advertising and cookies
Google AdSense is not embedded in the current site build. Before advertising is enabled, this policy must be reviewed against the actual advertising configuration. If Google advertising is used, Google and participating third parties may use cookies, web beacons, IP addresses, or similar identifiers in connection with ad delivery, as described in Google’s publisher policies.
Where required by applicable law or Google policy, advertising consent choices will be presented before relevant processing occurs. Users can manage personalized advertising through Google Ads Settings. Google also provides information about how it uses information from sites and apps that use its services at Google’s Business Data Responsibility site.
When advertising is enabled, the site may publish an ads.txt file at the root of the domain to declare authorized advertising sellers. That seller-authorization file is separate from the site's privacy disclosures and any consent choices required for advertising.
Changes to this policy
This policy should be updated when the site adds advertising, analytics, forms, additional third-party services, or any other processing that changes what information visitors should know about.
This page is site policy copy, not individualized legal advice. The site owner should have the final text reviewed for the jurisdictions in which the site operates before monetization.