PackCue Policy · Release candidate

PackCue for Android

Privacy Policy

This policy explains what PackCue keeps on your device, what may be processed by optional online services, and the choices available to you.

App name
PackCue
Android package
com.leon.packcue
Effective date
July 28, 2026

1. Summary

Your private trip content is local. Destinations, dates, checklist text, progress, map selections and alarm settings are used on your device.

No developer/private server. PackCue does not upload your private trip content to a PackCue or developer-operated server and does not run account, cloud-sync or trip-sharing infrastructure.

Some provider metadata may leave the device. Production ads, consent, Remote Config and map delivery can process technical data as described below.

This website does not track you. The static PackCue website uses no analytics scripts, advertising scripts, cookies or form backend.

2. Who operates PackCue

This policy applies to the Android app PackCue, package name com.leon.packcue. PackCue is published by LeonWang.

Privacy and data inquiries: wfkakathy@gmail.com.

3. Information stored on your device

PackCue stores the information needed to provide its features locally, including:

  • trip destination, dates, duration and selected city coordinates;
  • trip type, expected climate, companions, transport and laundry preference;
  • generated and custom checklist items, quantities and completion state;
  • travel-footprint places and visit dates;
  • appearance, language, reminder and widget settings;
  • trips received through a user-initiated local share.

All user-created and private trip content is used locally. PackCue does not upload this content to a PackCue, developer-operated or other private server. PackCue opts out of Android cloud backup and explicitly excludes app data from system backup and device-transfer extraction. A trip leaves the app only when you deliberately use Android sharing or NFC with a destination you select.

4. Information processed by online services

When production services are configured and applicable consent permits them, the following providers may process data off-device:

Service Possible data Purpose
Google Mobile Ads and UMP Consent state, device/app identifiers, approximate region, ad requests and interactions, diagnostics Consent, ad delivery, fraud prevention and measurement
Firebase Remote Config Firebase installation identifier plus app, device and request metadata required by the SDK; no trip content Retrieve non-secret feature, ad-frequency and allowed shopping-link configuration
OpenFreeMap and delivery infrastructure Map requests and ordinary connection metadata; temporary IP logging may occur during security incidents Deliver map styles and tiles, maintain service security

PackCue's AnalyticsTracker remains on-device. PackCue does not directly declare the Firebase Analytics SDK, and Firebase Analytics collection is explicitly deactivated in the Android manifest as defense in depth. PackCue does not upload product funnel events, destination names, dates, trip-profile choices, checklist text or state, custom labels, raw shopping keywords, selected map coordinates, reminders, share payloads, contact details, credentials or other free text for analytics.

Provider details: Google Privacy Policy, Firebase privacy and security, and OpenFreeMap Privacy Policy.

5. Maps

PackCue does not request your device location. You type the destination and, if you choose, select a city position on the map. Displaying a map downloads style and tile resources from OpenFreeMap infrastructure.

OpenFreeMap states that its regular server logs are anonymized and do not include IP addresses, while temporary IP logging may be enabled for up to 30 days during security incidents. Its delivery providers may have their own data practices. Review the linked provider policy for current details.

6. Notifications and exact alarms

If you enable a departure alarm, PackCue asks for notification access and Android's user-granted Alarms & reminders access. It schedules an exact local alarm for the time you selected. While ringing, an on-device foreground service can play the alarm sound, vibrate, keep the processor awake and show a stop action. Ringing ends when dismissed or after a ten-minute safety limit.

Android 14 and later can offer a separate setting for lock-screen full-screen display. If unavailable, Android may limit the presentation while retaining the behavior the operating system permits. Alarm configuration and trip text are not uploaded to a PackCue server.

7. Local trip sharing

Sharing begins only when you choose it. PackCue uses Android's share sheet, local attachment handling or NFC host-card emulation. PackCue does not upload the trip to a PackCue sharing server. The receiving app, device transport or nearby-sharing service may process the attachment under its own terms.

8. Shopping and affiliate links

Shopping actions appear only in Buy and open an external browser or Amazon app. Amazon and the browser handle later activity under their own policies. Some links may be affiliate links, which can generate a commission from qualifying purchases without changing the price you pay.

PackCue records coarse link-open events only in its on-device tracker. It does not upload the item text, raw search query or product event to Firebase Analytics or a PackCue/private server. Amazon and the browser may process the URL you open.

9. Ads, consent and choices

PackCue requests updated consent information through Google UMP at each launch and shows a consent form when required. Ads are requested only when UMP reports that they may be requested. Debug builds use Google's official test ad IDs.

In regions where Google requires a persistent privacy-options entry point, the production build will not be released until that entry point is restored and verified. You may also use applicable Google and Android advertising controls.

10. Sharing of information

PackCue does not sell locally stored trip or checklist content. Data processed by Google services may be shared with Google and advertising or measurement partners according to consent, service configuration, applicable law and Google's terms. User-selected Android sharing sends the selected trip only to the destination you choose.

11. Retention, deletion and your choices

  • Local trip data remains until you delete it, clear PackCue storage or uninstall the app.
  • You can use the packing workflow without notification, exact-alarm, full-screen alarm or NFC access.
  • PackCue opts out of Android cloud backup and app-data extraction for device transfer.
  • Firebase Remote Config installation/request metadata and Google Ads data follow final production account settings and provider policies.
  • PackCue has no user account, so there is no PackCue account-deletion flow.

Requests concerning production advertising or Firebase Remote Config data must be sent to wfkakathy@gmail.com. The publisher must establish and document this process before release.

12. Security

Production network connections for included Google SDKs, maps and external shopping links use HTTPS. Private trip content stays in Android private app storage and is excluded from system backup/data extraction. No storage or transmission method can be guaranteed completely secure.

13. Children

PackCue is not designed for children. The intended Google Play audience is adults. The publisher must confirm the final target-audience and advertising settings before release.

14. Changes to this policy

This policy may change when PackCue's features, SDK configuration, providers or legal obligations change. The effective date at the top of this page will be updated when a revised policy is published.

15. Contact

Developer / publisher: LeonWang
Privacy contact: wfkakathy@gmail.com

← Back to PackCue