Privacy Policy

1. Information the app handles

• Receipt and warranty content: Photos or files you choose, extracted text, merchant and product names, purchase dates, amounts, currencies, receipt numbers, line items, notes, categories, return dates, and warranty details such as serial numbers, coverage dates, and reminders. Your documents may contain additional personal information printed on them.
• Account information: When you choose Google sign-in, Google and Firebase process your account identity, such as your email address, account identifier, and profile information supplied during sign-in. ProofKeep uses your account to associate cloud records with you.
• Local settings and usage: App preferences, reminder choices, scan fingerprints used to recognize duplicates and count free scans, synchronization metadata, and your locally cached purchase-unlock status.
• Purchase information: Google Play provides purchase status, product identifiers, purchase tokens, and signed purchase information so the app can verify, acknowledge, and restore an unlock. ProofKeep does not receive your full payment-card details.
• Technical service information: Google services may process IP addresses, device/app information, service identifiers, and diagnostic or performance information as described below.

2. Why information is used

Information is used to recognize receipt text, organize purchase records, track warranties and spending, deliver reminders, create exports, maintain optional cloud synchronization, verify purchases, and provide and protect these services. Information you send in a support email is used to respond to your request.

3. Local scanning and Google services

Receipt scanning: ProofKeep uses Google ML Kit and Google Play services for text recognition and document scanning. Image and text processing for these APIs takes place on your device. These services may download models and updates and send usage and performance metrics to Google. On-device scanning does not mean that the app or its service providers never communicate over the internet.

Optional cloud backup: Signing in enables Firebase Authentication, Cloud Firestore, and Cloud Storage. Saved receipt fields, warranty details, and receipt photos are associated with your account and uploaded for backup and synchronization. Google processes authentication and technical service information, including information needed to prevent abuse. If you use Guest mode, ProofKeep does not upload your receipt collection through its cloud-sync feature.

Payments: Google Play processes checkout and payment information under its own policies. Purchase verification and restoration require communication with Google Play.

Learn more: Google Privacy Policy, Firebase privacy and security, and ML Kit privacy information.

4. When information leaves your device

Cloud data is processed through Google/Firebase when you choose cloud sign-in. Google services also receive the technical information needed for their operation. If you export or share a PDF, image, CSV, or backup, the destination you select receives that information and handles it under its own practices. Contacting support sends the content you choose to include to the support mailbox.

The reviewed app build has no advertising SDK or separate Firebase Analytics or Crashlytics integration. This does not prevent diagnostic collection by the Google services described above.

5. Permissions and your choices

• Camera: Used when you choose to photograph or scan a receipt.
• Selected images and documents: The app handles files you select or share into it.
• Notifications: Used for reminders if you permit them.
• Network access: Used for Google services, optional cloud backup and synchronization, and purchase checks.

You can manage permissions in Android settings. You can use Guest mode, review and edit saved records, and choose what you export. Signing out stops cloud use by the app while signed out, but does not delete the existing cloud copy or local records.

6. Storage, retention, and security

Local records remain in the app's storage until removed by an app operation or by clearing app data or uninstalling. Exported files and backups saved elsewhere are separate copies and must be managed separately. Cloud records remain until removed from the cloud; clearing local app data, uninstalling, or signing out does not remove them. Google applies its own retention practices to authentication, service logs, and purchase records.

In the current pre-release build, receipt deletion can mark cloud records as deleted for synchronization while earlier record fields remain stored. Photo removal is attempted during synchronization, and failures can leave a cloud copy. There is currently no automatic full-account deletion control in the app. A permanent deletion request therefore requires manual processing as described below.

Android app storage and Google/Firebase service security controls help protect information, and cloud services use encrypted connections. Cloud backup is not end-to-end encrypted. Access also depends on the developer's Firebase configuration. No storage or transmission method guarantees absolute security.

7. Request account and data deletion

To request deletion of your ProofKeep account and associated cloud receipt data, email durrenayab665@gmail.com with the subject ProofKeep account and data deletion. Identify the Google email address used to sign in to ProofKeep. Do not send your Google password, payment-card details, or an unnecessary copy of your receipts.

The developer may need to verify that you own the account before processing the request. Sending an email does not automatically delete data; the developer must remove the corresponding Firebase account, receipt and warranty records, and stored photos. No automated deletion service or fixed completion deadline is currently implemented.

A cloud deletion request does not automatically remove local copies, exports, backups, or copies shared with other people. Deleting a ProofKeep account does not delete your Google account or erase transaction records held by Google Play under Google's policies. This pre-release request route does not replace the in-app account-deletion control still needed before public release.

8. Policy changes

This policy may be updated when the app or its data practices change. The date at the top identifies the latest revision. Any new data practices should be reflected here before they are introduced.

9. Contact