Answers to the questionnaire for Generic Sensor API extension specifications can be found in corresponding repositories:
Yes, but not directly. Concrete sensor specifications require user permissions and an assesment of applicable mitigation strategies to address potential risks. For more information, please see: Security and Privacy section.
Yes, but not directly.
Sensor readings are explicitly flagged by the Secure Contexts specification [POWERFUL-FEATURES] as a high-value target for network attackers. Thus all interfaces defined by this specification or extension specifications are only available within a secure context.
Indirectly, sensor readings of a concrete sensor can be used to infer user input.
3.3 Does this specification introduce new state for an origin that persists across browsing sessions?
No.
No.
3.5 Does this specification expose any other data to an origin that it doesn’t currently have access to?
No.
No.
Not directly; concrete sensor specifications, ie. "Geolocation Sensor" require user permissions and implementation of applicable mitigation strategies to avoid potential risks.
Yes; concrete sensor specifications require user permissions to mitigate potential exposure and/or privacy issues.
See: Security & Privacy and Mitigation strategies sections.
3.9 Does this specification allow an origin access to aspects of a user’s local computing environment?
Yes. If user agent has permission to access concrete sensor, the API provides means to check whether the sensor is available within user’s local computing environment.
No; however it is acknowledged that:
Sensors can potentially be used in cross-device linking and tracking of a user.
See: Security & Privacy and Mitigation strategies sections.
No.
No.
No.
Specification does not restrict access to a particular mode. However, this can be revisited when privacy mode would be formally specified.
No.
Yes.
See: Security & Privacy section.
No.