Commentary

Stephen Wellman
 

So, Apple Is Not Spying On iPhone Users After All

Yesterday the blogosphere erupted when evidence surfaced that Apple was potentially spying on iPhone users. Now other bloggers are claiming that Apple is not spying on its users. So which is it?

Yesterday the blogosphere erupted when evidence surfaced that Apple was potentially spying on iPhone users. Now other bloggers are claiming that Apple is not spying on its users. So which is it?According to German site Heise Online, the user IMEI isn't being transmitted. Here is a look at the issue:


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

While the code says "IMEI," which stands for International Mobile Equipment Identity, it seems that the actual IMEI is not transmitted. Using a sniffer, Heise says they were able to get the information that the applications are actually sending. The strings aren't the same as the test iPhone's IMEI and, in fact, each application sends its own unique code.

According to further testing by Rene at blog docpool, these IDs are identical in all iPhones he has tried. The most plausible explanation: the codes could be just application identifiers. Rumor smashed. Mystery solved. Time to get a bourbon at Big Joe's.

So it seems as if the IDs are all the same, so the iPhone isn't really transmitting IMEIs, it's just labeling some form of code as such. It's still not clear what Apple is doing with this data -- or if this process actually compromises users' privacy. But so far, it looks like it doesn't violate privacy.

I guess that ends that. Or does it? What do you think? Is Apple actually collecting user-specific information from iPhone users? Or is this just all just paranoia?


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links