Built with Privacy and Security at its core

ChromeOS offers a robust, multi-layered approach to security that helps protect your organisation's data from various threats. Its combination of built-in defenses, cloud-centric architecture, and enterprise management tools, makes it a secure choice for businesses of all sizes.

ChromeOS combines built-in security features, a cloud-centric approach and robust management tools, to provide comprehensive protection for your organisation's devices and data.

ChromeOS deters users from falling hostage to harmful attacks and works with diverse application ecosystems to ensure apps are trusted while providing IT with essential controls.

• Read-only: The core operating system files are read-only, making it very difficult for malware to modify the system.

• Restriction on executable files: ChromeOS doesn't allow traditional executable files (.exe, etc.) to run, limiting the attack surface.

• Application verification: Apps from the Google Play Store and web apps are vetted and regularly scanned for security issues.

• Safe browsing: Built-in protection from malicious websites and downloads.

• Continuous and automatic updates: Frequent updates happen automatically in the background for continuous protection against the most recent threats.

• No need for anti-virus software: Active threat protection fights external attacks and employee negligence. The read-only OS, verified boot, and blocked executables eliminate the need for third-party antivirus software.

Yes, ChromeOS can be used as part of your overall GDPR compliance effort. At Chrome, we champion initiatives that prioritise and improve the security and privacy of personal data, and want you, as a ChromeOS user, to feel confident using our services in light of GDPR requirements. For most customers using ChromeOS, Google will act as a controller over personal data, as detailed in the Google Privacy Policy. However, if ChromeOS data processor mode is available in your area and you choose to use it, Google will act primarily as a data processor over personal data processed by the core Chrome features known as Essential Services. When data processor mode is activated in the Admin console, the purposes for which Google may process this data are limited further.

Learn more in the Overview of ChromeOS data processor mode.

As described in our Data Privacy Framework certification, Google complies with the EU-U.S. and Swiss-U.S. Data Privacy Frameworks (DPF) and the UK Extension to the EU-U.S. DPF as set forth by the US Department of Commerce regarding the collection, use and retention of personal information from the EEA, Switzerland and the UK, respectively.

Learn more about our legal frameworks for data transfers.

ChromeOS provides IT administrators with granular control over data collection and usage, through the Google Admin console. Additional controls are also available to customers using data processor mode.

Opting-in to data processor mode enables customers to shift Google’s operation as a data controller over personal data, to primarily a data processor role. Google will act primarily as a data processor when providing Essential Services, while retaining its data controller role over Service Data only in specific, pre-defined circumstances referred to as “legitimate business purposes” which are listed in the data processor mode terms. Google remains a data controller for Optional Services, which can be switched-off by IT administrators.

Learn more about data processor mode.

Services that are subject to the data processor terms when data processor mode is enabled. These are considered core ChromeOS services, so please note that not all Essential Services can be turned off.

Services that may process personal data, but are not governed by the data processor terms. These services are subject to Google’s Privacy Policy and any other feature-specific terms. All Optional Services can be turned off by IT administrators.

No, use of data processor mode is not required to comply with GDPR. It does however provide additional processing restrictions and controls for administrators.

Whether data processor mode makes sense for an organisation depends upon its resource model and privacy story. Work with your appropriate counterparts (e.g. legal, compliance, and privacy teams) to determine if data processor mode is right for your organisation.

Data processor mode covers Essential Services being used on a managed ChromeOS device. It does not cover Optional Services, apps, extensions, third-party services, or any Google products / services other than ChromeOS and browser. There may be integrations of third-party services or other Google products, but those are not in-scope for data processor mode.

The personal data processed by Essential Services when data processor mode is activated can be broadly split into two categories:

• Customer Personal Data - personal data provided to Google by (or on behalf of) customers and/or their managed end users, or which is received through these services by customer and/or their end users. Some examples of Customer Personal Data are: name, email address, and personal data contained in files and docs.

• Service Data - personal data that Google collects or generates when customers and end users are interacting with ChromeOS and browser. Some examples of Service Data are: noting which policies are preferred by administrators, how many customers use a particular setting, and how Chrome is interacting with other Google services.

For in-depth descriptions of what and why each Essential Service processes data, please review the Help Center content for each service, as the data processed by each may be different.

For in-depth descriptions of what and why each Optional Services processes data, please review the Help Center content for each service, as the data processed by each may be different.

Some Essential Services cannot be turned off because they are core to Chrome's ability to function, or for accessibility, usability, and/or user experience purposes.

You can make an administrator a super administrator who can perform all tasks in the Admin console. Or you can assign a role that limits which tasks the administrator can perform, for example, by allowing them only to create groups, manage service settings, or reset a user's password.

Data included is listed here.