SiteLog Account and Data Deletion
How to request deletion and understand what may remain for SiteLog.
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 “SiteLog 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. Synchronized records and files generally remain while needed to provide the account and for limited periods afterward for deletion processing, security, service recovery, backup rotation, support, billing records or other valid operational needs. Exact public-access, log and backup schedules can vary by record and production configuration.
The in-app deletion flow requests deletion of the SiteLog backend account, clears local Drift data and signs out. Backend deletion removes database records through relationship cleanup and attempts to remove associated uploaded files after the database change. File cleanup is best effort and residual copies can persist temporarily in backups or provider systems.
The current flow does not itself delete the separate Firebase Authentication identity or cancel a Google Play subscription. Users should manage subscriptions in Google Play and can contact [email protected] for identity or residual-data assistance. Provider security logs, support communications, purchase records and backup copies follow their applicable retention rules.
Contact
For deletion or privacy help, email [email protected]. For general product help, email [email protected]. Website: https://bluesparrow.dev.