Privacy Policy

This Privacy Policy describes how PulseQ collects, uses, and protects data when you use the application.

Last updated: 2026-10-19

Optional live driver location

When Transfers is enabled and current permissions allow it, the assigned driver can start sharing for an active transfer. Eligible drivers automatically receive access to record and view their own history unless an admin explicitly restricts it; another driver's history requires a separate viewing grant. PulseQ receives latitude, longitude, estimated accuracy and timestamps linked to the driver and transfer, about every 5 seconds when device and network conditions allow. Only authorized users can view the location.

Sharing requires the driver's explicit approval and location permission. Android shows an ongoing notification with Stop and can continue sharing with the screen off; a browser shares only while its tab is visible. Drivers can stop at any time. Sharing ends when the trip ends, the assignment or access changes, the driver signs out, or the session reaches its safety limit of 12 hours. After you explicitly accept automatic sharing in driver setup, taking a transfer yourself starts sharing automatically when permissions and current admin policy allow it. Consent is bound to your account, role, group/subgroup and disclosed history retention; changes require renewed approval. An admin assignment or merely opening the app does not start sharing.

Live sharing keeps only the latest point and clears it after sharing stops or the transfer ends. Separately enabled route history records GPS points, accuracy, capture and receipt times, and ordered steps only after the driver gives new explicit approval. Admins and super admins set recording, separate viewing rights and retention of 1–365 days for each group, subgroup or user. Stopping sharing stops new recording but does not erase retained history. Expired history is hidden immediately and deleted in bounded cleanup batches; cleanup can be delayed during a server outage. Increasing retention cannot recover deleted points. Protected full database backups can contain history until the backup's own retention ends. Starting, stopping and access changes are audited without coordinates. Street-map tiles load only on request and reveal the visible area to OpenStreetMap; opening an external map sends its selected point to that provider. A longer retention setting applies only after new consent; existing points never outlast the originally accepted period. Full backups are unencrypted archives and require protected storage and access.

PulseQ · Terms of Use