Privacy Policy
How QR64Code handles tool inputs, cookies, analytics, and advertising technology.
This policy was updated on September 1, 2026. QR64Code processes tool inputs on your device whenever possible. This does not mean that no usage data or advertising technology is ever processed.
Tool inputs
QR, Base64, JSON, URL, timestamp, hash, UUID, image conversion, QR reading, and metadata-cleaning inputs are processed on-device in supported browsers. QR64Code does not upload those texts or selected files to its own servers. Browser compatibility and third-party extensions depend on the user's environment.
Server logs
Hosting and security providers may process standard access logs including IP address, user-agent, request time, requested URL, and error details for a limited period. These records support security, debugging, and service continuity.
Analytics
Analytics is enabled only when configured and after required permission. It may process page views, device class, approximate region, and interaction events. Tool field contents must not be included in analytics events.
Google advertising
When Google AdSense is enabled, Google and its partners may use cookies, web beacons, IP addresses, and other identifiers for ad delivery, frequency control, measurement, and fraud prevention. A link to Google's explanation is provided below.
Consent management
Advertising consent in the EEA, UK, and Switzerland is managed through Google-certified CMP messages integrated with the IAB TCF. QR64Code's local privacy preference controls analytics tags; Google advertising tags follow CMP signals when serving ads in covered regions.
Rights and contact
Depending on applicable law, you may have access, correction, or deletion rights. Contact QR64Code through Cryxone Technology's contact channel. Identity and scope verification may be required to evaluate a request.