Privacy Icons: Difference between revisions
PrivacyIcons (talk | contribs) No edit summary |
PrivacyIcons (talk | contribs) |
||
Line 1: | Line 1: | ||
<big>'''Privacy Icons'''</big> | <big>'''Privacy Icons'''</big> | ||
== The Problem == | == The Problem == |
Revision as of 13:30, 6 January 2012
Privacy Icons
The Problem
We begin with one major problem about privacy policies (and privacy communications in general): the language in this space is so complicated that users can't understand it. As a result they've generally stopped caring, and when they do take time to think about privacy, they feel duped. Sites make it too complicated to understand, and besides, users have little choice: sometimes there's only one game in town, so to speak, and the price of admission is personal data. And so users don't bother trying to understand or differentiate among the privacy practices of most online sites and services. Businesses, in turn, have trouble conveying to users that they do care about privacy, and this affects their ability to differentiate themselves from competitors based on privacy.
We began our problem-solving process, then, with two points of view (POVs). The first is the POV of the consumer who wants to make better choices about privacy but has become inured to the current landscape and, moreover, has little time to research and process things. The second POV is that of the business that wants to do a better job of communicating its privacy practices.
As the first step of our prototyping and brainstorming sessions, we settled on the business POV—specifically, that of the smaller, less-established startup—because we determined that it's easier to find a platform and gain leverage from the business side. From there, good privacy practices can spread to other businesses, and the benefits will redound to users.
The Idea
We're to find the point where consumer needs—defined both by consumers' demonstrated frustration with the length and density of privacy policies and by the importance of being able to make quick judgments about whether to consent to a privacy practice—meet businesses' desires to make their privacy practices clearer.
To that end we want to give consumers and businesses alike a simple, easy-to-use way to convey and process privacy practices. But we don't mean just to translate websites' privacy policies into simpler icons, or to provide a granular, machine-readable language for mapping privacy practices. We think the solution has to be as simple as it can be. That way users don't get frustrated with learning curves and legalese, and businesses feel comfortable adopting a product that doesn't demand legal nitpicking and constant reconfiguration.
To do this, we're trying to develop some baseline statements or pledges that that consumers find helpful in making the threshold decision of whether to use a site or service, and businesses likewise find useful for communicating that same baseline principle. We plan to craft these statements with input from an ample set of Silicon Valley startups and privacy-interested users. Then we will find a group of startups willing to adopt a pledge or pledges, and publicize this adoption to gain public currency.
We also plan to discuss this concept with stakeholders in the privacy icon space, specifically Mozilla and Disconnect. Eventually we think these pledges could interact with existing or developing icon systems, and could eventually be made machine-readable and integrated into user-facing privacy tools.
Pledge Ideas
The following is a list of possible pledges that startups may make. It is not final.
- We will not sell or share your personal information with a third party unless you specifically opt into that exchange.
- We will not give your personal information to law enforcement unless they follow proper legal process.
- You have a right to download copies of any UGC you place on our service.
- If we ever go offline, or you decide to delete your account with us, we will provide you with a way to get your data back in a useful form.