JobSmart Account and Data Deletion
How to request deletion and understand what may remain for JobSmart.
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 “JobSmart 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 edited, deleted, cleared with app controls or removed with app storage. Synchronized records, uploads, invoices, notification and email queues, analytics, support information, security logs, subscription evidence and operational backups remain while reasonably needed for the feature, service integrity, applicable records or a verified deletion process. No fixed production period is promised where live retention and backup evidence has not been verified.
The in-app account-deletion flow requires recent Google authentication. It first asks the JobSmart API to remove the connected account. The API attempts to remove booking upload folders and invoice files, records a deletion tombstone, removes the subscription mirror and deletes the user row; database relationships then remove associated customers, contacts, sites, bookings, push registrations, aliases, events, payment records and queued messages. File removal is best effort and can fail independently. The app then clears local tables and attempts to remove local files, preferences and the Firebase Authentication identity before signing out.
Deletion tombstones, subscription-delivery receipts, limited security or administrative evidence, protected backups, provider records, already delivered email and recipient or exported copies can have separate lifecycles. Google Play and RevenueCat purchase records are not removed by the app flow, and deleting an account does not cancel a Google Play subscription. Contact [email protected] if any step fails or if app access is unavailable.
Contact
For deletion or privacy help, email [email protected]. For general product help, email [email protected]. Website: https://bluesparrow.dev.