Privacy Policy
Last Updated:
This Privacy Policy describes how ScanQR
("we", "our", or "the App") handles information when you use our mobile application.
We are committed to protecting your privacy and ensuring transparency about our data practices.
Important: Scan history, codes you create, and settings are kept on your device.
The App opts out of Android's standard cloud backup and device-to-device transfer for that local data.
We do not operate user accounts, and we do not upload scan contents to our own servers.
If a code you create or scan contains an email address or phone number, that content stays on your device by default.
It is passed to another app or site only when you tap actions such as Send email, Call, SMS, Web search, Share, or Export.
The App uses Google Firebase Analytics and Crashlytics for usage and crash diagnostics; we do not intentionally put scan contents in those reports.
A product barcode or ISBN is sent to a catalog only when lookup is enabled or you refresh product information. See sections 1 and 4 for details.
1. Information Collection
ScanQR is a QR code and barcode scanner. It reads codes with the camera, from an image you pick, or from text you type, and it can create codes. It does not require you to register or sign in, and it does not operate a user account.
1.1 Analytics and Crash Reporting
ScanQR uses Firebase Analytics and Firebase Crashlytics, provided by Google, to understand app usage, diagnose technical issues, and improve app stability.
These services may collect information such as app interactions, app instance identifiers, device and app information, and crash or diagnostic data, depending on the service configuration and the data generated during app use.
Google processes data through Firebase in accordance with its applicable privacy terms and data-processing practices.
For more information, please review the
Firebase Privacy and Security documentation
and
Google's Privacy Policy.
We do not intentionally include scanned barcode contents, QR code contents, Wi-Fi passwords, one-time-password secrets, camera images, or contact details in analytics events or crash reports.
The App does not add custom analytics events or custom Crashlytics keys that contain that content.
Data collected by these services may be transmitted to and processed by Google to provide analytics and crash-reporting functionality.
The data handled by these services is separate from the scan history stored locally by ScanQR.
1.2 Product and ISBN Lookups
When automatic product lookup is turned on in Settings, or when you choose to look up a product or refresh its product information, ScanQR sends the relevant barcode number or ISBN to the selected third-party data provider to retrieve matching information.
Depending on the type of item, these providers may include Open Food Facts, Open Beauty Facts, Open Pet Food Facts, MusicBrainz, Cover Art Archive, and Open Library.
These requests are made only to provide the lookup feature.
ScanQR does not intentionally include your scan history, saved QR codes, email addresses, phone numbers, or unrelated personal information in these lookup requests.
The selected provider processes the request under its own privacy policy and data practices.
You can turn automatic lookup off in Settings.
1.3 Email addresses and phone numbers in codes
The App can create and read codes that contain an email address or phone number (for example email, phone, SMS, or contact QR codes).
That content is stored on your device when you save history. It is not uploaded to our own servers.
It is passed outside the App only if you choose an action that opens another app or site, such as Send email, Call, SMS, Web search, Share, or Export.
In those cases Android hands the content to the app or site you select; we do not receive a copy.
After that handoff, how the other app or site stores, forwards, or otherwise processes the content is governed by that party's own privacy policy and settings, not by ScanQR.
You can avoid this by not creating or scanning those code types, or by not tapping those actions.
1.4 Information We Do Not Collect on Our Own Servers
We do not collect on our own servers:
- Account identity such as a registration name, login email, or login phone number (the App has no accounts)
- Location data or GPS
- Scan history or barcode contents on our own servers, except the product barcode or ISBN sent for lookup as described in section 1.2
- Your full address book (creating a contact code may use the system contact picker for only the contact you choose; those details stay in the form on your device)
- Advertising profiles or personalized advertising based on scan contents
2. Data Storage
It helps to distinguish four kinds of data handling:
- Data kept inside the App: Scan history (when saving is on), codes you create, and settings stay in the App's private storage on your device. This history is not uploaded to our own servers. You can turn off saving, skip history for a scan, delete an item, or clear history.
- Files you export: If you export history (for example JSON or CSV) or save an image, the file is written where you choose. Those copies are under your control and are not removed automatically when you uninstall the App.
- Data you send through system share or open-with actions: If you tap Share, Export, Web search, Send email, Call, SMS, or open a link, Android passes the relevant content to the app or site you select. That party then handles the content under its own rules.
- Diagnostic data processed by Firebase: Usage and crash diagnostics described in section 1.1 are processed by Google Firebase separately from your on-device scan history.
- Wi-Fi and one-time passwords: A Wi-Fi password or one-time-password secret is stored only if you save that code. One-time-password screens block screenshots. A Wi-Fi password is passed to Android only when you choose to connect.
You can delete App-stored data by clearing history in the App, clearing the App's data in system settings, or uninstalling the App.
The App opts out of Android's standard cloud backup and device-to-device transfer for its local App data, so that data is not included in those standard Android backup flows.
This does not cover files you have already exported, content you actively shared, or tools outside Android's standard backup that a device maker may provide.
3. Permissions and Their Usage
The App requests certain permissions to provide its features. Here's how we use each permission:
| Permission |
Purpose |
Usage |
| CAMERA |
To scan QR codes and barcodes with the camera. Frames stay on the device. You can deny the camera and still scan an image you pick or type a code. |
Optional feature (runtime permission) |
| INTERNET |
For product lookups, online images, links you open, and Firebase Analytics / Crashlytics. Not used for an account or for ads. |
Declared for online features; no runtime prompt |
| CHANGE_WIFI_STATE |
To support Wi-Fi QR connection functionality where permitted by Android, only when you choose to connect. |
Feature-dependent |
| ACCESS_WIFI_STATE |
To check Wi-Fi state for supported connection functionality. |
Feature-dependent |
| VIBRATE |
A short vibration after a successful scan. You can turn vibration off in Settings. |
Optional |
Product lookup can be turned off in Settings. You can also choose not to open links.
Note on contacts, storage, and location:
The App does not request the contacts permission, a location permission, or broad storage access.
Creating a contact code can open the system contact picker. Android then allows the App to read only the contact you choose, and those details stay in the form on your device.
Gallery scanning uses the picture you select. Location codes use coordinates you type. The App does not read GPS.
Libraries included with the App, such as Firebase, may also declare network-state, wake-lock, and advertising-ID related permissions in the merged Android manifest.
ScanQR does not include an advertising SDK and does not use an advertising ID to show or personalize ads.
If Firebase Analytics accesses an advertising ID as part of its default measurement behavior, that use is limited to analytics described in section 1.1, not to advertising in this App.
Declare that behavior accurately in Google Play's Data safety form based on the final release build.
4. Third-Party Services
The App uses the following third-party services:
- ZXing and zxing-cpp: Open-source libraries used to read and create codes on your device.
- Firebase Analytics and Firebase Crashlytics (Google): Used as described in section 1.1 for usage measurement and crash diagnostics.
They are operated by Google, not on ScanQR's own servers.
See
Firebase Privacy and Security
and
Google's Privacy Policy.
- Product and ISBN catalogs: Used as described in section 1.2.
Depending on the item type and your selection, requests may go to Open Food Facts, Open Beauty Facts, Open Pet Food Facts, MusicBrainz, Cover Art Archive, or Open Library.
Each provider processes the barcode or ISBN under its own privacy policy.
We do not use:
- Advertising networks or ad SDKs to show ads in the App
- Location tracking services
- A user account or sign-in service
- Any service that uploads your email address, phone number, or full scan history to our own servers
Note on external apps and sites:
When you open another app or website from ScanQR, that destination's privacy policy and settings govern what happens next.
ScanQR cannot control how that third party stores, forwards, or otherwise processes the content you chose to send.
5. Children's Privacy
ScanQR is not directed to children and is not designed specifically to collect personal information from children.
The App does not require user registration or operate user accounts.
It uses Firebase Analytics and Crashlytics as described in section 1.1.
If you have concerns about a child's use of the App or believe that information has been handled inappropriately, please contact us using the details in section 9.
6. Data Security
We take data security seriously:
- Local Data: Scan history, created codes, and settings are stored in the App's private storage and protected by your device's own measures, such as a lock screen and device encryption.
- No Server Storage of Scans: We do not operate an account server for scan history.
- Backup opt-out: The App opts out of Android's standard cloud backup and device-to-device transfer for its local App data.
- Network: Product lookup and Firebase transmissions use HTTPS.
- Control: You can delete App-stored data by clearing history, clearing the App's data, or uninstalling the App. Exported or shared copies remain where you sent them.
7. Your Rights
You have the following rights regarding your data:
- Access: Scan history and created codes are stored on your device and can be viewed in the App.
- Deletion: See section 7.1 for how to delete data and how to request deletion.
- Control: You can choose which permissions to grant, turn off saving scans, and turn off automatic product lookup.
- Camera: You can revoke the camera permission and still scan a picture you pick or type a code.
7.1 Data deletion requests
This section explains how to delete data for the Android app listed on Google Play as
QR Code Scanner: Food Barcode
(also referred to in this policy as ScanQR / Barcode Scanner).
The App does not require registration and does not operate user accounts.
Steps to delete your data or request deletion
Do the following:
- Delete history in the App: Open the App → History → delete individual items or delete all history.
- Clear App data: On your Android device, open system Settings → Apps → QR Code Scanner: Food Barcode (or Barcode Scanner / ScanQR) → Storage → Clear data (or Clear storage). This removes local scan history, created codes, and settings stored by the App.
- Uninstall the App: Uninstalling the App removes its local private storage on that device.
- Email a deletion request (optional): If you need help, email
doesantalya@outlook.com
with the subject line QR Code Scanner: Food Barcode data deletion request.
Describe what you want deleted and, if relevant, approximate dates or the device you used.
We will respond and explain what we can delete.
What is deleted or retained
- Deleted when you clear App data or uninstall: Local scan history, codes you created that were saved in the App, and App settings on that device.
- Not automatically deleted by uninstalling: Files you previously exported (for example JSON/CSV or saved images) and content you shared with other apps or websites. Those remain where you saved or sent them; delete them yourself if needed.
- Product lookups: Barcode or ISBN numbers sent to third-party catalogs are processed by those providers under their own policies; ScanQR does not keep a copy of those lookups on its own servers.
- Firebase Analytics and Crashlytics: Diagnostic and usage data processed by Google Firebase is subject to Google's applicable retention and deletion practices.
Because ScanQR has no user accounts, that data may not be linked to a login you can manage in the App.
See Firebase privacy documentation.
- Retention: Local App data remains on your device until you delete it, clear App data, or uninstall. There is no separate ScanQR cloud account retention period for scan history.
8. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. We will notify you of any changes
by posting the new Privacy Policy on this page and updating the "Last Updated" date.
You are advised to review this Privacy Policy periodically for any changes.
Changes to this Privacy Policy are effective when they are posted on this page.
9. Contact Us
If you have any questions or concerns about this Privacy Policy or our data practices,
please contact us at:
10. How This Policy Applies
This Privacy Policy explains how ScanQR handles information when you use the App.
Where required by applicable law or platform requirements, we will provide appropriate notices and obtain any necessary permissions or consent for specific data-processing activities.
© ScanQR. All rights reserved.