Commentary

Mike Fratto
Network Computing  

Privacy Policies Are For PhDs

BNET has a story, Privacy Policies Are Great -- For PhDs, highlighting the point that privacy policies are so obtuse that a college education or better is required to understand them. That point is perfectly clear to anyone who has read a privacy policy or an end-user license agreement (EULA). These policies are written for legal professionals, not the masses.

BNET has a story, Privacy Policies Are Great -- For PhDs, highlighting the point that privacy policies are so obtuse that a college education or better is required to understand them. That point is perfectly clear to anyone who has read a privacy policy or an end-user license agreement (EULA). These policies are written for legal professionals, not the masses.In our recent InformationWeek Analytics 2008 Strategic Security Survey (registration required), a little more than half of respondents indicated they post a privacy policy for customers. The question is, how many people actually read them and, as a follow-on, how many people understand them?

A privacy policy isn't meant to inform you of your rights. A privacy policy is a legal document to be used in legal matters. It is written in a way that legal professionals understand. That's great, but why can't companies create an easy-to-understand privacy policy for the rest of us? Because if they do, they run the risk of making conflicting assertions which can be used against them in a legal fight.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Bottom line: Privacy policies protect the companies that publish them, not you.

BTW, the score used in the BNET article is based on the Simple Measure of Gobbledygook (SMOG). This blog post scored a 13.94, which equates to some college 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