Privacy policy
Publisher: Harvey Steele. Effective 10 November 2026. Questions or data requests: Harveysteele@outlook.com.au.
Device-only use
Native device-only QR codes are generated on your device. Their names, URLs, and creation dates are saved in the app’s local library. They are not uploaded to QR Code Lab unless you create a cloud code. Exported QR images contain the encoded URL and are visible to anyone you share them with. Device or operating-system backups may include your local app data according to your device settings.
Optional cloud accounts
Cloud use sends QR names, destination URLs, Google Apps Script connection details, and sign-in requests to QR Code Lab’s Cloudflare service. The service stores account identifiers, encrypted Google connection credentials and authenticator secrets, passkey public keys, hashed recovery codes, hashed session/device tokens, QR destinations, and delivery state. A native remembered session is stored in the device’s Keychain; sign-out revokes that app session.
The native passkey option opens a system authentication window at QR Code Lab. Short-lived, single-use codes and PKCE link that sign-in to the app. Biometric templates and device passcodes remain under the operating system’s control and are not received by QR Code Lab.
QR scans and retention
A cloud tracking link records its QR identity and scan timestamp. The service delivers the QR name, Melbourne date/time, and an event identifier to your connected Google Sheet. The website displays the latest 100 scan rows and validated daily activity for the previous 30-day window. Worker activity events are retained for 45 days. Pending deliveries are retried for up to seven days. Google rows remain in your spreadsheet until you remove them there.
The QR scan feature does not add visitor IP addresses, advertising identifiers, or device fingerprints to its scan records. Network providers, including Cloudflare and Google, necessarily process connection information such as IP addresses to deliver and protect their services. The authentication service uses keyed hashes of network addresses for short-lived rate limiting. Service logs may include bounded error metadata and nonsecret event identifiers.
Service providers and use of data
Cloudflare hosts the cloud API and database. Google processes data in the spreadsheet and Apps Script account you connect. These providers process data under their applicable terms and policies and may process it outside your country. If you contact support by email, your message and contact details are processed to answer your request. This project includes no advertising SDK, analytics SDK, sale of personal data, or cross-app advertising tracking.
Your choices
You can use device-only creation without signing in, choose whether to keep a native session signed in, remove local codes, revoke sign-in methods, delete individual cloud QR codes, and delete your cloud account from the native app. Cloud account deletion removes associated QR Code Lab credentials, links, and retained activity but does not delete your external Google Sheet, already exported files, or device-only library. Provider-managed operational backups or security records may persist according to the provider’s retention practices.
You are responsible for the destinations and data you place in QR codes and your Google Sheet. Anyone scanning a QR can read its encoded link. For access, correction, or deletion questions, contact Harveysteele@outlook.com.au.