Privacy Policy

This policy explains how ReadyBag: Daily Bag Checklist handles information when you use the app.

Scope and contact

This policy applies to the ReadyBag Android app and its support website. Privacy questions and data requests can be sent to cheymae1126@gmail.com.

Information stored on your device

• Bag identifiers and names, checklist item identifiers and text, primary-bag status, and checked or unchecked states.
• Your selected app language and whether onboarding has been completed.
• Temporary identifiers used to control bag-creation and rewarded-ad flows; these are cleared after use.

ReadyBag uses this information only to provide its checklist, language, onboarding, and rewarded-feature behavior. It is stored in private app preferences on the device. The app does not require an account, and bag names and checklist text are not sent to the advertising or analytics services described below. If you email support, you choose the message content and your email provider and the support inbox process that message.

Advertising, device data, and consent

• ReadyBag uses Google Mobile Ads (AdMob) to request and display app-open, banner, interstitial, native, and rewarded ads.
• For an ad request or interaction, Google Mobile Ads can automatically collect or receive the device IP address, Advertising ID and other device or app identifiers, device and network information, app or ad interactions, and diagnostic information. Google uses this information for advertising, measurement, analytics, security, fraud prevention, and ad-frequency control.
• The app records advertising lifecycle details such as request, display, click, reward or failure status, time, ad format, placement, ad-unit identifier, session or trace identifier, loaded ad source, and paid-impression value and currency. These events are used for advertising measurement, analytics, diagnostics, attribution, and revenue reporting.
• Google's User Messaging Platform (UMP) requests and stores consent information where applicable. Ads are requested only after UMP reports that ads may be requested. When UMP requires a privacy-options entry for the user's region, it is available in Settings.
• Ad personalization or limited-ad behavior is determined by the consent choices and Google advertising controls available for the request. You can reset or delete the Advertising ID in Android settings.

Analytics and attribution

• Business-intelligence analytics: ReadyBag sends product and advertising lifecycle events, such as onboarding and checklist actions, ad requests, impressions, clicks, rewards, failures, and ad revenue. Payloads use operational fields such as identifiers, types, counts, booleans, timestamps, durations, placement, result, and error information rather than bag names or checklist text.
• Firebase Analytics: Firebase automatically processes app-instance and advertising identifiers, masked IP-derived approximate location, device and operating-system information, app launches, sessions, screen activity, and other app-lifecycle information. ReadyBag also sends selected advertising measurement events, including impression-level ad value, currency, ad format, ad source, ad unit, placement, session, and trace information.
• AppsFlyer: ReadyBag uses AppsFlyer for installation and campaign attribution and impression-level advertising revenue measurement. AppsFlyer can receive device or app identifiers, IP address, install and app-open information, media source, campaign, ad-set, creative, channel, first-launch status, ad format, placement, revenue, and currency.
• Google Play Install Referrer: AppsFlyer uses the Play Install Referrer service for installation attribution. ReadyBag retains only approved campaign fields such as media source, campaign, campaign ID, ad set, ad, channel, attribution status, and first-launch status; it does not intentionally send raw referrer URLs or raw attribution callback payloads to its BI service.

Third-party services

• Google Mobile Ads (AdMob) and User Messaging Platform: supply and measure ads, manage applicable consent choices, and support analytics, security, frequency control, and fraud prevention. See Google's Privacy Policy and Google Mobile Ads data disclosure.
• Google Firebase Analytics and Google Play Install Referrer: provide advertising analytics and installation attribution support. See Google's Privacy Policy.
• AppsFlyer: provides attribution and advertising-revenue measurement. See AppsFlyer's Privacy Policy.
• DataEye/business-intelligence analytics: processes the product, advertising, attribution, diagnostic, and revenue events described above. See DataEye's Policy Center.

Android permissions

• Internet: connects to advertising, consent, analytics, attribution, support, and policy services.
• Network state: allows network-dependent SDK components to understand network availability.
• Advertising ID: allows advertising and attribution services to use the resettable Android Advertising ID when available and permitted.

Sharing and disclosure

ReadyBag does not sell your personal information. Bag names and checklist text are not sent to the advertising, analytics, or attribution providers listed above. The advertising, device, network, consent, app-activity, attribution, revenue, and diagnostic information described in this policy is processed by those providers for the stated purposes. Information may also be disclosed when legally required or when necessary to protect users, the app, or others.

Retention, deletion, and Android backup

Bag and preference data remains in the app's private storage until you edit or delete the relevant bag, clear the app's storage through Android settings, or uninstall the app. The app currently provides per-bag deletion but does not provide a separate clear-all control. Android backup and device-transfer features may include the app's private preferences and may restore them after reinstallation, depending on device and account settings. Clearing app storage or managing device backups may therefore be necessary to remove backed-up copies.

Advertising, analytics, consent, and attribution providers retain transmitted information according to their own policies and the applicable service configuration. Because ReadyBag has no user account and does not maintain a developer server for checklist data, the developer may be unable to identify or selectively delete SDK records that are not linked to a name, email address, or account. You may contact us for assistance or use the privacy controls offered by Android and the relevant provider.

Your choices

• Edit or delete individual bags in the app.
• Use Android settings to clear all local app storage or uninstall the app.
• Use the privacy-options entry in Settings when UMP makes it available for your region.
• Use Android advertising controls to reset or delete the Advertising ID.
• Contact the address below with privacy questions or applicable access, correction, deletion, restriction, objection, or portability requests. Because there is no account, include enough details for us to understand the request, but do not send sensitive checklist content.

Security and international processing

ReadyBag stores checklist information in Android's private app storage. Network communication uses the security measures supplied by the relevant service providers, including encryption in transit documented for Google Mobile Ads and Firebase Analytics. No method of storage or transmission is completely secure. The providers listed above may process information in countries other than the one where you use the app, subject to their privacy policies and applicable safeguards.

Children's privacy

ReadyBag is a general-audience productivity tool and is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided personal information through the app, contact us so the matter can be reviewed.

Support website

The ReadyBag support website hosts product and privacy information. Its hosting provider may process ordinary request information, such as IP address, browser type, requested page, access time, and security logs, to deliver and protect the site. The privacy page does not intentionally use advertising, analytics scripts, cookies, forms, or third-party embeds.

Changes to this policy

We may update this policy when the app, service providers, or legal requirements change. The revised version will show a new update date and will be published through the privacy-policy address linked from the app and its store listing. Additional notice will be provided for material changes when required.

Contact

If you have questions about this policy or need support, contact cheymae1126@gmail.com.