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

EventSmart Account and Data Deletion

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

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 “EventSmart 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 and files remain until changed or deleted in EventSmart, cleared through device settings, or removed with the app. Generated exports and PDFs remain wherever the operator saved or shared them and must be managed there separately.

Cloud records are retained while needed to provide the connected workspace and until deleted, subject to short-lived operational copies, security records, delivery records, backups and any retention reasonably required for an applicable obligation. Public snapshots and recipient responses remain until their workspace data is deleted; expiry or revocation stops normal link access but is not described as immediate record erasure. Provider-held identity, purchase, notification and diagnostic information follows the relevant provider's retention controls.

The in-app account-data action first requests deletion of the signed-in EventSmart backend workspace, then signs out and clears supported local database records and app files only after the backend request succeeds. It does not delete the Firebase Authentication identity, a conditionally enabled Firestore mirror, RevenueCat or Google Play purchase records, store subscriptions, Crashlytics records, already delivered emails, recipient copies or exports saved elsewhere. The backend retains limited account-deletion audit information. Current production verification is still required for physical uploaded-file cleanup and the end-to-end backend deletion transaction. Contact [email protected] for a broader request and use provider controls where direct action is required.

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.