Privacy Policy

PRIVACY POLICY — QR DECODER
Effective Date: June 15, 2026
Last Updated: June 15, 2026

Most current version (web):
https://afkgamesstudio.github.io/qr-decoder/privacy-policy.html

This Privacy Policy is provided in-app and may also be available on the Studio website. If a web copy differs from the in-app copy included with your installed build, the in-app copy controls for that build.

1. SCOPE; ENTITY; ROLES
   This Privacy Policy describes how AFK GAMES STUDIO (“Studio,” “we,” “us,” or “our”) processes information in connection with the mobile application QR Decoder (the “App”).

The App is designed as a local-first utility for QR/barcode scanning, QR creation, document scanning, OCR, ID scan workflows, inventory/batch scan workflows, file viewing/editing, and ZIP/archive tools.

We do not require account registration, and we do not ask you to submit legal names, physical addresses, account credentials, or payment card details to the Studio for account-creation, account-management, or payment-processing purposes. However, depending on how you use the App, user-selected content such as QR codes, barcodes, documents, ID scans, files, or archives may contain personal or sensitive information, including names, addresses, contact details, identifiers, document contents, credentials, payment information, or other information.

The App uses third-party SDKs and services that may collect and process certain information automatically, including:

* Google AdMob / Google Mobile Ads SDK (ads and measurement)
* Google User Messaging Platform (UMP) (consent / privacy options flow where required/available)
* Firebase Analytics (app usage measurement)
* Firebase Crashlytics (crash reporting and stability diagnostics)
* Google ML Kit and/or Google Play services scanner components, as applicable to barcode scanning, text recognition, and document scanning features

For certain third-party processing, Google may act as a service provider/processor, as an independent controller, or under other applicable Google terms and policies, depending on the service, configuration, region, and legal context. See Section 6.

2. INFORMATION PROCESSED ON YOUR DEVICE (LOCAL-FIRST)

2.1 QR, Barcode, Document, OCR, ID, File, and ZIP Data
The App may process and store certain information locally on your device to provide core functionality, including:

* QR Scan Data: decoded QR codes, barcodes, URLs, text, Wi-Fi payloads, contact-like payloads, product codes, or other content contained in codes you scan
* QR Creator Data: text, URLs, Wi-Fi payloads, contact-like payloads, or other content you enter to generate QR codes
* Inventory / Batch Scan Data: scanned code values, timestamps, counts, lists, and exported inventory-style records
* Document Scan / OCR Data: document images, generated PDFs, recognized text, and related scan outputs
* ID Scan Data: ID-document images, PDFs, extracted text, or related local scan outputs created by your use of the ID scan workflow
* File Viewer / Text Editor Data: files you select through the Android system file picker, files stored in the App’s internal storage, and text or document content you choose to view or edit
* ZIP / Archive Tool Data: archive file names, archive contents, extracted files, user-selected output locations, and temporary processing data needed for normal ZIP operations
* App Settings and Local History: preferences, recent scan history, saved local records, and feature state needed to operate the App

The App does not require you to create an account with the Studio to use these features.

2.2 Camera Access
Camera access is used to scan QR codes and barcodes, capture documents, support OCR-related workflows, and support ID scan workflows. Camera images are processed for the user-selected feature and are not uploaded to Studio-operated servers.

You are responsible for the content you choose to scan, capture, save, export, or share through the App. QR codes, barcodes, documents, IDs, files, and archives may contain personal, confidential, or sensitive information.

2.3 Local Storage and Android Backup
The App is local-first. User content is generally stored on your device, in App-controlled storage, in user-selected locations, or through Android’s system file access framework.

Some local App data may be eligible for Android operating system backup or device/account backup depending on your device settings, operating system version, Google account settings, manufacturer settings, and applicable backup configuration. The Studio does not operate its own cloud backup service for your QR, document, OCR, ID, file, or ZIP content.

2.4 File Access / Android System Picker
The App uses Android system file access mechanisms, such as the system picker / Storage Access Framework, for user-selected files and folders. The App is not designed to scan your entire device storage without your selection, and it does not require broad all-files storage access.

2.5 ZIP Passwords
If you use password-protected ZIP/archive features, passwords you enter are used to attempt the requested archive operation. The App is designed not to store ZIP passwords as account credentials. You are responsible for keeping your archive passwords secure.

2.6 User Controls (Local Deletion)
You can delete local App data using available in-app controls, including scan history deletion where available, deleting generated/exported files, deleting files from user-selected storage locations, clearing App storage through Android settings, and/or uninstalling the App. Uninstalling the App typically removes locally stored App data, subject to your device and operating system backup settings.

