In order to provide the best possible experience, Chrome OS Flex collects hardware data about devices and shares it with Google in order to determine which updates should be delivered. In several additional cases, if you allow it to, it also shares that data with Google for additional purposes like support and improvements to the Chrome OS Flex experience and service.
Unique device identification
Whenever possible, we take measures to protect your privacy, including anonymizing data about your device across our different data sets. Due to the flexible nature of Chrome OS Flex’s hardware support, it is possible for a device’s hardware components to uniquely identify that device, despite these precautions.
While this possibility for unique device identification is uncommon, and our policy is to actively avoid and prevent this type of unique identification, we want you to be aware of the possibility, as it is inherent to Chrome OS Flex compared to Chrome OS.
How to view your hardware data
On a device running Chrome OS Flex, you can log in and visit the
CHROMEOSFLEX_HARDWARE_INFO section in chrome://system to see, locally on your device, the exact hardware data that might be shared with Google when using Chrome OS Flex.
Examples of the device data you’ll see here include the name of your model, CPU, GPU, whether a hardware security chip is present and supported, or how much RAM your device has.
How we use this data
Your hardware data is used for support and overall improvements to Chrome OS Flex and other Google products and services. For example, we might analyze the impact of a bug based on how many devices share a component, prioritize improving support for devices which are used most commonly, or reference individual hardware data to better understand a problem reported via feedback or in a support interaction.
Specific instances where data is, or might be, shared to Google from Chrome OS Flex are:
Using hardware data for update filtering
During Chrome OS Flex updates, your hardware data is analyzed to inform which updates you receive and avoid critical known issues that could impact your device. This data is essential to providing a reliable experience, and therefore you cannot opt out of this particular case of data sharing, even if you opt out of other sharing.
During updates, Chrome OS Flex devices include hardware data when sending requests to update servers. If any known issues with updates impact your device, the result of the update interaction will be adjusted as needed. The data transmitted during update requests is not retained or used by Google for other purposes.
Sharing hardware data for analysis and improvement (coming soon)
In order to understand, in aggregate, the types of devices and hardware that Chrome OS Flex is used on, you can optionally choose to share hardware data to a Chrome OS Flex Hardware Database (this database is still under construction). When you share this info with us, you help us understand and improve what devices are running Chrome OS Flex, and inform the work we do to support and improve it.
If you choose to share this data, then your hardware data (visible in chrome://system, as described above) is sent to the Chrome OS Flex hardware database and regularly updated. Your device’s unique identity in this data set is not related to other unique identifiers for your device or your user accounts.
You can control whether you want to help improve Chrome OS Flex by sharing device data by adjusting the toggle displayed during device setup, or later in the settings menu under Privacy and Security.
Sharing hardware data in feedback reports
As on other versions of Chrome OS, you can choose to send feedback to Google from your Chrome OS Flex device. If you check the box to optionally include system information in your feedback report, the information sent will include hardware information (visible in chrome://system, as described above). Along with other data and logs, this hardware data helps us understand your feedback in the context of your device, and potentially identify relationships between specific components and issue reports.