QR3776
How QR3776 handles user information.
1. Scanning
QR3776 uses the camera or a user-selected image to scan QR codes and barcodes. Recognition uses Google ML Kit Barcode Scanning and runs on-device. Lab 3776 does not send camera images, selected images, or decoded scan contents to a Lab 3776 server.
Google's ML Kit disclosure states that the SDK may collect device/app information, per-installation identifiers, performance and API metrics, feature/event information, and error codes for diagnostics and usage analytics. Google states that this data is encrypted in transit and is not shared by ML Kit with third parties.
2. Local history
Normal scan results are stored in an on-device database for the History feature and can be deleted in the app. The database is excluded from Android cloud backup and device-to-device transfer.
Supported TOTP/HOTP authentication QR codes and valid Wi-Fi connection QR codes are not saved to history by default. If the user enables the sensitive-QR history setting, their QR contents (which may include authentication secrets or Wi-Fi passwords) are encrypted with AES-GCM using an Android Keystore-protected key and stored in the on-device history database. The History screen shows limited metadata instead of the raw sensitive QR contents.
When sensitive-history saving is disabled, a QR is unsupported or invalid, or encryption or saving fails, sensitive QR contents are handled temporarily rather than saved in plaintext history. Stored Wi-Fi QR contents are decrypted for user-selected actions such as connecting, copying, or sharing. Legacy plaintext authentication and Wi-Fi QR history entries are removed during database migration. The history database is excluded from Android cloud backup and device-to-device transfer.
3. Settings and external actions
Theme, language, behavior settings, and a local Supporter Badge ownership cache are stored on-device. These settings do not contain authentication secrets or Wi-Fi passwords. Preference data may participate in Android backup or device transfer.
When the user explicitly chooses an action, a scanned value may be passed to a browser, share target, authenticator app, or Android Wi-Fi functionality. The receiving app or service then controls further handling.
4. Google Play Billing
QR3776 offers an optional one-time Supporter Badge through Google Play Billing. Google Play handles payment processing. QR3776 receives product and purchase-state information but does not access or store credit-card or bank-account details.
5. Advertising
The current QR3776 source does not include an advertising SDK. Some earlier versions used Google AdMob and may still be subject to AdMob data processing.
6. Contact
Developer: Lab 3776
Email: lab3776.tokyo@gmail.com