← Back to QR Studio

Private by design.

QR Studio's static QR generator is local-first and client-side. Static QR payloads and uploaded logos are processed in your browser. The optional Dynamic QR feature uses an isolated Supabase backend only to store redirect destinations, management metadata and aggregate scan counts.

What the app processes

Depending on the QR type, the browser may process URLs, plain text, Wi-Fi credentials, email content, phone numbers, contact details, coordinates and calendar-event details.

Saved history

Saved history is opt-in. When you choose Save locally, QR content and appearance settings are stored in this browser's local storage. Wi-Fi passwords are deliberately excluded from saved history, even when the current Wi-Fi QR contains a password.

Logos

Uploaded PNG, JPG and SVG files are processed locally. Before a logo is used, QR Studio rasterizes it to a local PNG representation. Logos are never uploaded to a QR service.

Clipboard and sharing

Copy and Share actions only run after you request them. Copying places QR data or an image on your device clipboard. Sharing hands the exported image to your operating system's share sheet and any app you select; those destinations have their own privacy practices.

Dynamic QR and network requests

The static generator does not use remote QR-generation APIs, advertising trackers or externally hosted fonts. Static application files are served by GitHub Pages. When you explicitly use Dynamic QR, the browser sends the destination and management request to QR Studio's isolated Supabase backend. Dynamic redirects also pass through that backend before sending the browser to the destination.

The Dynamic QR database stores total and daily aggregate scan counts. QR Studio does not persist raw IP addresses, user-agent strings, browser fingerprints or individual scan-event rows for Dynamic QR analytics. Network infrastructure may process ordinary request metadata as part of delivering the service.

The Dynamic QR management token is stored in this browser. An exported management backup contains that token and should be treated as sensitive.

Offline storage

The installable web app may cache its own static files so it can work offline. The service-worker cache contains application assets, not a server-side copy of your QR payloads.

Clearing local data

You can clear saved QR history from the History panel. Browser site-data controls can also remove preferences, history and cached application files.

Last updated: September 19, 2026.