Privacy
Privacy Policy
How HonestQR handles account data, QR campaign data, scanner analytics, hosted files, payments, and exports.
Account data
We process account email, email verification status, session records, subscription status, support requests, invoices, receipts, and audit events so customers can use and manage the product.
QR campaign data
We store QR slugs, destinations, design settings, hosted-file metadata, static payloads, password-protection state, and export records needed to operate customer QR codes.
Scan analytics and anonymisation
Scanner privacy: anonymised IPs, city-level location, no cookies on redirects. Scan analytics can include timestamp, code id, country, city where available, device class, browser, operating system, referrer where available, and anonymised unique-scan buckets.
- Raw scanner IP addresses are not stored in product analytics.
- Location is stored at city granularity at most.
- Public redirect scans do not set cookies.
- Aggregate analytics are used for customer reports, abuse detection, reliability, and improving the service.
File hosting
Hosted QR codes can store uploaded files and metadata such as filename, MIME type, size, hash, storage key, status, and related QR code. Files may be scanned or blocked for safety, abuse, legal, or service-reliability reasons.
Processors and payments
Payment, email, hosting, analytics, security, and infrastructure providers process data only as needed to run HonestQR. Stripe handles card details; HonestQR stores Stripe ids, invoice links, receipt links, and subscription state.
Customer rights and exports
Customers can request an account export or close their account from the dashboard. The export is a downloadable ZIP containing account details, QR records, asset details, and static fallback SVGs.