Fleet GPS and telematics: real mileage and geofencing

A GPS and telematics system on a rental fleet does three things that show up in the accounts: it verifies the vehicle's real mileage against what the customer declares, it alerts you if the car leaves the zone or the country agreed in the contract, and it locates or immobilises the unit when there is a clear non-payment or a suspected theft. In Spain it is lawful to use one, on a condition that allows no shortcuts: the customer must be informed clearly and in advance, and that data processing must be set out in the rental contract.

What does not hold up is the hidden tracker. The position of a vehicle driven by an identifiable person is personal data, and processing it without notice runs straight into the transparency principle of the RGPD, the European data protection regulation, and of the LOPDGDD, the Spanish data protection act. Before installing anything, read the official guidance of the AEPD, the Spanish data protection authority, on geolocation, and have the contract reviewed by a specialist lawyer.

What telematics actually solves in an independent agency

An agency that owns its fleet does not need a dashboard covered in charts. It needs answers to what comes up at the counter almost every week: how many kilometres has this car really done, where was it on Tuesday afternoon when the offence behind that fine was committed, has this customer driven to Portugal on a contract limited to the Spanish mainland? The big chains have whole departments to reconstruct an incident; you have the contract, the vehicle file and the memory of whoever handed over the keys.

Real mileage against declared mileage

The most common case is the customer who returns the car with mileage that does not match the agreed use. Without a device you have a photo of the dashboard at handover and another on return, and the discussion becomes a question of credibility. With an automatic odometer reading you have a dated series, and the same data lets you plan servicing by real use rather than by the calendar.

• Record the reading at handover and on return, and keep both with their time, not just the final figure.
• Explain in the contract how excess mileage is calculated and which source measures it. If the source is the device, say so in writing.
• Use the running total per vehicle to decide rotations and when to sell, not only to invoice extras.

Geofencing: alerts when the car leaves the agreed area

Geofencing means drawing a zone on the map and asking the system to alert you when the vehicle enters or leaves it. In rental there are three clear uses: checking that the unit does not leave the territory where the insurance and roadside assistance apply, spotting that a car rented for urban use has ended up at the other end of the country, and watching the yard when the agency is closed. A virtual fence prevents nothing: it produces an alert, and that alert arrives late where mobile coverage is poor.

• Define the zones from what the contract says: if you allow trips to Portugal or France, the fence must reflect that.
• Tell the customer in writing that the alert exists and what it is used for. An unexpected alert ends up as a bad review.
• Treat it as a prompt to call the customer, not as automatic proof of a breach.

Remote immobilisation: when it makes sense and when it does not

Remote starter cut-off is the most heavily sold function and the most delicate. Technically it stops the engine from starting again; it does not stop a car that is moving, and any supplier who presents it otherwise should make you doubt the rest of their pitch. In practice there are two scenarios: failure to return the vehicle after a clear non-payment, and suspected theft with a police report filed. Before you enable it you need a written protocol: who can order it, which contact attempts are mandatory first, and what gets logged. Leaving a car unable to start with a family on board, on a dual carriageway where traffic runs at 120 km/h, opens a liability front no agency wants.

What you must disclose and put in writing

This is where most agencies assume they are covered. A line of small print is not enough: you have to explain what data is processed, for what purpose, how long it is kept and who it is shared with.

1. 1A specific clause in the rental contract, separate from the general data notice, stating that the vehicle carries a tracking device and the purposes it serves.
2. 2Closed, legitimate purposes: vehicle security, performance of the contract, claims handling and recovery in case of theft. No generic commercial purposes just in case.
3. 3A short, justified retention period, with effective deletion when it expires. Keeping the trace of every rental indefinitely is hard to defend.
4. 4Restricted access inside the agency and a procedure for answering anyone who requests access to their data or objects to the processing, with a named person responsible.

None of this is a closed list: the position shifts with the guidance and decisions the AEPD publishes, so read the official information before installing the system and have the contract reviewed by legal counsel before you sign it with customers.

How this fits with booking management

Telematics tells you what the car is doing; the calendar tells you what it is about to do. A mileage alert is worthless if the back-office does not know that unit goes into the workshop on Thursday. That is where a rental platform helps, and it is worth saying what it does not do too. DRIVO is a European marketplace for renting directly from independent agencies: listing a fleet carries no listing fee and no monthly fee, commission is charged only on completed bookings, payouts are automatic through Stripe, and the back-office covers bookings, calendar and fleet management, with verified profiles, reviews and multilingual listings that reach travellers across Europe and North Africa. What DRIVO is not: a telematics system. It does not install devices and does not connect to your tracker.