Privacy/Roadmap 2011: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "<small>< Product Roadmaps </small> <section begin=summary />{{RoadmapSummary |icon=Privacy-512-noshadow.png |pagelocation=Privacy/Roadmap_2011 |pagetitle=Privacy an...")
 
No edit summary
 
(49 intermediate revisions by 3 users not shown)
Line 2: Line 2:


<section begin=summary />{{RoadmapSummary
<section begin=summary />{{RoadmapSummary
|icon=Privacy-512-noshadow.png
|icon=Privacy100.png
|pagelocation=Privacy/Roadmap_2011
|pagelocation=Privacy/Roadmap_2011
|pagetitle=Privacy and User Control 2011 Roadmap
|pagetitle=Privacy and User Control 2011 Roadmap
|owner=[[User:Sidstamm|Sid Stamm]]
|owner=[[User:Sidstamm|Sid Stamm]]
|updated=Feb 15, 2011
|updated=Apr 22, 2011
|status=Draft
|status=Draft
|description=
|description=The vision behind Mozilla's 2011 privacy roadmap is focused on users, calling for increased anonymity on the web, starting with sensible privacy defaults, giving users the ability to make informed choices about disclosing their information, facilitating web transparency so users understand how their data is being collected and used, and allowing for flexibility while maintaining sensible baselines for those who are not interested in privacy.
}}<section end=summary />
}}<section end=summary />


{{Draft}}
<div style="margin: 1em 0px; border: 2px solid orange; padding: 1em; background-color: #FFC; text-align: center;">'''DEPRECATED.'''
<div style="font-size:x-small">This page is old and crufty. For the latest, go back to [[Privacy/Roadmap]].</div></div>




Line 24: Line 25:
== Operating Principles: ==
== Operating Principles: ==