3. INFORMATION PROCESSED BY THIRD PARTIES (AUTOMATED COLLECTION)
   The App integrates third-party SDKs for advertising, consent, analytics, crash reporting, and certain scanner/document/OCR-related SDK operations. These SDKs may collect or process different categories of information for different purposes.

In particular, Firebase Analytics and Firebase Crashlytics are used for app measurement, crash reporting, and diagnostics available to the Studio. Google AdMob / Google Mobile Ads SDK is used for advertising and may automatically collect, process, and share certain information for advertising, measurement, frequency capping, security, and fraud-prevention purposes.

Third-party SDKs may automatically collect, receive, and/or process information such as:

A) Device or Other Identifiers

* Advertising ID or equivalent identifiers
* App instance identifiers
* Device identifiers or technical identifiers used for measurement, diagnostics, fraud prevention, service operation, or advertising

B) Approximate Location

* IP address and approximate location inferred from IP

C) App Interactions

* App interaction and usage events, such as app launches, screens viewed, feature usage, and engagement signals
* Advertising events, such as ad requests, impressions, clicks, interaction signals, frequency capping, and anti-fraud signals
* Consent or privacy-choice signals where UMP is available or required

D) Diagnostics

* Device/technical data such as device model, hardware/OS version, language, time zone, app version, SDK version, performance signals, and diagnostics

E) Crash Logs

* Crash reports and related diagnostic information, such as stack traces and crash-state signals, processed via Firebase Crashlytics to diagnose and fix stability issues

F) Scanner / Document / OCR SDK Metrics and Technical Signals

* Google scanner, barcode, text recognition, or document scanner components may process SDK metrics, diagnostics, device/technical information, or service-operation signals, depending on the SDK, device configuration, operating system services, region, and applicable Google policies

We do not operate our own user-account servers for these functions. Third parties process information under their own terms and policies and, in some cases, as independent controllers or service providers/processors depending on the service and legal context.

4. HOW INFORMATION IS USED
   We use information, or enable third parties to use information, to:

* Provide and maintain App functionality, including QR/barcode scanning, QR creation, document scanning, OCR, ID scan workflows, inventory/batch scan workflows, file viewing/editing, and ZIP/archive operations
* Store local scan history, settings, generated files, and user-selected outputs
* Display, measure, and optimize ads; prevent fraud and abuse; enforce policy compliance
* Request and manage advertising consent or privacy choices where required or available
* Measure and understand app usage through analytics/measurement
* Maintain security and stability, including troubleshooting, crash reporting, and performance diagnostics
* Improve App reliability and user experience
* Comply with legal obligations

5. LEGAL BASES (EEA/UK)
   Where GDPR/UK GDPR applies, processing may occur under:

* Consent: for personalized advertising and certain consent-based processing where required; consent choices are managed through UMP where available
* Legitimate Interests: limited processing for security, fraud prevention, measurement, crash diagnostics, App improvement, and stability, subject to your rights and applicable law
* Contract Necessity: local processing needed to provide the core App experience, such as scanning codes, creating QR codes, saving local history, opening user-selected files, and performing ZIP operations
* Legal Obligations: processing needed to comply with applicable laws, platform rules, enforcement requests, or legal obligations

6. SHARING; THIRD-PARTY SERVICES

6.1 Third-Party SDKs and Service Providers
The App uses third-party SDKs and service providers that collect and/or process information described in this Privacy Policy, including:

* Google AdMob / Google Mobile Ads SDK
* Google User Messaging Platform (UMP)
* Firebase Analytics
* Firebase Crashlytics
* Google ML Kit and/or Google Play services scanner components, as applicable

These services are provided by Google LLC and/or related Google services. Your use of these services is subject to Google’s terms and privacy policies.

Depending on the service, configuration, region, and legal context, Google may process certain information as a service provider/processor, as an independent controller, or under other applicable Google terms and policies.

The Studio uses Firebase Analytics and Firebase Crashlytics to view analytics, crash reporting, and diagnostic information for the App. The Studio does not use Firebase Analytics or Firebase Crashlytics to sell personal information or to create Studio-operated user account profiles.

6.2 Google AdMob / Google Mobile Ads SDK
The App uses Google AdMob / Google Mobile Ads SDK to display advertising. In the current build, the App implements App Open ads only. Google AdMob and related Google services may automatically collect, process, and share certain information for ad delivery, measurement, frequency capping, fraud prevention, security, and policy compliance.

