🕊️ BlueSparrow Labs
  • Home
  • About
  • Apps
  • Blog
  • Contact
Back to Blue Sparrow
SoloRythm

SoloRythm Account and Data Deletion

How to request deletion and understand what may remain for SoloRythm.

Updated 2026-08-24 [email protected]
PrivacyTermsDelete account
In-app option Use the deletion control shown in your current app version
Email help [email protected]
Verification A proportionate account check may be required
On this page
  1. Request deletion
  2. Retention and deletion boundaries
  3. Contact

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 “SoloRythm 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 records remain until removed through app controls, account deletion, app-data clearing or uninstalling, subject to device behavior. User-created exports remain wherever the user saved or shared them. Accessible Drive checkpoints remain until removed by checkpoint rotation, an available deletion action or Google account controls.

Operational account, device and entitlement information remains while needed to provide SoloRythm. Support messages, delivery records, security events, billing records and deletion tombstones can remain for purpose-based periods needed for support, fraud prevention, accounting, service protection or an applicable obligation. Production retention and backup-rotation schedules require operational verification before more exact promises can be made.

The in-app deletion flow always requires local deletion and reauthentication. A user can also select deletion of configured operational records and accessible Drive checkpoints. The flow then deletes local data and keys and attempts to delete the Firebase Authentication identity. If Drive deletion fails, the flow keeps sign-in access so the user can retry. Uninstalling, signing out or deleting the SoloRythm account does not cancel a Google Play subscription.

Provider logs, support communications, purchase records, deletion tombstones and rotating backups may remain for their applicable periods. Copies exported or shared by the user are outside SoloRythm's deletion control.

Contact

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

Questions about this document? Email [email protected].

Blue Sparrow website
Facebook Email Terms Privacy
© 2026 BlueSparrow Labs. All rights reserved.