Skip to content
Company vehicle in Cyprus.

Employee vehicle tracking and GDPR in Cyprus

A vehicle route can reveal a person’s movements. Set the purpose, access and private-use rules before turning tracking on.

Write down why location is necessary

A company vehicle is not an exemption from data-protection law. When a route is linked to a named driver, the location history can be personal data. In Cyprus the GDPR is complemented by Law 125(I)/2018, with the Commissioner for Personal Data Protection as the national supervisory authority. The Commissioner’s Opinion 2/2018 addresses biometric attendance rather than GPS vehicles, but its necessity and proportionality reasoning is a relevant local example. The Article 29 Working Party’s Opinion 2/2017 on data processing at work (WP249) is non-binding guidance. It recommends a proportionality assessment before a monitoring tool is deployed and warns that employee consent is rarely freely given. European data protection guidance treats systematic monitoring of employees, such as tracking the vehicles they drive, as processing that usually needs a data protection impact assessment (DPIA). Before you roll out tracking, check whether one is required; for employee tracking it usually is. The primary sources are linked below.

Name the purpose precisely. “Fleet management” is too broad to decide what should be collected. Dispatching a nearby vehicle may need the latest position during a shift. Investigating a missing vehicle may need a defined incident procedure. Reviewing travel expense may need distance and trip times, not continuous observation of a person. For each purpose, ask whether a less intrusive method would work, what level of location detail is necessary and how long that detail must remain available. Record the reasoning before installation.

Sources: [1][2][3][6][8][9]

Tell employees what the system actually does

A usable notice names the vehicles, data types, purposes, recipients, retention, private-use rules and the contact for questions. It should say who can open live positions and historic trails, whether alerts are generated, and how a mistaken driver assignment can be challenged. If a representative or consultation process applies in your organisation, complete it as part of the rollout. Do not assume a signature on a consent form cures excessive monitoring. The EU workplace opinion and the Cyprus Commissioner’s proportionality approach point to a necessity assessment, not a paper shortcut.

The policy must match the installed controls. Fleet can show private trips with distance and duration but without position. The private mode is triggered by the installed device configuration. A notice that promises “no tracking after hours” would be false if the device is still configured to record public routes after hours. Test the actual configuration and show employees how it works. If a private trip is interrupted or the tracker is moved, retest the rule.

Sources: [2][3][5][7]

Limit who can open a route

The Fleet live directory scopes managers by locations and departments, and the product has distinct permissions for viewing Fleet, opening the live map, managing vehicles and changing alert rules. Use these controls to build an access matrix. A dispatch role may need current vehicle status, while a payroll role needs approved staff hours and not a continuous route. Test a user outside the vehicle’s location scope and confirm the vehicle is absent. Recheck assignments when a manager changes branch or a van moves home location.

For high-risk processing, Article 35 GDPR requires a data protection impact assessment before processing begins. Whether a particular deployment meets that threshold needs a case-specific assessment; the mere presence of a private switch does not decide it. Keep the notice, purpose record, access matrix, retention decision and test result together. Review them when the fleet or use changes. This page is general information, not a ruling that any specific employer’s tracking is lawful.

Sources: [4][5]

Test necessity before installation

For each proposed use of location, write a sentence beginning “We need this record to decide...”. A latest position may be necessary to allocate the nearest available vehicle; a continuous historic trail may not be. An after-hours alert may serve a defined vehicle-security purpose; monitoring every private journey to assess a driver would be a different and much more intrusive purpose. The Cyprus Commissioner’s proportionality reasoning in Opinion 2/2018 concerns biometric attendance, so it is a local illustration of the test, not a GPS-specific permission. The EU workplace-monitoring opinion (WP249, non-binding guidance) recommends the assessment before deployment.

Document alternatives. Could dispatch ask the driver for availability? Could a zone entry event answer the site question without exposing the full route? Can historic access be limited to incidents? Record why a less intrusive method would or would not meet the legitimate need. Revisit the answer when the fleet grows or the software gains new data. A purpose written for ten delivery vans does not automatically cover surveillance of a new category of staff.

Sources: [2][3][6]

Write a notice drivers can use

The notice should be short enough to read and specific enough to test. Name the tracker, the ordinary reporting period, the categories of data, the purpose of live and historic views, the people who can open them and the planned retention. Explain whether driver identity comes from a key or a usual assignment. Say how a driver reports a wrong assignment or asks about a route. If private use is permitted, explain the private-mode control and what remains recorded. Do not say “off” if distance and duration remain in the private record.

Give the notice before the first tracked shift and keep evidence of the version staff received. If the actual configuration changes, update the notice rather than relying on old wording. Where employee representation or a consultation process applies to the organisation, include it in the rollout. Do not invent a universal works-council requirement for Cyprus. Ask the organisation’s adviser to review the specific employment and data-protection context.

Sources: [3][5][7]

Test access with a real vehicle

