Traccar Client sends device location reports to a configured tracking server. It is provided by Tananaev Solutions, identified in our Terms of Service. For privacy questions, contact support@traccar.org. Our main Privacy Policy also covers support and hosted services.
When tracking is enabled and the necessary permissions are granted, the app collects precise location, including in the background. Reports can include a device identifier, timestamps, coordinates, accuracy, speed, direction, altitude, battery status, and related tracking information. The receiving server also receives connection information such as your IP address.
Motion or activity recognition helps adjust tracking when the device is stationary or moving. In versions that report activity types, those types are sent with location reports. This can be classified as health-related data by app stores; the app is not a medical or fitness service. Versions with optional Bluetooth beacon detection can also report nearby beacon identifiers when that feature is enabled.
Settings and, when buffering is enabled, pending location reports are stored on the device to support tracking and delivery when connectivity returns.
Reports go to the server configured in the app, which may be operated by us, your organization, or another provider. Check the server address before enabling tracking; the default configuration may point to a Traccar demonstration server. The operator controls access, sharing, and retention on that server. Users authorized by the operator may be able to view your location.
Installing the app does not require a website account or payment details. A separate account may be needed to view data on the chosen server. For servers operated by others, consult their privacy notice; we cannot delete data they hold.
Distributed builds using Google Firebase include Analytics, Crashlytics, and Cloud Messaging. These services process app interactions, installation identifiers, device and operating-system information, crash reports, and diagnostic events to help us understand usage, fix errors, and deliver notifications or commands. Their processing is separate from sending location reports to your configured server.
The app sends its notification token to the configured server to support remote commands. See Firebase's privacy information for Google's processing and retention practices. Google may process data outside your country.
You can stop tracking in the app, revoke location or activity permissions in device settings, or uninstall the app. Stopping tracking does not necessarily stop diagnostics while the app remains in use. Server commands may start tracking where the app and permissions allow it.
Stopping or uninstalling the app does not delete reports already sent to a server. Request access, export, or deletion from its operator. Local settings and buffered reports can be removed through the device's app-data controls where available. Diagnostic retention depends on the Firebase service and configuration; it is separate from tracking-server retention.
Our main Privacy Policy explains legal bases and rights for information we process, including how to request access or deletion, withdraw applicable consent, and complain to a data protection authority. The tracking operator is responsible for the lawful basis and notices for its tracking activity. Permission to access location is not permission to track another person unlawfully.
Use a trusted server and HTTPS where supported. The security of reports depends on the device, connection, and server configuration; delivery is not necessarily encrypted if an HTTP address is used.
Contact us about suspected unlawful collection involving children. We will publish policy updates here and provide additional notice or obtain consent where required.
Effective date: September 21, 2026