Privacy Policy

Last reviewed: 17 August 2026

A tracking platform necessarily handles some detailed information. The useful way to explain it is to follow what happens when someone buys a tracker, opens a Fleetalyse account or connects a vehicle. This notice does that. It covers the Fleetalyse website and shop, the customer portal, tracker subscriptions, supported IoT SIM services and the help we provide before and after activation.

The short version

We use account details to deal with you, order details to send what you bought, and device or SIM identifiers to connect the right hardware to the right customer. Once tracking is active, the service receives location and telematics records so authorised users can see vehicles, journeys and alerts. We use specialist companies for matters such as hosting, card payments, mapping, tracker provisioning, mobile connectivity and email delivery.

We do not sell personal data. We do not receive or store the full card number entered at Stripe Checkout. Nor do we use Fleetalyse data to make solely automated decisions about a person that have legal or similarly significant effects.

Who is responsible for the data?

Fleeta Limited T/A Fleetalyse, company number 16675897, is responsible for the personal data used to run our website, shop, customer accounts, billing, sales and support. Our registered office is 50 Princes Street, Ipswich, England, IP1 1RJ. In data protection language, we are the controller for those activities.

There is an important distinction for live fleet data. A business that tracks its vehicles, drivers or staff will usually decide why that tracking takes place, who can see it and how long it is needed. That business is normally the controller for those records, while Fleeta Limited provides the platform as its processor. Drivers and employees should therefore raise day-to-day questions about workplace tracking with the fleet operator or employer first. We will assist our customer with a valid request.

What reaches Fleetalyse

Not every customer uses every feature, so not every item below will apply to you.

• Account and contact information: your name, business name, email address, telephone number, billing or delivery address, login records and acceptance of portal terms.
• Orders and subscriptions: the products and plans selected, delivery and refund history, trial dates, subscription state, prepaid or top-up records, and references returned by Stripe. Card details are entered on Stripe's systems rather than stored by Fleetalyse.
• Trackers, SIMs and vehicles: IMEI, ICCID, serial number, tracker model, SIM state, data usage, registration mark, vehicle description, installation and activation state, and the customer or subscription to which an item is assigned.
• Tracking and telematics: location, time, route, stops, mileage, geofence events, driving or sensor events, diagnostics and alerts generated by an active service. Remote tachograph or connected camera features can produce additional operational records when a customer enables them.
• Conversations and service history: emails, form submissions, support notes, fault reports, delivery messages and records of work carried out to provision or repair an account.
• Security records: IP address, browser and device information, sign-in attempts, bot checks, audit entries and evidence considered when a device claim, release request or activation appears unusual.

Where the information comes from

Much of it comes straight from you: for example, when you complete checkout, register for the portal, type an IMEI or contact support. A Fleetalyse business customer may also give us authorised-user or vehicle details. Our shop and payment providers send us the status of an order or payment, while connected trackers and telematics systems generate operational data during use.

We may already hold an imported tracker or SIM record before a customer claims it. Those inventory records can come from the device manufacturer, a connectivity supplier, our tracking platform or our own stock administration. If you purchased through a marketplace or reseller, the order and delivery details may come from that seller or marketplace. We match these sources carefully because an IMEI or ICCID on its own does not prove ownership.

What we use it for, and our legal basis

Providing what was requested. We use the details needed to answer an enquiry, fulfil an order, create an account, run a trial, take subscription instructions, provision a tracker, display SIM usage and provide support. This is generally necessary to take steps at your request or to perform our contract with you.

Running and protecting the service. We keep audit trails, investigate failed sign-ins, check device eligibility, prevent duplicate claims, reconcile service records and diagnose faults. Our legitimate interests are keeping Fleetalyse reliable, protecting customers and stock, preventing fraud, and understanding how to improve the service. We balance those interests against the effect on the people involved.

Keeping proper business records. Tax, accounting, consumer, company and law-enforcement requirements can oblige us to retain or disclose particular records. In those cases the basis is compliance with a legal obligation. We may also retain relevant evidence where necessary to establish, exercise or defend legal claims.

Optional communications and cookies. Where consent is required for a marketing message or a non-essential cookie, we will ask for it. Consent can be withdrawn without affecting earlier lawful use. Essential session and security cookies are used because the site and portal cannot work safely without them; our separate cookie policy explains more.