* Transparency / No Surprises
Mozilla uses [http://firstpersoncookie.wordpress.com/2011/01/12/mozillas-draft-privacy-data-operating-principles/ a set of privacy operating principles] as guidelines as we do work to grow the Web.  Those principles that specifically relate to privacy in Firefox are:
* User-Informed Choice
* Sensible Defaults
* Minimal Disclosure


== Themes: ==
; Transparency / No Surprises : Only use and share information about our users for their benefit and as disclosed in our notices.
; Real Choice : 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.
; Sensible Defaults : Establish default settings in our products and services that balance safety and user experience as appropriate for the context of the transaction.
; 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
 
== Themes and Goals: ==
Here the concrete goals are segmented into themes.  Some goals may potentially fit into multiple themes, but are only identified here under the most relevant one.
Here the concrete goals are segmented into themes.  Some goals may potentially fit into multiple themes, but are only identified here under the most relevant one.
   
   
Each specific goal relates to either Firefox (product users/web sites) or the ecosystem (standards bodies, other products' users) or both.  They are annotated as such.
Each specific goal relates to either Firefox (product users/web sites) or the ecosystem (standards bodies, other products' users) or both.  They are annotated as such.


=== Improve Private & Pseudoanonymous Browsing ===
'''NOTE:''' these goals are tentative and more may be added or some may be dropped.
* Per-tab/window private mode
 
* Incorporate fingerprint-minimizing features into private browsing ([[Security/Anonymous Browsing]]).
=== Improve Private & Semi-anonymous Browsing ===
* Explore randomizing non-essential HTTP request data that can be used for fingerprinting
 
* Bring private browsing mode's behavior and users' expectations together.
<table class="querytable sortable">
* Explore potentially using a journaled profile service so all modifications to a profile can be rolled back when user exits private mode
<tr>
* Rebuild and simplify Private Browsing Mode
<td class="header" style="width: 5%;">Pr</td>
** When entering, PB create a new profile
<td class="header" style="width: 35%;">Feature</td>
** When exiting, kill and shred profile.
<td class="header" style="width: 10%;">Stage</td>
<td class="header" style="width: 10%;">Release target</td>
<td class="header" style="width: 20%;">Product manager</td>
<td class="header" style="width: 20%;">Feature manager</td>
</tr>
{{#ask: [[Category:Feature Page]] [[Feature roadmap::Privacy]] [[Feature theme::Improve Private & Semi-anonymous Browsing]]
| ?#
| ?Feature name#
| ?Feature priority#
| ?Feature stage#
| ?Feature version#
| ?Feature product manager#
| ?Feature feature manager#
| mainlabel=-
| sort=Feature priority, Feature stage
| format=template
| limit=500
| template=FeatureListTable
}}
<tr>
<td> P3
<td> Explore randomizing non-essential HTTP request data that can be used for fingerprinting
<td> Concept
<td> `
<td> Sid Stamm
<td> `
</tr>
<tr>
<td> P3
<td> Investigate simplifying Private Browsing Mode into profile switching.
<td> Concept
<td> `
<td> Sid Stamm
<td> `
</tr>
<tr>
<td> P3
<td> Explore potentially using a journaled profile service so all modifications to a profile can be rolled back when user exits private mode
<td> Concept
<td> `
<td> Sid Stamm
<td> `
</tr>
</table>


=== Secure Network Connections ===
=== Secure Network Connections ===
* Help users understand which bits are unencrypted (e.g., identify form fields that will be transmitted in the clear)
 
* Identify and deploy a "safe" mixed-content SSL/TLS mode, displaying "secure" UI indicators to users. (e.g., http images + https html is safe)
<table class="querytable sortable">
* Create API for add-ons and components that provides check-point between TLS/SSL handshake and HTTP request, allowing add-ons greater scrutiny of secure connections before they are used.
<tr>
<td class="header" style="width: 5%;">Pr</td>
<td class="header" style="width: 35%;">Feature</td>
<td class="header" style="width: 10%;">Stage</td>
<td class="header" style="width: 10%;">Release target</td>
<td class="header" style="width: 20%;">Product manager</td>
<td class="header" style="width: 20%;">Feature manager</td>
</tr>
{{#ask: [[Category:Feature Page]] [[Feature roadmap::Privacy]] [[Feature theme::Secure Network Connections]]
| ?#
| ?Feature name#
| ?Feature priority#
| ?Feature stage#
| ?Feature version#
| ?Feature product manager#
| ?Feature feature manager#
| mainlabel=-
| sort=Feature priority, Feature stage
| format=template
| limit=500
| template=FeatureListTable
}}
</table>


=== Deploy Safe and Rational Defaults ===
=== Deploy Safe and Rational Defaults ===
* Reduce the amount of information sent with the HTTP Referer header
 
* Explore turning off more fingerprinting entropy sources
<table class="querytable sortable">
<tr>
<td class="header" style="width: 5%;">Pr</td>
<td class="header" style="width: 35%;">Feature</td>
<td class="header" style="width: 10%;">Stage</td>
<td class="header" style="width: 10%;">Release target</td>
<td class="header" style="width: 20%;">Product manager</td>
<td class="header" style="width: 20%;">Feature manager</td>
</tr>
{{#ask: [[Category:Feature Page]] [[Feature roadmap::Privacy]] [[Feature theme::Deploy Safe and Rational Defaults]]
| ?#
| ?Feature name#
| ?Feature priority#
| ?Feature stage#
| ?Feature version#
| ?Feature product manager#
| ?Feature feature manager#
| mainlabel=-
| sort=Feature priority, Feature stage
| format=template
| limit=500
| template=FeatureListTable
}}
<tr>
<td> P3
<td> Explore turning off more fingerprinting entropy sources
<td> not started
<td> `
<td> Sid Stamm
<td> `
</tr>
</table>


=== Enable Control of Tracking and Third-Party Sharing ===
=== Enable Control of Tracking and Third-Party Sharing ===
* Disable third-party cookies by default
 
* Create API so sites can request third-party cookies (may tie into next goal)
[[Privacy/Roadmap/Tracking]] shows more detail on the third-party tracking work.
* Create unified API for sites to request additional potentially privacy-sensitive features (geolocation, a:ping, local storage, etc)
 
** DougT started on this.  Initally was going to be part of the desktop notification w3c wg, but was punted out.
<table class="querytable sortable">
* Develop "tracking alert" that informs users when an entity is tracking them across sites.
<tr>
* investigate implementing ping attribute for explicit tracking for honest organizations who want to track when users consent.
<td class="header" style="width: 5%;">Pr</td>
* Changes to Geolocation
<td class="header" style="width: 35%;">Feature</td>
** Disable automated discovery
<td class="header" style="width: 10%;">Stage</td>
** Let the user pick where they are using a map or other UI
<td class="header" style="width: 10%;">Release target</td>
** Map could be assisted by automated discovery
<td class="header" style="width: 20%;">Product manager</td>
<td class="header" style="width: 20%;">Feature manager</td>
</tr>
{{#ask: [[Category:Feature Page]] [[Feature roadmap::Privacy]] [[Feature theme::Enable Control of Tracking and Third-Party Sharing]]
| ?#
| ?Feature name#
| ?Feature priority#
| ?Feature stage#
| ?Feature version#
| ?Feature product manager#
| ?Feature feature manager#
| mainlabel=-
| sort=Feature priority, Feature stage
| format=template
| limit=500
| template=FeatureListTable
}}
<tr>
<td> P3
<td> investigate implementing ping attribute for explicit tracking for honest organizations who want to track when users consent.
<td> Concept
<td> `
<td> Sid Stamm
<td> `
</tr>
<tr>
<td> P3
<td> Explore disabling third-party cookie sending by default
<td> Concept
<td> `
<td> Sid Stamm
<td> `
</tr>
</table>


=== Enhance User Controlled Disclosure ===
=== Enhance User Controlled Disclosure ===
* Plugin awareness of users privacy prefs (e.g., clear history)
 
* In-flight as-it-happens control of disclosure (versus a preference pane)
<table class="querytable sortable">
* Better site-based data management UI
<tr>
* Improve the geolocation UX so it's better connected to the user (user knows when geolocation data is being used)
<td class="header" style="width: 5%;">Pr</td>
<td class="header" style="width: 35%;">Feature</td>
<td class="header" style="width: 10%;">Stage</td>
<td class="header" style="width: 10%;">Release target</td>
<td class="header" style="width: 20%;">Product manager</td>
<td class="header" style="width: 20%;">Feature manager</td>
</tr>
{{#ask: [[Category:Feature Page]] [[Feature roadmap::Privacy]] [[Feature theme::Enhance User Controlled Disclosure]]
| ?#
| ?Feature name#
| ?Feature priority#
| ?Feature stage#
| ?Feature version#
| ?Feature product manager#
| ?Feature feature manager#
| mainlabel=-
| sort=Feature priority, Feature stage
| format=template
| limit=500
| template=FeatureListTable
}}
</table>


=== Enrich Add-ons ===
=== Enrich Add-ons ===
* Use privacy icons or similar to show what capabilities add-ons have
<table class="querytable sortable">
* Migrate as many add-ons as possible to a capabilities manifest system as proposed for Jetpack (add-ons ask for capabilities and that's all they get to do).
<tr>
<td class="header" style="width: 5%;">Pr</td>
<td class="header" style="width: 35%;">Feature</td>
<td class="header" style="width: 10%;">Stage</td>
<td class="header" style="width: 10%;">Release target</td>
<td class="header" style="width: 20%;">Product manager</td>
<td class="header" style="width: 20%;">Feature manager</td>
</tr>
{{#ask: [[Category:Feature Page]] [[Feature roadmap::Privacy]] [[Feature theme::Enrich Add-ons]]
| ?#
| ?Feature name#
| ?Feature priority#
| ?Feature stage#
| ?Feature version#
| ?Feature product manager#
| ?Feature feature manager#
| mainlabel=-
| sort=Feature priority, Feature stage
| format=template
| limit=500
| template=FeatureListTable
}}
</table>


=== Improve Local Privacy ===
=== Improve Local Privacy ===
* Explore requiring master password when using Sync to protect locally stored passwords.
<table class="querytable sortable">
* Improve the UX on master password so that it is comfortable to be used by default. ("Log-In to your Browser")
<tr>
<td class="header" style="width: 5%;">Pr</td>
<td class="header" style="width: 35%;">Feature</td>
<td class="header" style="width: 10%;">Stage</td>
<td class="header" style="width: 10%;">Release target</td>
<td class="header" style="width: 20%;">Product manager</td>
<td class="header" style="width: 20%;">Feature manager</td>
</tr>
{{#ask: [[Category:Feature Page]] [[Feature roadmap::Privacy]] [[Feature theme::Improve Local Privacy]]
| ?#
| ?Feature name#
| ?Feature priority#
| ?Feature stage#
| ?Feature version#
| ?Feature product manager#
| ?Feature feature manager#
| mainlabel=-
| sort=Feature priority, Feature stage
| format=template
| limit=500
| template=FeatureListTable
}}
</table>


=== Improve User Authentication ===
=== Improve User Authentication ===
* Account Manager
<table class="querytable sortable">
* Improve transparency of authentication state so users know when they're sending credentials to sites (and which ones)
<tr>
* Explore deploying an API for sites to trigger second-factor authentication (e.g., SMS) through the browser.
<td class="header" style="width: 5%;">Pr</td>
<td class="header" style="width: 35%;">Feature</td>
<td class="header" style="width: 10%;">Stage</td>
<td class="header" style="width: 10%;">Release target</td>
<td class="header" style="width: 20%;">Product manager</td>
<td class="header" style="width: 20%;">Feature manager</td>
</tr>
{{#ask: [[Category:Feature Page]] [[Feature roadmap::Privacy]] [[Feature theme::Improve User Authentication]]
| ?#
| ?Feature name#
| ?Feature priority#
| ?Feature stage#
| ?Feature version#
| ?Feature product manager#
| ?Feature feature manager#
| mainlabel=-
| sort=Feature priority, Feature stage
| format=template
| limit=500
| template=FeatureListTable
}}
</table>


=== Research & Understand Data Sharing ===
=== Research & Understand Data Sharing ===
* Find a way to visualize and present to users the way a site interacts with other entities (sharing cookies, XHR, etc).  This can help them understand data sharing patterns. (beltzner: Privacy Reports)
<table class="querytable sortable">
* Leverage information we have about sites' data sharing habits to publish anonymous statistics on privacy practices (Test Pilot?)
<tr>
* Use concept series to harness designers' talent in finding a good way to represent data sharing patterns to users.
<td class="header" style="width: 5%;">Pr</td>
<td class="header" style="width: 35%;">Feature</td>
<td class="header" style="width: 10%;">Stage</td>
<td class="header" style="width: 10%;">Release target</td>
<td class="header" style="width: 20%;">Product manager</td>
<td class="header" style="width: 20%;">Feature manager</td>
</tr>
{{#ask: [[Category:Feature Page]] [[Feature roadmap::Privacy]] [[Feature theme::Research & Understand Data Sharing]]
| ?#
| ?Feature name#
| ?Feature priority#
| ?Feature stage#
| ?Feature version#
| ?Feature product manager#
| ?Feature feature manager#
| mainlabel=-
| sort=Feature priority, Feature stage
| format=template
| limit=500
| template=FeatureListTable
}}
<tr>
<td> P3
<td> Leverage information we have about sites' data sharing habits to publish anonymous statistics on privacy practices (Test Pilot?)
<td> Research
<td> `
<td> Sid Stamm
<td> `
</tr>
<tr>
<td> P3
<td> Use concept series to harness designers' talent in finding a good way to represent data sharing patterns to users.
<td> Research
<td> `
<td> Sid Stamm
<td> `
</tr>
</table>
 
=== Uncategorized ===
<table class="querytable sortable">
<tr>
<td class="header" style="width: 5%;">Pr</td>
<td class="header" style="width: 35%;">Feature</td>
<td class="header" style="width: 10%;">Stage</td>
<td class="header" style="width: 10%;">Release target</td>
<td class="header" style="width: 20%;">Product manager</td>
<td class="header" style="width: 20%;">Feature manager</td>
</tr>
{{#ask: [[Category:Feature Page]] [[Feature roadmap::Privacy]] [[Feature theme::`]]
| ?#
| ?Feature name#
| ?Feature priority#
| ?Feature stage#
| ?Feature version#
| ?Feature product manager#
| ?Feature feature manager#
| mainlabel=-
| sort=Feature priority, Feature stage
| format=template
| limit=500
| template=FeatureListTable
}}
</table>


= Roadmap =
= Roadmap =
This is our plan for Product Privacy and Data Control improvements in 2011.


== Q1 2011 ==
Links to implementation plan and progress:
== Q2 2011 ==
* [[Firefox/Flight Tracking]]
== Q3 2011 ==
* [[Firefox/Features]]
== Q4 2011 ==
 
 
 
[[Category:Roadmaps]]

Latest revision as of 19:56, 27 April 2012

< Product Roadmaps

Privacy100.png Privacy and User Control 2011 Roadmap
Owner: Sid Stamm Updated: 2012-04-27
The vision behind Mozilla's 2011 privacy roadmap is focused on users, calling for increased anonymity on the web, starting with sensible privacy defaults, giving users the ability to make informed choices about disclosing their information, facilitating web transparency so users understand how their data is being collected and used, and allowing for flexibility while maintaining sensible baselines for those who are not interested in privacy.
DEPRECATED.
This page is old and crufty. For the latest, go back to Privacy/Roadmap.


Vision:

  • Provide Increased Anonymity -- users who don't want to be fingerprinted should still be allowed to surf the web with reasonable expectations of pseudo-anonymity.
  • Start with Sensible Defaults -- where possible, default to non disclosure of information
  • Provide User-Informed Choice -- provide users contextually helpful, timely, and understandable choices when disclosing information
  • Facilitate Web Transparency -- help sites and service providers be transparent with their data collection and use practices
  • Allow but don't require Flexibility -- provide users flexibility to customize their defaults, but maintain sensible baselines for those less invested in privacy

Operating Principles:

Mozilla uses a set of privacy operating principles as guidelines as we do work to grow the Web. Those principles that specifically relate to privacy in Firefox are:

Transparency / No Surprises
Only use and share information about our users for their benefit and as disclosed in our notices.
Real Choice
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.
Sensible Defaults
Establish default settings in our products and services that balance safety and user experience as appropriate for the context of the transaction.
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

Themes and Goals:

Here the concrete goals are segmented into themes. Some goals may potentially fit into multiple themes, but are only identified here under the most relevant one.

Each specific goal relates to either Firefox (product users/web sites) or the ecosystem (standards bodies, other products' users) or both. They are annotated as such.

NOTE: these goals are tentative and more may be added or some may be dropped.

Improve Private & Semi-anonymous Browsing

{{#ask: Feature roadmap::PrivacyFeature theme::Improve Private & Semi-anonymous Browsing | ?# | ?Feature name# | ?Feature priority# | ?Feature stage# | ?Feature version# | ?Feature product manager# | ?Feature feature manager# | mainlabel=- | sort=Feature priority, Feature stage | format=template | limit=500 | template=FeatureListTable }}
Pr Feature Stage Release target Product manager Feature manager
P3 Explore randomizing non-essential HTTP request data that can be used for fingerprinting Concept ` Sid Stamm `
P3 Investigate simplifying Private Browsing Mode into profile switching. Concept ` Sid Stamm `
P3 Explore potentially using a journaled profile service so all modifications to a profile can be rolled back when user exits private mode Concept ` Sid Stamm `

Secure Network Connections

{{#ask: Feature roadmap::PrivacyFeature theme::Secure Network Connections | ?# | ?Feature name# | ?Feature priority# | ?Feature stage# | ?Feature version# | ?Feature product manager# | ?Feature feature manager# | mainlabel=- | sort=Feature priority, Feature stage | format=template | limit=500 | template=FeatureListTable }}
Pr Feature Stage Release target Product manager Feature manager

Deploy Safe and Rational Defaults

{{#ask: Feature roadmap::PrivacyFeature theme::Deploy Safe and Rational Defaults | ?# | ?Feature name# | ?Feature priority# | ?Feature stage# | ?Feature version# | ?Feature product manager# | ?Feature feature manager# | mainlabel=- | sort=Feature priority, Feature stage | format=template | limit=500 | template=FeatureListTable }}
Pr Feature Stage Release target Product manager Feature manager
P3 Explore turning off more fingerprinting entropy sources not started ` Sid Stamm `

Enable Control of Tracking and Third-Party Sharing

Privacy/Roadmap/Tracking shows more detail on the third-party tracking work.

{{#ask: Feature roadmap::PrivacyFeature theme::Enable Control of Tracking and Third-Party Sharing | ?# | ?Feature name# | ?Feature priority# | ?Feature stage# | ?Feature version# | ?Feature product manager# | ?Feature feature manager# | mainlabel=- | sort=Feature priority, Feature stage | format=template | limit=500 | template=FeatureListTable }}
Pr Feature Stage Release target Product manager Feature manager
P3 investigate implementing ping attribute for explicit tracking for honest organizations who want to track when users consent. Concept ` Sid Stamm `
P3 Explore disabling third-party cookie sending by default Concept ` Sid Stamm `

Enhance User Controlled Disclosure

{{#ask: Feature roadmap::PrivacyFeature theme::Enhance User Controlled Disclosure | ?# | ?Feature name# | ?Feature priority# | ?Feature stage# | ?Feature version# | ?Feature product manager# | ?Feature feature manager# | mainlabel=- | sort=Feature priority, Feature stage | format=template | limit=500 | template=FeatureListTable }}
Pr Feature Stage Release target Product manager Feature manager

Enrich Add-ons

{{#ask: Feature roadmap::PrivacyFeature theme::Enrich Add-ons | ?# | ?Feature name# | ?Feature priority# | ?Feature stage# | ?Feature version# | ?Feature product manager# | ?Feature feature manager# | mainlabel=- | sort=Feature priority, Feature stage | format=template | limit=500 | template=FeatureListTable }}
Pr Feature Stage Release target Product manager Feature manager

Improve Local Privacy

{{#ask: Feature roadmap::PrivacyFeature theme::Improve Local Privacy | ?# | ?Feature name# | ?Feature priority# | ?Feature stage# | ?Feature version# | ?Feature product manager# | ?Feature feature manager# | mainlabel=- | sort=Feature priority, Feature stage | format=template | limit=500 | template=FeatureListTable }}
Pr Feature Stage Release target Product manager Feature manager

Improve User Authentication

{{#ask: Feature roadmap::PrivacyFeature theme::Improve User Authentication | ?# | ?Feature name# | ?Feature priority# | ?Feature stage# | ?Feature version# | ?Feature product manager# | ?Feature feature manager# | mainlabel=- | sort=Feature priority, Feature stage | format=template | limit=500 | template=FeatureListTable }}
Pr Feature Stage Release target Product manager Feature manager

Research & Understand Data Sharing

{{#ask: Feature roadmap::PrivacyFeature theme::Research & Understand Data Sharing | ?# | ?Feature name# | ?Feature priority# | ?Feature stage# | ?Feature version# | ?Feature product manager# | ?Feature feature manager# | mainlabel=- | sort=Feature priority, Feature stage | format=template | limit=500 | template=FeatureListTable }}
Pr Feature Stage Release target Product manager Feature manager
P3 Leverage information we have about sites' data sharing habits to publish anonymous statistics on privacy practices (Test Pilot?) Research ` Sid Stamm `
P3 Use concept series to harness designers' talent in finding a good way to represent data sharing patterns to users. Research ` Sid Stamm `

Uncategorized

{{#ask: Feature roadmap::PrivacyFeature theme::` | ?# | ?Feature name# | ?Feature priority# | ?Feature stage# | ?Feature version# | ?Feature product manager# | ?Feature feature manager# | mainlabel=- | sort=Feature priority, Feature stage | format=template | limit=500 | template=FeatureListTable }}
Pr Feature Stage Release target Product manager Feature manager

Roadmap

Links to implementation plan and progress: