QR Code - Scanner & Generator

Privacy Policy

Effective October 12, 2026

This Privacy Policy explains how Byeshe (“we,” “us,” or “our”) handles information when you use QR Code - Scanner & Generator (the “Application”), a freemium Android app with advertising and optional paid features or subscriptions. Features and providers may vary by version, region, and configuration. No Application account is required. Contact play@byeshe.com for privacy questions.

Camera, image selection, and recognition

Camera permission supports the in-app live scanner. Selected images can be read through Android’s content picker for barcode recognition or a custom logo. Barcode recognition uses on-device ML Kit, Google Code Scanner, or local code libraries. We do not upload camera frames or selected scan images to a Byeshe recognition server. Google Code Scanner can supply its own scan interface; ML Kit modules may be downloaded by Google Play services.

ML Kit and saved code content

Google’s ML Kit privacy information explains on-device input processing and separate performance metrics and model or compatibility communications. The Application saves raw and parsed code text, type and format, timestamps, favorites, folders, and created-code styling. Generated codes may include your entered names, addresses, messages, contact information, or Wi-Fi credentials. Optional security settings can include a password, validity dates, and watermark text stored with the created-code record.

Exports and external actions

Generated images and batch exports, including PDF or ZIP where available, can be saved to shared storage or shared with a destination you choose. Opening a scanned URL, email action, or other external action passes the relevant content to the destination app or service. Local recognition does not make external links safe or anonymous.

Android permissions

Optional permissions can be declined or revoked in Android settings. Features depending on that access may be limited. Reading this policy does not grant permission, and revoking access does not automatically erase saved records.

Local storage, backup, and support

Saved code contents, folders, style options, custom-logo references, security settings, and preferences are kept in an app-private Room database or preference storage. Android backup and device-transfer features may include eligible app data, depending on your device and backup settings. This is separate from a Byeshe server upload. Manage backup copies through Android or your backup provider.

If you contact support, we receive your email address, message, and attachments you choose to send. We use them to respond and resolve your request.

Advertising and privacy choices

The ad-supported version uses Google AdMob and mediation partners. They may process IP address, approximate region, advertising and app identifiers, device and operating-system information, network state, ad requests, impressions, clicks, interactions, and diagnostics. Processing supports ad delivery, measurement, attribution, personalization where permitted, security, and fraud prevention. Non-personalized ads can still involve technical data processing.

Google’s User Messaging Platform handles advertising consent where applicable. When required and available, you can revisit consent through Settings → Privacy options. Availability depends on region, provider, and configuration. You can also adjust Android advertising privacy settings, including advertising ID and supported advertising features. An ad-removal purchase changes ad display according to its offer; configuration, purchase validation, analytics, and other technical communications can continue.

Advertising partners may include Google AdMob, Meta Audience Network, AppLovin, Pangle, Liftoff Monetize (Vungle), Mintegral, InMobi, BidMachine, and Unity Ads and ironSource. Providers serving a particular request depend on mediation configuration and availability.

Analytics, configuration, attribution, and diagnostics

Firebase Analytics is enabled by default. It can process launches, sessions, screen views, feature interactions, settings changes, ads, and purchases, together with app-instance or available advertising identifiers, app version, device information, and approximate region. We use it to understand use, improve features, and measure conversions. Feature events may include code type or format, favorite state, and selected-item counts. External URL or email failures can send error-message text, truncated to 100 characters, to Analytics; errors may also be reported to Crashlytics. Such messages can contain contextual details. We do not intentionally send camera frames or complete saved-code databases as analytics inputs.

Firebase Remote Config retrieves app and advertising configuration using installation identifiers and technical requests. Firebase Crashlytics uploads crash and non-fatal error diagnostics, such as traces, error messages, identifiers, app version, and device state. Reports may be cached until a later launch and are not guaranteed to be anonymous. The Application has no dedicated in-app switch for Analytics or Crashlytics.

Google Play Install Referrer supplies installation source and click or installation timing. Meta App Events and TikTok Business services may process installation, launch, and conversion events and available identifiers depending on configuration. Purchase events can include order or transaction identifier, product, quantity, currency, and attributed value, which can differ from the amount charged. See Firebase privacy information, Google’s Privacy Policy, Meta’s Privacy Policy, and TikTok’s Partner Privacy Policy.

Purchases and subscriptions

Google Play processes payments. The Application and purchase services may process product identifiers, purchase tokens, order identifiers, purchase time, subscription status, and entitlements to acknowledge purchases, restore access, prevent fraud, and provide support. We do not receive your full payment-card number or payment credentials. Purchase conversion events may be sent to Firebase Analytics, Meta, and TikTok as described above. Clearing app data or uninstalling does not cancel a subscription.

Sharing, external destinations, and international processing

Advertising, technical, attribution, and purchase information is processed by the providers above for the described purposes. We may disclose information held by us to providers assisting us, where legally required, to protect rights and safety, or in a business transfer subject to applicable protections. Providers may process information outside your country under their policies and applicable safeguards. Shared codes, exported files, and external actions are handled by the recipient or destination provider under its own policy.

These pages use Firebase Hosting, which processes IP addresses and technical requests for delivery and security. The pages contain no advertising or analytics scripts, external fonts, or tracking cookies.

Retention, deletion, and your rights

Saved codes and folders have no automatic time-based expiry. Use the Application’s history and folder controls to remove records, or Android clear-storage or uninstall controls to remove app-private data. Exported images, PDFs, ZIP files, shared copies, and backup copies are separate and must be managed separately. Deletion does not revoke information already exposed in a code.

Support correspondence and purchase-related information held by us are retained as needed to resolve requests, maintain entitlements, prevent fraud, and meet legal obligations, then deleted when no longer needed. Advertising and technical providers have their own retention periods. Local deletion does not recall events or diagnostics already sent, erase store transaction history, or cancel subscriptions.

Contact play@byeshe.com to request access, correction, deletion, or rights available in your location, including objection, restriction, portability, or withdrawal of consent. We may need to verify your request. We cannot remotely retrieve or delete information held only on your device. Contact us for help with information processed on our behalf; providers’ independent processing follows their policies. You may also contact your local data-protection authority.

Security and children

We use reasonable safeguards, but no storage or transmission is completely secure. Protect your device, email, and backups. The Application is not directed to children under 13. Minors must meet applicable age requirements and obtain guardian permission where required. If you believe a child has provided personal information to us, contact us so we can take appropriate action.

Changes and contact

We may update this policy and its effective date when features or data practices change, with additional notice or consent where required. For privacy questions, contact Byeshe at play@byeshe.com.