App location tracking and data use
Tourfold can use a mobile app's location to show where a Device is and, when configured, update a connected Vehicle's position. Collection is controlled by workspace policy, the Device's settings, operational context and the operating system's location permission. A signed-in user and an enrolled or paired Device are separate identities: signing out does not necessarily stop a Device configured for continuous tracking.
This page explains what is collected, when collection runs and what happens when connectivity is interrupted. Workspace administrators should explain the chosen settings and intended use to the people carrying the Devices before enabling tracking.
Choose when collection is allowed
Administrators with permission to update Devices can set App location tracking under Settings → Devices → Policy. This is the workspace default. When creating or editing a Tourfold app Device, choose Inherit (currently …) or an explicit policy for that Device:
| Policy | Behavior |
|---|---|
| Disabled | The app stops collecting location. Non-location Device telemetry can still be sent. |
| During work | Location is collected only when the backend confirms eligible work and the app has the corresponding active work context. |
| Continuous | Location can be collected independently of an active Tour or user session while the app and OS permit it. |
For standard Tours, work eligibility is based on the participating user's actual in-progress Tour. Planning a Tour or opening its screen does not by itself authorize tracking. Assignment of a Vehicle to a Tour is a separate roadmap item; do not assume that a Vehicle assignment currently determines standard Tour eligibility.
An inherited policy follows future changes to the workspace default. To remove an override, edit the Device and choose Inherit. An explicit override takes precedence even when the workspace default is Disabled; that default is not a workspace-wide emergency stop. These controls do not configure independent GPS trackers or connected-car providers.
The Device details show the effective policy, whether it comes from the workspace or a Device override, and the last reported tracking mode separately. A configured policy allows collection; it does not prove that GPS is currently running. The reported mode may be older than the current setting, so check the last report time. Permission problems, lack of eligible work, authentication or an unsupported app build can prevent collection. Update unsupported app builds before relying on background tracking.
OS permission is an additional requirement: an administrator's policy cannot grant or restore a permission that a person has denied in the phone or browser settings.
How the app learns the policy
A new or unknown Device context first obtains a current decision from Tourfold. Afterward, normal telemetry responses include the current policy, so the app does not need a separate periodic policy poll. Telemetry without coordinates continues when GPS is disabled, allowing the app to discover later policy changes. Resuming the app or reconnecting prompts a refresh.
The client policy has no fixed five-minute expiry. If a request temporarily fails, the app keeps the last successful decision for the same context. A Device or workspace replacement requires a fresh decision. Changes to a during-work context invalidate its earlier collection decision; continuous tracking is independent of that work context.
The server checks every reported location against the current policy and verified work before storing it. If collection is no longer allowed, that fix is discarded and the response tells the app to stop GPS. An in-flight request, a lost response or an offline phone can delay the app learning a change. This means GPS may continue to run locally for a time after a remote policy change, even though the server will reject locations that are no longer allowed.
What is sent and stored
An app location observation contains latitude, longitude, the time the OS measured the position and, when available, an accuracy estimate. Measurement time is separate from the time the report is sent. A position is an estimate, not proof of a person's precise whereabouts.
The server accepts clock skew of up to five minutes into the future, measured against the time it first receives the report. A future timestamp does not mean a future location: its effective time is capped to that original receipt time. For example, if a report arrives at 10:00 with a measurement time of 10:03, the position is recorded at 10:00. The raw 10:03 timestamp is retained for diagnostics. Device state, history, Vehicle positions and ELOG all use the same effective time; internal retries do not move it forward.
Fixes more than five minutes ahead of receipt, more than five minutes old, or without a measurement timestamp are discarded. These are data-quality limits, not a five-minute tracking session limit. During-work intake checks the effective time and rejects measurements from before the relevant work or Device-user association began.
Independent telemetry can include battery level, charging state, Device model, operating-system and app version information. It does not need coordinates. Discarding a location does not discard valid non-location telemetry from the same report. The app does not persist an offline GPS backlog for later upload; failed observations are dropped and later reports use fresh observations.
Accepted telemetry updates Device state and history. Updating a Vehicle additionally requires an appropriate active connection and location-source configuration. The Device and Vehicle can therefore have different last-known positions. Disconnecting a Device or disabling tracking does not erase an already stored position or history. The last position retains its observation time and can become stale; it must not be presented as a guaranteed live position. See Vehicle connections and location.
Native app and browser behavior
| Installed iOS/Android app | Mobile app in a browser | |
|---|---|---|
| Location provider | Native OS location services | Browser geolocation |
| Credential renewal | Native Device credential storage and renewal | Browser authentication runtime |
| Policy updates | Native telemetry responses, including while permitted background tracking runs | Telemetry responses while the page can execute |
| Background limits | Subject to OS permissions, suspension, force-stop and power management | Subject to tab suspension, browser permissions and page closure |
Android uses a location foreground service with a notification. iOS uses background location updates with a visible system indicator. A session started while the app is open can continue with “While Using the App” permission; “Always” permission is not required for that session. Neither platform can guarantee uninterrupted operation after force-stop, permission withdrawal or OS intervention. When GPS is stopped and the OS suspends the app, background heartbeats and automatic restart are not guaranteed; reopening the app refreshes its decision. A browser page cannot promise the same background behavior as an installed app.
Access-token expiry remains separate from policy. The app renews short-lived credentials; it does not extend or ignore an expired token. Legacy-login Devices use their access/refresh token pair. Keycloak-enrolled Devices obtain tokens using their enrolled signing key. Native credentials use Android Keystore-backed protection or iOS Keychain storage; browser keys stay in the browser's non-extractable WebCrypto key store. A rejected Device credential ends the native tracking runtime until authorization is restored.
Data-use decisions for your workspace
Before enabling tracking, decide and communicate:
- The operational purpose, affected Devices and intended collection periods.
- Whether continuous collection is appropriate, including outside working hours or after user logout.
- Which workspace roles may view Device information, Vehicle positions and history.
- How long history should be kept and which deletion procedures apply to your deployment.
- Whether external integrations receive location data and for what purpose.
Turning tracking off prevents new collection once the app learns that decision; it is not a history deletion operation. This feature does not establish a universal retention period. Confirm your workspace's configured retention and access arrangements rather than assuming that disabling GPS automatically removes previously accepted data.
Enterprise operational rules
For enterprise customers, Tourfold can adapt the conditions that determine eligible work and the routing of accepted observations. Potential rules include duty status, an active assignment, organizational-unit settings or a dedicated operational workflow. Integrations can apply additional conditions before forwarding data to an external system.
These rules require an agreed design and implementation; they are not all standard settings. They should make collection conditions understandable, preserve the server's per-report checks and clearly distinguish collecting a Device's position from updating a Vehicle or sharing data with an external service.