ProofPocket Account and Data Deletion

Request deletion

• Use any account or data deletion control currently presented inside the app. Labels and placement can change between versions, so this page does not prescribe an exact navigation path.
• If you cannot use the app, email [email protected] with “ProofPocket deletion request” in the subject. If an account exists, write from its associated email address where practical.
• Do not send passwords, authentication codes, identity documents, customer records or other unnecessary sensitive content. Blue Sparrow may ask for proportionate verification before acting on connected records.
• Removing connected records does not retrieve exports, delivered messages, recipient copies or files already shared outside the app. Device-only copies may need to be removed separately.
• Account deletion does not cancel a Google Play subscription. Manage cancellation separately through Google Play.

Retention and deletion boundaries

Local archive data remains until you delete individual records, sign out through a flow that clears the device, complete account deletion, clear app storage or uninstall in a way that removes app data. Android system cloud backup and device-transfer extraction are disabled for ProofPocket. Exported, printed and recipient copies have independent lifecycles.

Drive checkpoint and recovery objects remain until retention cleanup or successful explicit deletion. Standard checkpoint retention is one for Free and up to five for Premium. Portable recovery uses its own rolling retention process. Because cleanup is best effort, older encrypted objects can temporarily remain. Firestore profile data remains while needed for account and entitlement features until deleted through the verified flow or another applicable request.

Crashlytics reports, Google Play and RevenueCat purchase records, support messages and provider security records follow the relevant feature need, applicable requirements and each provider's controls. Deleting ProofPocket does not cancel an active Google Play subscription.

The in-app account-deletion flow is designed to fail closed before identity deletion if required cleanup cannot complete. It attempts to delete portable recovery objects, standard Drive backups, Drive sync data, the Firestore user document, local recovery profile, local database, attachments, preferences and encryption keys, and then the Firebase Authentication account. Google session and RevenueCat session cleanup follow. A recent Google sign-in may be required, and Google Play subscription cancellation remains a separate action. Provider billing records, prior exports, recipient copies, support records and records required under applicable obligations are not automatically erased by this device flow.

Contact

For deletion or privacy help, email [email protected]. For general product help, email [email protected]. Website: https://bluesparrow.dev.