Privacy Policy
1.Our role: controller vs. processor
Fleet Tracker is deployed by organizations ("Customers," typically an employer) to track devices they manage. In most cases the Customer is the data controller — they decide which devices are tracked and are responsible for the lawfulness of that tracking, including any required notice to and consent from the individuals involved. Fleet Tracker acts as a service provider / processor, handling data on the Customer's behalf and per their configuration.
2.Information we collect
| Category | Examples |
|---|---|
| Location data | Latitude/longitude, accuracy, altitude, speed, heading, and capture timestamps, sent at intervals while the app runs. |
| Device identifiers | Intune device ID, Microsoft Entra device ID, serial number / IMEI, Android ID, device name. |
| User identifiers | Work email, user principal name (UPN), and/or username, plus the assigned fleet tag — as provided by your MDM configuration. |
| Account & dashboard data | Login usernames and authentication tokens (the dashboard stores a session token in your browser's local storage). |
| Contact form data | Name, company, email, fleet size, and message you submit on our website. |
The exact identifiers received depend on what the Customer maps in their MDM (Intune) configuration.
3.How we collect it
- Automatically from the device — the app reports location and identifiers on a recurring basis (including in the background) once deployed.
- From your MDM — managed app-configuration values (fleet tag, device IDs, email, etc.) are injected by Intune / Managed Google Play.
- Directly from you — when you log in to the dashboard or submit the contact form.
4.Why we use it (purposes)
- To provide the core service: recording and displaying device location and location history.
- To identify and group devices (fleet tags) and scope access per user.
- To operate, secure, maintain, and troubleshoot the Service.
- To respond to contact-form enquiries.
Where required by law, the lawful basis for processing (e.g. legitimate interests, consent, or contract) is determined by the Customer as controller.
5.Data retention
Location history is retained on a tiered basis: recent pings are kept in full detail, older data is automatically thinned/down-sampled over time (for example, reduced to roughly one point per 15 minutes and then hourly), and a representative history may be retained long-term. Duplicate pings are removed automatically. Customers may request deletion of their data (see Section 8).
6.How we share it & sub-processors
We do not sell personal information. Data may be processed by the following categories of third parties strictly to operate the Service:
- Microsoft (Intune / Entra) — device management and configuration.
- Google (Managed Google Play) — app distribution.
- Map provider — to render maps in the dashboard.
- Form/email provider (Formspree) — to deliver contact-form messages.
- Hosting / database infrastructure — where the backend and location data are stored.
We may also disclose information if required by law or to protect rights, safety, or the integrity of the Service.
7.Data security
We use reasonable technical and organizational measures (such as authenticated, scoped dashboard access and encrypted transport) to protect data. However, no method of transmission or storage is completely secure, and we cannot guarantee absolute security.
8.Your rights
Depending on your location, you may have rights under laws such as the GDPR and CCPA/CPRA — including the right to access, correct, delete, or restrict processing of your personal data, and to object or opt out. Because tracked individuals' data is controlled by the Customer (employer), such requests are generally directed to and handled by the Customer; we assist them as their processor. To make a request, contact the relevant Customer or reach us using Section 12.
9.Workforce / employee monitoring
The Service may be used to track employer-owned or managed devices. Laws governing employee monitoring, location tracking, surveillance, notice, and consent vary by jurisdiction and can be strict. The Customer is solely responsible for providing required notices, obtaining any required consent, and otherwise complying with all applicable laws. Fleet Tracker does not verify the legality of any tracking performed by a Customer.
10.International transfers
Data may be processed or stored in countries other than where you live. Where required, we and our Customers rely on appropriate safeguards for such transfers.
11.Children's data & cookies
The Service is intended for organizational/business use and is not directed to children. The dashboard uses your browser's local storage to hold a session/authentication token so you stay signed in; it is not used for advertising or cross-site tracking.
12.Changes & contact
We may update this Policy from time to time; the "Last updated" date reflects the current version. Questions or requests? Contact us through the form on our home page, or email temp@trilogy.network.
This Policy and our provision of the Service are governed by the laws of the State of Florida, United States. As described in Section 1, the organization that deploys the Service (the Customer/employer) is the data controller for tracked devices and is responsible for the privacy obligations arising from that role; where users reside in jurisdictions with their own data-protection laws (e.g. California's CCPA/CPRA or the EU's GDPR), those laws may also apply.
This Policy describes current practices and does not create rights beyond those required by applicable law. See also our Terms of Service.