BagCue Privacy Policy

Effective date: November 13, 2026

This Privacy Policy describes how the BagCue mobile application (the “Application”), operated by Sergey V. (the “Service Provider”), accesses, processes, and shares information. BagCue helps adults prepare reusable packing lists for work and regular activities.

Privacy summary: Your item names, templates, bag labels, storage-place notes, packing sessions, and reminder settings stay on your device. BagCue has no user accounts and does not upload this content to the Service Provider. Network data may be processed by the Service Provider's minimal privacy-region endpoint, Yandex Mobile Ads SDK, Firebase Crashlytics for release crash diagnostics, and, only when you enable Usage analytics in Settings, Google Analytics for Firebase, as described below.

1. Information Stored on Your Device

BagCue stores your user-created items, templates, bag labels, storage-place notes, packing-session history, completion state, reminder preferences, and privacy choices locally on your device. This data is used to provide the Application's core offline functionality and is not sent to the Service Provider.

You can edit or delete supported records in the Application. Clearing the Application's storage or uninstalling it removes local data subject to normal operating-system and backup behavior. BagCue does not provide cloud backup, account synchronization, import, or export in this release.

2. Information Not Requested

BagCue does not require an account and does not ask for your name, email address, phone number, contacts, date of birth, precise location, photos, or payment information. The Application is designed not to send user-entered item names, template names, bag labels, storage-place notes, or selected packing dates to advertising or analytics providers.

3. Notifications

If you enable optional evening or morning reminders, BagCue asks for the operating system's notification permission and schedules reminders locally. Denying or revoking this permission does not prevent you from creating, editing, completing, or reviewing packing sessions.

4. Third-Party Services and Network Data

Yandex Mobile Ads SDK

BagCue uses Yandex Mobile Ads SDK to display at most one non-blocking inline advertisement after an Android packing session has been completed with all items packed. Yandex may process network and technical information needed to deliver, secure, and measure an advertisement, such as an IP address, general device and application information, and ad interaction events. BagCue is configured not to request or use the device advertising identifier and does not provide Yandex with your user-created packing content.

Where the Application's current privacy-region result requires a choice, BagCue asks for advertising consent before initializing Yandex Mobile Ads. A decline, missing or expired result, policy-version mismatch, endpoint failure, or unresolved choice keeps advertising disabled without blocking the Application. BagCue does not use advertising mediation, Google Mobile Ads, rewarded ads, or interstitial ads.

Google Analytics for Firebase

Usage analytics is disabled by default. You may enable or disable it at any time using the Usage analytics switch in Settings. When enabled, Google Analytics for Firebase processes an app-instance identifier, application and device information, approximate location derived from network information, automatically collected analytics events, and the limited product events listed below. This does not require access to your device's precise location. BagCue disables Advertising ID collection, Google Signals, ads personalization, User-ID, custom user properties, and linking Analytics data to Google Ads.

For these six custom product events, BagCue sends only the event name, without app-defined event parameters. Firebase may also collect automatic events and associated technical parameters when Usage analytics is enabled. BagCue does not add user-entered text, local entity identifiers, exact packing dates, bag assignments, storage locations, item-count or duration ranges, completion outcomes, or reminder types to these events, and does not send individual item-check events. Turning analytics off stops future collection and requests a reset of locally held analytics data and the app-instance identifier. If the local reset fails, Settings offers a retry action. Disabling analytics does not guarantee immediate deletion of information already processed by Google.

Firebase Crashlytics

Release versions automatically use Firebase Crashlytics to diagnose crashes and improve reliability. Crash reporting operates independently of the Usage analytics switch and advertising consent. Reports include stack traces, exception types and messages, crash timestamps, application and device information, and SDK-generated installation and session identifiers. These are not advertising identifiers. BagCue does not attach user-created packing content, a custom user ID, custom content keys, or content logs. Exception messages may contain runtime diagnostic details. When Usage analytics is enabled, its events may also appear as breadcrumbs in crash reports. Debug builds disable automatic reporting.

