|
|
| Line 1: |
Line 1: |
| == Scheduling a Consultation == | | == Criteria == |
|
| |
|
| The Data Safety Team holds consolations on a pre-set data each month. Teams are asked to provide background information ahead of the meeting and then given 30 minutes to present their proposals. Input is provided during the meeting and contributors on the Data Safety Team commit to work with presenting teams to resolve open questions about user data, privacy and security following the team's presentation.
| | To ensure appropriate oversight and governance of how Mozilla collects, uses and/or retains user data in the product development lifecycle and product functionality, three key conditions apply: |
|
| |
|
| To get your team on the agenda for an upcoming Data Safety Consultation, please contact Alina Hua.
| | No Data Safety Review is needed if your product / project has an architecture employing user-controlled key encryption without Mozilla access or where data stored on the user’s client or device is under the user’s control. If you need / want to use hosted data that can be accessed by Mozilla staff, contributors or developers, then a Data Safety review is required. |
|
| |
|
| == Template ==
| | Anything we do with user data will require Security, Privacy and Legal reviews at a minimum, just as it does today. You can find more information about these reviews here: |
|
| |
|
| Please use the following template in preparing for a presentation to the Data Safety Team. [Data_Safety_Consultation_Template]
| | * Privacy Reviews |
| | * Security Reviews |
|
| |
|
| = Consultation Archive =
| | Data Safety approval related to the following areas is dependent on the circumstances for each project. Approvals may require additional consideration and/or may be granted as an exception to the usual conditions in the following two areas. |
|
| |
|
| [In process of moving over…]
| | Test |
| | | Test |
| = Contributors =
| |
| | |
| The following people have joined together to form a Mozilla Data Safety Team to develop these ideas and bring them into our product offerings:
| |
| | |
| * Jay Sullivan, who leads the definition of great Mozilla products that embody our values,
| |
| * Sid Stamm, who leads engineering for privacy in Firefox and the web platform,
| |
| * Jonathan Nightingale, who runs the Firefox engineering group,
| |
| * Alex Fowler, who leads privacy and policy and focuses on enhancing information management,
| |
| * Brendan Eich, who has led from day one the technical direction of the Mozilla Project,
| |
| * Michael Coates, who leads infrastructure security, overseeing applications, servers, & networks,
| |
| * Chris Beard, who leads our marketing and engagement programs,
| |
| * David Ascher, who leads Mozilla’s thinking on how users share and discover the Web,
| |
| * Ben Adida, who leads the Identity work at Mozilla.
| |
| | |
| We plan to grow this team to include individuals with more diverse backgrounds, people from inside and outside the Mozilla Project, and people from around the world.
| |