Privacy Policy
Warranty Vault: Receipts
1. Overview
Warranty Vault: Receipts is an offline-first utility that does not require an account. The checked-in Android app source stores the records you enter on the device and has no app-record cloud-sync path. Optional campaign notifications and, when configured, Google Play purchases use service providers described below. This review covers the local source only; it does not verify a currently published binary or provider-side retention settings.
2. Information You Enter
Product and brand names, serial numbers, purchase and warranty dates, prices and retailer details, support contact information, extended-warranty status, and notes. A claim-pack PDF may contain the information for the selected item. These records are stored in app-private local storage in the checked-in source. The app does not send these records to a developer-operated account or sync service.
Reports or PDFs are generated on the device. They leave the app only if you choose to print, save, or share them; after that, the chosen destination app or recipient handles its copy.
3. Campaign Notifications, Purchases, and Advertising
Campaign notifications. The app includes optional Firebase Cloud Messaging (FCM) campaign notices. In the checked-in source, FCM auto-registration is disabled until you opt in and allow Android notifications. If enabled, Firebase processes a device registration token, app/category/portfolio topic subscriptions, and delivery data to route notices. Your locally stored app records are not included in campaign targeting. Turning campaign notices off asks the app to unsubscribe from topics, disable FCM registration, and delete its token; provider-side retention after those requests is not established by client source.
Purchases. The source includes Google Play Billing code for a one-time Pro product, but purchase availability depends on build configuration and the Play listing. If enabled, Google Play handles payment. To verify an entitlement, the app can send the package name, product ID, Play purchase token, and purchase source to the verification endpoint configured for that build. The app does not receive payment-card details. The endpoint and its retention or deletion settings have not been confirmed in this static review.
Advertising. No Google Mobile Ads SDK or ad-loading placement was found in the checked-in app dependency lockfile or Dart source. The Android manifest retains an AdMob application ID. Whether an older or currently published binary displays ads was not verified, so the production release must be checked before relying on this source-based statement.
4. Android Permissions
The checked-in app manifest declares Android POST_NOTIFICATIONS for campaign notices. It does not declare camera, photo/file, contacts, location, or microphone permissions. Library-added permissions in a final merged release manifest were not checked. These statements describe the app's checked-in main manifest, not the final merged release manifest.
5. Data Retention and Deletion
Delete individual records using the app's available delete controls. Clearing the app's storage in Android Settings or uninstalling the app removes its app-private local data. A report or PDF already saved or shared outside the app must be removed from that destination separately.
Turning campaign notices off requests FCM topic removal and token deletion. Purchase-verification data, Firebase messaging data, and other provider-held copies are outside the app's local storage; their server-side retention and deletion were not confirmed by this source review. Contact the relevant provider or the support address below with a data request.
6. Children's Privacy
The application is designed for a general adult audience and professionals (target audience 18+). We do not knowingly solicit or collect data from children under the age of 13.
7. Policy Updates
Any future revisions to this privacy policy will be posted on this page with an updated modification date.
8. Contact Us
If you have questions regarding this privacy policy or data practices, please contact developer support at raghebchess2005@gmail.com.