Depending on configuration, region, and user choices, this may include IP address, Advertising ID or equivalent identifiers, app set ID or other device/account identifiers, app interactions, advertising events, diagnostic information, performance signals, approximate location inferred from IP, and anti-fraud signals.

Advertising-related processing may be considered “sharing” under some privacy laws and under Google Play Data Safety depending on the data type, purpose, and configuration. Where required or available, user choices may be managed through UMP “Privacy Options” and/or device advertising settings.

6.3 Google User Messaging Platform (UMP)
The App uses Google User Messaging Platform (UMP) to provide consent and privacy options flows where required or available. UMP may process consent state and related technical signals as needed to present, store, and apply your choices.

6.4 Firebase Analytics
The App uses Firebase Analytics for app usage measurement and analytics available to the Studio. Firebase Analytics may collect and process app interaction events, app lifecycle events, app-instance identifiers, Advertising ID where available/configured, masked IP-derived coarse location, device/technical information, and related analytics signals.

The Studio uses Firebase Analytics to understand general App usage, feature engagement, stability context, and aggregate measurement trends. The App does not require account registration with the Studio for Firebase Analytics, and the Studio does not use Firebase Analytics to maintain Studio-created user account profiles.

Based on the current App implementation, the Studio does not intentionally log custom analytics events, set Studio-controlled user IDs, or set Studio-created user properties in Firebase Analytics. Firebase Analytics data is processed by Google/Firebase under applicable Google terms and policies. The Studio does not share Firebase Analytics data with non-Google third parties for advertising.

6.5 Firebase Crashlytics
The App uses Firebase Crashlytics for crash reporting and stability diagnostics available to the Studio. Crashlytics may collect and process crash logs, stack traces, relevant application state, device metadata, app state, Crashlytics installation identifiers, Firebase installation identifiers, and related diagnostic information when crashes or stability events occur.

The Studio uses Crashlytics to identify, prioritize, and fix crashes and stability issues. Based on the current App implementation, the Studio does not intentionally attach custom keys, custom logs, free-text user IDs, non-fatal reports, or test-crash UI data to Crashlytics reports.

Crashlytics data is processed by Google/Firebase under applicable Google terms and policies for crash reporting and diagnostics. The Studio does not share Crashlytics data with non-Google third parties for advertising.

6.6 Google Scanner / ML Kit / Document Scanner Components
The App may use Google ML Kit and/or Google Play services scanner components to provide barcode scanning, text recognition, document scanning, and OCR-related functionality.

Where implemented with on-device components, supported scanner and recognition features are designed to process supported inputs on the device. Google ML Kit and Google Play services components may still process SDK metrics, diagnostics, device/technical information, or service-operation signals as described in Google’s applicable documentation and policies.

The Studio does not operate its own servers to upload your scanned QR content, documents, OCR text, ID scan outputs, files, or ZIP contents.

6.7 User-Directed Sharing / Export
If you choose to share, export, copy, save, print, send, or open App-generated content through another app or service, that action is user-directed. The receiving app, service, storage provider, or device destination may process the content under its own terms and privacy policy.

6.8 Open Source
The App may include open source components governed by their respective licenses. See the App’s “Third-Party Notices” or “Licenses” section.

7. YOUR CHOICES; PRIVACY RIGHTS

7.1 Consent & Ads Preferences (UMP)
Where available, you can review or change ad consent choices using the in-app “Privacy Options” or equivalent control, which surfaces UMP choices. Depending on your region and choices, ads may be personalized or non-personalized. Some processing may still occur for measurement, security, fraud prevention, frequency capping, and policy compliance as permitted by applicable law and platform rules.

7.2 Device Controls
Depending on your device and region, you may be able to reset or delete your Advertising ID and limit ad personalization through device settings, for example by searching “Ads” or “Advertising” in system settings.

7.3 Local App Controls
You can manage local App data through available in-app controls, such as scan history deletion where available, deleting generated QR codes, deleting document/OCR/ID outputs, deleting local/exported files, clearing App storage through Android settings, and/or uninstalling the App.

7.4 California (CCPA/CPRA)
We do not “sell” personal information for money. Depending on how “share” is defined under applicable law, certain advertising-related disclosures may be considered “sharing” for cross-context behavioral advertising. Where required, we provide an option to opt out of such “sale” or “sharing” via in-app “Privacy Options” or applicable device settings.

