DigiWell 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 “DigiWell 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 wellness records remain until you remove relevant records, clear app storage, uninstall or complete account deletion with local data selected. Soft-deleted records and reminder history can remain in the local database and checkpoint until replaced by later data or the selected data scope is removed. User-created exports have the lifecycle of their chosen destination.

Active operational account, device, access, delivery and security records remain while needed to provide and protect connected features. The checked-in service does not establish a verified production purge schedule for every table, log or database backup, so this policy does not promise a fixed period.

The in-app account-deletion flow first asks for fresh Google confirmation. If selected and available, it marks the Blue Sparrow operational account deleted, clears its verified email and push token, removes current service entitlement detail, disables devices and cancels pending delivery. It retains limited account and deletion state, including the Firebase identifier and a deletion tombstone, to prevent unintended recreation or subscription reactivation. Some delivery, security, provider, accounting and backup records may remain where needed or controlled by a provider.

The flow can also attempt to delete accessible Drive checkpoint files when you select that scope, cancel local reminders, remove the encrypted local database and keys, and delete the Firebase Authentication account. Required steps stop on failure so you can retry without silently claiming an incomplete deletion. Google Play subscriptions are not cancelled, RevenueCat or Google Play records are not directly erased by this flow, and provider backups may take additional time. Manage any store subscription separately and contact [email protected] if the in-app flow is unavailable or you need help with remaining service information.

Contact

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