ZEROQR

Welcome to the ZEROQR security protocol definition. We believe in absolute user autonomy, data sovereignty, and simplicity. This policy explains our data processing rules in plain, transparent terms.

1. Philosophy of Zero

Our baseline is simple: zero friction, zero signup, zero tracking. We do not require you to create an account, register an email address, or provide any personal details to generate QR codes.

2. 100% Client-Side QR Processing

All QR code compilation processes execute entirely in your local browser instance. When you input a URL or text into the Input Stream:

• The data is processed in-memory using Alpine.js.
• The QR symbol is drawn mathematically by the qrcode npm module.
• No input payload is transmitted to external servers or remote endpoints for QR compilation.

3. Device-Bound Session Cache

We use browser local storage (localStorage) to store your Session History. This history is saved strictly to your device's storage for your convenience, allowing you to reload previous inputs. You can wipe this cached archive from your device at any moment by clicking the [ WIPE ARCHIVE ] button in the history panel. We have no remote access to this cache.

4. Telemetry and Third-Party Sub-Nodes

To maintain standard operations, we utilize the following third-party integrations:

• Umami Analytics: We load a cookie-free, privacy-focused instance of Umami hosted at umami.viardant.com to track global traffic metrics (like total pages viewed). No personal information, unique hardware profiles, or user IP addresses are permanently archived.
• StaticForms: If you choose to transmit user review or feedback logs using the Feedback panel, the feedback rating, message, and form metadata are processed via StaticForms (https://api.staticforms.dev) for delivery to our team.

5. Inquiries and Contacts

For queries regarding ZeroQR protocols, code audits, or system behavior, please contact the developer node (Daniele).