Effective October 5, 2026

Privacy Policy

Qubo creates static QR codes on your device. Your QR content, selected logos, editor draft, and exported files are not uploaded to a Qubo server.

The short version: no account or Qubo backend is required. Qubo keeps your QR project local, uses TelemetryDeck for limited anonymous product analytics, shows occasional ads through Google AdMob, and may send limited crash diagnostics to Sentry.

1. Who this policy covers

This Privacy Policy explains how Qubo (the “App”) handles information when you use it. Qubo is operated by the independent developer identified in the App Store or Google Play listing. For privacy questions or requests, use Qubo’s contact form. Please do not include QR contents or other sensitive information in your request.

2. Information handled on your device

Qubo processes the information you enter or select to create a QR code. Depending on the QR type, this may include URLs, plain text, Wi-Fi credentials, contact details, email or messaging content, phone numbers, or location coordinates. The App also handles your colors, styling, selected logo, export preferences, and current editor draft.

This QR content and design data is used on your device to render and export the code. Qubo does not send it to the developer, TelemetryDeck, AdMob, Sentry, Tally, or an account service. QR codes themselves can reveal their encoded contents to anyone who scans or receives them, so you should avoid placing confidential information in a QR code unless you intend to share it.

3. Anonymous product analytics

The iOS and Android apps use TelemetryDeck for anonymous product analytics. Qubo sends one session-start event per app launch and events when an export completes or fails. These events may include the QR content category, PNG or SVG format, broad visual-style categories, whether the exported design contains an image logo or emoji, a bucketed emoji count, app and operating-system versions, platform, language, locale, a non-content failure category, and an approximate country or region derived from the network connection.

Qubo does not send QR payloads or user-entered fields, location coordinates encoded in a QR code, logo files or references, exact emojis, exported files, account identifiers, or advertising identifiers to TelemetryDeck. A random identifier stored by this installation is hashed by the SDK before transmission and is used only for aggregate installation, session, and retention measurement. A separate random identifier groups events from one app launch.

TelemetryDeck hosts this usage data in the European Union. It may derive an approximate country or region from the network connection without retaining the originating IP address. Analytics is best-effort and does not affect offline QR creation or export. It is not enabled in Qubo’s web app. Learn more in TelemetryDeck’s Privacy Policy.

4. Advertising

Qubo uses Google AdMob to show occasional interstitial advertisements. The Google Mobile Ads SDK may automatically process information such as your IP address and approximate location derived from it, device or app-scoped identifiers, advertising data, interactions with the App or an ad, and crash, performance, or other diagnostic information. Google may use this information to provide, secure, measure, and improve advertising and to prevent fraud.

Qubo requests non-personalized ads, does not request App Tracking Transparency permission, and does not intentionally request access to Apple’s Identifier for Advertisers (IDFA). Non-personalized ads can still use contextual information and may still involve device identifiers, local storage, IP addresses, measurement, and fraud-prevention processing. Qubo does not send QR payloads, typed content, selected logos, export files, or precise QR location coordinates to AdMob.

Where required, Google User Messaging Platform (UMP) asks for privacy choices before the App requests an ad. Qubo displays a Privacy options entry in Settings when Google requires it so you can review or change those choices. Declining optional advertising choices does not disable QR creation or export.

For more information, see the Google Privacy Policy and how Google uses information from apps that use its services.

5. Crash and reliability diagnostics

Versions of Qubo that include crash reporting use Sentry to identify crashes, errors, and reliability problems. A diagnostic event may include an error type and stack trace, the App version, platform and operating-system version, device model, timestamps, runtime or performance information, and an IP address received during transmission.

Sentry is used for error and crash diagnostics, not session replay or product analytics. Qubo does not intentionally attach QR payloads, typed QR content, selected logos, exported files, advertising identifiers, account identities, or precise location coordinates to Sentry events. System and third-party error reports can nevertheless contain incidental technical context, so the App and the Sentry project should be configured to minimize and scrub unnecessary data.

Sentry processes diagnostic events as a service provider under its own infrastructure and contractual terms. Learn more in Sentry’s Privacy Policy.

6. Feedback and privacy requests