Create a matrix with roles on one side and actions on the other: see live vehicles, open an old route, manage a vehicle, set an alert, review fuel and inspect staff hours. Assign only the actions each job needs. Fleet has separate permissions and its live directory scopes vehicles through locations and departments. Pick one test van and two managers with different scopes. Confirm that the authorised manager can open it and the other cannot. Repeat after a vehicle changes home location.

Think about historic access separately from live dispatch. A manager handling a complaint may need a past trip; a daily dispatcher may not need months of personal movement. The Fleet product records position views per vehicle, but the organisation must still set an access policy and retention decision. Review access after staff changes. A system with a correct private mode can still expose too much public-route data if permissions are broad.

Verify private mode end to end

A private trip is triggered by the relevant device state and is stored without position; distance and duration remain. Before relying on this, ask the installer to show how the private-mode control activates that state on the actual vehicle. Drive a private test trip, check the manager’s map, check the stored trail and inspect any alert raised during it. The test should establish that no location can be recovered through those views. Record the result with the vehicle and device identifier.

A change to the tracker, its wiring or configuration calls for retesting. Explain to drivers what the office will still know during private mode and who can see that information. Do not make an absolute promise that no data exists. The protection applies to position in Fleet; other business records, such as vehicle distance, may remain. A precise promise is easier to keep and easier for staff to trust.

Keep the decision open to review

Article 35 GDPR requires a data protection impact assessment when the processing is likely to create high risk. That threshold cannot be settled from a marketing page for every employer. Ask the responsible adviser to assess the actual deployment, including scale, monitoring purpose and existing controls. Keep the purpose assessment, any impact assessment, notice, access matrix, retention choice and pilot results together. A change in workforce, device or use should trigger a fresh look.

When an employee challenges a location record, examine the original timestamp, GPS-fix state, device assignment and driver identification. A last known position is not proof of current presence, and a usual-driver name is not proof of who drove. Correct an inaccurate personal assignment through the appropriate process and document the outcome. The goal is a system that supports a legitimate operational decision while leaving room to recognise uncertainty and correct mistakes.

Sources: [4][8][9]

A rollout record a reviewer can inspect

Keep a written purpose for each kind of location use, the less intrusive options considered and the reason the chosen detail is needed. Attach the version of the staff notice given before tracking began. List the roles and specific vehicle scopes that may open live or historic positions. Note the retention decision and any data protection impact assessment required for the actual deployment. This record does not itself make tracking lawful, but it lets an adviser or regulator see what the organisation decided and whether the installed system matches the decision.

Include a private-trip test from a real vehicle. Record how the private-mode control was activated, the trip time and the fact that distance remained while position did not. Test a manager outside the vehicle’s location and department scope and record that access was denied. If a new tracker is installed, repeat the tests. A policy that has never been checked against the fitted device is an aspiration, not an operational control.

Set a route for correction. If an employee disputes a journey, inspect the device timestamp, valid-fix state, tracker-to-vehicle assignment and driver-identification source. Do not treat an old point as proof of current presence or a usual-driver field as proof of the person at the wheel. Record the outcome and amend inaccurate assignments through the appropriate workflow. Revisit the purpose and access matrix when work patterns or vehicle use change.

Test the private trip and the permission boundary

The FTC164 can switch between private and business travel using an installed input or a schedule. Fleet can withhold or drop private positions while retaining distance for the split, and opening private-trip detail requires a distinct Fleet permission. That technical control helps implement a policy, but it does not itself decide the legal basis, notice or retention period. Demonstrate a private journey and check exactly what each role can see before deploying the policy.

A company mileage logbook needs the journey split and a clear account of missing or private route detail. A GNSS-based distance can be less reliable where the sky view is poor, so do not turn it into an insurer-grade odometer claim. The FTC164 has no confirmed insurer approval, and Fleet has no insurance scoring. If a record is disputed, retain the original event and the human explanation separately.

Sources

  1. Cyprus Law 125(I)/2018
  2. Cyprus DPC Opinion 2/2018
  3. Article 29 Working Party Opinion 2/2017
  4. GDPR Article 35
  5. GDPR Article 88
  6. GDPR Article 5
  7. GDPR Article 13
  8. Article 29 Working Party Guidelines on Data Protection Impact Assessment (WP248 rev.01)
  9. EDPB Opinion 10/2019 on the Cyprus draft list of processing operations subject to a DPIA
  10. Teltonika FTC164 features
  11. Teltonika FTC164 system settings

Frequently asked questions

Can an employer track a company vehicle at all?

Potentially, for a documented and proportionate purpose. Assess necessity, transparency and access before deployment; the facts of each workplace matter.

Is employee consent enough?

Do not rely on a signature to cure disproportionate tracking. EU workplace guidance says employee consent is rarely freely given.

Does private mode make the whole deployment compliant?

No. It is one control. The purpose, notice, permissions, retention and any required impact assessment still need review.

Discuss your fleet requirements

Ask for a quote based on your vehicles and operational needs.