From 894f5ef836aba610585b1ed803c99e276a6de51d Mon Sep 17 00:00:00 2001
From: Joseph Abhayaratna Efficacy of Mobility Data
should be undertaken to prove the efficacy of the application before the application is introduced and
geospatial data captured as a result.
+ Extensive User testing required to prove underlying technology. +
There is context to efficacy of course, you might want to try a technique that is unproven if circumstances are severe, a global pandemic might be such an example? If so would it be acceptable to experiment first to @@ -372,7 +374,9 @@
+ Data collection for specific purposes limited in coverage."> +
Related to the temporal aspect of such data collection of course is the spatial context, an application collecting information on the movements of a commuter in Paris should not collect data when the user is on @@ -396,7 +400,9 @@
+ Solutions should be accessible to all members of society."> +
Access to technology may also vary for other societal or cultural differences and this may not be easily understood or unexpected, it there is an urgent need to build solutions based on ambient location, there @@ -427,7 +433,9 @@
These design principles are by no means comprehensive but a useful starting point.
- ++ Location Data collection and or sharing should be voluntary. +
It should be clear the collection and sharing of location data are different things. There are many use cases that might require a user's location to be obtained, but that data does not need to be stored on @@ -439,8 +447,10 @@
+ There should be an explicit mechanism to obtain user consent to the collect and then share Ambient Location + Information. +
Even if the collection and sharing of location data is not optional there should be an explicit notification and ongoing reaffirmation of the users agreement. This is important particularly if location sharing is a @@ -454,7 +464,9 @@
+ The purpose of data collection and/or sharing must be explained. +
This is already a key foundation of most good data protection regulations, you need to explain clearly why you are collecting location information and how it will be used. @@ -465,7 +477,9 @@
+ Data Collection/Sharing should be limited in scope. +
Again a key data protection principle is to only collect the minimum amount of data required, there is no allowable concept of “nice to have in case we need it”. @@ -483,7 +497,9 @@
+ Data must be kept securely and by default anonymously. +
There needs to be a really, really good reason for Ambient Location information not to be anonymous. For most of the current popular applications where Ambient Location information is used to “sense” the world, @@ -507,7 +523,9 @@
+ Location data may be Personally Identifiable Information (PII)? +
The data that can be considered to be personally identifiable extends beyond the obvious name, address and telephone number and there are grey areas specifically with types of Geospatial Information. @@ -527,7 +545,9 @@
+ Location data storage must be time & space limited. +
Is the collection of Ambient Location Information temporary and limited to a defined period of storage, and if not why not ? Again of course there may be applications where the user might want data to be stored