Privacy Policy
QRMaker privacy policy — every code is generated and decoded on your device; nothing you type or upload reaches our servers.
Last updated: October 2026.
QRMaker handles sensitive inputs — Wi-Fi passwords, names, phone numbers — so it is built around one rule: the data stays in the tab. This page lists what is processed, what is transmitted, and what we never see.
Data that never leaves your device
Everything you type into the generator — URLs, SSIDs and passwords, contact details, message text, coordinates — is assembled into a payload and encoded by JavaScript running locally. The rendered image, the PNG/SVG downloads, and any logo you add never touch a network. The same holds for the scanner: an image you drop in is decoded by jsQR in the browser and forgotten when you close the page. There is no upload endpoint for any of it; you can verify that by loading the site, going offline, and continuing to use every feature.
Automatic data
- Hosting (Cloudflare): serving the pages involves ordinary request metadata — IP address, user agent, requested URL and time — for delivery and abuse protection. QR payloads, images and passwords are not attached to those requests.
- Advertising (Google AdSense): where ads run, the network may set or read cookies to count impressions and, where permitted, personalise them. Opt out via Google’s Ads Settings or your browser’s cookie controls; the generator is unaffected either way.
Storage
The tool writes nothing to cookies or localStorage. Your inputs live in the page’s memory only and are discarded on reload.
Google Analytics 4
We use Google Analytics 4 (GA4) to understand traffic, feature use and site performance. This root uses its own GA4 Measurement ID. Before GA is configured, Google Consent Mode sets analytics_storage, ad_storage, ad_user_data and ad_personalization to denied. We set ads_data_redaction to true, url_passthrough to false, and both allow_google_signals and allow_ad_personalization_signals to false. GA4 therefore sends cookieless measurement requests and may not read or write analytics or advertising cookies.
Our adapter supplies the page location as the origin and path only—never the query string or fragment—and reduces the referrer to its origin. Tool use is sent as a tool_action event with a normalized action_name.
Enhanced Measurement is currently enabled, so GA4 may also automatically measure page views, scrolls, outbound-link clicks, site searches, video interactions, file downloads and form interactions, together with relevant link, file or form metadata. Our integration does not send form values.
Google receives each measurement request, including the IP address in transit, and may derive a coarse location. It also receives browser, device, language and network metadata. Our custom adapter never sends tool inputs or content, uploads or photos, form values, a user ID, or values from local storage.
Google processes this information for us and may process it outside your country. See Google’s Privacy Policy. You can block Google Analytics requests in your browser or a content blocker; the core tools continue to work.
Contact
Privacy questions: hello@photopassport.online.