Information we handle
Trackify may process account details, company details, fleet records, driver records, support requests, billing metadata, device metadata, training content interactions, and marketing enquiries.
The marketing website keeps main public pages static. Blog and training/course content may be served from Trackify's Mongo-backed content services.
Operational data
Fleet and compliance data can include vehicle, trip, location, EWD, checklist, fault, incident, tracker, and reporting information depending on the product features used by a customer.
Regulatory telematics evidence, TCA/TMA/RIM workflows, and FMC650 tracker data are handled as operational product data, not as public marketing content.
Security
Access to Trackify systems is role-based. Superadmin and MCP access paths must not expose tokens, passwords, OTPs, or raw authorization headers in public content, logs, or exports.
Customers should configure user access, driver records, and support workflows according to their own internal policies and legal obligations.
Contact
For privacy questions, contact Trackify using the support details on the Contact page.