Crash reports can be stored locally until a later launch with a network connection allows upload. Turning Usage analytics off does not disable crash reporting or delete previously collected crash data.

Service Provider privacy-region endpoint

BagCue calls https://168.222.252.178/v1/privacy/region to determine whether advertising consent choices are required for the current network region. Like any HTTPS service, the endpoint receives the network information inherent in the request, including the source IP address. It returns only a consent-required flag, policy version, and short expiry. It does not receive user-created packing content, an advertising identifier, a stable request/user ID, or the consent choice stored on your device.

The providers' own terms and policies also apply:

5. Purposes of Processing

6. Legal Bases and Choices

Where applicable law requires a legal basis, processing may rely on consent, the Service Provider's legitimate interests in operating and improving the Application, or compliance with legal obligations. Advertising consent and the optional Usage analytics switch are separate choices. Withdrawing consent or disabling analytics does not affect the lawful processing that occurred before the change.

When a fresh privacy-region result requires advertising consent, you can change or withdraw your choice in Settings under Advertising privacy by selecting Decline advertising. Once saved, this choice stops new advertising requests and removes the current ad. If the privacy status is unresolved or expired, ads remain off; use Refresh privacy status to obtain a fresh result. When a fresh result does not require consent, no advertising choice control is shown. Core packing features remain available regardless of your choice.

You can separately disable Usage analytics in Settings. Neither declining advertising nor disabling Usage analytics disables automatic release crash reporting by Firebase Crashlytics.

7. Data Sharing

The Service Provider does not sell your user-created packing content. Information is processed through Yandex Mobile Ads when advertising is permitted, Google Analytics for Firebase when Usage analytics is enabled, Google Firebase Crashlytics for automatic release crash diagnostics independently of Usage analytics and advertising consent, and the Service Provider's privacy-region endpoint. Processing is for the purposes described in this Policy. Information may also be disclosed when required by law or needed to protect users, the Service Provider, or the public from fraud, security threats, or harm.

8. Retention and Deletion

Local packing data remains until you delete it, clear Application storage, or uninstall the Application, subject to operating-system backup behavior. The minimal privacy-region result and matching advertising choice are kept locally only while needed under the current policy version; region-result freshness is capped at 72 hours. This is a freshness limit for the locally cached region result, not a retention period for server-side network information or third-party diagnostic data.

Firebase Crashlytics retains crash traces and associated identifiers for 90 days before starting removal from live and backup systems, according to Google's published policy. This is independent of Analytics. Google Analytics user-level and event-level retention is configured to two months. Some standard aggregated reports may not be affected by that setting. Yandex and Google may retain information under their own policies and legal obligations. Disabling Usage analytics stops future collection and resets local analytics state, but does not itself guarantee immediate deletion of previously processed server data. To submit a privacy request concerning data controlled by the Service Provider, use the contact address below; provider-controlled requests may need to be directed to Yandex or Google.

9. International Transfers

Third-party providers may process data outside your country. Where required, transfers are subject to safeguards supplied by the relevant provider and applicable law.

10. Security

The Service Provider uses reasonable technical and organizational measures appropriate to the Application. Core content is kept locally and network communications use encrypted connections. No method of electronic processing or transmission is completely secure, so absolute security cannot be guaranteed.

11. Adults and Children's Privacy

BagCue is intended for adults aged 18 and older and is not directed to children. The Application does not ask users to provide a date of birth. If you believe a child has provided personal information to the Service Provider, contact the Service Provider so the matter can be investigated.

12. Your Privacy Rights

Depending on where you live, you may have rights to access, correct, delete, restrict, or object to processing; withdraw consent; receive information about data sharing; or lodge a complaint with a data protection authority. Because BagCue has no account and does not receive your user-created packing content, the Service Provider may not hold content that can be associated with you.

13. Changes to This Policy

This Policy may be updated when the Application, SDKs, legal requirements, or data practices change. The revised version will carry a new effective date, and material changes will be communicated where required by law.

14. Contact Us

For questions or privacy requests related to BagCue, contact info[@]sedsoftware.com.