Home
Larry Seltzer

Larry Seltzer



Google And Privacy: Nothing To See Here, Move On

Comments | Larry Seltzer, BYTE | January 27, 2012 02:29 PM

Category: Gaming, Social Networking

People say they take their privacy seriously, and who can blame them? There are all kinds of reasons to keep personal data personal, some of them better than others.

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

The way the Web works--and this is at least as much a business issue as a technical one--requires that we share some amount of personal information with the (generally free) services we use. A vast group of private companies and public interest groups have been built to feed off the genuine concerns as well as the paranoia about this issue.

Thus it was entirely predictable that outrage would be expressed when Google announced a major consolidation of their privacy policies. The most obvious effect of this change is to make their privacy policies simpler, which should be considered a significantly good thing and something that so-called privacy advocates have long called for.

But some people are only interested in constructing theoretical problems. Congressman Ed Markey of Massachusetts, always one to blow hard on these matters, says: "...it is imperative that users will be able to decide whether they want their information shared across the spectrum of Google's offerings..." Why? So Google might use your e-mail information in their calendar program? Both are run by Google. Whether it's shared or not, you're still trusting Google to keep it private.

The only reason I can imagine for users not wanting one Google service to have access to their personal data from another Google service is that they don't trust the other service as much to keep it private. There just isn't any logic to this. All the services follow the same policy. From a policy standpoint, none is any more or less trustworthy than the other. From a technical standpoint, perhaps you could argue that sharing among services increases the risk of accidental disclosure. Maybe there's a theoretical case for this, but it's basically just sophistry.

I read the whole policy and it's pretty accessible and understandable, which is not a common thing for privacy policies. Microsoft's privacy policies are much longer and more complicated, although that seems to come mostly from covering more bases. Google's policy seems designed to express broad principles in a simple way. Both approaches are defensible. Neither company's record on privacy is perfect, but I see no reason to believe that they don't both take it very seriously for the simple reason that users and the law demand it.

Nobody's forcing you to use any Google services and some (such as search) can be used anonymously. Don't like it? Take your business elsewhere.

The reason privacy policies have always been--and always will be--a contentious issue is that the isues are extremely complicated. The sort of user power that the EFF and Ed Markey advocate would result in significantly less-capable software. People say they take their privacy seriously, but the fact is that they're happy to share some of that information if it makes their software run better. Who can blame them for that?

Follow Larry Seltzer and BYTE on Twitter, Facebook, LinkedIn, and Google+:



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

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE 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. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

COMMENTS

Tune In to BYTE
Facebook Twitter LinkedIn Newsletter RSS
Whitepapers
whitepaper
In this paper you will learn the five trends shaping the future of enterprise mobility. Learn how the rise of social media as a business application, the lurring between work and home, the emergence of new mobile devices, the demand for tech savvy employees and changing expectations of corporate IT will fundamentally change the workplace.
whitepaper
In a survey of more than 1,700 information workers (iWorkers) in North America, notebooks, desktops, and smartphones were found to be “must-have” devices, while tablets, slates, and netbooks were relegated to “nice-to-have” status, according to a commissioned study conducted by Forrester Consulting on behalf of Dell and Intel.
Sponsored by: Dell
Upcoming Events