Billnix Account and Data Deletion
How to request deletion and understand what may remain for Billnix.
This page gives cautious, version-independent instructions and repeats the retention boundaries from the current Privacy Policy.
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 “Billnix 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
Active synchronized records remain while needed to provide the account until you archive or delete individual records, complete account deletion or make an applicable request. Soft-deleted records, synchronization changes, mutation receipts, reminder jobs, delivery attempts, Telegram setup tokens, purchase-delivery receipts, security logs and deletion markers can remain for operational integrity, retry, abuse prevention and provider requirements. The audited backend does not establish a universal automatic expiry for every table, so Billnix does not promise a fixed deletion schedule for all operational records.
The in-app account-deletion flow reauthenticates with Google, then attempts server deletion, optional Drive cleanup, local cleanup and Firebase Authentication deletion in that order. A required failure stops later destructive steps so you can retry. Server deletion removes the main user row and cascades account-scoped application tables, while a limited Firebase-UID deletion marker remains to prevent accidental account recreation. The current backend reports RevenueCat customer deletion as not configured, so purchase-provider records are not removed by this flow. Google Play cancellation is always separate.
Drive cleanup occurs only if selected and authorization is still available. Local cleanup removes app-scoped database rows, reminders, preferences, caches and app-created artifacts it can identify. Uninstalling, clearing app data, revoking Drive access, deleting an account or signing out does not retrieve exports, delivered messages, provider records or copies held by another destination.
Contact
For deletion or privacy help, email [email protected]. For general product help, email [email protected]. Website: https://bluesparrow.dev.