Privacy Policy
NeatShift
Privacy Policy
NeatShift saves data on your device. It can also sync data to your private iCloud storage, independently of household sharing. Sharing gives access to the members you invite.
Android
On Android, tasks, household members, availability, vacations and completion history are stored locally on your device. No NeatShift account is required and the household does not synchronize between devices. Removing the app removes its local database. A PDF you choose to share is sent to the app or recipient you select; that recipient manages its copy.
Google Play handles Android purchases and acknowledgments. In Android versions with server-side purchase verification, the app sends the signed Google Play purchase JSON and signature over HTTPS to a Cloudflare Worker operated for the developer. The receipt may include the app and product identifiers, purchase token and order information. The Worker uses the purchase token to check purchase or subscription status and, for subscriptions, expiry with Google. These checks can occur after a purchase, during restoration, or when the app starts or resumes with an owned purchase. The app does not receive your payment-card details.
The Android client keeps recent verification results and access deadlines in memory. In versions with a restart cache, a private copy of a PRODUCTION verification result and a hashed purchase identifier can also be kept on your device. This copy can be reused for at most 60 seconds after reception, never beyond Google’s subscription expiry, and is refused after a device reboot or inconsistent elapsed time. TEST verification results stay in memory only. The one-time Pro purchase is also rechecked with Google; its verification result stays in memory only and does not use the subscription restart cache. Signed purchase receipts, signatures and raw purchase tokens are not saved to disk. The receipt-verification request does not include household tasks or member data. The Google Play Billing SDK also sends technical diagnostics to Google to support reliability. See Google’s privacy policy and Cloudflare’s privacy policy for these providers’ data practices.
The optional support form sends the app name, support subject, chosen category, reply email address, any app and operating-system versions you enter, your message, and an anti-spam field to Cloudflare Workers for validation. The request is then forwarded to the developer’s support inbox. This information is used to respond to your request and maintain the app, not for advertising.