Privacy

What stays on your device

QR payloads, destinations, contact details, Wi-Fi credentials, labels, project names, asset history, receipts and style settings are generated and stored in your browser. They are not uploaded to us by the core local-first QR workflow. Clearing your browser storage removes them permanently, so export a workspace backup if you want to keep them.

What we host

• Authentication: your email address and sign-in session.
• Profile: display name, account role, account timestamps and your optional Product & Evolution Brief preference.
• Entitlement: your product key, tier, access module, status and purchase timestamps, plus Stripe customer, session, payment and event identifiers used to verify the purchase.
• Operational telemetry: feature/event names, app routes, timestamps and compact technical or funnel metadata used to understand product health and purchase flow.

Operational telemetry is intentionally designed not to include the contents encoded inside customer QR payloads.

You can read only your own entitlement record through normal account access. Privileged product-operations views are restricted server-side.

Product & Evolution Brief preference

Product-update email preference defaults off. If you opt in, we store that preference and its timestamp so QRForge can distinguish customers who requested product/evolution updates from those who did not. You can opt out from the account page without changing a valid Founder entitlement.

Payments

Stripe processes all payments and card data. We never see or store card numbers. We store only the Stripe identifiers needed to confirm purchases, restore access, process entitlement state such as a full refund, and measure the purchase funnel.

Deletion

To delete your hosted account and entitlement record, contact DV Labs from your sign-in email. Deleting the account ends Founder access. Local QR assets remain governed by the browser storage on your device until you clear that storage.