Data Safety: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 1: Line 1:
DRAFT
<p>DRAFT
This page is edited by afowler. Please don't change without permission.
This page is edited by afowler. Please don't change without permission.
 
</p>
= Charter =
<h1> Charter </h1>
 
<h2> Privacy Principles </h2>
== Privacy Principles ==
<p>Six core privacy principles guide our data practices and operations. These principles stem from the Mozilla Manifesto.  
 
</p>
Six core privacy principles guide our data practices and operations. These principles stem from the Mozilla Manifesto.  
<ul><li> No Surprises. Only use and share information about our users for their benefit and as disclosed in our notices.
 
</li><li> Real Choices. Give our users actionable and informed choices by informing and educating at the point of collection and providing a choice to opt-out whenever possible.
* No Surprises. Only use and share information about our users for their benefit and as disclosed in our notices.
</li><li> Sensible Settings. Establish default settings in our products and services that balance safety and user experience as appropriate for the context of the transaction.
* Real Choices. Give our users actionable and informed choices by informing and educating at the point of collection and providing a choice to opt-out whenever possible.
</li><li> Limited Data. Collect and retain the least amount of information necessary for the feature or task. Try to share anonymous aggregate data whenever possible, and then only when it benefits the web, users, or developers
* Sensible Settings. Establish default settings in our products and services that balance safety and user experience as appropriate for the context of the transaction.
</li><li> User Control. Do not disclose personal user information without the user’s consent. Advocate, develop and innovate for privacy enhancements that put people in control over their information and online experiences.
* Limited Data. Collect and retain the least amount of information necessary for the feature or task. Try to share anonymous aggregate data whenever possible, and then only when it benefits the web, users, or developers
</li><li> Trusted Third Parties. Make privacy a key factor in selecting and interacting with partners.
* User Control. Do not disclose personal user information without the user’s consent. Advocate, develop and innovate for privacy enhancements that put people in control over their information and online experiences.
</li></ul>
* Trusted Third Parties. Make privacy a key factor in selecting and interacting with partners.
<p>For more information on how we arrived at these principles, you can read our blog post from January 12, 2011 entitled, "&lt;a href="http://blog.mozilla.com/privacy/2011/01/12/mozillas-privacy-data-operating-principles/%7CMozilla's"&gt;Privacy &amp; Data Operating Principles&lt;/a&gt;."
 
</p>
For more information on how we arrived at these principles, you can read our blog post from January 12, 2011 entitled, "[http://blog.mozilla.com/privacy/2011/01/12/mozillas-privacy-data-operating-principles/|Mozilla's Privacy & Data Operating Principles]."
 
<h2> Data Safety Design Principles </h2>
<h2> Data Safety Design Principles </h2>
<p>Taking our Privacy Principles down to the data governance layer, we propose a few starting design guidelines:
<p>Taking our Privacy Principles down to the data governance layer, we propose a few starting design guidelines:
Line 26: Line 24:
</li><li> Aggregate whenever possible: we will explore whether we can implement the feature with data aggregated across a significant number of users, rather than keeping individual data points. (Given the richness of these datasets, we cannot pretend that de-identification is particularly useful to protecting individual users.)
</li><li> Aggregate whenever possible: we will explore whether we can implement the feature with data aggregated across a significant number of users, rather than keeping individual data points. (Given the richness of these datasets, we cannot pretend that de-identification is particularly useful to protecting individual users.)
</li></ul>
</li></ul>
<p>Background on these principles are included in our January 13, 2012 blog post entitled, "<a href="http://blog.mozilla.com/privacy/2012/01/13/mozilla-to-offer-new-user-centric-services-in-2012> Mozilla to Offer New User Centric Services in 2012</a>."
<p>Background on these principles are included in our January 13, 2012 blog post entitled, "&lt;a href="http://blog.mozilla.com/privacy/2012/01/13/mozilla-to-offer-new-user-centric-services-in-2012&gt; Mozilla to Offer New User Centric Services in 2012&lt;/a&gt;."
</p>
<h1> Preparing for a Data Safety Consultation </h1>
<h2> Criteria </h2>
<h2> Template </h2>
<h2> Definitions </h2>
<h2> Data Classification </h2>
<h1> Consultation Archive </h1>
<h1> Contributors </h1>
<p><br />
</p>
</p>
= Preparing for a Data Safety Consultation =
== Criteria ==
== Template ==
== Definitions ==
== Data Classification ==
= Consultation Archive =
= Contributors =
Confirmed users
152

edits

Navigation menu