Skip to content

Latest commit

 

History

History
64 lines (32 loc) · 2.75 KB

security-privacy-questionnaire.md

File metadata and controls

64 lines (32 loc) · 2.75 KB
  1. What information might this feature expose to Web sites or other parties, and for what purposes is that exposure necessary?

This does not expose any information to web sites. The data flow is the other way around where sites expose data to the user agent.

  1. Is this specification exposing the minimum amount of information necessary to power the feature?

Yes, this is the bare minimum.

  1. How does this specification deal with personal information or personally-identifiable information or information derived thereof?

The recommendations that are provided by the site could be considered personal information but are only used by the user agent.

  1. How does this specification deal with sensitive information?

N/A

  1. Does this specification introduce new state for an origin that persists across browsing sessions?

The fetched media feed content is persisted across browsing sessions but will be cleared if a user clears their history.

  1. What information from the underlying platform, e.g. configuration data, is exposed by this specification to an origin?

None.

  1. Does this specification allow an origin access to sensors on a user’s device?

No.

  1. What data does this specification expose to an origin? Please also document what data is identical to data exposed by other features, in the same or different contexts.

None. The origin exposes data to the user agent but not the other way around.

  1. Does this specification enable new script execution/loading mechanisms?

No

  1. Does this specification allow an origin to access other devices?

No

  1. Does this specification allow an origin some measure of control over a user agent’s native UI?

Yes, the feature allows a site to show content from these feeds in the user agent's UI. However, a user will have the option of switching them on/off at an individual feed level. The user agent will collect a feature level consent that tells the user that periodic background fetch is occuring. For feeds discovered after the feature level consent is collected, we will show a popup notification when the user opens the feature which will let them know that this is occuring and provide a mechanism to disable it.

  1. What temporary identifiers might this this specification create or expose to the web?

None.

  1. How does this specification distinguish between behavior in first-party and third-party contexts?

This feature does not distinguish between these contexts.

  1. How does this specification work in the context of a user agent’s Private Browsing or "incognito" mode?

We will not discover or fetch Media Feeds in these modes.

  1. Does this specification have a "Security Considerations" and "Privacy Considerations" section?

Yes.

  1. Does this specification allow downgrading default security characteristics?

No.