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

Decaf Account and Data Deletion

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

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 “Decaf 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 with a relevant app control, device clear-storage control or uninstall process. Operating-system and user-created copies can have a separate lifecycle. Community caches can be refreshed from the server while signed in.

Active community profiles, content, replies, reactions, reports, notification settings, delivery records and server security records are retained while needed to operate, secure and moderate the community and then deleted, anonymised or restricted according to the applicable process. A post deleted through the app is soft-deleted on the service along with its visible replies; limited records may remain for integrity, safety, abuse prevention, backup or applicable obligations. No verified fixed production retention period is promised in this policy.

Firebase account and profile data, RevenueCat and Google Play purchase records, Google Drive archives, push delivery data and support messages follow the feature need, applicable requirements and each provider's controls. A store subscription is not cancelled by deleting local data or signing out.

The in-app Delete all data action clears core profile, check-in, symptom, settings, community-cache, queued-action and entitlement-cache tables, optionally attempts to delete Decaf Drive backups, and signs out. It does not call a Decaf API account-erasure endpoint, delete community posts or replies, delete Firebase Authentication or the Firestore profile, remove RevenueCat or Google Play records, cancel a subscription, or erase support messages. The current local wipe also does not explicitly clear the saved-post, hidden-member and custom-milestone tables. Use the device's clear-storage or uninstall controls for a full local reset, and email [email protected] for an account, community and connected-service deletion request.

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.