461
edits
Talk:Drumbeat/Challenges/Privacy Icons: Difference between revisions
Jump to navigation
Jump to search
Talk:Drumbeat/Challenges/Privacy Icons (view source)
Revision as of 00:38, 5 March 2010
, 5 March 2010Adding in a few thoughts around taking a more user-centric approach.
m (Embedding privacy icons image) |
(Adding in a few thoughts around taking a more user-centric approach.) |
||
| Line 2: | Line 2: | ||
1) Designing a creative commons-like system of symbols and heuristics to categorize different websites policies and make them easier to understand for lay users, and | 1) Designing a creative commons-like system of symbols and heuristics to categorize different websites policies and make them easier to understand for lay users, and | ||
<blockquote>I'd bet that our first step should be to try and understand the audiences that we're serving, along with how much information the audience needs and how much complexity they can stomach.<br /><br /> | |||
For the 80% majority of users, it might be that they only care to know if a website's privacy policy and terms of service are safe or unsafe, and that the most complexity they can accept is some kind of simple sliding scale.<br /><br /> | |||
We've ([http://lexpubli.ca LexPublica]) done some thinking around this. I'll work up a [http://blog.lexpubli.ca blog post asap].<br /><br /> | |||
[[User:Zak|Zak Greant]] 00:38, 5 March 2010 (UTC) | |||
</blockquote> | |||
2) Designing modular privacy policy elements so that users can opt in and out of various provisions of the policy to create their own contract with the company. | 2) Designing modular privacy policy elements so that users can opt in and out of various provisions of the policy to create their own contract with the company. | ||
As for the first project, I think the realm of possibilities in privacy statements is too great to be able to simplify it. It wouldn't be practical to come up with a visualization of each kind of information sharing policy, storage encryption, deletion policy, etc. Instead, it would be better to create visualizations for the various categories of policies. From Aza and a variety of other sources, the primary categories of concern seem to be: | As for the first project, I think the realm of possibilities in privacy statements is too great to be able to simplify it. It wouldn't be practical to come up with a visualization of each kind of information sharing policy, storage encryption, deletion policy, etc. Instead, it would be better to create visualizations for the various categories of policies. From Aza and a variety of other sources, the primary categories of concern seem to be: | ||