California residents may also have rights to access, delete, or correct certain personal information, subject to verification and legal exceptions.

7.5 EEA/UK and Other Regions
Subject to applicable law, you may have rights to access, delete, correct, restrict, object to, or obtain a copy of certain personal information. To submit a request applicable to Studio-controlled processing, contact us as described in Section 13.

Please note that we may be unable to access or delete information held by third parties directly. In those cases, you must use the controls provided by the third party, the applicable platform, or your device settings.

8. DATA RETENTION

* Local QR Scan Data, QR Creator Data, Inventory / Batch Scan Data, Document Scan / OCR Data, ID Scan Data, File Viewer data, ZIP/archive outputs, App settings, and local history are retained on your device until you delete them using available in-app controls, delete the relevant files, clear App storage, or uninstall the App, subject to your device and operating system backup settings.
* User-selected files and exported files may remain in the locations you choose until you delete them.
* Files or outputs shared, copied, exported, printed, sent, or opened through another app or service may remain with the receiving app, service, storage provider, or device destination according to that provider’s own terms, settings, and privacy policy.
* Temporary processing data may be created during scanning, editing, exporting, OCR, ID scan, or ZIP/archive operations and may be cleared according to App behavior, operating system behavior, available storage controls, or user action.
* ZIP passwords entered for encrypted archive operations are used for the requested operation and are not intended to be stored as account credentials.
* Third-party data retention is governed by the third parties’ own policies and settings, and the Studio may not directly control third-party retention periods.

9. CHILDREN’S PRIVACY
   The App is not directed to children under 13 and we do not knowingly collect personal information from children under 13. If you believe a child has provided information through the App, contact us and we will take appropriate steps consistent with applicable law.

10. SECURITY
    We use reasonable administrative and technical measures designed to protect information. However, no method of transmission or storage is 100% secure.

You are responsible for reviewing the content you scan, create, save, export, or share through the App. QR codes, barcodes, documents, IDs, files, and ZIP archives may contain sensitive information. Use caution when scanning unknown codes, opening unknown files, extracting archives, sharing generated files, or storing sensitive documents on your device.

11. INTERNATIONAL TRANSFERS
    If you use the App outside the United States, information processed by third-party partners may be transferred to and processed in countries other than your own, including the United States, subject to the partners’ safeguards and policies and applicable law.

12. DATA DELETION (HOW TO DELETE DATA)

12.1 Local Scan History and App-Controlled Data
Because the App is local-first, most App content is stored locally on your device or in locations you select. You can delete local scan history and App-controlled local data using available in-app controls where provided.

12.2 Generated, Exported, or User-Selected Files
Generated QR codes, exported files, PDFs, OCR outputs, ID scan outputs, inventory exports, extracted ZIP files, and files saved to user-selected locations may remain where you saved them until you delete them. You can delete such files through the App where controls are available, through Android’s file manager, through the storage provider where the files were saved, or through another app that manages that location.

12.3 Android App Storage
You can delete App storage by using Android system settings to clear the App’s storage or by uninstalling the App. Uninstalling the App typically removes locally stored App data, subject to your device and operating system backup settings.

12.4 Android Backup / Restored Data
Some local App data may be included in Android operating system backup or restored data depending on your device, operating system, Google account, manufacturer settings, and backup configuration. To manage or delete backup copies, use the backup and account controls provided by your device, operating system, or account provider.

12.5 Third-Party Data
Some information may be processed by third-party SDKs and services, including Google AdMob, Google UMP, Firebase Analytics, Firebase Crashlytics, and Google scanner/OCR components.

Firebase Analytics and Firebase Crashlytics are used by the Studio for analytics, crash reporting, and diagnostics. The Studio may view related analytics and crash information in Firebase Console, but the Studio does not use Firebase Analytics or Crashlytics to sell personal information or share data with non-Google third parties for advertising.

Google AdMob / Google Mobile Ads SDK may collect, process, and share certain information for advertising, measurement, frequency capping, fraud prevention, security, and policy compliance.

The Studio may be unable to directly access, delete, or control all data held by third-party providers. Where available, use:

* The App’s “Privacy Options” or equivalent UMP control to manage advertising consent/choices
* Your device settings, such as reset/delete Advertising ID or limit ad personalization
* The third party’s own controls, terms, and privacy policies

12.6 Requests
If you have a privacy or deletion request that applies to Studio-controlled processing, contact us using the details in Section 13.

13. CONTACT
    AFK GAMES STUDIO
    Email: afkgames.helpdesk@gmail.com