Mervinskiy 516

Page 142

DPIA Google G Suite Enterprise for SLM Rijk | 9 July 2020, with update 12 February 2021

First, Google collects content from Customer Data such as files, emails or chats when a data subject uses a Feature, such as Spelling and Grammar. Second, Google collects content from data that Google obtains as Customer Data such as file and path names of documents in its Diagnostic Data, and snippets of content in telemetry data from the Enhanced Spellchecker. There are multiple risks related to the possible further processing of these Customer Data and content from Customer Data collected through Diagnostic Data by Google. Google permits itself to process personal data in Customer Data for 8 and perhaps 20 purposes. As explained in Section 5.2, Google does not qualify as a data processor for the processing of Customer Data due to the lack of transparency about the purposes, lack of purpose limitation and the fact that Google determines compatible purposes of use. Additionally, Customer Data may be included in Diagnostic Data. Diagnostic Data may contain Confidential Information or organisation data of a potentially sensitive nature, such as files names and subject lines of email, sentences and words if the Spelling and grammar is used, and sensitive or special categories of personal data of all kinds of data subjects. Such Diagnostic Data do not fall within the scope of the G Suite DPA. This means, inter alia, that third parties engaged by Google that receive these data are not authorised as subprocessors, and are not bound by G Suite DPA (and potentially also not by the GDPR). Furthermore, where government organisations and Google are joint controllers for Diagnostic Data that includes (content) data obtained by Google as Customer Data, government organisations generally do not have a legal ground for such processing, because it will mostly not be necessary to process such data. There is a risk that Google may be ordered by a foreign government to hand over Customer Data or Diagnostic Data from Dutch government customers. Google may be prohibited from forwarding such a request to the government organisation and may also be prohibited from even informing the organisations thereof by a gagging order. Customer Data and Diagnostic Data may also be accessed unlawfully by a rogue administrator or hostile state actor. Such access would be in breach of confidentiality requirements and the fundamental right to protection of communication secrecy.

16.2

Assessment of Risks The risks can be grouped in the following categories: 1. Loss of control over the processing of personal data; 2. Loss of confidentiality; 3. Inability to exercise fundamental rights (GDPR data subject rights as well as related rights, such as the fundamental right to send and receive information); 4. Reidentification of pseudonymised data; and 5. Unlawful (further) processing. These risks have to be assessed against the likelihood of their occurrence and the severity of their impact. The UK data protection commission ICO provides the following guidance regarding the assessment of risks: “Harm does not have to be inevitable to qualify as a risk or a high risk. It must be more than remote, but any significant possibility of very serious harm may still be

p. 134/162


Turn static files into dynamic content formats.

Create a flipbook

Articles inside

Conclusions

2min
page 170

17.4 Google measures 12 February 2021

19min
pages 161-169

16.3 Summary of risks

2min
pages 155-156

16.2 Assessment of Risks

36min
pages 142-154

15.7 Right to file a complaint

0
page 139

15.3 Right to access

5min
pages 136-137

14.3 Assessment of the subsidiarity

2min
page 134

14.1 The principle of proportionality

2min
page 130

14.2 Assessment of the proportionality

8min
pages 131-133

12.1 Transfer of special, sensitive, secret and confidential data to the USA

5min
pages 128-129

11.3 Google’s own legitimate business purposes

5min
pages 126-127

all Diagnostic Data

5min
pages 124-125

Services

22min
pages 116-123

Part B. Lawfulness of the data processing

2min
page 115

8.1 Anonymisation

15min
pages 106-111

6.3 Joint interests

11min
pages 101-105

6.2 Interests of Google

2min
page 100

6.1 Interests of the Dutch government organisations

2min
page 99

5.2 Data processor

5min
pages 88-89

5.3 Data controller

18min
pages 90-96

5.4 Joint controllers

5min
pages 97-98

4.4 Specific purposes Chrome OS and the Chrome browser

2min
page 86

5.1 Definitions

2min
page 87

4.3 Purposes Additional Services and Google Account, when not used in a Core Service

8min
pages 83-85

4.2 Purposes Google

13min
pages 77-82

4.1 Purposes government organisations

2min
page 76

2.5 Types of personal data and data subjects

7min
pages 60-62

3.2 Privacy controls administrators

7min
pages 70-75

3.1 Privacy controls G Suite account for end users

9min
pages 63-69

2.3 Outgoing traffic analysis

8min
pages 52-55

2.4 Results access requests

10min
pages 56-59

2.2 Diagnostic Data

7min
pages 47-51

Related services that may send Customer Data to Google, such as the Feedback form and the Enhanced Spellchecker in the Chrome browser.

4min
pages 13-15

2.1 Definitions of different types of personal data

7min
pages 44-46

Part A. Description of the data processing

0
page 25

The enrolment framework for G Suite Enterprise

2min
pages 42-43

G Suite Core Services, Google Account, Support Services, Additional Services, and Other related services

23min
pages 28-41

Functional Data

2min
page 27

Introduction

7min
pages 16-18

1 Legal framework and contractual arrangements between government organisations and

4min
pages 23-24
Issuu converts static files into: digital portfolios, online yearbooks, online catalogs, digital photo albums and more. Sign up and create your flipbook.