Privacy Icon


Thanks to Aza Raskin for starting the Privacy Icon project at Drumbeat. It's a very timely effort, if not late. I've been thinking about taking a step forward into this project for a long time, until finally Aza snapped me into it with these icons (I expect people to read that post before even being here); and frankly speaking, it also gave me a head up.

Article List

1. Preamble
Things to care
2. Perversion
Leakage Types
3. Persistence
Storage Duration
4. Provision
User Permissions
5. Preparation
Gearing Tech-Specs
6. Plead
A Request to W3C
7. Preach
Browser Integration
8. Phraud
Malpractice Handling

To make the entire proposal an easy read, I've broken it up in 8 sub-posts, each having a small but complete purpose. The collective ensemble of all of them gives the Privacy Icon proposal a complete meaning.

I won't compel my readers to read each of them against their will. So, read which one ever you wish - although I'd expect you to read all & it'll be necessary for the sake of complete understanding...

First I set my goals. Then I started to put in details one by one, where each element of the icon has something to mean [The Shell, The Loop and The Character]. Although, I ended up designing a solo icon, it has various modes depending upon the privacy policy. So, to express different terms of the privacy policy, it won't require to supply an icon-bundle, but the same icons in varied form. I expect that meaning of the icons are understandable (at least vaguely) by just looking at them, without requiring to read the details. So here are some different representation of the icons -


Example of some gentleman-websites' Icons



And here are some not-so-gentleman Privacy Icons

Designing the icon is only half the task for the agenda which I'm upto. The project is never complete without the World Wide Web embracing, implementing & enforcing it within. So, I've also made an open request to W3C to consider adding Privacy Icon within HTML specification, as soon as possible. The Icon was made taking care of this condition, so that it behaves well when put on the plate. But the implementation is not enough; we also need the web-browsers to understand the specification - and to do something more, possibly.

The only question that can arise, is the abuse & mal-practicing with the Privacy Icon. I am not the one who says the plan is flawless, but I've taken care of it too, as much possible by me. It definitely doesn't stop the cheaters, but warns the user a better way, in case something is not right. There always are better ways to secure things & I'd like people to step forth & light a few bulbs.

I know many of you, at some point, have given it a thought or some have given lots of thoughts - nothing counts out - all are important. Join the Privacy-Icon project at Drumbeat, brainstorm and comment, come out with new ideas, prove me wrong - everyone is welcome.