W3C home > Mailing lists > Public > public-geolocation@w3.org > May 2009

Re: Additional security and privacy considerations?

From: Rigo Wenning <rigo@w3.org>
Date: Fri, 22 May 2009 21:00:04 +0200
To: Erik Wilde <dret@berkeley.edu>
Cc: Doug Turner <doug.turner@gmail.com>, Alissa Cooper <acooper@cdt.org>, "public-geolocation@w3.org" <public-geolocation@w3.org>
Message-Id: <200905222100.05598.rigo@w3.org>
Hi dret, 

not all data is personal data. Personal data is only data that links 
some property to a natural person or human being. So it really depends 
on the sensor. If a person carries around a sensor (say some small 
matchbox) that delivers location information about her, it still makes 
sense for the user to be informed when location data is transmitted. 
And if you have no UI, you may have a blinking LED or something. I 
think this would be still covered by the wording Thomas is proposing. 

But if the sensor is just a sensor on some package allowing you to 
track it's location, there is no human being involved, thus no 
personal data, no privacy considerations, no UI needed. 

Best, 

Rigo


On Friday 22 May 2009, Erik Wilde wrote:
> another thought i would like to add to this: not all devices  
> implementing the API necessarily have a browser-like UI, or a UI at
>   all. i am thinking of the web of things, where embedded devices
> might implement the API and run widget code, but might have no UI
> at all. do we want to consider this? it certainly doesn't make it
> any easier to come up with a reasonable privacy policy..



Received on Friday, 22 May 2009 19:00:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 August 2009 20:54:11 GMT