Confirmed users
313
edits
Loop/Architecture/Context: Difference between revisions
Jump to navigation
Jump to search
m
→Information Privacy: removed a gender specific term
m (→Information Privacy: removed a gender specific term) |
|||
| Line 4: | Line 4: | ||
== Information Privacy == | == Information Privacy == | ||
The context information is user-supplied, so we need to carefully consider privacy handling. The design below serves this purpose by storing the information on the Loop server in an encrypted form. Each room will have its own symmetric key, which will be available to the room owner and anyone to whom | The context information is user-supplied, so we need to carefully consider privacy handling. The design below serves this purpose by storing the information on the Loop server in an encrypted form. Each room will have its own symmetric key, which will be available to the room owner and anyone to whom they provide the room URL. These room keys will never be available to any server. | ||
This section explains the means by which this achieved at the level of information flow. Details are provided in the sections below. See also {{Bug|1132293}}, which describes the API being implemented by the FxA client to facilitate the behavior described below. | This section explains the means by which this achieved at the level of information flow. Details are provided in the sections below. See also {{Bug|1132293}}, which describes the API being implemented by the FxA client to facilitate the behavior described below. | ||