- 1 Document Overview
- 2 Architecture
- 3 User Data Risk Minimization
- 4 Alignment with Privacy Operating Principles
- 5 Follow-up Tasks and tracking
|Projected Feature Freeze Date:||(tbd)|
|Product Champions:||Erin Lancaster|
|Privacy Champions:||Curtis Koenig|
|Security Contact:||David Chan|
|Architectural Overview:||(date TBD)|
|Recommendation Meeting:||(date TBD)|
|Review Complete ETA:||tbd|
In this section, the product's architecture is described. Any individual components or actors are identified, their "knowledge" or what data they store is identified, and data flow between components and external entities is described.
The main objective of this feature/product is: (describe the goals of the feature/product here)
Design Documents: Link to any design or architectural documents here.
Describe any major components in the system and how they interact. Also include any third-party APIs (those Mozilla does not control) and what type of data is sent or received via those APIs.
This component does A, B and C and interacts with component Y to do D.
The tables below simply summarize the data encountered by this component.
|data type||where stored|
Communication with Component Y
|In:||message 1||types of data received from component Y with the message|
|Out:||message 2||types of data sent to component Y with the message|
User Data Risk Minimization
In this section, the privacy champion will identify areas of user data risk and recommendations for minimizing the risk.
Alignment with Privacy Operating Principles
In this section, the privacy champion will identify how the feature lines up with Mozilla's privacy operating principles.
Principle: Transparency / No Surprises
(How the feature addresses this)
Recommendations: (what can be improved)
Principle: Real Choice
Principle: Sensible Defaults
Principle: Limited Data
Follow-up Tasks and tracking
|[NEW] Initial Overview Discussion||?||Meeting time TBD|