chromium/src
0
Fork 0
Code Activity

[Telemetry] Add API Use Terms to doc

Browse Source 
This change adds Use terms to the public documentation of the
telemetry extension.

Bug: b/259641744
Change-Id: Ie1373337b2890a546d24e3acfd0f113fb16a24a7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4036963
Reviewed-by: Oleh Lamzin <lamzin@google.com>
Commit-Queue: Bastian Kersting <bkersting@google.com>
Cr-Commit-Position: refs/heads/main@{#1077532}
This commit is contained in:
Bastian Kersting
2022-11-30 17:29:00 +00:00
committed by Chromium LUCI CQ
parent 9ce54f19d5
commit db7db9f34d
2 changed files with 51 additions and 0 deletions
docs/telemetry_extension
OWNERSREADME.md

2
docs/telemetry_extension/OWNERS Normal file

@ -0,0 +1,2 @@
bkersting@google.com
lamzin@google.com

49
docs/telemetry_extension/README.md

@ -106,6 +106,30 @@ chrome.runtime.onMessageExternal.addListener(
});
```
[//]: <> (This section is part of the API terms of use, internal version is)
[//]: <> (here go/telemetry-extension-tos. DO NOT EDIT unless changes in source)
## Permission to API Functionality Mapping
For an overview of all exposed function under `chrome.os.telemetry` and
`chrome.os.diagnostics`, please visit
[this page](https://github.com/GoogleChromeLabs/telemetry-support-extension-for-chromeos/blob/main/src/README.md#functions).
Some telemetry data requires special permissions to be accessed:
1. `VpdInfo.serialNumber` requires additional permission:
"os.telemetry.serial_number" with string
"Read Chrome OS device and component serial numbers"
2. `OemData.oemData` requires additional permission:
"os.telemetry.serial_number" with string
"Read Chrome OS device and component serial numbers"
3. `Batteryinfo.serialNumber` requires additional permission:
"os.telemetry.serial_number" with string
"Read Chrome OS device and component serial numbers"
4. MAC Address in `InternetConnectivity` requires additional permission:
“os.telemetry.network_info” with string “Read ChromeOS network information”
# The Chrome extension
In order for a Chrome extension to have access to telemetry and diagnostics
@ -242,6 +266,31 @@ able to set the root CA. Just select the `Authorities` tab and click `Import`.
Select the generated `CA.pem` file and click open. Now your Chrome instance
and testing environment trust each other.
[//]: <> (This section is part of the API terms of use, internal version is)
[//]: <> (here go/telemetry-extension-tos. DO NOT EDIT unless changes in source)
# Restrictions on Data Use
Due to the powerful nature of this API there are limits on how the data can be
utilized:
1. This API can only be used to receive telemetry data and diagnostic
information from ChromeOS-based devices to provide Customer Support Services.
2. This API will only be used, access or otherwise process personal data or
device identifiers at the Customer’s express direction in each instance.
3. Company will not access the ChromeOS API on an ongoing basis, or at recurring
intervals, without express direction by the Customer.
4. Company will not store (on device or server), or use for geolocation
purposes, the device SSID or BSSID.
5. Company will not use data obtained through the API for marketing purposes.
6. Company will provide and adhere to a privacy policy that clearly and
accurately describes to Customers what data is collected and how the data is
used and shared.
# Further reads
For information around configuration of certain cros-config values please visit: