Privacy Policy

Effective date: September 23, 2026

BuyCue is an offline-first purchase-memory, restock, and replacement utility. This policy explains what information the app stores locally and what information may be processed by third-party services used for analytics, crash reporting, and advertising.

1. Information stored on your device

BuyCue lets you save product names, brands, sizes or amounts, prices, currencies, stores, purchase dates, purchase history, notes, product photos, item type, estimated cycles, and reminder settings. This information is primarily stored locally on your device using an on-device SQLite database and local files.

BuyCue does not currently provide accounts, login, cloud synchronization, a proprietary backend, or family cloud accounts. BuyCue does not upload this product content to a BuyCue-operated server.

2. Third-party services

The app includes Google Firebase Analytics, Firebase Crashlytics, Google AdMob, and Google's User Messaging Platform (UMP). These services may automatically process technical and usage information as described by Google. Their handling of information is governed by Google's applicable terms and privacy policies.

3. Analytics

Firebase Analytics helps us understand general app usage and feature adoption. It may automatically process app-instance or advertising identifiers, coarse location derived from masked IP addresses, app lifecycle information, screen or session activity, and feature interaction events.

BuyCue's developer-defined analytics events are limited to non-content categories such as item type, selected filter, theme, locale, and whether a setting is enabled. They do not include product names, brands, stores, notes, photo paths, or prices.

4. Crash reporting

Firebase Crashlytics helps diagnose crashes, non-fatal errors, and application-not-responding events. It may process stack traces, relevant application state, device metadata, diagnostic information, installation identifiers, and Analytics breadcrumb events. BuyCue does not intentionally attach saved product content or free-text user identifiers to Crashlytics reports.

5. Advertising

BuyCue displays banner and native advertisements using Google AdMob. The Google Mobile Ads SDK may process and share IP addresses, approximate location derived from IP address, product interactions, diagnostic information, advertising identifiers, app-set identifiers, and other device or account identifiers for advertising, analytics, and fraud-prevention purposes. BuyCue does not send saved product names, brands, stores, notes, prices, or photos to AdMob as advertising-targeting parameters.

BuyCue uses Google User Messaging Platform (UMP) as its consent management platform. In regions where consent is required, including where applicable the European Economic Area, the United Kingdom, and Switzerland, UMP may display a consent form. You may consent to, refuse, or manage applicable advertising privacy choices. When Google requires an ongoing privacy entry point, BuyCue provides Privacy Options in Settings. BuyCue loads advertisements only after UMP reports that the app can request ads. In regions where consent is not required, ads may load normally.

Ad availability and personalization may depend on your region, device settings, consent choices, and Google's advertising controls. The advertising SDK may also use the Android Advertising ID, App Set ID, Android Privacy Sandbox Ads APIs, and Google Play Install Referrer information, subject to platform availability, your device settings, consent choices, and Google's policies.

6. Data retention

Locally stored product and purchase information remains on your device until you delete individual records, clear app data, or uninstall the app. When you delete a product, BuyCue also attempts to delete its app-private product image if no other product references that image. Shared or exported images remain wherever you save or send them and must be deleted from those locations separately.

Retention of Firebase and AdMob data is controlled by the corresponding Google service settings and policies. We may adjust available retention settings in the relevant service consoles.

7. Your controls

You can edit or delete products and purchase records inside BuyCue. You can remove locally stored app data through Android settings or by uninstalling BuyCue. You can disable notification permission in Android settings and manage advertising identifiers or ad personalization through your Google and Android settings. Where required by Google UMP, BuyCue also provides Privacy Options in Settings so you can review or change applicable advertising privacy choices.

For questions or requests concerning third-party data associated with BuyCue, contact us at amiworks.dev@gmail.com. Some data may be controlled directly through Google account or device privacy settings.

8. Device permissions

• Notifications, wake locks, and vibration, to support locally scheduled restock or replacement reminders and relevant SDK operation. BuyCue uses inexact local scheduling and does not request exact-alarm permission.
• The Android system camera intent or Photo Picker, when you choose a product photo. BuyCue does not directly request the CAMERA runtime permission and does not request broad access to read your photo library. These system experiences are initiated only by your action.
• Photos or media storage, to save a share card; older Android versions may require legacy write access.
• Internet and network state, for Firebase and AdMob.
• Boot-completed access, to support scheduled reminders after restart.
• Advertising ID, App Set ID, Android Privacy Sandbox Ads APIs, and Install Referrer access, which may be used by Google advertising, analytics, attribution, diagnostics, or fraud-prevention services subject to consent, platform availability, and device settings.

Core product records remain usable if network services are unavailable. Denying an optional permission only affects its related feature.

When you create a Share Card, it may contain a product photo, product name, size or amount, price, store, and note, depending on the options you select. This content is sent outside BuyCue only when you actively tap Share and choose a third-party app. Further processing is governed by the privacy policy of the third-party app or service you select.

9. Children's privacy

BuyCue is a general-consumer utility and is not directed to children. We do not knowingly design the app to solicit personal information from children. Contact amiworks.dev@gmail.com if you have a concern.

10. Changes to this policy

We may update this policy when the app, third-party services, or legal requirements change. The updated policy will show a revised effective date.

11. Contact

Developer email: amiworks.dev@gmail.com