Privacy policy
Effective date: 27 September 2026
This Privacy Policy describes how the LuPet mobile application (“LuPet” or the “App”) handles information. LuPet is a pet-care companion for pet caregivers. This page covers the Android version distributed through Google Play; some system backup and permission behaviour may vary by device and operating-system settings.
This policy covers the App, not this website.
1. Information you enter and how LuPet uses it
LuPet lets you create pet profiles and keep care and health records. Depending on the features you use, information you choose to enter may include a pet’s name, species, gender, birthday, weight, appearance and notes; care routines, dates and times, reminders and completion records; health measurements (such as weight, temperature or blood pressure) and notes; and files or images you attach. LuPet uses this information to show and manage your profiles, records, local reminders, reports, companion-room features and backups.
LuPet does not require an account. The app stores these records in its local app storage and does not send pet profiles, care or health records, notes, or attachments to a server operated by the LuPet developer. From version 0.4.7, LuPet uses a Firebase / Google Cloud backend solely for purchase verification, permanent purchase entitlements and refund or revocation handling, as described below. Pet records are not uploaded to this backend.
2. On-device storage, notifications and backups
Care reminders are scheduled as local notifications on your device. LuPet does not use a developer-operated push-notification server for these reminders. You can manage notification permission in your device settings.
You may choose to export a LuPet backup and then save or share it using the system file or sharing interface. The destination you select (including another app or cloud-storage provider) will handle the exported file under its own privacy terms. LuPet backup files are not password-encrypted by the App; they can contain pet profiles, records, settings and attachments, so protect the file and share it only with a destination you trust.
On Android, the operating system may include app data in its device backup and restore service, depending on Android version, device and account settings. This is controlled by the operating system and your backup settings, not by a LuPet account. Copies you export or store outside LuPet may remain there after you delete the app.
3. Advertising and privacy choices
LuPet uses Google Mobile Ads (AdMob) to display ads and Google’s User Messaging Platform (UMP) to present consent messages where required. In connection with ad delivery, measurement, security and fraud prevention, Google and its advertising partners may process information such as IP/network information, device and advertising identifiers, ad requests and interactions, diagnostic information, and consent choices. The information and purposes may vary with your location, device settings and privacy choices. Google’s services may use network information to determine a general region.
Google handles this information under its own terms and privacy practices. Learn more at Google’s partner sites and apps policy and Google’s Privacy Policy. Where the App displays a privacy-options entry, you can use it to review or change the choices offered by Google’s consent form.
4. In-app purchases
Optional appearance items are offered through Google Play Billing. Google Play processes the checkout and payment method. LuPet does not ask for or receive your full payment-card details; it receives purchase or restore results needed to provide the item and stores the unlocked appearance state on your device. Google Play’s own terms and privacy practices apply to payment and purchase processing.
The appearance pack is a one-time permanent purchase, not a subscription. First purchase and restoration require an internet connection. The App sends a Google Play purchase token, product and package identifiers, a short-lived verification challenge and a Play Integrity token over HTTPS to the LuPet purchase backend. The backend checks the purchase with Google, acknowledges it and receives Google Play purchase/refund notifications. Play Integrity processes app metadata, request binding, licensing and device-integrity information for fraud prevention; LuPet has not enabled optional app-access-risk or Play Protect verdicts.
After successful verification, the App stores a signed permanent entitlement receipt locally. It has no 30-day offline expiry. Network failure alone does not remove verified access. A confirmed refund or revocation can remove access when the App connects. After reinstalling, clearing app data or changing devices, restore the purchase online using the same Google Play account.
LuPet’s Firestore database stores a hash of the purchase token, product/package identifiers, entitlement or revocation status and timestamps. The hash is a pseudonymous purchase identifier, not anonymous data. Firestore does not store the raw purchase token, order number, Integrity token, device/account identifiers, pet records or complete entitlement receipt. Raw tokens are processed in server memory and may be present in Google Pub/Sub delivery/retry messages; application logs do not record these tokens or receipts. Google Cloud request logs may contain IP addresses, request times and user-agent information. Firebase / Google Cloud services process purchase information for LuPet; the purchase backend is configured in the United States (us-central1). Other Google services may process information in other locations under Google’s policies.
5. Sharing, retention and deletion
The LuPet developer does not operate a server that receives your pet profiles or care records. LuPet does not sell those records. Information remains in the App’s local storage while it is present on your device. You can delete records or a pet in the App; clearing LuPet’s app data or uninstalling LuPet removes local app data, subject to operating-system backup and restore behaviour. Separately saved backup files must be deleted from the location or service where you saved or shared them.
Google and its advertising partners process ad-related information as described above, and Google Play processes purchase information. Their retention and deletion practices are governed by their own policies and account controls.
Backend entitlement and revocation records have no automatic expiry, to support permanent purchases and prevent refunded purchases from being reactivated. Verification challenges expire after approximately five minutes; notification deduplication records become eligible for automatic deletion after 35 days. Database expiry cleanup is asynchronous. The purchase-notification subscription has a seven-day message-retention setting. Google Cloud’s default log bucket retains logs for 30 days; its required audit-log bucket retains applicable audit records for 400 days. Uninstalling LuPet does not delete backend purchase records or Google Play transactions.
For questions about purchase-related data or a deletion request, contact barbieclapton@gmail.com. A request may require purchase verification; records needed to maintain a purchase entitlement, prevent fraud or meet applicable obligations may need to be retained. Do not send payment-card details or passwords.
6. Security
LuPet stores its records in app-private storage provided by the operating system. No method of storage or transmission is completely secure. The App’s exported backup is not password-encrypted, so keep your device secure and take care when saving or sharing a backup file.
7. Changes and contact
27 September 2026 update: added Firebase / Google Cloud purchase verification, permanent offline entitlement behaviour, purchase-data retention and deletion-request information. Pet-record storage and existing advertising and backup practices are unchanged.
We may update this policy when LuPet or its data practices change. The latest version will be published on this page with its effective date. For privacy questions, contact the LuPet developer at barbieclapton@gmail.com.