Does your company use a Satnav’s in your company vehicles or on their fleet vehicles? If so, you might be concerned to know that Satnav’s are about to be affected under the new General Data Protection Regulation legislation which is due to come into force in May this year.

The new GDPR Law outlines that companies will need to take responsibility for any records they hold and will need to delete any old data material before selling on a vehicle or returning a vehicle to a lease company. This will affect all in built car Satnav’s and will cover all types of data including addresses and routes, plus telephone records.

Given the fact that independent vehicle brands come with differing Satnav’s and individual technology, this could be quite a task for businesses, especially when handling large volumes of fleet vehicles which could potentially hold a few years’ worth of data.

Sam Watkins, deputy chair at the Vehicle Remarketing Association (VRA), says: “It’s probably a good idea in general that this data should be deleted – it provides a very good indication of a person’s movements, work and social activities – but GDPR makes it a legal responsibility. At some point in the supply chain, it has to be deleted. The question is – who should be responsible for doing this?”

Managing and cleaning Satnav data will become a costly task for organisations

The consensus is that this is inevitably going to be a headache for remarketing companies who manage fleet vehicles, due to the time involved and the complications raised when clearing down the systems, however it will be essential that businesses comply to the legislation and implement the process as part of their daily activity.

For more information on data protection and what compliance is required of your company, please contact our dedicated data protection team here at Crendon Insurance Ltd. Specialising in GDPR legislation and all related data protection issues, we are able to support businesses with the right tools to ensure that their company implements the correct data protection insurance.


Blogs used to write this article: