Back to Trickee
Trickee GPS Driver

GPS Driver Privacy Policy

This policy explains how Trickee GPS Driver handles account, location, vehicle, trip, and device telemetry when an authorized driver uses the application.

Last updated 11 August 2026

1. Who this policy covers

This policy applies to the Trickee GPS Driver Android application and the services used to authenticate drivers, receive trip telemetry, synchronize offline records, and provide fleet updates. “Trickee,” “we,” and “our” refer to the Trickee product and operations team responsible for these services.

A driver may use Google Sign-In, but access to a fleet or vehicle is granted separately by Trickee or the driver's fleet organization.

2. Data we process

  • Account information: name, email address, Google account identifier, authentication status, and assigned application role.
  • Fleet and vehicle information: fleet, driver and vehicle identifiers, vehicle specifications, assignment status, and driver-entered state-of-charge information.
  • Location and motion telemetry: latitude, longitude, accuracy, speed, bearing, altitude when available, GPS availability, timestamps, and accelerometer or gyroscope summaries during an active trip.
  • Trip information: trip start and end events, route progression, distance, duration, connectivity gaps, safety events, synchronization state, and estimates derived from trip telemetry.
  • Device and service information: app version, operating-system information, device or session identifiers, notification state, request metadata, and technical diagnostics needed to secure and operate the service.

The GPS Driver telemetry pipeline does not require raw microphone recordings. Android permission prompts and any future voice feature will be described in the application before activation.

3. When location is collected

Location and motion collection begins after an authorized driver starts a trip and grants the required Android permissions. Android displays a persistent foreground-service notification while trip collection is active. Collection stops when the driver ends the trip or stops the foreground service.

Mobile networks and GPS signals are not continuously available. When connectivity is lost, records may be stored securely on the device and synchronized after connectivity returns. The service records GPS-unavailable periods instead of inventing or repeating coordinates.

4. Why we use data

  • Authenticate authorized users and enforce fleet, driver, and vehicle access.
  • Record trips and provide live or delayed fleet visibility.
  • Calculate route, range, energy, driving, and operational insights.
  • Recover telemetry after temporary network interruption.
  • Investigate errors, abuse, security incidents, and data-quality problems.
  • Meet contractual, safety, legal, and compliance responsibilities that apply to the service.

5. How data is disclosed

Driver and trip information may be visible to authorized members of the driver's assigned fleet. We also use infrastructure and identity providers, including Google services, to operate authentication, hosting, databases, storage, monitoring, and delivery. These providers process information on our behalf under their applicable service terms and safeguards.

We may disclose information when required by law, to protect users or the service, to investigate misuse, or as part of a legitimate organizational transaction with appropriate protections. GPS Driver trip telemetry is not used for third-party advertising.

6. Storage and retention

Telemetry is transmitted over encrypted connections and may be queued in protected application storage before upload. The current operational target is to retain raw GPS samples for up to 90 days. Trip summaries, assignments, derived operational records, security logs, backups, and archives may be retained longer when needed for fleet operations, contractual records, safety review, dispute resolution, or legal obligations.

Retention settings may vary by fleet agreement. When information is no longer required, it is deleted, anonymized, or isolated from ordinary use according to operational and backup schedules.

7. Security

We use access controls, scoped service identities, encrypted transport, authenticated APIs, restricted infrastructure access, and operational monitoring. No system can be guaranteed completely secure, so drivers should report suspected account or device compromise promptly.

8. Your choices and requests

  • You can deny or revoke Android location and notification permissions, although active-trip features may then stop working.
  • You can end a trip to stop its foreground location collection.
  • You can request access, correction, deactivation, or deletion by contacting your fleet administrator or Trickee.
  • Some records may be retained when required for security, contractual, legal, or legitimate fleet-operation purposes.

9. Children

GPS Driver is an operational fleet application intended for authorized adult drivers and fleet personnel. It is not directed to children, and users must meet the driving, employment, and age requirements that apply in their jurisdiction.

10. Changes and contact

We may update this policy when the application, infrastructure, or legal requirements change. The revised date will be shown at the top of this page. Material changes may also be communicated through the application or fleet administrator.

Privacy requests: privacy@trickee.co.in
General support: support@trickee.co.in