Kindle Fire Draws Privacy Slam From Congressman

Massachusetts Rep. Ed Markey says Amazon needs to come clean about what it’s doing with user data generated by the hot-selling tablet.

Amazon Kindle Fire: Visual Tour
Amazon Kindle Fire: Visual Tour
(click image for larger view and for slideshow)
A senior Congressman said Amazon is dodging questions about how it's using what he called a "massive" trove of information collected from Kindle Fire users.

In an October letter to Amazon CEO Jeff Bezos, U.S. Rep. Edward Markey (D-Mass) asked for details on how Kindle Fire user data is collected, stored, and used. Amazon replied last month, but in a statement issued Tuesday Markey said the answers were insufficient.


More Security Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

"Amazon's responses to my inquiries do not provide enough detail about how the company intends to use customer information, beyond acknowledging that the company uses this valuable information," Markey said.

[ The consumerization of IT raises security issues. Read Kindle Fire Hits The Office: 5 Security Concerns. ]

The hubbub between Markey and Amazon arose following an Oct. 3rd report in the New York Times, in which the paper noted that Kindle Fire and its Silk browser, which splits page rendering between the device and Amazon's cloud-based AWS servers, "may give Amazon unique insights into the Web clicks, buying patterns, and media habits of Fire users."

In his letter to Bezos, Markey, who is co-chairman of the Congressional Bi-Partisan Privacy Caucus, said, "I am concerned that such a combination will enable Amazon to collect and utilize an extraordinary amount of information about its users' Internet surfing and buying habits." Markey demanded that Amazon provide Congress with details about how it's using the information.

In response, Amazon global public policy VP Paul Misener said the company takes a number of steps to ensure user privacy and security. He said Amazon separates data collected from users from customer identities, only caches content that Web site owners have tagged as acceptable for caching, and routes secure SSL page requests directly from Kindle Fire to the origin servers, bypassing the AWS platform.

"In addition to the other customer-focused protections described above, customers have the option to turn off the cloud acceleration feature of Silk. In that 'off cloud' mode, Web pages go directly to a user's device rather than pass through AWS servers, and customers still enjoy a good browsing experience (though it cannot be as fast as with cloud acceleration turned on)," Misener said in his letter, a copy of which was provided by Markey's office.

In his statement Tuesday, Markey said he wasn't satisfied. "Amazon states 'Customer information is an important part of our business,' but it is also important for customers to know how the company uses their personal information." Markey added, "Amazon is collecting a massive amount of information about Kindle Fire users, and it has a responsibility to be transparent with its customers."

Privacy concerns don't appear to be dampening demand for Kindle Fire, as the device was one of the hottest selling products over the Black Friday to Cyber Monday weekend.

Amazon said it sold four times as many Kindle products on Black Friday as it did last year, and that Kindle Fire, which features a color touchscreen and direct links to Amazon and third-party content like Netflix, topped all Kindle sales. And retail giant Target said the Kindle Fire outsold Apple's iPad 2 in its stores.

Markey said he planned to "follow up" with Amazon to get more information about how the company uses data generated by Kindle Fire users.

In today's uncertain and highly scrutinized financial services industry, achieving effective risk management is vital for survival. The report examines the need for enterprise risk management, the benefits of holistic data management, and ERM best practices. Download the report now. (Free registration required.)


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