Privacy Policy
In short
- Tracfast is fleet management software used by businesses. Most of the personal data on the platform (drivers, vehicle locations, documents) belongs to the fleet operator who uses Tracfast. For that data they are the controller and we are their processor, acting on their instructions.
- When you contact Tracfast itself, by our website form, website chat, phone, text message, WhatsApp, Messenger, Instagram or email, Tracfast Ltd is the controller. The same applies to your Tracfast account, billing and support.
- Calls to and from Tracfast are recorded, and you are told before you are connected. Recordings are kept for 6 months and voicemail for 3 months.
- The platform and our communications system run on servers we operate in the United Kingdom. We use a short list of service providers, set out in section 9, some of them outside the UK. We never sell personal data.
- Our home page has one optional advertising cookie, the Meta Pixel. It only runs if you choose Accept in the cookie banner, and you can change your mind at any time (section 15).
- To ask us to delete your data, see How to ask us to delete your data. Any other questions: help@tracfast.io.
- Who we are
- Controller or processor?
- What we collect
- Why we use it and on what basis
- Phone calls, recordings and voicemail
- AI features, including Jason
- Vehicle tracking, cameras and manufacturer data
- Businesses we contact about Tracfast
- Who we share data with
- International transfers
- How long we keep data
- How to ask us to delete your data
- Your rights
- Security
- Cookies and similar technologies
- Children
- If you are a driver
- Changes to this policy
1. Who we are
Tracfast Ltd is a company registered in England and Wales, company number 15045190, registered office 6 Seax Way, Basildon, Essex SS15 6SW. We operate the Tracfast fleet management platform at tracfast.io, our help centre at tracfast.info, our developer portal at tracfast.dev, the Tracfast Android app, this website, and the communication channels described in section 3.
Contact us about this policy or your data at help@tracfast.io, or write to Tracfast Ltd, 6 Seax Way, Basildon, Essex SS15 6SW.
Tracfast was built inside, and is used daily by, our sister company Skilled Solutions Ltd, which is one of the fleet operators on the platform.
2. Controller or processor?
| Data | Our role |
|---|---|
| Fleet data a customer puts into the platform: vehicles, drivers, hirers, assignments, documents, photos, video, GPS positions, charges, messages and notifications the platform sends to drivers on the customer's behalf, and the customer's internal team chat | Processor. The fleet operator (our customer) is the controller and decides what is collected and why. We process it under our Terms of Service, which include data-processing terms. Drivers should read their operator's own privacy notice first (see section 17). |
| Messages, calls and enquiries you send to Tracfast itself, on any of our channels | Controller. |
| Your Tracfast user account, logins, audit trail, questions you ask Jason, and support requests | Controller (shared with your employer, who administers the account). |
| Billing and contract records for customers and Pilot Partners | Controller. |
| Business contacts we approach about Tracfast (section 8) | Controller. |
| Website visits, help centre and developer portal | Controller. |
3. What we collect
When you contact Tracfast
| Channel | What we collect |
|---|---|
| Website contact form | Your name, email address, company, phone number (if you give one), the number of vehicles and (if you give it) the number of drivers, the kind of vehicles you run, the type of enquiry, your message, and that you ticked the box to say you have read our Terms of Service and this policy. To stop spam we also use a hidden form field, a signed time stamp, a short-lived cookie (section 15) and, when it is switched on, Cloudflare Turnstile, which checks your IP address and browser signals to tell people from bots. |
| Website chat (on our website and login page) | The name, email address or phone number and topic you give us (we do not verify them), your messages, any photos or PDF files you send, and the page you were on. A chat token is kept in your browser so you can carry on the conversation. The same spam checks as the contact form may apply. |
| Phone calls | Your phone number (unless you withhold it), the date, time and length of the call, the menu option you chose, who answered, a recording of the call, voicemail if you leave one, and the notes and outcome our staff record. See section 5. |
| Text messages (SMS) | Your mobile number, your messages, the times they were sent and their delivery status. |
| WhatsApp, Messenger and Instagram | On WhatsApp: your phone number and the profile name you have set. On Messenger and Instagram: the identifier Meta gives you for our Page or account. On all three: your messages and anything you send us (photos, voice notes, video, documents, locations or contacts you share, reactions), and delivery and read status. We only receive these when you message us. |
| Email (help@tracfast.io) | Your email address and name as they appear on the email, the people copied in, your message and its attachments. |
| All channels | Our replies, our staff's internal notes and labels, which colleague or team handled the conversation, timings, and whether you have opted out of marketing. If you contact us on more than one channel with the same email address or phone number, we link the conversations to one contact record. |
Please do not send us sensitive information (for example about your health) unless we need it to help you. If you do, we use it only to deal with your message.
When you use the Tracfast platform
- Account holders: name, work email, phone, role and permissions, the organisation you belong to, login and activity logs, the questions you ask Jason and its answers, and support chats (including "Talk to a person" in Jason, which reach our team in the same communications system as our other channels).
- Customers: company details, billing contacts, invoices and payment status, correspondence.
- Website, help centre and developer portal: server logs (IP address, browser, pages requested, times) and the cookies in section 15.
As processor, for fleet operators
- Staff users: name, work email, phone, role and permissions, login and activity logs, and their internal team-chat messages.
- Drivers and hirers: name, contact details, address, date of birth, driving licence details and check results, signatures, photographs of identity and compliance documents, agreement and payment records, penalty charge notices, insurance claims, and the notifications sent to them.
- Vehicle use: GPS position, speed, heading, ignition and driving events from telematics devices or from the vehicle manufacturer; mileage, fuel and vehicle health; trip histories and reports; check-out and check-in photographs; dashcam stills and clips where the operator has fitted cameras.
- Documents: anything the operator uploads, scans or emails to the platform (agreements, PCNs, invoices, inspection reports), including text extracted from them.
4. Why we use it and on what basis
| Purpose | Lawful basis (UK GDPR Art. 6) |
|---|---|
| Answering your enquiries and messages on any channel, and keeping a record of them | Legitimate interests (responding to people who contact us and running our business); steps before entering a contract, if you are considering becoming a customer; contract, if you are a customer |
| Recording calls and keeping voicemail (section 5) | Legitimate interests (training, quality, an accurate record of what was said, and dealing with complaints and disputes) |
| Providing the platform to our customers and their users | Contract; for processor data, the customer's instructions |
| Account security, spam and fraud prevention (including the anti-spam checks in section 3), audit logs, service monitoring | Legitimate interests (running a secure service); legal obligation |
| AI help: answering platform users' questions, and summarising conversations or drafting replies for our staff (section 6) | Legitimate interests (faster and better answers); contract, for platform users |
| Telling businesses about Tracfast (section 8) | Legitimate interests; your consent where the law requires it (for example before we send you a marketing text) |
| Measuring our Facebook and Instagram adverts with the Meta Pixel on our home page, and helping Meta show those adverts to similar businesses (section 15) | Your consent, given in the cookie banner. You can withdraw it at any time under Cookie settings at the bottom of the home page. |
| Product and service news to existing customers | Legitimate interests; you can opt out at any time |
| Billing, accounting and tax records | Contract; legal obligation |
| Improving the product using aggregated, non-identifying usage statistics | Legitimate interests |
| Training our own vehicle-damage detection models on vehicle photographs we own, or that the fleet operator has agreed we may use (section 6) | Legitimate interests |
| Meeting legal and regulatory requirements, and establishing or defending legal claims | Legal obligation; legitimate interests |
Where we rely on legitimate interests, we have weighed our interests against yours, and you can object (section 13). We do not make decisions about anyone that have legal or similarly significant effects by automated means alone. Rules in our communications system decide which colleague or team sees a message first; they do not decide anything about you.
5. Phone calls, recordings and voicemail
- Our phone line is provided by Twilio, and our staff answer and make calls in our own browser-based phone system.
- Calls are recorded. When you call us, a recorded message tells you that calls are recorded before you are connected to anyone. When we call you, you hear a short notice that the call may be recorded when you answer. Both sides of the conversation are recorded from the moment the call is answered.
- If nobody is free, or we are closed, you may be able to leave a voicemail. A voicemail is recorded only if you choose to speak after the tone.
- Recordings and voicemail are copied to our own servers. We delete Twilio's copy of a call recording about a minute after ours is safely stored.
- We may transcribe recordings and voicemail automatically so our staff can read them. Transcription runs on our own servers, not with a third party.
- Call recordings and their transcripts are deleted after 6 months, and voicemail after 3 months, unless we need to keep one for a complaint or legal claim.
- If you would rather not be recorded, you can contact us by email or message instead.
6. AI features, including Jason
- Jason is the AI assistant in the Tracfast platform. It uses Anthropic's Claude models through Anthropic's API (currently Claude Sonnet 5 by default, with Claude Haiku 4.5 as an option). When a platform user asks Jason a question, the question and the platform data needed to answer it are sent to Anthropic for processing, and the answer comes back. Jason can only use data the user is already allowed to see, and personal details are hidden from users whose role is below manager. We keep a log of questions and answers on our own servers.
- In our communications system, our staff can ask Jason to summarise a conversation or draft a reply. When they do, recent messages from that conversation (up to the last 40, shortened) and basic facts about it are sent to Anthropic. Jason does not reply to you by itself: our staff write or approve every reply.
- Reading documents (for example extracting the details from a penalty charge notice or an invoice), detecting vehicle damage in photographs and transcribing calls all run on our own servers in the UK.
- We train our own vehicle-damage detection models, on our own servers, using vehicle photographs that we own, or that the fleet operator has agreed we may use. These models look at vehicles, not people.
- We do not use your messages, calls or account data to train AI models.
7. Vehicle tracking, cameras and manufacturer data
Tracfast receives vehicle data in three ways, all chosen and enabled by the fleet operator:
- Telematics devices fitted to vehicles (for example Teltonika or Meitrack units) send position and event data directly to Tracfast servers over mobile data. The device manufacturers do not receive this data from us.
- Dashcams and imaging: where fitted, clips and stills are uploaded to Tracfast servers. Cameras capture the road and, if the operator chooses, the cab.
- Manufacturer ("OEM") connected-vehicle data: for eligible vehicles, the operator can ask Tracfast to receive the data the vehicle already sends to its manufacturer (location, odometer, fuel or charge level, vehicle health and service alerts). We obtain this through High Mobility GmbH, a connected-car data platform in Germany, which in turn receives it from the manufacturer. The operator confirms it has authority over the vehicle before enrolling it, and access is revoked when the vehicle leaves the fleet.
The fleet operator is responsible for having a lawful basis for monitoring, for telling drivers what is collected, and for its own policy on private use. Tracfast provides the tools; we do not decide which vehicles or people are tracked.
8. Businesses we contact about Tracfast
We tell UK businesses that run vehicles about Tracfast. To do this we keep a list of companies built from the public register at Companies House (company name and number, registered address, industry code, and the names of directors and people with significant control as published there), with work contact details for people at those companies found on the company's own website or through email-finding services such as Hunter.io. You can ask us where we got your details.
- Email: every outreach email names Tracfast and has an unsubscribe link. One click takes you off every outreach list.
- Text messages: we only send marketing texts with your recorded consent.
- WhatsApp: we never use WhatsApp to contact anyone who has not contacted us first.
- Calls: we only call a business number after checking that it is not registered with the Corporate Telephone Preference Service (CTPS).
- If you tell us not to contact you, we mark you "do not contact", which stops marketing on every channel. Replies to messages you send us are not affected.
You can object to this use of your data at any time, or ask us to delete your details (section 12).
9. Who we share data with
We do not sell personal data. Apart from the Meta Pixel, which runs only if you accept advertising cookies on our home page (section 15), we do not share personal data with advertisers. We use the following providers, each under contract and only for the purpose shown:
| Provider | Purpose | Location |
|---|---|---|
| Twilio | Our phone line (calls, call recordings until we have copied them, voicemail) and text messages; text notifications that customers switch on in the platform | Ireland for our UK phone and text numbers; USA for platform text notifications. Twilio is a US company. |
| Meta Platforms Ireland Ltd | WhatsApp Business Platform, Messenger and Instagram messaging: carries messages between you and us. If you accept advertising cookies on our home page, the Meta Pixel also tells Meta about your visit (section 15). | Ireland, USA and other countries where Meta operates |
| Cloudflare, Inc. | Turnstile bot check on the website contact form and website chat (IP address and browser signals) | Global network; Cloudflare is a US company |
| Microsoft (Microsoft 365) | Our email (help@tracfast.io, and platform email from no-reply@tracfast.io), staff sign-in, Microsoft Teams (including alerts to our team about new website enquiries) and notifications into customers' Microsoft Teams | UK / EU |
| Anthropic | The AI models behind Jason (section 6) | USA |
| High Mobility GmbH and vehicle manufacturers | Manufacturer connected-vehicle data for vehicles the operator enrols (section 7) | Germany / EU |
| Vultr (The Constant Company) | Edge server in London that passes encrypted traffic to our UK servers without decrypting it; it does not store platform data | UK |
| DVLA | Vehicle tax and MOT status by registration; driving-licence checks with the driver's consent, where the operator uses this feature | UK |
| Vehicle data providers (e.g. JATO, CheckCarDetails, TecDoc) | Vehicle specification by registration or VIN: vehicle data, not personal data | UK / EU |
| OpenStreetMap | Map tiles and address lookup for coordinates shown on screen | UK / EU |
| Google Play | Distribution of the Tracfast Android app | USA |
When you use WhatsApp, Messenger, Instagram or another provider's app or service directly, that provider also handles your data under its own privacy policy, as part of your own relationship with it.
We also disclose data where the law requires it, to enforcement bodies acting lawfully, to our professional advisers, and in connection with a sale or reorganisation of the business (on the same terms as this policy).
10. International transfers
The platform, our communications system (messages, files, call recordings and voicemail) and our backups are stored on servers we operate in the United Kingdom. Some of our providers process data outside the UK:
- Twilio handles our UK phone line and text number in its Ireland region. Twilio is a US company and may access data from the USA, for example for support and security. Text notifications from the platform are processed in the USA.
- Meta processes WhatsApp, Messenger and Instagram messages in Ireland, the USA and other countries.
- Cloudflare's Turnstile check runs on its global network, and Cloudflare is a US company.
- Anthropic processes requests to Jason in the USA.
- Google Play is operated from the USA.
Transfers to the European Economic Area (for example Ireland and Germany) are covered by UK adequacy regulations. For the USA and other countries, we rely on the UK Extension to the EU-US Data Privacy Framework where the provider is certified under it, or otherwise on the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses in the provider's data-processing terms. You can ask us which safeguard applies to a particular provider.
11. How long we keep data
Your conversations and calls with Tracfast
| What | How long |
|---|---|
| Message content on every channel (email, text, WhatsApp, Messenger, Instagram, website chat and website enquiries) | 24 months after the conversation is resolved. The text is then removed; only the date, channel and counts remain, for our statistics. |
| Photos and files sent in conversations | 12 months |
| Call recordings and their transcripts | 6 months |
| Voicemail and its transcript | 3 months |
| Twilio's copy of a call recording | Deleted about a minute after we have stored our own |
| Delivery records from our messaging providers | 30 days |
| Records of how a conversation was routed to our team | 90 days |
| Audit trail of what our staff did (including deletions) | 6 years |
| Your contact details in our communications system | While we have an open conversation or a business relationship with you, or until you ask us to delete them (section 12) |
We keep something longer only when it is needed for a complaint or a legal claim. Copies of emails are also held in our Microsoft 365 mailbox, and our providers keep their own records (for example delivery logs) under their own retention rules.
The platform, customers and our website
- Processor data: for as long as the customer's subscription lasts and as their settings require. Within 90 days of a subscription ending we return or delete it, unless the law requires us to keep it.
- Accounts, including Jason question logs: while the account is active, then up to 12 months in audit logs.
- Contract and billing records: six years from the end of the financial year they relate to, as UK law requires.
- Business contacts (section 8): while the business remains a possible customer, or until you ask us to stop contacting you or to delete your details.
- Server logs: up to 12 months.
- Backups: deleted data stays in our backups until they are overwritten in the normal rotation.
12. How to ask us to delete your data
Anyone can ask us to delete their personal data, including people who contacted us through WhatsApp, Messenger or Instagram. You do not need a Tracfast account, and it is free.
How to ask
- Email help@tracfast.io with the subject "Delete my data". Tell us the email address, phone number or social media account you used to contact us, and the channels (for example WhatsApp, Instagram or the website chat).
- Or message us on the same channel: send "Delete my data" in your WhatsApp, Messenger, Instagram, text message or website chat conversation with us. A request from the same number or account usually tells us it is you.
- Or write to Tracfast Ltd, 6 Seax Way, Basildon, Essex SS15 6SW.
If we cannot tell that a request comes from you, we may ask a question or two to check, and no more than we need.
What we delete
- Your messages, and the photos, files, call recordings, voicemail and transcripts in your conversations with us.
- Your name, email addresses, phone numbers and social media identifiers in our communications system, with any drafts and routing records about you.
- Your place on our outreach lists, and your entry in our list of business contacts if you are on it.
- Your Tracfast login and the personal data in it, if you have one and ask us to. If your employer still administers that account, we will tell you and work with them.
What we keep, and why
- A record of your request: the date, what was deleted and which member of staff did it, in our audit trail for 6 years, so we can show we handled it properly.
- Records of consent and opt-out decisions, with your name, number and address removed, as evidence that we respected your choices.
- The dates, channels and status of conversations, with all content removed, for our statistics. These no longer identify you.
- Records the law requires us to keep, such as invoices and contract records if you are or were a customer (six years from the end of the financial year).
- Anything needed for an actual or likely complaint or legal claim. We will tell you if this applies.
- Backups, until they are overwritten in the normal rotation. We only restore from backups to recover from a failure, and if deleted data is ever restored, we delete it again.
- Data we hold for a fleet operator (for example if you are a driver): we pass your request to that operator, who decides, and we help them carry it out.
Copies held by Meta and others
Deleting your data with us does not delete it from WhatsApp, Messenger or Instagram. The conversation stays in your own app until you delete it there, and Meta keeps its own records under its own privacy policy; use the privacy settings in the app to manage them. Your mobile network and email provider also keep their own records. Our service providers delete the records they keep for us under their own retention rules.
How long it takes
We act on your request without undue delay and within one month. If a request is complex we may need up to two more months; if so, we will tell you why within the first month. We will tell you when it is done and what, if anything, we have kept and why.
13. Your rights
Under UK data protection law you can ask us for access to your personal data, correction, erasure (section 12), restriction and portability. You can object to processing based on legitimate interests, and you can always object to direct marketing, in which case we will stop. Where we rely on your consent, you can withdraw it at any time. Where we act as processor we will pass your request to the fleet operator who controls the data and help them respond.
Email help@tracfast.io or use any channel in section 3. It is free, and we respond within one month.
You can complain to the Information Commissioner's Office at ico.org.uk/make-a-complaint, on 0303 123 1113, or by post to Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF. We would appreciate the chance to resolve any concern first.
14. Security
All traffic is encrypted in transit (TLS). Sensitive fields such as contact details, licence numbers and credentials are encrypted at rest at field level. Access is role-based and tenant-separated, with every tenant's data partitioned and privileged actions logged. Our staff's Microsoft 365 accounts require multi-factor authentication. Servers are in access-controlled premises in the UK, with nightly backups to a separate system. We review security as part of our development work and will notify customers and, where required, the ICO of a personal data breach without undue delay.
15. Cookies and similar technologies
| Cookie / storage | Purpose | Type |
|---|---|---|
Sign-in cookie (fp_token) | Keeps you signed in to the platform; it expires after a set time or when you sign out | Strictly necessary |
| Help centre and developer portal sign-in cookies | Keep you signed in for up to 8 hours | Strictly necessary |
Website chat cookie (tf_wc_…) and browser storage (tfchat:…) | Let you carry on a chat you started, for up to 30 days | Strictly necessary |
Anti-spam cookies (tf_fs on the contact form, tf_cs_… for the chat) | Tie a signed time stamp to your browser so we can tell people from bots; they last about 25 hours and hold a random code, not your details | Strictly necessary |
| Cloudflare Turnstile (when switched on) | A bot check that runs in a frame from Cloudflare; Cloudflare processes your IP address and browser signals to do it | Strictly necessary (security), third party |
| Browser local storage on the platform | Remembers your interface preferences (filters, columns, theme) on your own device; never sent to us | Functional |
Your cookie choice (tf_ads_consent) | Remembers whether you accepted or rejected advertising cookies on our home page, for 6 months | Strictly necessary |
Meta Pixel (_fbp, and _fbc if you arrive from one of our adverts, plus Meta's own cookies if you are logged in to Facebook or Instagram) | Only if you choose Accept: tells Meta that your browser visited our home page and whether you then registered interest in our Pilot Partner programme, so we can see whether our adverts work and Meta can show them to similar businesses. We do not send Meta your name, email address or anything you type into the form. _fbp lasts up to 90 days. | Advertising, third party (Meta); only with your consent |
Apart from the Meta Pixel, the cookies above are strictly necessary for a service you have asked for, or only remember your own settings. The Meta Pixel runs only on our home page, and only if you choose Accept in the cookie banner; Reject is just as easy. You can change your mind at any time with Cookie settings at the bottom of the home page, which also deletes the Pixel's cookie. For the information the Pixel collects and sends, Meta Platforms Ireland Ltd and Tracfast Ltd are joint controllers; what Meta then does with it is covered by Meta's Privacy Policy, and you can see and clear it in your Facebook or Instagram settings under "Your activity off Meta technologies". We do not use analytics cookies.
16. Children
Tracfast is for businesses and adults. Our website, platform and messaging channels are not aimed at children, and we do not knowingly collect personal data from anyone under 18. If you think a child has contacted us, email help@tracfast.io and we will delete the data.
17. If you are a driver
If you drive a vehicle managed on Tracfast, the business that employs you or hires the vehicle to you is the controller of your data. Its privacy notice explains what it monitors and why. Tracfast only processes your data on that business's instructions, does not share it with anyone else except as set out above, and will refer any request you send us to that business so it can be answered properly.
18. Changes to this policy
We will post any changes here with a new version number and effective date, and tell customers of material changes by email. Version 1.1 added our communication channels (website chat, phone, text, WhatsApp, Messenger, Instagram and email), call recording, our anti-spam checks, AI features, the businesses we contact, and how to ask us to delete your data. Version 1.2 added the optional Meta Pixel on our home page and the cookie choice that controls it (section 15). Version 1.3 says the Pixel tells Meta whether you registered interest in our Pilot Partner programme, where it said whether you applied to be a Pilot Partner. Version 1.4 added the extra details our home page form asks for (phone number, number of drivers, kind of vehicles) and the Pixel's second cookie.
Contact: Tracfast Ltd, 6 Seax Way, Basildon, Essex SS15 6SW · help@tracfast.io.
