|Projected Feature Freeze Date:||(tbd)|
|Product Champions:||Doug Turner (dougt)|
|Privacy Champions:||(the privacy Friend you're working with)|
|Security Contact:||Curtis Koenig (curtisk)|
|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:
To expose light and proximity to web content and applications in order to allow applications to detect light changes and do something interesting with them.
Major components of this system that are not control by Mozilla, of course, consists of the hardware units.
|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|