Plain-language privacy
Your QR content stays on your device
QR generation, scanning, checking and campaign preparation happen locally in your browser. We do not receive or store the content you enter into those tools.
Information processed only in your browser
This includes destination URLs, Wi-Fi names and passwords, contact details, phone numbers, addresses, messages, event details, campaign values, uploaded QR images, camera frames and decoded QR contents. These are not intentionally transmitted to our application server, an analytics service, an AI service or a third-party QR API.
No accounts or payload history
The site has no user accounts or database. It does not save a history of the QR codes you create or scan, and it does not store payloads in local browser storage by default.
What the web server receives
Like other websites, the hosting and network services necessarily receive request information needed to deliver a page, such as an IP address, date and time, requested path, browser headers and security-related logs. Tool contents are not included in those requests by the application.
Analytics, advertising and cookies
The site currently has no application analytics, advertising, tracking pixels or consent-dependent marketing cookies. Search Console may be used after launch to understand search visibility; it does not receive QR payloads from the tools. Any future analytics or advertising change must preserve the rule that generated and decoded content is never captured.
Camera and uploaded images
Camera access requires browser permission and a secure context. Frames remain local and are not recorded or uploaded. Selected raster images are decoded in the browser, temporary preview resources are released when no longer needed, and SVG uploads are rejected.
Changes and questions
Material changes to this privacy explanation will be published on this page. For a privacy concern, use the contact route.