In Italy alone, according to ANIASA data, more than 40% of commercial vans in circulation are in some form of rental or lease — operational lease, financial lease, long-term rental, full-service. Across Europe the share is comparable or higher. For fleet managers, the arrival of Cloud OEM (vehicle tracking via factory connectivity, without aftermarket devices) dramatically changes the telematics setup calculation. No OBD to install at your own expense, fast activation, scalability without limits.
But “everything via Cloud OEM” is not automatic. Five contractual and operational points need verifying before signing a Cloud OEM contract on a leased fleet, on pain of finding yourself six months later with a blocked activation or a cost that doesn’t scale as planned.
This article lists them one by one. Written for fleet managers who have already read the basics of the EU Data Act and want to get to the operational part.
Point 1: who is the “user” of the vehicle for Data Act purposes
The EU Data Act grants the right to access connected vehicle data to the owner or user of the product. In traditional leasing these two roles collapse into the owner; in operational leases and long-term rentals they separate.
The baseline rule, reaffirmed in the European Commission’s Vehicle Data Guidance of late 2024: in an operational lease or long-term rental, the user of the vehicle (i.e., you, the company paying the fee and using the vehicle for its business) is recognised as the “user” for Regulation purposes. So you have the right to request data access and nominate a third-party recipient, even though the formal owner is the leasing company.
But — and this “but” makes the difference — this right often needs to be exercised through formal authorisation from the formal owner (the leasing company). The manufacturer, in order to activate data flow to a third-party provider, wants to see that the consent chain is unambiguous. And in the chain, the lease is a link.
What to verify in the contract:
- Is there a clause recognising the user as “user” for Data Act purposes? If yes, consent is simplified.
- Is there a clause reserving telematics data access to the leasing company? If yes, it needs renegotiating before starting — otherwise the third-party provider will be blocked.
- Does the contract envisage use of telematics data for driver scoring or financial calculation (e.g., integrated insurance)? If yes, there’s likely a layer of leasing-company interest to reconcile.
On new contracts from 2026 onwards, it has become standard practice to request an explicit “Data Act compliance” clause that declares the user’s recognition as user and the absence of constraints on third-party providers.
Point 2: operational lease vs financial lease vs long-term rental
Three contractual forms, three different logics. Worth clarifying before talking about telematics.
Financial lease: the leasing company buys the vehicle, gives it to you for use over a defined period (typically 48-72 months), you pay a fee, at the end you can buy out the vehicle at a pre-set value. On the Data Act side, you’re already de facto the substantive owner — the right to access data is the easiest to exercise, because consent is almost always built into the contract.
Operational lease: the leasing company buys the vehicle and gives it to you for use, but at end of contract the vehicle returns to the leasing company (which resells it on the used market). The fee is lower (predictable-mileage discount), you have right of use but aren’t owner even substantively. On the Data Act side, you’re “user” but consent runs through the formal owner — more formalities.
Long-term rental (LTR): contractually similar to operational lease, but usually includes services (maintenance, tyres, insurance). LTR is the most widespread form in Europe for commercial fleets. Same Data Act logic as operational lease: you’re “user”, consent runs through the rental provider.
The practical difference is that long-term rental often includes a manufacturer or rental telematics package — a package the LTR provider has an interest in keeping active because it monetises it. Enabling Cloud OEM with a third-party provider requires dialogue with the LTR: sometimes it’s allowed without issues, sometimes it requires a contractual amendment.
Point 3: the manufacturer’s or rental provider’s telematics package
Almost all commercial vehicles from Stellantis, VW Group, Ford, Renault sold from 2019 onwards leave the dealership with a base manufacturer telematics package already active. This package is often included in the lease/LTR fee without having been explicitly chosen.
This package does not conflict with Cloud OEM to a third-party provider — the Data Act explicitly allows multiple data recipients. But in practice, three cases to manage:
-
Base telematics package active, data flows only to the manufacturer: no interference with Cloud OEM to third party. You activate both flows in parallel.
-
Premium integrated telematics package (e.g., manufacturer GPS tracking + fuel consumption reporting), for which you pay an additional cost: worth assessing whether to deactivate it once the third-party Cloud OEM provider is operational, to avoid double cost for the same visibility.
-
Rental provider telematics (e.g., Ayvens, Arval, LeasePlan have their own platforms): here the data flow is already activated towards the rental provider’s platform. Cloud OEM activation to a third party is still possible, but it needs verifying that the LTR contract doesn’t explicitly forbid sharing with third parties.
The practical check: in the proposal phase, ask the Cloud OEM provider (e.g., Optivo) to verify for each manufacturer in your fleet what’s already active and what needs activating additionally. It’s a 1-2 day screening that prevents double costs.
Point 4: data portability at end of contract
One of the most important clauses of the Data Act is the right to portability. In a leased fleet that means concretely: data collected during vehicle use (mileage, consumption, driver scoring) is yours, even when the vehicle returns to the leasing company at end of contract.
In practice:
- You have the right to export historical data from the Cloud OEM provider in readable format (CSV, JSON, etc.) — useful for trend analysis, internal benchmarking, ESG audits.
- You have the right to port it to another provider if you decide to change telematics partner — no lock-in.
- The vehicle returns to the lease without the historical data from your activity (the data stays with you), barring specific agreements for anonymous or aggregate vehicle-scoring data.
What to verify in contracts: the Cloud OEM provider must guarantee portability in standard format, without hidden export costs, and without forced retention in its own system. Optivo does this as standard — but worth asking explicitly of any provider you’re evaluating.
Point 5: scalability when vehicles enter or exit
The main advantage of Cloud OEM on a leased fleet is frictionless scalability. When a new vehicle enters, you add the VIN from the dashboard — no workshop, no installation, no vehicle downtime. When a vehicle returns to the lease, you revoke consent and the flow stops.
This is true in theory. In practice, two aspects need contractual handling:
Aspect one: the provider’s pricing model. Cloud OEM contracts typically envisage a fee per active VIN. For a leased fleet with turnover (e.g., 5 vehicles entering and exiting every month on a 25-unit fleet), pricing must be clear: do you pay on active-in-month? Activated-in-year? Is there a minimum threshold below which the fee is fixed? Verify before signing, because on high-turnover fleets the difference between models can be significant.
Aspect two: deactivation vs activation timing. For an exiting vehicle, deactivation is near-instant (you revoke consent, the flow stops). For a new vehicle entering, activation is fast but not instant: it requires the Mobilisights / manufacturer-portal procedure, which takes hours or a few days. On a high-turnover fleet, plan with a small margin — don’t wait until a new vehicle is already in operation to request activation.
To manage this turnover in an orderly way, Optivo offers a VIN management dashboard where you see in real time the status of each vehicle (active, activating, deactivating, off-fleet) — typically integrated with your lease or LTR management system.
When Cloud OEM is the right choice for a leased fleet
Putting the five points together, the ideal profile of a leased fleet for Cloud OEM is:
- Natively connected vehicles (post-2019 models of supported brands)
- Lease/LTR contract explicitly recognising the user as Data Act “user”
- Simple consent chain (bilateral relationship between company and leasing provider, no multiple intermediaries)
- Mid-sized fleet (≥10 vehicles, where Cloud OEM has clear ROI)
- Required telematics visibility at “operational” level (position, consumption, basic scoring — not engine immobilisation or cold chain)
When these five criteria are met, Cloud OEM beats aftermarket OBD on every dimension: lower upfront cost, less management, more scalability.
When one or more criteria are not met (e.g., pre-2019 vehicles, LTR contracts with restrictive clauses, advanced telemetry needs on part of the fleet), the path is a mixed mode: Cloud OEM on the part of the fleet where it works, OBD or CAN bus on the rest. The important thing is that all tracking modes converge into the same dashboard — otherwise the operational advantage is lost.
If you want to understand how your leased fleet maps to these five points, see what we support on Cloud OEM or request a VIN assessment. Response within 24 business hours with how many of your vehicles can be activated immediately and which require additional contractual steps.
Read next: Cloud OEM Stellantis with Mobilisights: how it really works — if your fleet is predominantly Stellantis (Fiat, Peugeot, Citroën, Opel), this is the most frequent operational case for Cloud OEM. Steps, timing, costs of the Mobilisights process explained in detail.