QR & Barcode Scanner Launcher Privacy Policy

QR & Barcode Scanner Launcher is designed so that many core functions work locally on your device. This policy describes the information handled by the current app version, which includes scanning, generating, history, launcher, widget, advertising, attribution, remote configuration, analytics, and diagnostics-related features.

1. Information We Handle

Depending on the feature you use, the app may handle the following categories of information:

  • Camera input used to scan QR codes and barcodes.
  • Text, links, contact details, calendar details, Wi-Fi details, phone numbers, email addresses, and other code content that you scan, generate, copy, save, or share.
  • Images you choose from your device photo picker when you ask the app to scan a code from a picture.
  • Local history records containing scan or generation results, format information, and timestamps.
  • Widget-related data that you choose to pin to the home screen, such as code content and display text.
  • Launcher layout and installed-app display information needed to provide home screen, app drawer, search, widget hosting, or uninstall-request functionality.
  • Advertising and consent-related information such as ad request context, ad interaction or load/show status, consent state, and whether privacy options are required under supported consent flows.
  • Installation attribution and campaign-related information such as Google Play install referrer values, campaign parameters, and channel classification used to distinguish paid, organic, or unknown acquisition sources.
  • Device and app metadata used for configuration, reporting, and diagnostics, such as package name, app version, Android version, brand, and an installation-scoped identifier used for automatic login/reporting flows.
  • Network-derived information such as IP address, country, city, or region when available, used for metadata, analytics/reporting support, or attribution-related context in the current version.
  • Analytics, diagnostics, and crash-related information about page views, button interactions, ad events, app state, and error conditions.

2. How the Information Is Used

The app uses this information only to provide the features you trigger, such as scanning a code, generating a new code image, displaying a result, saving a result to local history, opening a corresponding external app, pinning a widget, or rendering the launcher interface and app list.

The app may also analyze saved history locally on your device to generate summary cards, category counts, and usage insights shown as an AI summary feature inside the app.

In version 1.0.1, the app may also use information to request and display ads, manage consent status, control runtime behavior through remote configuration, measure page and element events, report ad load or show outcomes, associate installation source information with app activity, perform automatic login/reporting with an installation-scoped identifier, and record crash or stability diagnostics.

3. What Stays on Your Device

Scan history and widget-related content are stored locally on your device. Generated or captured code images are also handled on device, and if you choose to save an image to your photo library, the image is written to your device storage through Android media APIs.

However, the current version also includes network-connected components. These include advertising, consent, configuration, attribution, analytics, diagnostics, IP information lookup, and developer-operated reporting or login interfaces. As a result, not all operational data stays only on your device.

4. Camera and Photo Access

The app requests camera access so it can scan QR codes and barcodes in real time. If you choose to scan from an existing image, the app uses the Android photo picker to let you select an image. The app processes the selected image to detect readable codes and show you the result.

5. Launcher and Installed App Information

If you use the launcher capabilities, the app may access installed-app information so it can show apps on the home screen or in the app drawer, support app search, display labels and icons, and allow launcher actions such as opening app info or starting an uninstall request. This is the purpose of the installed package visibility access used by the launcher module.

6. Advertising, Consent, and Remote Configuration

The current version may use Google AdMob to load and display app open, interstitial, and native ads. It may also use Google User Messaging Platform (UMP) to request or manage consent before ad requests where applicable.

The app may use Firebase Remote Config to download configuration values that influence certain runtime behavior, including ad-related switches or timing logic. The app may fall back to bundled local configuration when remote values are unavailable.

If Meta/Facebook SDK components are configured for the build, the app may also send supported ad revenue or app event information to Meta/Facebook services according to the current implementation.

7. Attribution, Login, and Reporting Interfaces

The app may use the Google Play Install Referrer service to understand whether the install came from paid, organic, or unknown sources and to capture available campaign parameters or raw referrer data for attribution processing.

The app may also contact developer-operated interfaces to perform automatic login or registration using an installation-scoped identifier and to upload batched analytics or operational report data. These requests may include metadata such as package name, app version, Android version, brand, channel information, country, city, and IP address when available.

8. Analytics and Crash Diagnostics

The current version may use Firebase Analytics to record page events, button interactions, ad-related events, and similar usage telemetry. It may also use Firebase Crashlytics to record crash information and handled exception details for stability monitoring.

Official references for some third-party services used in the current version include:

9. Widgets and Home Screen Hosting

If you add widgets, pin shortcuts, or use QR & Barcode Scanner Launcher as the default home app, Android may allow the app to host or request home screen widgets. The app uses this information only to render the widgets or shortcuts you choose to place.

10. External Actions You Choose

When you tap actions such as open website, call number, send SMS, draft email, open map, insert contact, insert calendar event, open Wi-Fi settings, share text, or save an image, the app sends the relevant content to Android or another app selected by the system. Those other apps then process the information under their own privacy policies.

11. Permissions and Why They Are Used

  • CAMERA: used for live code scanning.
  • INTERNET and ACCESS_NETWORK_STATE: used for ads, consent flows, remote configuration, attribution, analytics, diagnostics, and developer-operated network requests.
  • AD_ID and supported Android advertising services permissions: used by advertising or attribution-related integrations where supported by the device and current build.
  • QUERY_ALL_PACKAGES: used by the launcher features to display installed apps, app search results, icons, labels, and launcher actions.
  • BIND_APPWIDGET: used for launcher and widget hosting behavior where supported by Android.
  • REQUEST_DELETE_PACKAGES: used to start uninstall requests from launcher actions when you choose them.
  • EXPAND_STATUS_BAR: used for launcher-related system UI interactions on supported devices.

12. Sharing and Disclosure

We do not describe the app as a cloud storage product for your scan history or generated code content. However, the current version may send limited operational, attribution, analytics, ad-related, consent-related, crash, or login/reporting data to third-party or developer-operated services that support the app's runtime behavior. Information may be shared when:

  • you intentionally send content to another app or system component;
  • Android or your device manufacturer processes widget, launcher, photo, or intent-based actions;
  • advertising, consent, attribution, analytics, crash, configuration, or reporting services process supported event or metadata payloads;
  • disclosure is required by applicable law or a lawful request.

13. Data Retention and Control

Because the app stores key usage content locally, you can control much of that data directly on your device. For example, you can clear history from inside the app, remove pinned widgets, delete saved images from your photo library, or uninstall the app.

Operational data sent to third-party or developer-operated services may be retained according to those services' own retention or logging practices and the current app implementation.

14. Children

The app is not intentionally directed to children under 13. This policy does not state that the current version is built as a child-directed service.

15. Security

We use the protections available through the Android platform and local app storage patterns, together with the third-party services and network interfaces used by the current version, but no device, network, or software environment can be guaranteed to be completely secure. You are responsible for protecting access to your own device.

16. Changes to This Policy

We may update this Privacy Policy when features, permissions, integrations, or legal requirements change. The updated version will be posted in the app with a new effective date.

17. Contact

If you have questions about this Privacy Policy or the app's data handling, you can contact the developer at sonysonyaa40@gmail.com.

This document is written to match the current merged feature set of QR & Barcode Scanner Launcher on July 24, 2026. It should be reviewed again before adding advertising SDKs, analytics services, cloud sync, account systems, or remote APIs.