« May 2007 | Main | July 2007 »

June 25, 2007

A Clean, Well-Lighted Policy

In the course of our work at WebWatch, we spend a lot of time reviewing privacy policies. And most policies---good or bad---tend to have one thing in common: excessive wordiness.

For example, Yahoo's privacy policy runs to some 1,500 words, while WebMD's clocks in at more than 8,000 words. We don't hold verbosity against them, and rated both these policies as "excellent" on our HealthRatings.org site, since they both spell out exactly how they use your personal information. Both their policies are also well-organized, and WebMD even offers hyperlinks to take you to the relevant section.

But that said, there's something to be said for brevity, especially for consumers without the time or patience to wade through lengthy legalese. And while reviewing sites that sell shoes for one of our sister publications, ShopSmart, we ran across a privacy policy Hemingway himself would have found difficult to state more succinctly.

You can read the policy here, or save yourself a click and read on:

"Jildor Shoes will not sell, rent or share your personally identifiable information with any third party. Your information is used solely for the purpose of completing your purchase or contacting you regarding your purchase."

June 20, 2007

Couldn't Have Said It Worse Ourselves

This story's a little old, but a fun read. Towards the end is this quote:
"The Internet's just a big bluff...If you can make a site look pretty and sound credible, you can pull inquiries in for just about anything and turn the Internet into one great sales-generation machine."
I can't really add or subtract much from that. I found this while preparing for a couple of panels next week for the 29th international ICANN meeting in San Juan, Puerto Rico, which is open to the public.
Worth reading also is this profile of Kevin Ham. It may make you want to quit your day job.

June 05, 2007

The Devil's In the Grammar and Punctuation

Readers of this blog know phishing scam e-mails range from the relatively unsophisticated to those that can fool financial services experts. I've pasted a middling sort of phishing letter below to make the point: If you're good at spelling and grammar, you can spot just about any phishing scam letter.
Most of my high school teachers were Jesuits, and it was Fr. Edward P. McTighe, S.J., that drilled the mechanics of grammar into my head. (Ironically, though, I owe my career to Mrs. Shuster, my 10th grade typing teacher).
So in honor of "Evil Eddie," as some students called him, here's how grammar and punctuation errors flag this note as flim-flam. Problems in italics, explanations in bold.

Dear Washington Mutual Customer,

Washington Mutual is constantly working to ensure security by regularly screening the banking accounts in our system. We recently reviewed your banking account, and we need more information to help us provide you with secure service. Until we can collect this information, your access to sensitive banking account features will be limited. We would like to restore your access as soon as possible, we apologize for the inconvenience. There's the first clue.

Evil Eddie would call that sentence a run-on. It's two separate sentences with subjects, verbs and direct objects ("for the inconvenience" is a noun clause). It needs a conjunction, like "and," but just a period after "possible" and a new sentence would be better.
Why is my banking account access limited ? This one's very minor, but there's an extra typographical space between the last letter of the sentence and the question mark.
Your banking account access has been limited for the following reason(s):

We have reason to believe that your banking account was accessed by a third party. Because protecting the security of your banking account(s) is our primary concern, we have limited your access to sensitive Washington Mutual banking account features. There's a big dangling modifier clause at the beginning of this sentence. A professional writer of memos would probably have switched the order: "We have limited your access to sensitive Washington Mutual banking account features, because protecting your account security is our primary concern." Actually, "sensitive Washington Mutual banking account features" is kind of a giveaway. Wny not just say: "We have limited your online access to your account."
We understand that this may be an inconvenience but please understand that this temporary limitation is for your protection. So here we have two complete sentences separated by a conjunction, which calls for a comma after "inconvenience."
Your case ID for this reason is 0xD2.0x8D.0xDF.0x4B.


How can I restore my account access ? Here's another extra space before a question mark.
Please Log On under your personal link into your banking account and update your account information:

0xD2.0x8D.0xDF.0x4B/online.wamu.com/
Who says "Please Log On" with three capital letters? Someone who learned English at Polytechni Bucuresti. And don't click on links in e-mails like this, but you knew that already.
Completing all of the checklist items will automatically restore your account access.
Actually, completing all of the checklist items will give some bunch of jolly lads in Plovdiv the info they need to clean you out.
Be aware that until we can verify your identity we will have no other liability for your account or any transactions that may have occurred as a result of your failure to upgrade your account as instructed above. Okay, that's just plain flapdoodle, besprinkled with some quasi-legality.


Sincerely,
Washington Mutual Security & Control Department. Okay, here's another little one: You don't put a period after a generic signature. Well, maybe in Kaliningrad, but not here.
© 2007 Washington Mutual All Rights Reserved
Thanks! I don't actually bank at WaMu, anyway, so you guys should buy better spam leads. Or steal better databases.