Information you provide
Text entered to generate a QR code or barcode is processed on your device for the purpose of creating the code. QRKit does not require an account to use the core create and scan features.
History for scanned links and links you choose to copy, share, or download from the create screen is stored locally on your device so you can revisit recent results. You can delete individual items or clear all history from inside the app.
QRKit does not upload or collect this local history list as part of the history feature itself.
Device permissions
Camera permission is used only to scan QR codes and barcodes. Photo or media library permission is used only when you choose to save a generated code image.
Permission behavior may differ by platform, but QRKit requests access only for features you initiate.
Ads, analytics, and diagnostics
QRKit Tools may use Google AdMob, HilltopAds, Google Analytics, Firebase Analytics, Crashlytics, Ahrefs Web Analytics, or performance diagnostics to show ads, understand feature usage, detect crashes, and improve reliability.
These services may collect device identifiers, app interaction events, crash logs, approximate location inferred from network data, and other information described in their own policies.
What analytics events never contain
Analytics events record which feature was used and whether it succeeded — for example that a Wi-Fi QR code was downloaded as a PNG.
They never contain the content you encode: no QR or barcode payload, no Wi-Fi network name or password, no text, URL, email address or phone number you enter, and no logo or image you upload. This is enforced in code by an allow-list of event properties, so no analytics call can carry your content even by accident.
Campaign attribution (UTM)
If you arrive through a link containing utm_source, utm_medium, utm_campaign, utm_content or utm_term parameters, those five values are kept in your browser session storage so we can tell which campaign brought you in.
They are stored on your device only, are discarded when you close the tab, and contain no personal information. No other query parameters are read or stored, and no cookie is set for this purpose.
Offline support
The website registers a service worker that caches the interface so it can load without a connection. It caches only application files, never QR content, API responses or anything you generate.
Third-party links
When a scanned code contains a link and you choose to open it, the destination website is controlled by a third party. Review that website policy before sharing personal information.
Contact
For privacy questions, use the contact page or the developer contact options shown on the Google Play listing for com.tvttechnology.scanly.