Some information is necessary rather than optional. Without contact and delivery details we cannot fulfil an order. Without an IMEI or ICCID we cannot identify the hardware or SIM being claimed. Without the required account and Stripe checkout information we cannot open a paid service or arrange its trial. You do not have to provide it, but the relevant transaction or feature will not be available if you do not.

Location data deserves a little more explanation

A vehicle position can become personal data when it can be linked to a driver or another identifiable person. Fleetalyse displays that information only within the connected service and according to the account permissions set for authorised users. A customer using tracking at work is responsible for having a lawful reason, telling affected people what is happening and setting appropriate access and retention rules. The platform should not be used for covert or unlawful surveillance.

When an eligible second-hand tracker is moved to a new customer, the previous customer's journey history is not part of the transfer. A hardware identifier may be reassigned; the former account's tracking records are not handed to the new owner.

The companies that help us provide Fleetalyse

We share only the information a provider needs for its part of the service. Our current service chain includes Hostinger for hosting, Stripe for checkout and subscription billing, Mapon CMR for supported tracking account and device provisioning, 1GLOBAL/Truphone for supported IoT SIM connectivity, Cloudflare for website and form security, and suppliers used for business email or delivery. Those companies handle data under their own legal duties and, where they process it for us, under contractual instructions.

We may also disclose information to professional advisers, insurers, payment or fraud specialists, regulators, courts, law enforcement, or a purchaser of the business where there is a proper legal reason. We do not give customer location history to advertisers.

Information processed outside the UK

Internet infrastructure and some of the providers above operate internationally. This means a limited amount of personal data may be processed outside the United Kingdom. When UK law treats the destination as not providing an adequate level of protection, we use an available safeguard such as the UK International Data Transfer Agreement, the UK Addendum to approved standard contractual clauses, or another lawful exception that fits the transfer. You can ask us for further information about the safeguard relevant to your data.

How long records stay with us

There is no honest single answer for every Fleetalyse record. An open portal account and its current device assignments are needed while the service is running. Order, payment and accounting records are kept for the period required by tax law and for resolving contractual claims. Security logs and support evidence are kept only while they remain useful for account protection, fault investigation or a live dispute.

Tracking history follows the retention configuration and agreement for the relevant fleet service. When an account closes, we delete or anonymise data that is no longer required, allowing for a reasonable backup cycle and anything we must retain by law. In deciding a period, we consider the type and volume of the record, how sensitive it is, why it was collected, the risk if it were misused and whether a shorter or anonymised record would do the job.

Automated checks and human review

The portal carries out routine checks when somebody signs in, claims a tracker, requests a device release or starts service. It can flag an IMEI that is already assigned, an unsupported item, inconsistent ownership evidence or behaviour that resembles abuse. A check may stop the immediate action and place it in a review queue. A Fleetalyse administrator can then examine the record and correct a mistaken result. These checks do not make solely automated decisions about individuals with legal or similarly significant effects.

Your choices and rights

Depending on the circumstances and the legal basis being used, you may ask for a copy of your personal data, correction of inaccurate data, deletion, restriction of use, or transfer of information you supplied in a portable format. You may withdraw consent where processing relies on consent. You can also complain about how your information has been handled.

Rights are not absolute, and the answer can depend on whether Fleetalyse or the fleet operator is the controller. We may need enough information to confirm identity before releasing or changing account data. We will explain if an exemption applies rather than simply refusing the request.

Security and changes to this notice

We use access controls, password hashing, encrypted web connections, CSRF and bot protection, audit logging, restricted administration and separation from the card-payment environment. No online service can promise zero risk. If something goes wrong, we investigate, limit the impact and make any notification required by law.

Fleetalyse changes as tracker models, connectivity services and customer tools change. We will revise this page when that alters how personal data is used. A material change will be brought to account holders' attention where that is appropriate; the review date above shows when this wording was last checked.

Contacting us or making a complaint

Write to Fleeta Limited T/A Fleetalyse at 50 Princes Street, Ipswich, England, IP1 1RJ, or email info@fleetalyse.co.uk. Please say that your message concerns privacy or a data rights request so it reaches the right person. We would like the opportunity to resolve a concern directly.

You also have the right to complain to the Information Commissioner's Office. The ICO provides an online complaint service, a helpline on 0303 123 1113, and a postal address at Wycliffe House, Water Lane, Wilmslow, Cheshire, SK9 5AF.