Location, location, location

The widelyreported furore over location tracking in smartphones (first with the iPhone, then with the Android platform) has yet again highlighted the apparent contradiction between certain people’s constant need to publicise what they are doing and where they are doing it, whilst also maintaining the absolute right to privacy throughout.

I find this rather strange. Perhaps being a technology geek, I am very much aware of the technical infrastructure (and constant stream of personal data) required to support the services that we use every day. I therefore make a conscious and informed choice when I allow these services to access my information or publish my location. In fact, I am happy to publish my iPhone location data below, as I am aware of the perceived risks:

Tom Crick's iPhone data -- I've been a busy boy

But with Apple today finally breaking radio silence and clarifying how and why they are storing the geo-tagged Wi-Fi hotspot and cell tower data, it all boils down to this: it’s a bug.

Hmmmmm. Being a computer scientist, I have written a fair amount of buggy code in my time, but it is rare when it prompts the question “feature or bug?“. Normally, I would ascribe things like this to cock-up before conspiracy, but it is seems more likely to be about potential revenue generation rather than anything more sinister such as government tracking (as I would question the value of timestamped location data from inaccurate cell tower data).

I think that being able to access my own data is pretty cool, but the collection process should be more explicit and transparent to all types of users: clearly explained and not buried in the 15,200 word iTunes terms and conditions. You should also be able to easily purge the data and it should (at the very least) be encrypted/hashed. You can encrypt your iPhone backup, but this option is not enabled by default.

So, does Apple apologising for forgetting to set an expiry on your data that it collects resolve the issue? Not really. This is a worrying trend from companies such as Microsoft, Google, Apple, et al., who are acting as if personal data is a resource that can be harvested at will. Of course you are free to not use their products or services, but it is vital for this data collection to be open and explicitly opt-in. After recent events, I wouldn’t be surprised if Apple receive a number of Subject Access Requests over the coming weeks in the UK. A positive outcome from all of this would be a wider public debate on the storage and use of personal data.

FYI: your smartphone already knows more about you then you may think.

5 Comments

  1. It shouldn’t be tricky deciding whether something is a bug or a feature: if it was designed in, it’s a feature; otherwise, it’s a bug.

    The tricky part about this is that it all relies on having design specifications: not just having them, in fact, but having complete ones, so that for any aspect of behaviour, it’s possible to determine whether it is described in the design spec or not.

    For a large amount of software, that’s unnecessary, and for all non-trivial software, it’s cumbersome (subject to an appropriate definition of “trivial”), but for something as important as whether or not your phone records its geographical position long-term, and saves this (potentially extraordinarily useful) information, I think it would be hard to imagine that it appeared in a software release by mistake.

    1. Exactly, what is more likely for this functionality appearing across multiple versions of the software: chance/incompetence or design?

      There is a wider problem of the number of clauses granting widespread use of personal data buried in labyrinthine click-through terms and conditions. For example, when there is a change in the App Store terms and conditions, you are presented with a c.130 page document to read and agree to on an iPhone…

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s