Académique Documents
Professionnel Documents
Culture Documents
Using Floating Car Data from various sources results in a number of benefits compared to other ways of measuring travel time and speed
information. As cars drive on all roads that are open for traffic it is possible to measure with floating car data travel times and speeds on all roads,
even when construction works take place, forcing traffic for example to go on a temporary lane or drive on the other side of a dual carriageway.
Also when new roads are opened, speed and travel time data can directly be measured and quickly analysed. Additionally, the system does not
have to wait until a vehicle has reached the end of a road section before the travel time is calculated as data can be received regularly along the
route. Floating Car Data enables TomTom to accurately measure speeds, also in cases of low speeds or standstill conditions.
Traffic solutions
From all data collected TomTom provides a range of different services. A quick overview of
products:
1. TomTom Traffic. TomTom Traffic is a product that provides traffic delay information.
This information is used in the navigation application. When there is a delay on the users
route the navigation engine will calculate what the impact is for your specific route. The
Estimated Time of Arrival (ETA) gets updated and if there is a faster route available an
alternative route will be offered. By using this application the driver will always have
access to an accurate travel time prediction and will offer the fastest route available.
Image 1. Real-Time navigation
2.
Custom Travel Times. Road operators have a need for traffic statistics for roads they
are responsible for. Collecting relevant data can be achieved by driving around with
a car or deploying cameras, but with the historical statistics from TomTom this can
easily be deducted. By means of a portal or via an API road operators can query the
historical database. They can obtain statistics like average and median travel times,
but also segment specifics speeds. For example on the image on the right, where you
see a black Saturday analysis for one of the French toll roads. The average speed
was significantly lower than on other weekdays during the summer months.
3.
We will tell the user which data from or about you we use, why we use it, how long we use it, who else can use it and where it is kept.
We will only use the users data for the purposes we have stated to the user.
We keep as little of the users data as possible, and only for as long as we need it. When we no longer need data we destroy it or we
irreversibly anonymize it, so it is no longer linked to the user.
4. If we ask the users permission to use your data for specific purposes, we also allow the user to withdraw the permission.
5. If we have not been able to ask the users permission to collect and use its data and the user dont want us to do so, the user can tell us
and we will act accordingly.
6. We will allow the user to access and correct the users data if it is linked to the users MyTomTom account.
7. We will keep protecting the users data against unauthorized access and accidental loss as best as we reasonably can.
8. If we engage others to use the users information on our behalf, we will ensure they act in accordance with our policies.
9. If we share the users data with others, we will first ask the user for permission, unless there is a legal obligation that prohibits us from
asking.
10. We are open to any questions the user may have about how we use its
data and we will answer them.
In order to fulfill the above promises we take two key items into account in
everything we do. The first item is about the data collection. We ask for explicit
consent with an easy to understand message. On the right side of this page you
find the message that TomTom navigation users will see. This message has been
approved by the Dutch Privacy Authority.
Image 4. Asking for consumers consent on a TomTom navigation device.
Next to the consent of the user it is also important to take key item two into
account, which is the protection of privacy by avoiding re-identification of trips.
TomTom applies a strict code of conduct to respect privacy laws. Historic trip archives can only be used for road traffic and related purposes. No
raw data is provided outside TomTom. When creating products out of the historical archive TomTom will do the processing and TomTom ensures
that re-identification is impossible. This is for example done by providing travel time statistics not per trip, but aggregated in averages and
percentiles. Having this code of conduct has been instrumental in being allowed to consider the historic trip archive as anonymous data.
The future
The connected car will continue to develop itself. With the availability of extended Floating Car Data (x-FCD), new data sources will appear on
the horizon. Experts claim that in the future each car will create gigabytes of data per minute, with data about all kinds of relevant items, from the
activation of ABS to the state of the road or the distance towards the car driving in front of you. With engine sensors and others in and around the
car, a wide range of sensor derived content could be created. This data has most value when shared with the car manufacture or service provides.
The privacy points raised in this paper are also applicable to these developments and it will force each partner in this field to make careful decisions.
With the development of vehicle to vehicle (V2V) and vehicle to infrastructure (V2I), privacy questions are raised. The concept of these two terms
is that cars will not only communicate with a service provider, but also with the infrastructure and surrounding cars. Due to this technology it
becomes possible for cars to share data with each other, for example about upcoming danger. However, this will raise new privacy questions,
specifically when everyone could plug into this communication channel and, without consent, start archiving data. Strict decisions on encryption
and use-cases are required in order to have these new innovations respect privacy laws.
Recommendations
The connected car brings privacy challenges and we as TomTom found our way how to keep innovating while protecting the privacy of our
customers. Handling privacy is not something that can be done instantly the correct way, but requires constant tweaking and adjusting in order to
get it right. We would like to share some recommendations for other technology organizations dealing with similar privacy challenges. This can
be in the field of transportation, but also for any other technology organizations.
First of all it is important to use the privacy by design approach in the development process. This means that you incorporate privacy requirements
from the start of the development of the product. By making this part of the design phase of your project it is easier to react to new insights and
risks.
Another recommendation is to always have proper documentation available, answering the what, why, when, who and where questions. When
documented it is much easier to reflect and adjust decisions, but also to allow externals to validate your approach. And along with this
recommendation we also advise to have a privacy specialist in your organization!
We also have recommendations about the data itself:
Always assume that location data is unique and personal, so it needs to be treated with care;
Try to minimize on the data archive in both volume and time stored;
Create a user-friendly explanation to obtain a valid consent and avoid at all times forcing consent by putting it in the terms and conditions;
Consider the use of pseudonyms, the use of early anonymization and always aggregate the data before publishing;
Be careful when destroying data. Residues, artifacts and meta-data could result in re-identification;
Always keep anonymized data limited to the pre-defined purposes as defined in the consent questions;
Make sure that you control the access at all times;
Consider external auditing.