Upkeeva privacy notice

Who is responsible

Upkeeva is operated by WizPlayo. For any privacy question or request, write to wizplayo.developer@gmail.com. There is no Upkeeva account, so we do not hold a profile about you.

Support correspondence is separate from the app. If you email the published address, WizPlayo receives your email address and the message you choose to send, and uses them to reply and follow up. Email providers (ours is Gmail) process the messages under their own policies (Google Privacy Policy). Privacy and deletion requests are made through the same address.

What stays on your phone

Your homes, devices, care plans and care sessions, maintenance history, costs and warranty details, tracked parts, issues with an optional repair contact that you type, shopping items, general home tasks with their history, notes and preferences are stored locally, in the app’s private storage on your phone. Photos, receipts and manuals that you select (PNG, JPEG or PDF) are copied into that private storage as attachments, and an issue can have an optional image. Upkeeva has no account and no Upkeeva cloud sync, and it does not upload this content. It has no broad access to your photo library, camera, address book or location.

We have not added any advertising or behavioral analytics SDK. Google Play, Android and the Google Play Billing library on your phone may still process technical diagnostics and metadata under Google’s own policies, which Upkeeva does not control. See: Google Privacy Policy.

Exports and Android backup

Export: Backup and restore lets you export a JSON file to a place you choose. Upkeeva does not encrypt that file, and it can contain household details, personal notes and the bytes of your private attachments. It does not include Lifetime Premium, entitlements or exported settings. Where you save it, including any cloud file provider, is your choice and is governed by that provider’s terms. If you open or export an attachment with a viewer, app or provider you choose, that one may receive the selected file. Deleting Upkeeva’s app storage or uninstalling the app does not delete exported files, copies held by a provider or copies made by Android.

Android backup: Android’s own backup and device transfer may include Upkeeva’s local household data and files, depending on your settings and your phone maker. Upkeeva’s backup rules exclude only its private Premium verification folder (databases-premium). We still have to confirm in release testing that these rules behave as intended, and we cannot guarantee that every phone maker honors them. Upkeeva does not promise encryption, deletion or sync on every platform.

Notifications

Reminders are your choice and stay off until you turn them on. Care reminders are scheduled on your phone from the care dates you saved, and warranty end alerts, if you turn them on, from the warranty end dates you saved. The normal Android notification permission is requested only after you turn reminders on. General home tasks and shopping items are in-app only and never send notifications. Upkeeva does not use exact alarms or a battery-optimization exemption, so Android may deliver a reminder late. Reminder content stays on your phone.

Lifetime Premium purchase check

Availability: purchase verification can be switched on or be unavailable, and the app reports whether it is available. This section describes what happens when it is used; it does not mean a purchase is available to you.

When verification is used and you buy, restore or re-check Lifetime Premium, the app sends five items over encrypted HTTPS to Upkeeva’s verification service: the app package name, the product ID, the Google Play purchase token, a random installation ID and a one-time request nonce. The service asks Google Play to verify the purchase and acknowledges it. No household content is sent. Upkeeva does not receive payment-card data: Google handles payment under its own policies (Google Play Terms of Service), and refunds follow Google Play refund help.

Purchase ledger: the service keeps one record per purchase with a SHA-256 digest of the purchase token (not the token itself), the app and product identifiers, the purchase state, whether it was acknowledged and the time of the decision. It supports the Lifetime purchase and prevents reuse of a refunded purchase. There is no automatic expiry and no automated deletion endpoint: records are kept while they are needed for purchase validation, and privacy requests are handled through wizplayo.developer@gmail.com.

The random installation ID and the nonce tie a request to its answer and support rate limiting; rate counters are short-lived and held in the service’s memory.

Signed proof: the signed proof of your purchase is stored privately on your phone, separately from household records and exports. Offline, the app relies on the last verified proof. A refund is learned only when the app next checks online (at start, on return to the app or when you choose Restore purchase); there is no immediate push when a purchase is refunded.

Temporary tester access

Availability: tester access exists only in builds that include it and only while the operator has switched it on; the app reports whether it is available. If a build enables it, it works as described here. It is temporary, costs nothing and is separate from the Lifetime purchase.

When you enter a tester code, it is sent once over encrypted HTTPS with the package name, the random installation ID and a nonce. The service compares only a digest of the code with a digest kept as a secret; the raw code is not kept on your phone, in the database or in logs. To renew access the app sends the signed access record, the package name, the installation ID, a nonce and the campaign it belongs to. Access lasts at most 24 hours and never beyond the end of the campaign. The app checks when it starts, when you choose Check again and when you return after at least 30 minutes. Access is not ended immediately while you are offline. Changing the code alone does not end access already granted; ending or replacing the campaign does, at the next online check. When tester access ends, your saved records are kept.

App review access

Status: app review access is off unless a build includes it and the operator switches the service on. It lets a person reviewing the app open the paid features for a limited time without buying anything. It is the same page and behavior for everybody, it does not recognize reviewers, accounts or devices, and it is not a purchase.

When the review code is entered, it is sent once over encrypted HTTPS with the package name, a random installation ID and a nonce. The service compares only a digest of the code with a digest kept as a secret; the raw code is not kept on your phone, in the database or in logs. It answers with a signed access record tied to that installation, valid for at most 24 hours. That record, the installation ID and the latest time seen are stored privately on your phone, separately from household records and exports, and are excluded from Android backup. To renew, the app sends the signed record, the package name, the installation ID and a nonce when it starts, when you return to it and while it is open before the 24 hours end.

The code itself does not expire. The operator ends or replaces access by changing the service settings, which the app learns at its next online check; offline, access ends at the latest when the signed record expires. The service keeps short-lived request counters in memory to limit repeated guesses and, like the other services, runs on Cloudflare Workers (see the hosting section). Nothing about your devices, homes or care history is sent, no purchase is made or recorded, and your saved records stay when access ends.

Hosting and service providers

The verification, tester and public-page services run on Cloudflare Workers, and the purchase ledger is stored in Cloudflare D1. Whenever the app or your browser contacts these services (including when you open this page), Cloudflare can see technical metadata such as the IP address, network details and request (invocation) information. Upkeeva’s own code does not log request bodies, purchase tokens or tester codes. We do not claim that Cloudflare keeps no logs: its retention is set by Cloudflare, so please read Cloudflare Privacy Policy and Cloudflare Workers Logs documentation, as retention periods can change.

Links on this site lead to other organizations. They are contacted only when you open them and have their own policies.

Your choices and requests

You can turn reminders off in Settings › Notifications and block notifications in Android settings. To keep your records before clearing app storage, export a backup first.

To ask about, correct or delete information we may hold (for example a purchase ledger record), write to wizplayo.developer@gmail.com. We handle such requests individually and do not promise a fixed response time or an automated process.

If this notice changes, the effective date at the top changes. For help using the app, see Upkeeva support.