Qubo links to a form hosted by Tally when you choose Request a feature or use the contact link on this page. Submitting the form is optional. The App may add the Qubo version and your platform to the form URL. It does not add QR payloads, selected logos, exported files, advertising identifiers, or sensitive device identifiers.

Your answers and any reply email you choose to provide are processed by Tally and received by the developer. Do not place QR contents, passwords, or other sensitive information in the form. See Tally’s Privacy Policy.

7. Device permissions, logos, and exports

If you choose a custom logo, Qubo asks the operating system for access needed to select that image and stores an app-controlled local copy. Saving a PNG to Photos requires photo-library add permission. Sharing a PNG or SVG uses your operating system’s share interface.

When you save or share an export, the destination you choose—such as Photos, Files, another app, a cloud provider, or a recipient—handles that file under its own terms and privacy practices. Qubo does not control the file after it leaves the App.

8. How information is used

Information handled by Qubo is used to create and preserve your local editor draft, render and export QR codes, measure anonymous aggregate product usage, remember advertising frequency and privacy state, show and measure advertising, maintain security, diagnose failures, respond to requests, and improve reliability. Qubo does not operate user profiles or a backend for QR creation.

9. Sharing and disclosure

Qubo does not sell your QR contents or upload them to the developer. Information may leave your device only in these limited situations:

10. Storage, retention, and deletion

The current editor draft, design settings, selected logo copy or reference, anonymous analytics installation identifier, advertising cadence, and advertising education acknowledgment are stored locally. Deleting Qubo removes this app-managed local data, subject to device backups controlled by you or your platform provider. Files saved to Photos, Files, cloud storage, or another app must be deleted from those destinations separately.

TelemetryDeck, Google, Sentry, and Tally retain information according to their settings, contractual terms, and policies. Previously transmitted anonymous analytics may remain according to TelemetryDeck’s retention practices. The developer keeps diagnostic events and voluntary form submissions only as long as reasonably needed for reliability, security, support, and legal obligations.

11. Your choices and rights

You may decline or revoke optional device permissions in system settings. Where Google requires a privacy message, you can review or change advertising choices through Settings → Privacy options. Deleting Qubo removes its local analytics installation identifier and stops future TelemetryDeck analytics and Sentry diagnostics from that installation.

Depending on where you live, you may have rights to request access, correction, deletion, restriction, objection, or portability regarding personal information processed off-device. Submit a request through Qubo’s contact form. Because Qubo has no account and does not intentionally attach a real-world identity to analytics or crash reports, the developer may be unable to associate an event with you.

For users in the European Economic Area, United Kingdom, or Switzerland, applicable advertising processing relies on the choices collected through Google’s consent platform or another lawful basis presented there. Anonymous product analytics and limited crash diagnostics are processed for the legitimate interests of understanding and improving Qubo and keeping it reliable and secure, subject to your rights under applicable law.

12. International processing

TelemetryDeck hosts Qubo’s anonymous analytics data in the European Union. Google, Sentry, Tally, and their subprocessors may process information in countries other than your own, including the United States or European Union. Where required, those providers rely on contractual or other lawful transfer safeguards described in their policies.

13. United States state privacy disclosures

Qubo does not directly sell personal information. Advertising technology may involve processing or disclosure that some U.S. state laws define as “sharing,” targeted advertising, or a sale, even when Qubo requests non-personalized ads. Where applicable, use Privacy options in Qubo Settings to exercise the choices made available through Google’s consent platform, or contact the developer.

14. Children

Qubo is a general-audience utility and is not directed to children under 13. The developer does not knowingly collect personal information from children under 13. Do not encode a child’s personal information in a QR code unless you have the authority and a lawful reason to do so.

15. Security

Qubo minimizes off-device processing of QR content and relies on operating-system protections for local files and permissions. No storage or transmission method is completely secure, but reasonable measures are used to limit the information sent to third parties and protect information handled by the App.

16. Changes to this policy

This policy may be updated when Qubo’s features, providers, configurations, or legal obligations change. The effective date will be revised, and material changes will be communicated through the App or its store listing when appropriate.

17. Contact

Questions and privacy requests may be submitted through Qubo’s contact form. Please include a reply email if you want a response, and do not include sensitive QR content.