Log In Sign Up

We Value Your Privacy ... Now Take Some Cookies: Measuring the GDPR's Impact on Web Privacy

The European Union's General Data Protection Regulation (GDPR) went into effect on May 25, 2018. Its privacy regulations apply to any service and company collecting or processing personal data in Europe. Many companies had to adjust their data handling processes, consent forms, and privacy policies to comply with the GDPR's transparency requirements. We monitored this rare event by analyzing the GDPR's impact on popular websites in all 28 member states of the European Union. For each country, we periodically examined its 500 most popular websites - 6,579 in total - for the presence of and updates to their privacy policy. While many websites already had privacy policies, we find that in some countries up to 15.7 25, 2018, resulting in 84.5 websites with existing privacy policies updated them close to the date. Most visibly, 62.1 more than in January 2018. These notices inform users about a site's cookie use and user tracking practices. We categorized all observed cookie consent notices and evaluated 16 common implementations with respect to their technical realization of cookie consent. Our analysis shows that core web security mechanisms such as the same-origin policy pose problems for the implementation of consent according to GDPR rules, and opting out of third-party cookies requires the third party to cooperate. Overall, we conclude that the GDPR is making the web more transparent, but there is still a lack of both functional and usable mechanisms for users to consent to or deny processing of their personal data on the Internet.


page 4

page 5

page 9

page 11


State of Security and Privacy Practices of Top Websites in the East African Community (EAC)

Growth in technology has resulted in the large-scale collection and proc...

The Impact of User Location on Cookie Notices (Inside and Outside of the European Union)

The web is global, but privacy laws differ by country. Which set of priv...

Accept All: The Landscape of Cookie Banners in Greece and the UK

Cookie banners are devices implemented by websites to allow users to man...

Whose Hands Are in the Finnish Cookie Jar?

Web cookies are ubiquitously used to track and profile the behavior of u...

Associating eHealth Policies and National Data Privacy Regulations

As electronic data becomes the lifeline of modern society, privacy conce...

Dark Patterns after the GDPR: Scraping Consent Pop-ups and Demonstrating their Influence

New consent management platforms (CMPs) have been introduced to the web ...

Does Facebook Use Sensitive Data for Advertising Purposes? Worldwide Analysis and GDPR Impact

The recent European General Data Protection Regulation (GDPR) and other ...

I Introduction

On May 25, 2018, the General Data Protection Regulation (GDPR) went into effect in the European Union. The GDPR is supposed to set high and consistent standards for the processing of personal data within the European Union and whenever personal data of people residing in Europe is involved. As a result, the GDPR affects millions of web services from around the world which are available in Europe. In addition to potentially changing how they process personal data, companies have to disclose transparently how they handle personal data, the legal bases for their data processing, and need to offer their users mechanisms for individual consent, data access, data deletion, and data portability. Even outside Europe, online services had to prepare for the GDPR because it not only applies to companies in Europe but any company that offers its service in Europe. As a result, the GDPR is expected to have a major impact on companies across the world.

Previous work has found that about 70 to 80 % of websites in the U.S. have privacy policies [26, 28]. But analysis of privacy policies has been focused on English-language policies, performing in-depth studies on their content [42, 18, 25, 39]. Cookie consent notices have just recently seen research attention with respect to their usability [29], but their use and implementations have not been studied in detail, yet.

In this paper, we describe an empirical study to measure changes that occurred on a representative set of websites at the time the GDPR came into force. We monitored this rare event by analyzing the 500 most visited websites, according to Alexa country rankings, in each of the 28 member states of the EU over the course of eleven months. In total, this resulted in a set of 6,759 websites available in 24 different languages. We used a combination of automated and manual methods and compared the privacy policies of these websites before and after the GDPR enforcement date and, together with historic data, retrieved 112,041 privacy policies.

Our results show that changes made around the GDPR enforcement date had overall positive effect on the transparency of websites: more websites (+4.9 %) now have privacy policies and/or inform users about their cookie practices and increasingly inform users about their rights and the legal basis of their data processing. But even though on average 84.5 % of the websites we checked for each country now have privacy policies, differences remain high. By tracing the changes on policies, we found that, despite the GDPR’s two-year grace period, 50 % of websites updated their privacy policies in May 2018 just before the GDPR went into effect, and more than 60 % did not make any change in 2016 or 2017. We further found that actual practices did not change much: The amount of tracking stayed the same and the majority of sites relies on opt-out consent mechanisms. We identified only 37 sites that asked for explicit consent before setting cookies.

For web users in Europe, the most visible change is an increase in cookie consent notices and the features they offer, e. g., specific user choices for tracking and social media cookies. On average, 62.1 % of the analyzed websites now use such cookie banners (46.1 % in January 2018). In order to better understand this phenomenon, we manually inspected 9,044 domains for their use of cookie banners and evaluated 28 common cookie consent libraries for features useful for the implementation of GDPR-compliant consent. We found that existing implementations greatly vary in functionality, especially the granularity of control offered to the user and the ability to apply the desired cookie configuration.

In summary, our paper makes the following contributions:

  1. We conduct an empirical, longitudinal study of privacy policies and cookie consent notices of 6,759 websites representing the 500 most popular websites in each of the 28 member states of the EU. From January to

    October 2018, we performed monthly scans to measure changes in adoption rates. Between January and the end of May, we observed an average rise of websites providing privacy policies by 4,9 percentage points and cookie consent notices by 16. After May the development slowed down: Between June and November, the number of websites that added privacy policies and cookie consent notices increased by 0.9 and 1.1 percentage points, respectively.

  2. While prior studies primarily focused on English-language privacy policies, we analyze privacy policies in 24 different languages. We use natural language processing techniques to identify how privacy policies’ content has changed and whether the GDPR’s new transparency requirements are reflected in the texts. We find that not too many websites make use of GDPR terminology, but for those that do, the amount of information about users’ rights and the legal basis of processing increased.

  3. We compare the use of cookies and third-party libraries in our set of websites between January and June 2018 to determine whether the GDPR’s transparency and consent requirements affected the prevalence of web tracking. While both were not significantly impacted, 147 sites stopped using tracking libraries and 37 chose to ask for explicit consent before activating them.

  4. We categorize observed cookie consent notices based on their options for interaction. In our data set, we found many distinct implementations of cookie consent notices. We analyze these libraries for key features required to implement the GDPR notion of “informed consent” and identify technical obstacles to achieving this goal.

Ii Background

As background, we discuss the GDPR’s legal requirements and technical aspects of their implementation.

Ii-a Legal Background

In 2012, the EU started to take regulatory action to harmonize data protection laws across its member states. Existing data protection legislation comprised the Data Protection Directive (95/46/EC) [11] and the ePrivacy Directive (2002/58/EC) [1], along with national laws in the EU member countries implementing the requirements of the two directives.111In contrast to EU regulations, which are directly applicable in each member state, EU directives are only binding as to the result leaving the member states to decide upon the form and methods for achieving the aim.

As pointed out by Recital 9 of the GDPR, these national implementations differed widely, resulting in a complex landscape of privacy laws across Europe. Some member states embraced stricter privacy laws and enforcement while others opted for lighter regulation. The General Data Protection Regulation (GDPR) [12] is intended to overcome this situation and harmonize privacy laws throughout the EU. It was proposed in January 2012, adopted on May 24, 2016, and its provisions became enforceable on May 25, 2018. A second regulation, the ePrivacy Regulation, is meant to complement the GDPR and complete the harmonization process. It is currently passing through the EU’s legislative process.

The GDPR has several implications for web services and is therefore expected to impact the technical design of websites, what data they collect, and how they inform users about their practices. GDPR thus governs any processing of personal data for services offered in the EU, even if the service provider does not have any legal representation there. Article 3 states that the regulation applies to “the processing of personal data in the context of the activities of an establishment of a controller or a processor in the [European] Union, regardless of whether the processing takes place in the [European] Union or not.” For online services this means that any website offering its service in the EU has to comply with GDPR standards.

Following are selected key requirements of the GDPR relevant for our study. A more detailed discussion of the regulation can be found in legal literature [32].

Transparency. Article 12 GDPR requires that anyone who processes personal data should inform the data subject about the fact (e. g., in a privacy policy) and present the information in “a concise, transparent, intelligible, and easily accessible form, using clear and plain language”. Since IP addresses are considered personal data in the EU, this means that every website and the underlying web server that processes these addresses is required to provide this information. Article 13 more specifically lists what information needs to be provided. This includes contact data, the purposes and legal basis for the processing, and the data subject’s rights regarding their personal data, e. g., the right to access, rectification, or deletion. These requirements make it necessary for every website to have a privacy policy and modify existing privacy policies to comply with the new transparency requirements.

Data protection by design and by default. Article 25 states that entities processing personal data should “implement appropriate technical and organisational measures […] designed to implement data-protection principles […] in an effective manner”, “taking into account […] the state of the art”. They are required to “ensure that by default personal data are not made accessible without the individual’s intervention to an indefinite number of natural persons”.

Higher protection standards are required for sensitive categories of personal information like health data (Article 9).

Consent. According to Article 6, the processing of personal data is only lawful if one of six scenarios applies.

They include the case when the processing is necessary “for the purposes of the legitimate interests [of] the controller or […] a third party” (Article 6(1)(f)) or to comply with a legal obligation (Article 6(1)(c)).

Most importantly, the processing of personal data is lawful if “the data subject has given consent” (Article 6(1)(a)). Consent, in turn, is defined in Article 2(11) as “any freely given, specific, informed and unambiguous indication of the data subject’s wishes […]”.

Here, “freely given” means the data subject has to be offered real choice and control; if they feel compelled to agree to the processing of their personal data, this does not constitute valid consent [5]. For children under the age of 16 consent can only be given by the holder of parental responsibility (Article 8).

Consent to the use of cookies. In an earlier harmonization effort, Directive 2009/136/EC had

changed Article 5(3) of the ePrivacy Directive (2002/58/EC) to state that “the storing of information […] in the terminal equipment of a […] user” is only allowed if the user “has given his or her consent, having been provided with […] information […] about the purposes of the processing” [2]. This consent requirement does not apply if storing or accessing the information is “strictly necessary” for the delivery of the service requested by the user. For websites, this is understood to exempt cookies from consent if the site would not work without setting the cookie. Examples include cookies remembering the state of the shopping cart in an online shop or the fact that the user has logged in.

This piece of legislation has caused websites across the EU to display cookie consent notices, often referred to as cookie banners – boxes or banners informing users about the use of cookies by the website and associated third parties. These notices may explicitly ask users for their consent or interpret a user’s continued website use as implied consent.

However, according to EU guidelines, valid consent needs to be a freely given, active choice based on specific information about the purpose of the processing and given before the processing starts [3]. It has to be noted that Article 5(3) applies to any kind of information stored on the user’s system even if it does not contain any personal information. In case it does, consent according to GDPR rules is also required, though the two types may be merged in practice [32].

Ii-B Technical Background

Figure 1: Overview of the website analysis process combining automated analysis, manual validation, and annotation.

Different technical solutions have been proposed to help users cope with the ever-growing number of online tracking and profiling services. In 2002, the Platform for Privacy Preferences (P3P) Project [8] was officially recommended by the W3C. It relied on machine-readable privacy policies directly interpreted by the browser,

which was enabled to automatically negotiate, e. g., the handling of certain cookies based on the user’s preferences. However, none of the major web browsers support P3P anymore due to a lack of adoption by websites [7]. Another approach is the Do Not Track (DNT) Header for the HTTP protocol, proposed in 2009 [37]. DNT is supported by all major browsers and allows the user to signal online content providers their preference towards tracking and behavioral advertising. However, many websites do not honor DNT signals [9].

Companies in the online behavioral advertising (OBA) business point to their self-regulation program AdChoices. The user is informed by a little blue icon in the advert and given additional information on click. The WebChoice tool allows users to opt-out of OBA for each participating company. For users this remains challenging as studies have shown that users can hardly distinguish between different OBA companies [23] and have problems to even recognize and locate the corresponding icons [16].

Apart from these solutions based on browser settings, natural language privacy policies remain the main means to inform the user about websites’ data processing practices. Studies have shown that users rarely read privacy policies because of their length and complex vocabulary [27, 30].

Advances in natural language processing [18, 39] have led to the development of automated solutions to read and understand key contents of privacy policies and display them to users in an accessible fashion. However, existing solutions rely on the presence of an English-language privacy policy.

Iii Studying Privacy Policies

To analyze the impact of GDPR enforcement on websites in the EU, we used automated tools combined with manual verification and annotation of websites in 24 different languages. We built a system to automatically scan websites for links to privacy policies, manually reviewed sites where a policy could not be extracted automatically and annotated the whole set of websites for their topic and the use of cookie consent notices. Figure 1 provides an overview of the main components of our privacy policy detection and analysis system. We describe the data collection and policy analysis method in this section, followed by the policy analysis results in Section IV. Sections V and VI describe the cookie consent notice analysis and its findings.

We started by reviewing the 500 most popular websites in each of the 28 EU member states as listed by the ranking service Alexa.222 To extend the scope of our study, we retrieved updated top lists once per month. After a pretest in December 2017, the websites were scanned once per month from January to April 2018, three times in May (two times before and one time after May 25, 2018) and again once per month until October 2018, resulting in 12 scans in total.

Iii-a Automated Search for Privacy Policies

Our automated web browser was set up in a German data center with the Selenium web driver using the latest version of Firefox (version 57 onward) on servers running Ubuntu Linux and an Xserver so that all pages were actually rendered. The results were stored in a MongoDB database. The following steps were performed for each website on its homepage after it had been completely rendered by the browser.

Find privacy policy: We identified phrases pointing to privacy policies, using dictionaries and verifying the results in a prestudy. The list, which is available in our Github repository333, contained phrases from all 24 official languages, plus 4 other languages spoken in the EU.

In our automated search, we only used phrases specific to privacy policies to avoid false positive results. Using an XPath query, we searched for hyperlinks that contained these phrases and saved the corresponding pages in a text file.

Analyze website: We searched for domain names of third-party advertising and tracking libraries in the fully rendered page based on EasyList444See, which is often used in popular ad-blocking browser extensions. A screenshot of the rendered homepage was made to allow for manual inspection for cookie consent notices.

Due to the complexity of websites and an often poor implementation of standards, as well as different ways of displaying long online texts such as privacy policies, we considered a fully automated approach not sufficient to conclusively determine whether a website has a privacy policy. The word list worked well on business and news websites, but it missed privacy policy links on other sites.

Problems occurred, for example, in countries where multiple languages are spoken (e. g., Belgium, which has multiple official languages, or Estonia with its large Russian-speaking minority) as websites often present a screen asking the user to choose a language before proceeding to the actual site with its privacy policy links. Other websites did not use common phrases or would

incorporate the privacy policy into their “terms of service”. Our system marked the websites on which automatic detection failed for manual review. We complemented the automated search with manual validation.

Iii-B Manual Review

In order to validate the results of the automated detection of privacy policies, we implemented a web-based annotation tool to review and further process the collected data. The automatic tool assigned each website one of the following status codes:

  • Done: A link to a privacy policy has been found and the corresponding document was downloaded (see Section IV for how we evaluated the content of these documents).

  • Review: The automated analysis found word(s) from the list suggesting that a privacy policy might exist, but the system failed to download any pages.

  • No Link Found: None of the words form the list of privacy policy identifiers was found.

All websites categorized as Review or No Link Found were manually inspected and annotated by the authors.

Manual inspection was done with off-the-shelf browsers and, if necessary, using Google Translate when inspecting pages in languages the annotator was unfamiliar with. Translations through Google were available in all encountered languages and good enough to figure out the general topic of a website and whether it had a privacy policy, together with

common design principles like using footers for notices and information. If a privacy policy or similar page was identified, the policy link was added to the database, and the policy was subsequently downloaded.

If the annotator was not able to identify a privacy policy on the website, even after trying to create an account on the website, it was annotated as No Policy. Websites that could not be reached were labeled Offline. Under this label we merged all sites that were not reachable, occupied by a domain grabbing service, produced a screen indicating that the website was not available because of the detected location of our IP address, or belonged to a discontinued or not publicly accessible service. To ensure the quality of the data sets, a full manual review was done in January, after May 25, and in October 2018. For the measurements in the months in between, we used the lists from previous months to download privacy policies. In the majority of cases, we found links to privacy policies in the footer of a website (an approach also used by Libert [25]) or through links in cookie consent notices. When there was no footer or no link to a privacy policy, annotators inspected the site in more detail. Several websites made it rather complicated for users to find these links as they, for example, had a privacy policy link in the site’s footer but used infinite scrolling to dynamically add more content when the user scrolled to the bottom of the page, moving the footer out of the visible area again. Sites without footers were inspected for links to other documents that may contain information about the handling of personal data like terms of service, user agreements, legal disclaimers, contact forms, registration forms, or imprints.

Iii-C Archival data

The GDPR was passed in April 2016, allowing for a two-year grace period before it went into effect. Given that we started collecting data in January 2018, we used the Internet Archive’s Wayback Machine to retrieve previous versions of the privacy policies in our dataset. This allowed us to analyze whether and when privacy policies had been changed before our data collection started. Using the Wayback Machine’s API, we requested versions for each policy URL for each month between March 2016 and December 2017. On average, we were able to access previous versions for 2,187 policies for each month. The extent of this dataset is limited due to the fact that not every website or page is archived by the Internet Archive and some of the pages we tried to access might not have existed previously.

Iii-D Data Cleaning

After retrieving a total of 112,041 privacy policies, we pre-processed these files with Boilerpipe, an HTML text extraction library, to remove unnecessary HTML code from the documents [21]. Boilerpipe removes HTML tags and identifies the main text of a website removing menus, footers, and other additional content. We validated the results with text that had been manually selected while inspecting sites for privacy policies. Except for policies that were very short (less than four sentences) and excluded because Boilerpipe was not able to identify their main text, it correctly extracted the policy texts. We scanned the remaining files for error messages in multiple languages and manually inspected sentences many texts had in common to exclude those if they indicated an error.

We observed some websites that linked to a privacy policy at a domain different from its own, either as the only privacy policy link or in addition to the website’s own policy. A valid and common reason for a privacy policy being linked from multiple hosts was websites referencing the policy of a parent company, e. g., RTL Group (linked on 11 domains), (9), Vox Media Group (4). We excluded these (duplicate) policies from further analysis. We also marked as offline websites linking to privacy policies of unrelated third parties (e. g., Google or domain grabbing services) as they evidently did not have a policy specific to their data collection practices.

72 sites used JavaScript to display their privacy policies, which was not properly detected by our script, resulting in file downloads that contained the websites’ home pages instead of their privacy policies. Unfortunately, we did not discover this issue until

the analysis, at which point we decided to exclude them. We also had to exclude 163 websites from our content analysis that provided their policies as a file download (e. g., as a PDF or DOC file) – although their availability was detected, our crawler was not designed to process these.

After the data cleaning process, our dataset for text mining consisted of 81,617 policies from 9,461 different URLs and 7,812 domains. We also removed lines from the files downloaded from the Internet Archive that contained additional information about the data source.

To compare different versions of policies and policies from different websites we used the Jaccard similarity index on a sentence level [19], which is commonly used to identify plagiarism [24]

. The Jaccard index measures similarity as the sum of the intersection divided by the sum of the union of the sentences. It ranges between 0 and 1, where 1 means two documents only have the same sentences.

We used the Polyglot555 library to split the texts into sentences and stored a policy as a list of MD5-hashed sentences to speed up the text comparison process. This resulted in a database of policies where each policy consisted of a number of hashed sentences and calculated the similarity between two policies and where and marked documents from two different crawls but from the same domain and URL as

We compared monthly versions of each crawl to analyze when and if privacy policies had changed. We also compared versions over larger intervals, e. g., between January 2017 and December 2017. To do the latter, we had to exclude several websites from the comparison, e. g., when there was no data available on the Internet Archive but also when the URL of their privacy policy had changed. Although we downloaded pages that appeared with new links, we only compared texts from the same URLs as we were not able to automatically determine which version to compare.

For example, multiple websites previously listed their privacy policy as part of the terms of service page and then moved it to a separate page. Again, we took a conservative approach and only compared different versions of the same files.

The Jaccard index would still detect a change compared to the first document we had on file, in that case, the terms of service.

Lastly, we applied lemmatization/stemming to the documents to perform an analysis on the word level and check whether privacy policies mentioned phrases specific to the GDPR. First, we created a word list with translations of important phrases from Articles 6 and 13 GDPR. The EU provides official translations of all documents in 24 different languages from which we extracted the corresponding phrases.

Leveraging our extended personal networks, we recruited native speakers for 17 of the 24 languages to check and validate the word lists.666We could not find native speakers for Danish, Latvian and Lithuanian but did our best to validate the words using dictionaries and translation tools.

We then searched for these words by first determining the language of a policy using two libraries, The Language Detection Library 777 and Polyglot.

We excluded 1.7 % of texts from our analysis because the libraries produced diverging results.

Because of the high diversity in the policies’ languages – 24 official languages of EU member states, plus 7 other languages occurring in our dataset

– we used three different natural language processing libraries (NLTK, Spacy, and Polyglot) to process the policies and compared the results to ensure that the linguistic properties of the respective languages such as conjugation where factored in correctly. We chose Polyglot as it performed best on the specific word lists we had created.

Since Polyglot does not include lemmatization, we utilized distinct lemmatization lists.888Available at

. We also utilized Named Entity Recognition (NER) and regular expressions as an ensemble approach to search the policies for contact data.

Iii-E Limitations

Scheitle et al. [36] showed that many publicly available top lists, including Alexa, are biased, fluctuate highly, and that there are substantial differences among lists.

Indeed, we observed high fluctuation as, on average, a country’s top list from January and May only had 387 entries in common. Nevertheless, we relied on Alexa’s top lists, as they are the only source for country-specific rankings. However, we accounted for high fluctuation by refraining from analyzing correlations between the top list ranking and other factors measured, except for the impact of consent notice libraries.

We accounted for bias potentially introduced due to the rankings used by

conducting the pre-post analysis only on domains present in the January top list. To account for potential top list manipulation [22],

especially give some countries’ small population,

we excluded domains that were offline during one of the crawls or were blocked by the protection mechanisms of the browser. Moreover, the obligation to comply with legal regulations is independent of the legitimacy of being listed in top lists.

Regarding the use of GDPR-related terms in text analysis, our keyword list can only provide limited insights into the GDPR compliance of policy texts. Although we created a comprehensive list of translations of relevant terms, privacy policies are not required to use these terms. In fact, the GDPR’s requirement to provide privacy policies in an “intelligible” form could potentially decrease the use of legal jargon in privacy policies, although we did not see evidence of that in our dataset. Nevertheless, our keyword lists should be seen as a starting point for additional research and analysis in order to assess legal compliance in more detail and at scale.

Iv Evaluation of Privacy Policies

In total, the lists of the 500 most frequently visited websites for all 28 EU member states in January 2018 contained 6,759 different domains; the final list in November contained 13,458 domains. Unless mentioned otherwise the pre-/post-GDPR comparison is based on the data points for the domains first annotated in January, while the analysis of the cookie consent notices is based on the extended list we had created by the end of May. The overall prevalence of privacy policies on these websites was already high (79.6 %) before the GDPR went into effect and only increased slightly to 84.5 % afterwards. However, we found big differences among the 28 EU member states, with privacy policy rates between 75.6 % and 97.3 % at the end of May, and also between different content categories varying from 53.7 % and 98.2 %. Although the GDPR was officially adopted in 2016, half of the websites (50.4 %) updated their privacy policies in the weeks before May 25, 2018. 15 % did not make any update since the adoption.

The GDPR’s most notable (and visible for users) effect we observed is the increase of cookie consent notifications, which rose from 46.1 % in January to 62.1 % in May. We found that especially popular websites implement cookie consent notices and choices using third party libraries. Our in-depth analysis of

common libraries found in our dataset revealed shortcomings in how those consent mechanisms can satisfy the requirements of Article 6 of the GDPR (see Section V for details).

Iv-a Privacy Policies

Our dataset of privacy policies was based on 6,759 domains since multiple services (e.g., Facebook and Google) appear in more than one country’s top list. Of those domains, 5,091 had a complete or partial privacy policy statement. In January, our system found the majority of policies (3,476) automatically, the remaining 3,283 sites were checked manually, resulting in the identification of another 1,624 privacy policies. 1,276 websites did not have a privacy policy and the remaining 383 websites could not be reached.

Iv-A1 Websites added policies

Table I gives an overview of the changes in the number of websites with privacy policies for the (a) 500 most popular websites in a country and (b) country-specific top-level domains (TLD). For this analysis, we compared the results of January 2018 with those from right after May 25, 2018. In both sets, we excluded sites that we found to be offline during at least one of the crawls. Results for October 2018 only slightly deviate from the measurement made at end of May. The average increase from May to October was +1.0 percentage point.

The data shows that the majority of websites (79.6 %) already had privacy policies in January 2018. That level rose by 4.9 % to 84.5 % after May 25, 2018. However, there are clear differences in the country and domain level. Countries with a lower rate of privacy policies added more privacy policies than those where privacy policies were already common. For example, in Latvia’s top-500 list 10.2% of the websites added privacy policies, and an even higher amount (+27 %) of all websites with the Latvian TLD .lv added one. At the same time, in countries like Spain (ES), Germany (DE) or Italy (IT), where over 90 % of websites on the top lists had privacy policies, few sites added them. On the domain level, these few additional sites helped to reach 100 %.

We also checked the prevalence of privacy policies on non-EU and generic TLDs, of which we found 207 unique ones in our dataset; 39 occurred in the top lists of 20 or more countries. Table I lists the 5 most frequently found TLDs that are not EU-country specific. Besides generic TLDs (.com, .org, .info, .net, .eu, .tv) Russia’s TLD .ru frequently showed up in top lists of countries with a Russian-speaking minority.

Table II shows data from the same comparison between January and May ordered by website category. Overall, 4.9 % of websites added policies, note that the average differs since websites were listed in multiple top lists and could also be assigned multiple categories. Based on these findings, GDPR seems to have had the biggest impact on sites that are more likely to collect sensitive information like health or sports-related websites or that are connected to children (Kids & Teens, Education). The processing of the personal information of children must also adhere to higher standards in the GDPR.

It is a positive result that the highest rates of privacy policies occur in the Finance, Shopping, and Health categories, where websites routinely process more sensitive data. Between May and October, 10 sites removed their privacy policy. The manual analysis showed that in most cases the sites were redesigned and no policy was (re-)added. For some websites, e. g.,, the privacy policy was still available under a link we had previously stored, but the link is not made available to users that are not already registered with the service. In general, more websites added policies when they had been less prevalent in their country/category. The largest changes were observed in the Baltic states (on .lv, .lt and, .ee domains), but affected all top lists.

top list TLD
N Pre Post Diff N Pre Post Diff
AT 455 91.6 % 94.5 % 2.9 % .at 132 95.5 % 98.5 % 3.0 %
BE 460 89.6 % 92.4 % 2.8 % .be 141 92.2 % 97.9 % 5.7 %
BG 451 83.1 % 88.9 % 5.8 % .bg 166 80.1 % 89.8 % 9.6 %
CY 432 76.4 % 83.6 % 7.2 % .cy 58 62.1 % 69.0 % 6.9 %
CZ 459 81.9 % 88.0 % 6.1 % .cz 251 80.9 % 89.2 % 8.4 %
DK 447 91.3 % 95.1 % 3.8 % .dk 174 95.4 % 99.4 % 4.0 %
DE 455 88.8 % 91.6 % 2.9 % .de 172 98.8 % 100.0 % 1.2 %
EE 441 63.5 % 76.2 % 12.7 % .ee 132 56.8 % 72.7 % 15.9 %
ES 429 90.0 % 92.1 % 2.1 % .es 86 98.8 % 100.0 % 1.2 %
FI 462 85.1 % 92.0 % 6.9 % .fi 145 80.7 % 93.1 % 12.4 %
FR 453 90.7 % 93.6 % 2.9 % .fr 139 95.7 % 98.6 % 2.9 %
GB 463 95.5 % 97.2 % 1.7 % .uk 108 98.1 % 98.1 % 0.0 %
GR 443 77.9 % 83.7 % 5.9 % .gr 233 72.1 % 80.3 % 8.2 %
IE 447 91.1 % 93.1 % 2.0 % .ie 104 98.1 % 99.0 % 1.0 %
IT 423 90.3 % 93.9 % 3.5 % .it 174 96.6 % 97.7 % 1.1 %
HU 440 85.7 % 90.5 % 4.8 % .hu 228 85.5 % 91.2 % 5.7 %
HR 430 82.8 % 86.3 % 3.5 % .hr 141 82.3 % 84.4 % 2.1 %
LV 434 59.9 % 75.6 % 15.7 % .lv 126 46.8 % 73.8 % 27.0 %
LT 452 67.9 % 78.1 % 10.2 % .lt 174 58.0 % 73.6 % 15.5 %
LU 440 81.4 % 84.8 % 3.4 % .lu 61 65.6 % 73.8 % 8.2 %
MT 446 86.3 % 88.3 % 2.0 % .mt 46 63.0 % 71.7 % 8.7 %
NL 459 86.3 % 90.0 % 3.7 % .nl 115 96.5 % 100.0 % 3.5 %
PL 462 91.1 % 94.4 % 3.2 % .pl 256 93.4 % 96.5 % 3.1 %
PT 430 85.6 % 88.6 % 3.0 % .pt 116 86.2 % 91.4 % 5.2 %
RO 434 81.3 % 85.9 % 4.6 % .ro 160 86.3 % 91.9 % 5.6 %
SE 459 89.1 % 93.2 % 4.1 % .se 166 87.3 % 94.6 % 7.2 %
SK 438 79.5 % 86.3 % 6.8 % .sk 189 73.5 % 84.1 % 10.6 %
SI 451 91.4 % 95.6 % 4.2 % .si 132 90.9 % 96.2 % 5.3 %
Total 6357 79.6 % 84.5 % 4.9% 4125 82.7 % 89.4 % 5.7 %
.com 2026 82.5 % 83.9 % 1.4 %
.ru 147 65.6 % 68.8 % 3.2 %
.org 122 47.5 % 50.0 % 2.5 %
.net 248 64.6 % 70.6 % 6.0 %
.eu 43 58.1 % 67.4 % 9.3 %
Table I: Availability of privacy policies in the top 500 websites by country, pre- (January 2018) and post-GDPR (after May 25, 2018).
Category n pre post diff
Adult 256 68.8 % 72.7% 3.9%
Arts & Entertainment 521 70.1 % 75.8 % 5.7 %
Business 529 81.5 % 87.3 % 5.8 %
Computers 686 87.9 % 90.8 % 2.9 %
Education 380 70.0 % 79.7 % 9.7 %
Finance 427 92.3 % 96.5 % 4.2 %
Games 245 87.8 % 92.7 % 4.9%
Government 132 66.7 % 73.5 % 6.8 %
Health 99 89.9 % 97.0 % 7.1 %
Home 134 97.8 % 99.3 % 1.5 %
Kids and Teens 37 83.78% 91.89% 8.11%
News 958 80.8 % 86.6 % 5.8 %
Recreation 90 81.1 % 86.7 % 5.6 %
Reference 497 83.5 % 88.1 % 4.6 %
Regional 108 81.5 % 88.0 % 6. %
Science 31 90.3 % 96.8 % 6.5 %
Shopping 925 94.4 % 98.2 % 3.8 %
Society & Lifestyle 444 86.0 % 90.1 % 4.1 %
Sports 267 80.2 % 86.5 % 6.3 %
Streaming 337 50.5 % 53.7 % 3.2 %
Travel 250 88.8 % 93.2 % 4.4 %
avg. 350.14 86.9 % 5.3 % 5.4 %
Table II: Availability of privacy policies per website category, pre- (January 2018) and post-GDPR (after May 25, 2018).

Iv-A2 Changes in privacy policies

Figure 2: Percentage of policies changed in a certain time span. n(2016) = 860, n(2017) = 806, n(2018) = 726, n(May2018) = 6195, n(2016-2018) = 1610. The line shows the average month-to-month change.

We compared different versions of privacy policies to see if they changed and whether these changes were GDPR-related. The majority of websites updated their privacy policies in the last two years. Comparing versions from March 2017 (before the GDPR was passed) and May 2018, 85.1 % were changed at least once. About 72.6 % of those policies were (also) updated between January and June 2018, but the majority of changes (50.0 %) occurred within one month preceding May 25.

Analyzing the variance between two month using ANOVA showed significant changes from November to December 2017 (most likely due to the fact that policies before that date were based on archival data) and around the GDPR deadline early May to June to July.

Some websites seemingly missed the GDPR deadline: 118 sites that had not updated their privacy policy since early 2016 did so between our two post-GDPR measurements at the end of May and the end of June 2018.

In all cases, privacy policy changes meant the addition of text to the privacy policy. The average text length rose from a mean of 2,145 words in March 2016 to 3,044 words in March 2018 (+41 percentage points in 2 years) and increased another 18 percentage points until late May (3,603 words).999We refrained from comparing policy lengths across countries due to language differences impacting length (e. g., the use of compounds instead of separate words). This demonstrates a tension between the GDPR’s requirement for concise and readable notices with its additional disclosure requirements, such as mentioning the legal rights of a data subject, providing the data processor’s contact information, and naming its data protection officer.

Iv-A3 GDPR compliance issues

By the end of May, 350 of the 1,281 websites that did not have a policy in January had added one.

The remaining 931 sites can be considered not compliant with the GDPR’s transparency requirements due to the lack of a privacy policy or similar disclosure.

Websites without privacy policy remain most common in the Baltic states. More than 24% of top-listed sites in Lithuania, Latvia, and Estonia still had no privacy policy. While some of those pages might not be actively maintained or may not care about legal obligations due to illicit content, 73 websites have no privacy policy but serve a cookie consent notice (down from 161 in January). We even found 14 websites that added this kind of notification in 2018 without adding a privacy policy.

Iv-A4 Policy content

Comparing the content of privacy policies between January and May, we saw that an additional 9 % of policies contained e-mail addresses, up from 37.7 to 46.6 %. Similarly, an additional 9 % mentioned a data protection officer. Searching for GDPR keywords in our set of policies in all languages yielded an increase in the use of all keywords. Since website owners are not required to use these specific terms (see III-E), we focused on analyzing the change in their importance by ranking the terms based on the number of policies that included them. Overall, terminology related to user rights (“erasure” (+8 %), “complaint” (+11 %), “rectification” (+6 %), “data portability”(+7 %)) appeared more often. We also saw an increase in mentions of possible legal bases of processing. While the number of policies mentioning consent was stable (J: 28 %, M: 29.2 %), an increasing number of policies explicitly mentioned other aspects described in Article 6 GDPR like “legitimate interest” (J: 7 %, M: 19.2 %).

Iv-A5 Tracking and cookies

We did not observe a significant change in the use of tracking services or cookies. In January, websites used on average 3.5 third-party tracking services that would be blocked by an off-the-shelf ad blocker.

Still, some websites made notable changes: we manually checked websites that did not use trackers in June but did so in January and found that 146 stopped using ad or tracking services and 37 did not track before explicit user consent was given. Notable examples are and Only after consenting into tracking – or subscribing to paid services – users are directed to the regular homepage of these sites.

In May, right before the GDPR came into effect, and in June we measured the number of first- and third-party cookies a website sets by default. Regarding third-party cookies no effect is visible; websites set about 5.4 cookies on average. The number of first-party cookies decreased from 22.2 to 17.9 cookies on average. This effect can be explained by a decrease in first-party cookie use in Croatia (-11.3) and Romania (-21.1). The medians stayed the same for both cookie groups.

Iv-A6 Https

We also measured whether the adoption of HTTPS by default changed over the course of twelve months. We always checked the HTTP address of a host and observed whether the visited website automatically redirected to HTTPS. Our data confirm a general trend towards HTTPS that was reported before [14]. Figure 3 shows the increase in the use of HTTPS by default from 59.9 % in December 2017 to 80.2 % in November 2018. At the end of May, 70.8 % of websites redirected to HTTPS, close to the 74.7 % reported by Scheitle et al. [36], who measured the HTTPS capabilities of the Alexa top 1 million websites. The average increase was +1.9 percentage points in a month-by-month comparison. Statistically significant changes in the variance (ANOVA) were found from December 2017 to January 2018 (+2.9), early May to June (+3.9), and October to November 2018 (+2.7). The high increase from May to June was preceded and followed by months of less increase, which can be interpreted as a concentration of activities around the GDPR enforcement date that followed an overall trend. Looking at the TLD level, the majority (18 out of 28) show an adoption larger than 80 % in November 2018. For three countries, we found an increase of more than 30 percentage points (.pl, .gr., .es), but only for .es the adoption is now above the average.

Figure 3: Change in HTTPS adoption over time. The dotted line marks the GDPR enforcement date.

Our findings indicate that at the time the GDPR came into force the number of websites with privacy policies increased, affecting some countries and sectors more than others. Effects have so far been limited to transparency mechanisms as the use of tracking and cookies appears largely unchanged. In the next sections, we focus on a second development, the increase in the use of cookie consent notices, which, in principle, should not only inform users but also offer actual choice.

V Studying Cookie Consent Notices

In January and May, we manually inspected all websites for cookie consent notices. In January, we only noted whether a website displayed a cookie banner or not. Because the observed sophistication of cookie banners increased substantially, during the May annotation, we also analyzed and categorized the type of consent notice based on its interaction options. We identified the following distinct types with examples shown in Figure 4:

Figure 4: Types of cookie consent notices with different interaction models.

No Option: Cookie consent notices with no option (Figure 4 (a)) simply inform users about the site’s use of cookies. Users cannot explicitly consent to or deny cookie use. This category also includes banners that feature a clickable button whose label cannot be considered to express agreement (e. g., “Dismiss,” “Close,” or just an “X” to discard the banner).

Confirmation: In contrast, confirmation-only banners (Figure 4 (b)) feature a button with an affirmative text such as “OK” or “I agree”/“I accept” which can be understood to express the user’s consent.

Binary consent notices (Figure 4 (c)) give users the options to explicitly agree to or decline all the website’s cookies.

Slider: More fine-grained control is offered by cookie banners that group the website’s cookies into categories, mostly by purpose. Slider-based notices (Figure 4 (d)) arrange these categories into a hierarchy. The user can move a slider to select the level of cookie usage they are comfortable with, which implies consent with all the previously listed categories.

Checkbox-based notices (Figure 4 (e)) allow users to accept or deny each category individually. The number of categories varied, ranging from 2 to 10 categories; we observed that most notices of the “checkbox” type featured 3–4 different cookie categories. A common set of categories comprises advertising cookies, website analytics, personalization, and what is usually referred to as (strictly) necessary cookies, such as shopping cart cookies. According to Article 5(3) of the ePrivacy Directive (2002/58/EC), this type of cookies does not require explicit user consent.

Vendor: We assigned this category to banners that allow users to toggle the use of cookies for each third party individually. Figure 4 (f) shows one such mechanism.

Other: This category, assigned five times in total, was used for cookie banners that did not match any other category, e. g., one site allowed users to choose between two “cookie profiles”.

In addition to the cookie banner annotation, all websites were manually categorized by topic to specify what information or services they provide. We used Alexa’s website categorization scheme.101010 but performed the categorization manually since Alexa only provided categories for about a third of the websites in our data set. We also added the categories “Government” and “Streaming” because our dataset contained a substantial number of websites fitting those categories.

V-a Analysis of Cookie Consent Libraries

During manual website annotation, we noticed that websites made use of third-party implementations to provide cookie consent notices. This raised questions about how common certain cookie consent solutions are and to what degree they can help website owners comply with Directive 2002/58/EC and the GDPR.

We compiled a list of the cookie consent libraries identified during manual annotation. If possible, we downloaded each library or requested access to a (demo) account from the vendor. We subsequently implemented each consent solution – one at a time – into a live WordPress website. We then visited the site using Microsoft Edge 41 configured to not block any cookies, interacted with the cookie banner, and used Edge’s Developer Console to observe the effect of user selection on the cookies stored to the machine. For each library, we tested the user interfaces it offered and whether its settings and documentation allowed us to block and unblock cookies (i.e., we did not write any custom code to implement new core functionality). We also tested if the libraries provided mechanisms to reconsider a previous consent decision and to log and store the users’ consent, as required by Article 7 GDPR.

It is in the interest of web service providers not to display consent notices to users that are not subject to GDPR. Thus, many libraries offer the option to display the notice only to users accessing the site from specific regions of the world. We tested these geolocation features using Tor Browser and a circuit

exiting in a country for which the cookie banner was configured not to show up.

We measured the popularity of identified cookie libraries in a separate scan of domains’ home pages in July and December 2018.

To determine if a website used a cookie library, we reviewed the default locations of JS and CSS resources and likely variants based on the installation instructions. Additionally, we checked for requests to third parties used by the libraries.

We manually verified this procedure with a list compiled during the manual annotation phase. To reflect the exposure a library or service has to end users, we calculated a score based on the ranking of the domain in’s EU top lists. This favors domains which are highly ranked in many top lists over domains which are only in a single top list.

This better accounts for the exposure a library has to end users. This inherits the bias the Alexa top list has (see Section III-E). It is calculated by subtracting the of a domain from for each top list () and summing up these values. Sites no longer present in the top lists were assigned rank . The is then normalized by dividing by :

V-B Limitations

Parts of our study were conducted with automated browsers using a server hosted on a known server farm. It is known that some websites change their behavior when an automated browser or specific server IP addresses are detected. We observed that several websites using Cloudflare’s services blocked direct requests and asked to resolve a CAPTCHA before redirecting to the actual site. As described above, we checked for these effects as we manually visited all websites to determine, e. g., which type of cookie banner they used. Another drawback of

our technical setup was that some websites might have changed their default language based on the IP of the server (in Germany) or the default browser language (English). While this might have influenced the language of the privacy policy and cookie banner presented, it should not have changed the fact that either exists.

(a) Cookie banner types by country (October 2018). Dotted line indicates the average.
(b) Distribution of cookie banner libraries based on the websites’ Alexa rank (December 2018).
Figure 5: Distribution of cookie consent notices and popularity of libraries.

Vi Evaluation of Cookie Consent Notices

We found that the adoption of cookie consent notices had increased across Europe, from 46.1 % in January to 62.1 % at the end of May (post-GDPR) and reached 63.2 % in October 2018. Adoption rates significantly differ across individual member states, as does the distribution of different types of consent notices. The libraries we encountered on popular sites do not always support important features to fulfill GDPR requirements like purpose-based selection of cookies and consent withdrawal.

Vi-a Adoption

Table III compares the prevalence of cookie consent notices in January 2018 with May 2018. Grouped by Alexa country list, the percentage of sites featuring a consent notice, on average, has increased, ranging from +20.2 percentage points in Slovenia to +45.4 in Italy. Looking at the sites by top-level domain (TLD), the average adoption rate increased from 50.3 % to 69.9 % post-GDPR. For the .nl and .si TLDs, the number of sites implementing a cookie banner did not increase substantially from January to May 2018 as they both already had high adoption rates of 85.2 % and 75.8 %, respectively. The highest increase in cookie banner prevalence by TLD was observed in Ireland – for the 104 .ie domains in our dataset, the adoption rate increased from 17.3 % to 87.5 %.

Figure 5 (a) shows the distribution of the different types of cookie consent notices (see Section V) by country post-GDPR (end of May 2018). The use of checkbox-based cookie consent notices stands out in France and Slovenia, while websites in Poland use the highest number of no-option notices.

Top list TLD
n pre post diff N pre post diff
AT 455 33.0 % 55.2 % 22.2 % .at 132 45.5 % 69.7 % 24.2 %
BE 460 40.9 % 61.1 % 20.2 % .be 141 59.6 % 78.7 % 19.1 %
BG 451 37.9 % 60.5 % 22.6 % .bg 166 52.4 % 71.7 % 19.3 %
CY 432 26.4 % 50.2 % 23.8 % .cy 58 13.8 % 27.6 % 13.8 %
CZ 459 34.0 % 52.7 % 18.7 % .cz 251 44.6 % 58.2 % 13.5 %
DK 447 41.2 % 68.9 % 27.7 % .dk 174 72.4 % 87.4 % 14.9 %
DE 455 26.2 % 49.0 % 22.9 % .de 172 42.4 % 64.5 % 22.1 %
EE 441 9.5 % 35.8 % 26.3 % .ee 132 14.4 % 35.6 % 21.2 %
ES 429 41.5 % 64.3 % 22.8 % .es 86 72.1 % 84.9 % 12.8 %
FI 462 27.5 % 53.9 % 26.4 % .fi 145 37.9 % 55.9 % 17.9 %
FR 453 49.2 % 66.9 % 17.7 % .fr 139 77.0 % 87.1 % 10.1 %
GB 463 37.4 % 67.0 % 29.6 % .uk 108 58.3 % 82.4 % 24.1 %
GR 443 40.0 % 59.8 % 19.9 % .gr 233 56.7 % 69.1 % 12.4 %
IE 447 21.3 % 64.2 % 43.0 % .ie 104 17.3 % 87.5 % 70.2 %
IT 423 21.3 % 66.7 % 45.4 % .it 174 30.5 % 90.8 % 60.3 %
HU 440 46.4 % 62.7 % 16.4 % .hu 228 67.1 % 76.3 % 9.2 %
HR 430 28.6 % 54.7 % 26.0 % .hr 141 48.9 % 70.9 % 22.0 %
LV 434 16.8 % 41.9 % 25.1 % .lv 126 38.1 % 61.1 % 23.0 %
LT 452 27.0 % 47.3 % 20.4 % .lt 174 50.0 % 63.2 % 13.2 %
LU 440 24.8 % 51.8 % 27.0 % .lu 61 36.1 % 57.4 % 21.3 %
MT 446 25.8 % 58.1 % 32.3 % .mt 46 21.7 % 43.5 % 21.7 %
NL 459 37.3 % 54.2 % 17.0 % .nl 115 85.2 % 87.8 % 2.6 %
PL 462 53.9 % 68.6 % 14.7 % .pl 256 75.4 % 83.2 % 7.8 %
PT 430 31.4 % 53.7 % 22.3 % .pt 116 52.6 % 65.5 % 12.9 %
RO 434 30.2 % 53.5 % 23.3 % .ro 160 52.5 % 73.1 % 20.6 %
SE 459 33.3 % 63.6 % 30.3 % .se 166 50.6 % 78.3 % 27.7 %
SK 438 42.2 % 56.8 % 14.6 % .sk 189 60.3 % 69.3 % 9.0 %
SI 451 43.9 % 64.1 % 20.2 % .si 132 75.8 % 77.3 % 1.5 %
Total 6357 46.1 % 62.1 % 16.0 % 4125 50.3 % 69.9 % 19.6 %
.com 1915 28.7 % 50.7 % 22.0 %
.net 248 25.4 % 35.5 % 10.1 %
.ru 148 5.4 % 6.7 % 1.3 %
.org 119 13.5 % 23.5 % 10.8 %
.eu 43 23.3 % 37.2 % 13.9 %
.tr 32 6.3 % 6.3 % 0.0 %
Table III: Availability of cookie consent notices in the top 500 websites by country, pre- (January 2018) and post-GDPR (after May 25, 2018).

Vi-B Cookie Banner Libraries

In addition to categorizing the observed cookie notices, we also analyzed commonly encountered third-party cookie libraries in more detail.

During the manual annotation phase of the post-GDPR crawl, we noticed that apart from the increase in usage and complexity of cookie consent notices, the usage of specialized libraries and third parties increased to help websites meet the new legal requirements. Overall, we identified 31 cookie consent libraries with automated means. We measured their distribution in July 2018 and found that 15.4 % of the websites displaying cookie consent notices used one of the identified libraries. Figure 5 (b) displays the scores we computed for the different libraries. We excluded from our in-depth analysis two libraries not available in English and a WordPress plugin discontinued in November 2018.

Our results of the analysis of 28 cookie consent libraries are presented in Table IV. We compared the libraries with respect to the following properties:

Source identifies whether the code for the consent notice can be hosted by the first party (self-hosted) or whether it is retrieved from a third party.

Mechanism refers to the three distinct mechanisms for consent management. One solution is to have the website asking for consent implement the (un)blocking of cookies according to the user’s wishes (local consent management). The consent information is stored in a first-party cookie the website can query to react accordingly. Decentralized consent management leverages the opt-out APIs provided by third parties, such as online advertisers, to tell them the user’s preferences and they are expected to react accordingly. They may remember the user’s decision by setting a third-party opt-out cookie. A third option is to use the services of a third party offering centralized consent management, who is informed of the user’s cookie preferences and triggers the corresponding notifications to participating vendors that would like to set cookies on the user’s system. The libraries in our data set that follow this approach have implemented IAB (Interactive Advertising Bureau) Europe’s Transparency and Consent Framework. This framework, developed by an industry association, aims to standardize how consent information is presented to the user, collected, and passed down the online advertising supply chain [20]. IAB-supporting consent notices may display a list of vendors participating in the framework, and the user can select which vendor should be allowed to use their personal data for a variety of purposes. The user selection is encoded in a consent string and transmitted to the participating vendors who committed to comply with the user’s selection. Libraries that do not provide any type of consent management are only capable of displaying a cookie notice.

Consent notices are presented in one of two ways: Overlays block usage of the website until the user clicks one of the banner’s buttons. In contrast, standard banners are non-modal and thus do not prevent website use while the notice is displayed. Regarding the options the interface may offer to the user, we use the same definitions as in our analysis in Section VI-A.

AutoAccept refers to mechanisms that automatically assume the user to consent to the use of cookies if they scroll or click a link on the website and react by removing the banner. Some consent libraries offer the website owner to automatically scan their site for cookies to assist with sorting them into categories or just display them to provide additional information to the user.

The following two properties are crucial for a library’s ability to comply with the user’s cookie preferences. The first is the ability to block cookies111111For the rest of this section, when we talk about cookies in the context of consent, we only refer to cookies that are not considered strictly necessary and thus can only be set with the user’s consent., i. e., prevent the website from setting cookies if the user has not (yet) consented to their use. If the user changes settings for previously set cookies, the library is expected to delete cookies. Custom expiration refers to the site administrator being able to manually set the expiration date of the cookie and thus determine when the consent notice will be shown again. Geolocation functionality allows to display the cookie banner only to users from selected areas. The Legal section lists two properties Article 7 GDPR considers vital for valid consent, the necessity for a data collector to prove that consent was given and the possibility for a user to withdraw consent. If a library allows the user to reconsider and modify their previous consent by displaying a small button or ribbon that opens the consent interface again, we captured this via the consent change property. Consent logging lets the website owner store information about users’ consent decisions for auditing purposes.

Combining the different types of user interfaces with the ability to block and delete cookies allows for the implementation of different types of consent.

  • Implied Consent mechanisms assume the user agrees to the use of cookies if they continue to use the website. Implementing this just requires displaying a banner with or without a confirmation button; AutoAccept may also be used. Note that implied consent does not meet the requirements outlined in Article 7 of the GDPR (see II).

  • If a site displays a notice

    that prevents the user from accessing the site unless the use of cookies is acknowledged, this is referred to as forced opt-in. This requires support of the overlay banner type to block access to the website and a confirmation button.

  • An opt-in mechanism does not set any non-essential

    cookies by default, but users have the opportunity to explicitly allow the use of all the website’s cookies. This requires a banner with one (allow) or two (allow / disallow) buttons that blocks cookies by default.

  • In the opt-out case, all cookies are set by default, but the user can opt out. This requires the library to display a banner with one (disallow) or two (disallow / allow) buttons and delete cookies that have already been set.

  • More fine-grained types of user selection (slider, checkboxes, individual vendors) just require the library to implement more fine-grained deletion and blocking of cookies. Giving the user more control of which types of cookies to allow and to refuse is in alignment with the GDPR’s requirement that consent be given with regard to a specific purpose. It is questionable whether slider-based mechanisms are GDPR-compliant because they force the user to also allow the previous categories in the hierarchy.

Source Mechanism User Interface Technical Details Legal


Third party

Local CM





No Option







Block Cookies

Delete Cookies

Cookie Scan

Custom Expir.




General Libraries
Civic Cookie ControlW12 $
Clickio Consent Tool*13 ? ? ?
consentmanager.netW14 ?
cookieBARW15 1.7.0
CookiebotW16 $
Cookie Consent17
Cookie Information*18 ? ? ? ? ?
Cookie Script19* $ ? $ $
Crownpeak (Evidon)*20
Didomi*21 ? ?
jQuery EU Cookie Law popups23
OneTrust*24 ?
Quantcast ChoiceW25
TrustArc (TRUSTe)*26
WordPress Plugins
Cookie Bar27
Cookie Consent28 2.3.11
Cookie Law Bar29 1.2.1
Cookie Notice for GDPR30 1.2.45
Custom Cookie Message31 2.2.9
EU Cookie Law32 3.0.5
GDPR Cookie Compliance33 1.2.6 $ $
GDPR Cookie Consent34 1.7.1 $ ? $ $
GDPR Tools35 1.0.2 $ ? $ ?
WF Cookie Consent36 1.1.4
Drupal Modules
Cookie Control37 1.7-1.6 B
EU Cookie Compliance38 7.x-1.25 ?
Simple Cookie Compliance39 7.x-1.5
Table IV: Properties of cookie consent libraries. : supports this property, : does not support this property, B (for “bug”): functionality exists but did not work, ?: could not be determined, $: paid version only. * indicates a library we could not install on our test website. W: also available as a WordPress plugin.

Examining the libraries listed in Table IV, we made the following observations:

The notion of implied consent is widely supported and easy to implement – adding a banner stating that the website uses cookies just requires adding a JavaScript library to the website or activate a WordPress plugin. The same applies to forced consent. In contrast, types of consent offering the user multiple options require more effort because whether cookies are set and read or not should depend on user consent.

The opt-in scenario can be implemented (a) by overwriting the document.cookie JavaScript object and add a conditional block that only executes when querying the consent cookie returns that the user has consented. We also found libraries that (b) trigger a JavaScript event when the user has consented, upon which the cookie-setting code is run. Implementing an opt-out is challenging because it requires the cookie consent library to trigger deletion of the cookies that have already been set. A website can easily delete cookies originating from its own domain – unless they are HttpOnly or Secure cookies. It cannot delete third-party cookies due to the same-origin policy preventing access to cookies set by another host. Working opt-out mechanisms we found in the (b) scenario use JavaScript events to learn when consent has been revoked for all or selected categories of cookies and then leverage third-party opt-out mechanisms to delete these cookies. Google Analytics, for example, can be triggered to remove its cookies by setting window[’ga-disable-UA-XXXXXX-Y’] = true, where UA-XXXXXX-Y references the website ID. This mechanism requires third parties to provide APIs for opt-outs. In case the third party does not, the user is ideally alerted that their opt-out (partially) failed, as demonstrated by Civic Cookie Control, which displays a warning message that the cookies cannot be deleted automatically and provides a link to the third party’s opt-out website. This also poses limitations for cookie settings interfaces: Once a user has agreed to the use of third party cookies, revoking consent is limited to cookies for which deletion can be triggered by the website.

If a library supports consent for different cookie categories, it needs to know which cookies should be considered “strictly necessary” such that Art. 5(3) Directive 2002/58/EC applies and consent is not required. If the mapping of cookies into categories is done by the website owner, nothing prevents them from declaring all cookies “strictly necessary”. We found one notable example on the website of a major U.S. TV network, where cookies for Google Analytics and Google Ad Serving were categorized as necessary for website operation. One online marketing website used a complex consent solution but had simply declared all cookies necessary, causing the library to merely display a “no option” solution.

Fine-grained consent for individual vendors is supported by libraries that implement the IAB framework. The IAB-based consent notices we encountered both provided too much and too little information: By default, the IAB framework’s vendor-based cookie selection mechanism displays all of the vendors participating in the framework, not just the ones used by the website.404040As of December 13, 2018, the IAB supports 460 vendors (

This renders the fine-grained control offered by the framework unusable. We drew from our dataset a sample of 24 websites with IAB-supporting consent notices (10 Didomi, 7 Clickio, 7 Quantcast) and found that only two sites using Didomi had customized their list of vendors, reducing their number to 21 and 8.

At the same time, the functionality of IAB-based consent notices is limited to IAB vendors, unless the library also supports other vendors as in Didomi’s consent mechanism, which has integrated additional vendors including Google and Facebook. As we observed during the manual annotation of consent notices, IAB banners tend to display a standard text that does not inform users that the website may also use other third parties in addition to listed IAB vendors and that those other parties are not bound by the user’s consent decision made in the IAB-based tool.

Our analysis shows that implementing GDPR consent requirements in practice with existing libraries is a challenge. The GDPR’s requirements for informed consent include an affirmative action by the user upon having been provided with sufficient information about the purposes of cookie use. This is at odds with usability as studies have shown the ineffectiveness of previous choices mechanisms 


The options to implement meaningful choices for the user, including the ability to withdraw consent, are limited by technical restrictions, such as the same-origin policy, a core principle of web security, and the business interests of third parties, not all of which are interested in providing an opt-out API. Under the GDPR, consent has to be given for specific purposes of data processing, which raises the question who defines the purpose of the use of a certain cookie. If left to the developers or site owners, it is prone to abuse of the “strictly necessary” category to circumvent the consent requirement in Directive 2002/58/EC.

Vii Discussion and Future Work

Our results show that at the time the GDPR came into force websites made changes that can be considered improvements for web privacy, but the goal of harmonization is not yet met. We discuss resulting challenges and opportunities for researchers, policymakers, and companies. We also discuss some limitations of our study.

Vii-a Impact of the GDPR

Our analysis focuses on the 28 EU member states, but the GDPR also impacts websites from other countries – first because some non-EU countries have decided to adopt similar rules (e. g., Norway, Switzerland, Iceland and Liechtenstein [41])

and second, because websites that offer services in the EU have to comply with the GDPR. For example, according to Alexa, 53% of the U.S. top 500 websites and 48% of the most visited Russian sites also appear in at least one EU state’s top 500 list. A positive finding of our study is that even though the majority of websites already had privacy policies, the prevalence of privacy policies increased even further. Our results suggest that the harmonization of data protection rules could eventually lead to consistent privacy policy adoption rates across Europe. We also see the increased mention of GDPR-specific terms across all countries as a sign for the GDPR’s impact and a step towards harmonization. However, despite this trend, actions taken to comply with GDPR vary greatly, especially regarding consent and cookies.

Vii-B Need for More Detailed and Practical GDPR Guidance

Although the GDPR makes it clear that websites require a privacy policy, details about what is permissible or required remain unclear. Especially with respect to cookie consent notifications, the observed variance in implementation indicates the need for clearer guidelines for service providers. Such guidance should, for example, clarify what types of cookies can be set on what legal grounds. This requires determinations on questions such as whether website operators can claim a “legitimate interest” in web analytics or if user tracking requires explicit consent.

There is hope that a future ePrivacy Regulation may provide some clarity regarding these issues, but at the time of writing it is unclear when and it what form it may be adopted. Our results also show that some countries lag behind in the adoption of privacy policies. To improve the situation, data protection authorities could support companies by providing effective means for cookie handling, consent mechanisms, and privacy statements.

Vii-C False Sense of Compliance

Some of this uncertainty about how to interpret the GDPR may result in a false sense of compliance. Although the majority of websites in our dataset now have an up-to-date privacy policy, 15.5 % still do not have one and 14.9 % have not updated it in the last years. While the prevalence of privacy policies in the finance or shopping sector is close to 100 % and we do not expect semi-legal services in the streaming sector to be compliant, a number of websites in news, business, or education are likely not compliant with GDPR. Companies should also be aware that the widely used cookie banners that only inform users are not sufficient to obtain users’ consent. As the Article 29 working group stated, “merely proceeding with a service cannot be regarded as an active indication of choice” [5]. After all, companies violating GDPR risk fines of up to 4 % of their worldwide annual turnover.

Vii-D Opportunities for Web Privacy and Security Research

The presence of a privacy policy does not mean that a service is compliant with privacy law. More research is needed to study whether a privacy policy’s content actually meets legal requirements. So far, research on web privacy has largely been focused on English-language privacy policies and web users. Our study shows differences among countries and suggests that rather tiny language communities would benefit from a more multi-lingual research approach. Thus, the GDPR creates an interesting environment for privacy and security research not just to study its implementation but also to evaluate new ideas on how to improve security and privacy online. GDPR requires service providers to use “state-of-the-art technology” and our results indicate that the GDPR has already fostered increased adoption of HTTPS and cookie consent mechanisms. The increased prevalence of privacy policies as natural language descriptions of data practices, with more technical approaches like Do Not Track and P3P failing at the same time, increases the need for research that closes the gap between legal and technical privacy means. Research could help to raise minimum security standards by creating new, easy to adopt security mechanisms and improve usability with browser-based implementations of consent mechanisms. To foster research in this area, the tools and data sets used for this study are publicly available in a GitHub repository.414141

Viii Related Work

Privacy policies have been studied extensively as they constitute one of the primary means of transparency. While few have studied longitudinally the prevalence of privacy policies, prior work has analyzed how they are perceived by users, what they disclose, and how they present information to users.

Viii-a Adoption of Privacy Policies

The U.S. Federal Trade Commission first evaluated the use of privacy policies in 1998 and found that only 14 % of 674 websites studied had a privacy policy [13]. Numbers had increased when Liu & Arnett in 2002 received a privacy policy from 64 % of companies [26]. In 2017, Nokhbeh & Barber [28] found that of the 600 biggest companies by stock value 70 % had a privacy policy. Both studies were based on stock exchange listings, not popularity online. Both found huge differences between industry sectors, with the technology sector among the ones with higher privacy policy adoption rates of around 80 %. Story et al. examined one million Android apps in the U.S. Google Play Store and found that the percentage featuring privacy policies had increased from 41.7 % in September 2017 to 51.8 % in mid-May 2018 [38].

Viii-B Usefulness of privacy policies

Researchers have also studied privacy policies’ content and how users deal with these increasingly complex documents. McDonald and Cranor [27] concluded that a typical web user would have to spend 244 hours annually if they wanted to read every privacy policy of the websites they visit; it would further require a college degree to actually understand them [31]. Obar et al. recently confirmed that few people open privacy policies or terms of service they agree to when registering for a service, and over 90 % miss important details [30]. Still, reading privacy policies can help consumers build trust in companies [10], although recently Turow et al. [40] published a meta-study and showed that the pure existence of a privacy policy seems to be sufficient to achieve this goal, due to misconceptions of companies’ data practices.

Such misconceptions are even higher for younger adults.

Viii-C Analysis of Privacy Policies

Based on the results about the usefulness of privacy policies, researchers have started to support users and make privacy policies easier to comprehend or completely automate their assessment. To support machine learning approaches, Wilson et al. 

[42] created a corpus of 115 privacy policies of U.S. companies, which was extensively annotated by law students to identify described data practices.

Harkous et al. [18]

used the same corpus to train a deep learning system that allows querying privacy policies with natural language questions. Gluck et al. 

[17] evaluated how the length of privacy notices affects awareness of certain practices and concluded that (automatically) shortening privacy policies has potential, but important aspects may get lost if not done carefully. Leveraging the design space for privacy notices and controls may help create concise and actionable notices with integrated choice [34, 35]. Other researchers aim to extract information from privacy policies. Libert [25] analyzed English-language privacy policies to automatically check whether they disclose the names of companies doing third-party tracking on websites. Sathyendra et al. [33] evaluated how the options users have, especially about opting out, can automatically be identified in privacy policies. Tesfay et al. [39] collected privacy policies from the top 50 websites in Europe as identified by the Alexa ranking and developed a tool to summarize them and visualize the results inspired by GDPR criteria.

All these approaches currently focus on English-language documents as English

dominates the Web. Few researchers have evaluated other or multiple languages. Fukushima et al. [15]

evaluated machine learning approaches on a set of annotated Japanese privacy policies and found that automatic classifiers struggle with identifying important sections due to redundancy in the language. Cha

[6] compared privacy policies of Korean and U.S. websites based on the rules set by the EU privacy directive and found Korean websites to provide stronger privacy policies, but also to request more data from their users. To the best of our knowledge, no prior studies have evaluated and compared privacy policies from numerous countries, let alone all EU member states.

Viii-D Cookie Consent Notices

Taking into account that cookie consent notices are not supposed to be necessary (see Section II), research on them is scarce. In February 2015, the Article 29 Working Party conducted a “Cookie Sweep” to determine the effects of Directive 2009/136/EC’s requirements [4]. In eight EU member states, 437 sites were manually inspected for information they provided about cookies, including the type and position of the interface used. At that time, 116 (26 %) of the analyzed sites did not provide any information about cookie use; for another 39 % the information was deemed not sufficiently visible. Of the remaining 404 sites, 50.5 % (204) sites were found to “request […] consent from the user to store cookies” while 49.5 % (200) simply stated that cookies were being used. 16 % (49 sites) offered the user to accept or decline certain types of cookies. The study did not investigate whether the banners asking for consent implemented a proper opt-in mechanism. More recently, Kulyk et al. [29] collected cookie consent notices from the top 50 German websites in the Alexa ranking to investigate how users perceive and react to different types of banners. They identified five distinct groups of notices based on the amount of information they provide about cookie use but did not analyze users’ options for interacting with the banner.

Ix Conclusion

Our analysis of the top 500 websites in each of the EU member states, involving the analysis of privacy policies in 24 languages, indicate positive effects on web privacy taking place around the GDPR enforcement date. While most websites already had privacy policies, a large majority made adjustments. Most notable is the rise of cookie consent banners, which now greet European web users on more than half of all websites. While seemingly positive, the increase in transparency may lead to a false sense of privacy and security for users. Few websites offer their users actual choice regarding cookie-based tracking. Moreover, most of the analyzed cookie consent libraries do not meet GDPR requirements.

Browser manufacturers and the industry so far have not been able to agree on technical privacy standards, such as Do Not Track. This puts an additional burden on users, who are presented with an increasing number of privacy notifications that may fulfill the law’s transparency requirements but are unlikely to actually help web users make more informed decisions regarding their privacy. In addition, regulators need to provide clear guidelines in what cookies a service can claim “legitimate interests” and which should require actual consent.


The authors would like to thank Yana Koval for her help with manual website annotation and all native speakers who helped us verify the word lists. This research was partially funded by the MKW-NRW Research Training Groups SecHuman and NERD.NRW, and the National Science Foundation under grant agreement CNS-1330596.


  • [1] “Directive 2002/58/EC of the European Parliament and of the Council of 12 July 2002 concerning the processing of personal data and the protection of privacy in the electronic communications sector,” Offical Journal of the European Communities, Jul. 2002.
  • [2] “Directive 2009/136/EC of the European Parliament and of the Council of 25 November 2009 amending Directive 2002/22/EC, Directive 2002/58/EC and Regulation (EC) No 2006/2004,” Offical Journal of the European Communities, Nov. 2009.
  • [3] Article 29 Data Protection Working Party, “Working Document 02/2013 providing guidance on obtaining consent for cookies,” Tech. Rep. 1676/13/EN WP208, Oct. 2013.
  • [4] ——, “Cookie Sweep Combined Analysis – Report,” Tech. Rep. 14/EN WP 229, Feb. 2015.
  • [5] ——, “Guidelines on consent under Regulation 2016/679,” Tech. Rep. 17/EN WP259 rev.01, Oct. 2018.
  • [6] J. Cha, “Information privacy: a comprehensive analysis of information request and privacy policies of most-visited Web sites,” Asian Journal of Communication, vol. 21, no. 6, pp. 613–631, Dec. 2011.
  • [7] L. Cranor, “Necessary But Not Sufficient: Standardized Mechanisms for Privacy Notice and Choice,” Journal on Telecommunications & High Technology Law, vol. 10, pp. 273–307, 2012.
  • [8] L. Cranor, M. Langheinrich, M. Marchiori, M. Presler-Marshall, and J. Reagle, “The Platform for Privacy Preferences 1.0 (P3P1.0) Specification,” W3C Recommendation, Aug. 2002,
  • [9] S. Englehardt, D. Reisman, C. Eubank, P. Zimmerman, J. Mayer, A. Narayanan, and E. W. Felten, “Cookies That Give You Away: The Surveillance Implications of Web Tracking,” in International Conference on the World Wide Web (WWW).   ACM, 2015, pp. 289–299.
  • [10] T. Ermakova, B. Fabian, A. Baumann, and H. Krasnova, “Privacy Policies and Users’ Trust: Does Readability Matter?” in Americas Conference on Information Systems (AMCIS).   AIS, 2014.
  • [11] European Parliament, “Directive 95/46/EC of the European Parliament and of the Council of 24 October 1995 on the protection of individuals with regard to the processing of personal data and on the free movement of such data,” Oct. 1995.
  • [12] ——, “Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation),” Apr. 2016.
  • [13] Federal Trade Commission, “FTC Releases Report on Consumers’ Online Privacy,”, Jun. 1998.
  • [14] A. P. Felt, R. Barnes, A. King, C. Palmer, C. Bentzel, and P. Tabriz, “Measuring HTTPS Adoption on the Web,” in USENIX Security Symposium, 2017, pp. 1323–1338.
  • [15] K. Fukushima, T. Nakamura, D. Ikeda, and S. Kiyomoto, “Challenges in Classifying Privacy Policies by Machine Learning with Word-based Features,” in International Conference on Cryptography, Security and Privacy.   ACM, 2018, pp. 62–66.
  • [16] S. Garlach and D. Suthers, “‘I’m supposed to see that?’ AdChoices Usability in the Mobile Environment,” in Hawaii International Conference on System Sciences, 2018.
  • [17] J. Gluck, F. Schaub, A. Friedman, H. Habib, N. Sadeh, L. F. Cranor, and Y. Agarwal, “How Short Is Too Short? Implications of Length and Framing on the Effectiveness of Privacy Notices,” in Symposium on Usable Privacy and Security (SOUPS), 2016, pp. 321–340.
  • [18] H. Harkous, K. Fawaz, R. Lebret, F. Schaub, K. G. Shin, and K. Aberer, “Polisis: Automated Analysis and Presentation of Privacy Policies Using Deep Learning,” in USENIX Security Symposium, 2018, pp. 531–548.
  • [19] A. Huang, “Similarity Measures for Text Document Clustering,” in New Zealand Computer Science Research Student Conference (NZCSRSC), 2008, pp. 49–56.
  • [20] IAB Europe, “GDPR Transparency and Consent Framework,”
  • [21] C. Kohlschütter, P. Fankhauser, and W. Nejdl, “Boilerplate Detection Using Shallow Text Features,” in International Conference on Web Search and Data Mining (WSDM).   ACM, 2010, pp. 441–450.
  • [22] V. Le Pochat, T. Van Goethem, S. Tajalizadehkhoob, M. Korczynski, and W. Joosen, “Rigging Research Results by Manipulating Top Websites Rankings,” arXiv:1806.01156 [cs.CR], Nov. 2018.
  • [23] P. Leon, B. Ur, R. Shay, Y. Wang, R. Balebako, and L. Cranor, “Why Johnny Can’t Opt Out: A Usability Evaluation of Tools to Limit Online Behavioral Advertising,” in Conference on Human Factors in Computing Systems (CHI).   ACM, 2012, pp. 589–598.
  • [24] J. Leskovec, A. Rajaraman, and J. D. Ullman, Mining of Massive Datasets, 2nd ed.   Cambridge University Press, 2014.
  • [25] T. Libert, “An Automated Approach to Auditing Disclosure of Third-Party Data Collection in Website Privacy Policies,” in International Conference on the World Wide Web (WWW), 2018, pp. 207–216.
  • [26] C. Liu and K. P. Arnett, “Raising a Red Flag on Global WWW Privacy Policies,” Journal of Computer Information Systems, vol. 43, no. 1, pp. 117–127, Sep. 2002.
  • [27] A. M. McDonald and L. F. Cranor, “The Cost of Reading Privacy Policies,” I/S: A Journal of Law and Policy for the Information Society, vol. 4, pp. 543–568, 2008.
  • [28] R. Nokhbeh Zaeem and K. S. Barber, “A Study of Web Privacy Policies Across Industries,” Journal of Information Privacy and Security, pp. 1–17, Nov. 2017.
  • [29] O. Kulyk, A. Hilt, N. Gerber, and M. Volkamer, “‘This Website Uses Cookies’: Users’ Perceptions and Reactions to the Cookie Disclaimer,” in European Workshop on Usable Security (EuroUSEC), 2018.
  • [30] J. A. Obar and A. Oeldorf-Hirsch, “The Biggest Lie on the Internet: Ignoring the Privacy Policies and Terms of Service Policies of Social Networking Services,” Information, Communication & Society, pp. 1–20, Jul. 2018.
  • [31] R. W. Proctor, M. A. Ali, and K.-P. L. Vu, “Examining Usability of Web Privacy Policies,” International Journal of Human–Computer Interaction, vol. 24, no. 3, pp. 307–328, Mar. 2008.
  • [32] D. Rücker and T. Kugler, New European General Data Protection Regulation, 1st ed.   C. H. Beck, Hart, Nomos, Jul. 2018.
  • [33] K. M. Sathyendra, F. Schaub, S. Wilson, and N. Sadeh, “Automatic Extraction of Opt-Out Choices from Privacy Policies,” in AAAI Fall Symposium, Sep. 2016.
  • [34] F. Schaub, R. Balebako, and L. F. Cranor, “Designing Effective Privacy Notices and Controls,” IEEE Internet Computing, vol. 21, no. 3, pp. 70–77, 2018.
  • [35] F. Schaub, R. Balebako, A. L. Durity, and L. F. Cranor, “A Design Space for Effective Privacy Notices,” in Symposium on Usable Privacy and Security (SOUPS).   USENIX, 2015, pp. 1–17.
  • [36] Q. Scheitle, O. Hohlfeld, J. Gamba, J. Jelten, T. Zimmermann, S. D. Strowes, and N. Vallina-Rodriguez, “A Long Way to the Top: Significance, Structure, and Stability of Internet Top Lists,” arXiv:1805.11506 [cs], May 2018.
  • [37] D. Singer and R. Fielding, “Tracking Preference Expression (DNT),” W3C, Candidate Recommendation, Oct. 2017,
  • [38] P. Story, S. Zimmeck, and N. Sadeh, “Which Apps have Privacy Policies? An analysis of over one million Google Play Store apps,” in Annual Privacy Forum, 2018.
  • [39] W. B. Tesfay, P. Hofmann, T. Nakamura, S. Kiyomoto, and J. Serna, “PrivacyGuide: Towards an Implementation of the EU GDPR on Internet Privacy Policy Evaluation,” in International Workshop on Security and Privacy Analytics (IWSPA).   ACM, 2018, pp. 15–21.
  • [40] J. Turow, M. Hennessy, and N. Draper, “Persistent Misperceptions: Americans’ Misplaced Confidence in Privacy Policies, 2003–2015,” J. of Broadcasting & Electronic Media, vol. 62, no. 3, pp. 461–478, 2018.
  • [41] M. Vahl, “General Data Protection Regulation incorporated into the EEA Agreement,”, Jul. 2018.
  • [42] S. Wilson, F. Schaub, A. Dara, S. K. Cherivirala, S. Zimmeck, M. S. Andersen, P. G. Leon, E. Hovy, and N. Sadeh, “The Creation and Analysis of a Website Privacy Policy Corpus,” in Proc. 54th Annual Meeting of the ACL.   ACL, Aug. 2016, pp. 1330–1340.

X Appendix

Country Code TLD Lang Words identifying links to privacy policies GDPR
Austria AT .at DE datenschutz, datenrichtlinie see DE
Belgium BE .be NL,FR,DE see FR/NL/DE see FR/NL/DE
Bulgaria BG .bg BG поверителност, политика за данни, политика за бисквитки Закона за електронната търговия , Общ регламент относно защитата на данните
Cyprus CY .cy EL, TR gizlilik, veri ilkesi, see EL
Czech Republic CZ .cz CS soukromí, zásady používání dat, ochrana soukromí, podmínky, ochrana dat, ochrana osobních údajů obecné nařízení o ochraně osobních údajøo
Germany DE .de DE datenschutz, privatsphäre, datenschutzbestimmungen, datenschutzrichtlinie Datenschutzgrundverordnung
Denmark DK .dk DA beskyttelse af personlige oplysninger, datapolitik, cookiepolitik, privatlivspolitik, personoplysninger, regler om fortrolighed, personlige data generel forordning om databeskyttelse
Estonia ET .ee ET privaatsus,data policy, isikuandmete, isikuandmete töötlemise, küpsised, konfidentsiaalsuse, andmekaitsetingimused isikuandmete kaitse üldmäärus
Spain ES .es ES privacidad, política de datos, protecció de dades, aviso legal Reglamento general de protección de datos
Finland FI .fi FI yksityisyys, tietokäytäntö, tietosuojakäytäntö, yksityisyyden suoja, tietosuojaseloste, rekisteriseloste, tietosuoja, yksityisyydensuoja yleinen tietosuoja-asetus
France FR .fr FR confidentialité, politique d’utilisation des données, mentions légales, cgu, cookies, vie privée, donnees personelles, mentions légales r‘eglement général sur la protection des données
Greece GR .gr EL απόρρητο, όροι και γνωστοποιήσεις, προσωπικά δεδομένα, πολιτική απορρήτου Γενικός Κανονισμός για την Προστασία Δεδομένων
Croatia HR .hr HR privatnost, privatnosti, pravila o upotrebi podataka, zaštita podataka, kolačići Opća uredba o zažtiti podataka
Hungary HU .hu HU adatvédelem, adatkezelési, adatvédelmi, személyes adatok védelme általános adatvédelmi rendelet
Ireland IE .ie GA,EN see EN An Rialachán Ginearálta maidir le Cosaint Sonraí
Italy IT .it IT normativa sui dati regolamento generale sulla protezione dei dati
Lithuania LT .lt LT privatumas, slapukai, privatumo Bendrasis duomenų apsaugos reglamentas
Luxembourg LU .lu DE/FR see DE, FR see DE, FR
Latvia LV .lv LV privātums, privātuma, sīkdatņu, sīkdatne Vispārīgā datu aizsardzības regula
Malta MT .mt MT privatezza Regolament Ġenerali dwar il-Protezzjoni tad-Data
Netherlands NL .nl NL gegevensbeleid, privacybeleid algemene verordening gegevensbescherming
Poland PL .pl PL prywatność, zasady dotyczące danych, prywatności ogólne rozporządzenie o ochronie danych
Portugal PT .pt PT privacidade, política de dados Regulamento Geral sobre a Proteção de Dados
Romania RO .ro RO confidențialitate, politica de utilizare, cookie-uri, confidentialitate, cookie-urilor, protecţia datelor Regulamentul general privind protecția datelor
Slovakia SK .sk SK ochrana súkromia,zásady využívania údajov, ochrana údajov, ochrana osobných údajov, súkromie, piškotki, zásady ochrany osobných všeobecné nariadenie o ochrane údajov
Slovenia SI .si SL zasebnost, piškotkih, varstvo podatkov Splošna uredba o varstvu podatkov
Sweden SE .se SV sekretess, datapolicy, personuppgifter, webbplatsen, integritetspolicy allmän dataskyddsförordning
United Kingdom UK .uk EN privacy, privacy policy General Data Protection Regulation
Table V: Countries and codes
администратор správca Verantwortliche controller υπεύθυνος επεξεργασίας responsable
длъжностното лице по защита на данните pověřenec pro ochranu osobních údajů Datenschutzbeauftragte data protection officer υπεύθυνος προστασίας δεδομένων delegado de protección de datos
цел účel Zweck purposes σκοπός fin
правното основание právní základ Rechtsgrundlage legal basis νομική βάση base jurídica
обработване zpracování Verarbeitung processing επεξεργασία tratamiento
законните интереси oprávněné zájmy berechtigte Interessen legitimate interests έννομα συμφέροντα intereses legítimos
получателите příjemce Empfänger recipients αποδέκτης destinatarios
трета държава třetí země Drittland third country τρίτη χώρα tercer país
срок doba Dauer period χρονικό διάστημα plazo
информация přístup Auskunft access πρόσβαση acceso
коригиране oprava Berichtigung rectification διόρθωση rectificación
изтриване výmaz Löschung erasure διαγραφή supresión
ограничаване omezení Einschränkung restriction περιορισμός limitación
възражение právo vznést námitku Widerspruchsrecht object αντίταξης oponerse
преносимост на данните přenositelnost údajů Datenübertragbarkeit data portability φορητότητα δεδομένων portabilidad de los datos
оттегляне на съгласието odvolat souhlas Einwilligung widerrufen withdraw consent ανακαλώ τη συγκατάθεσή retirar el consentimiento
жалба stížnost Beschwerde complaint καταγγελία reclamación
надзорен орган dozorový úřad Aufsichtsbehörde supervisory authority εποπτική αρχή autoridades de control
договор smlouva Vertrag contract σύμβαση contrato
задължително изискване zákonný požadavek gesetzlich vorgeschrieben statutory requirement νομική υποχρέωση requisito legal
договорно изискване smluvní požadavek vertraglich vorgeschrieben contractual requirement συμβατική υποχρέωση requisito contractual
последствия důsledek Folgen consequences συνέπεια consecuencias
автоматизирано вземане на решения automatizované rozhodování automatisierte Entscheidungsfindung automated decision-making αυτοματοποιημένη λήψη αποφάσεων decisiones automatizadas
профилирането profilování Profiling profiling κατάρτιση προφίλ elaboración de perfiles
по-нататъшно обработване další zpracování Weiterverarbeitung further processing περαιτέρω επεξεργασία tratamiento ulterior
съгласие souhlas Einwilligung consent συγκατάθεση consentimiento
изпълнение на договор splnění smlouvy Erfüllung eines Vertrags performance of a contract εκτέλεση σύμβασης ejecutar un contrato
законово задължение právna povinnost rechtliche Verpflichtung legal obligation έννομη υποχρέωση obligación legal
жизненоважни интереси životně důležitý zájem lebenswichtiges Interesse vital interest ζωτικό συμφέρον interés vital
обществен интерес veřejný zájem öffentliches Interesse public interest δημόσιο συμφέρον interés público
официално правомощие veřejná moc öffentliche Gewalt official authority δημόσια εξουσία poder público
публичен орган orgán veřejné moci Behörde public authority δημόσια αρχή autoridad
Table VI: List of GDPR Phrases I
vastutav töötleja rekisterinpitäjä responsable du traitement rialaitheoir voditelj obrade adatkezelő titolare del trattamento pārzinis duomenų valdytojas
andmekaitseametnik tietosuojavastaava délégué à la protection des données oifigeach cosanta sonraí službenik za zaštitu podataka adatvédelmi tisztviselő responsabile della protezione dei dati datu aizsardzĩbas speciālistu duomenų apsaugos pareigūnas
eesmärk tarkoitus finalités críocha svrh cél finalità nolūks tikslas
õiguslik alus oikeusperuste base juridique bunús dlí pravna osnova jogalap base giuridica juridiskais pamats teisinį pagrindą
töötlemine käsittely traitement próiseáil obrada adatkezelés trattamento apstrāde duomenų tvarkymas
õigustatud huvi oikeutetut edut intérĕts légitimes leasanna dlisteanacha legitimne interese jogos érdek legittimo interesse leġitĩmās intereses teisėtas interesas
vastuvõtja vastaanottajat destinataires faighteoirí primatelje címzettek destinatario saņēmējs duomenų gavėjas
kolmas riik kolmas maa pays tiers tríú tír treća zemlja harmadik ország paese terzo trešā valsts trečioji valstybė
ajavahemik säilytysaika durée tréimhse razdoblje időtartalom periodo laikposms laikotarpis
juurdepääs pääsy accès rochtain pristup hozzáférés accesso piekļuve prieiga
parandamine oikaisu rectification ceartú ispravak helyesbítés rettifica labošana ištaisyti
kustutamine poistaminen effacement scriosadh brisanje törlés cancellazione dzēšanu ištrinti
piiramine rajoitus limitation srian ograničavanje korlátozás limitazione ierobežošanu apriboti
vastuväide vastustaa s’opposer agóid a dhéanamh ulaganje prigovora tiltakozni opporsi iebilst nesutikti
andmete ülekandmine tietojen siirto portabilité des données iniomparthacht sonraí prenosivost podataka az adat hordozhatóság portabilità dei dati datu pārnesamĩba duomenų perkeliamumas
nõusolek tagasi võtta peruuttaa suostumus retirer consentement toiliú a tharraingt siar povučiti privolu hozzájárulás visszavonása revocare il consenso atsaukt piekrišanu atšaukti sutikimą
kaebus valitus réclamation gearán prigovor panasz reclamo sūdzĩba skundąs
järelevalveasutus valvontaviranomainen autorité de contrôle údarás maoirseachta nadzorno tijelo felügyeleti hatóságként autorità di controllo uzraudzĩbas iestāde priežiūros institucija
leping sopimus contrat conradh ugovor szerződés contratto lĩgums sutartis
õigusaktist tulenev kohustus lakisääteinen vaatimus caractère réglementaire ceanglas reachtach zakonska obveza jogszabályos kötelezettség obbligo legale noteikta ar likumu teisės reikalavimas
lepingust tulenev kohustus sopimuksellinen vaatimus caractère contractuel ceanglas conarthach ugovorna obveza szerződéses kötelezettség obbligo contrattuale noteikta ar lĩgumu sutartyje numatytas reikalavimas
tagajärg seuraukset conséquences hiarmhairtí posljedice következmények conseguenza sekas pasekmės
automatiseeritud otsuste tegemine automaattinen päätöksenteko prise de décision automatisée chinnteoireacht uathoibrithe automatizirano donošenje odluka automatizált döntéshozás processo decisionale automatizzato automatizēta lēmumu pieņemšana automatizuotas sprendimų priėmimas
profiilianalüüs profilointi profilage próifíliú izrada profila profilalkotás profilazione profilēšana profiliavimas
edasine töötlemine jatkokäsittely traitement ultérieur phróiseáil tuilleadh dodatno obrađivati további adatkezelés ulteriore trattamento turpmāk apstrādāt tolesnis tvarkymas
nõusolek suostumus consentir toiliú privola hozzájárulás consenso piekrišanu sutikimą
lepingu täitmine sopimuksen täyttäminen exécution d’un contrat comhlíonadh conartha izvršavanje ugovora szerződés teljesítés esecuzione di un contratto lĩguma izpilde sutarties vykdymas
juriidiline kohustus lakisääteinen velvoite obligation légale oibleagáid dhlíthiúil pravna obveza jogi kötelezettség obbligo legale juridisku pienākumu teisinė prievolė
eluline huvi elintärkeä etu interĕt vital leasanna ríthábhachtacha ključni interes létfontosságú érdekek interesse vitale vitāla interese gyvybinius interesus
avalik huvi yleinen etu intérĕt public leas an phobail javni interes közérdek interesse pubblico sabiedrĩba interese viešojo intereso
avalik võim julkinen valta autorité publique údaráis oifigiúil službene ovlasti közhatalom pubblico potere oficiālās pilnvaras viešosios valdžios
avaliku sektori asutus viranomainen autorité publique údaráis phoiblí javne vlasti közhatalmi szervek autorità pubblica publiskas iestāde valdžios institucija
Table VII: List of GDPR Phrases II
kontrollur verwerkings- verantwoordelijke administrator responsável pelo tratamento operator prevádzkovateľ upravljavec personuppgiftsansvarige
uffiċjal tal-protezzjoni tad-data functionaris voor gegevensbescherming inspektor ochrony danych encarregado da proteção de dados responsabil protecția datelor; ofițer protecția datelor zodpovednej osoby pooblaščena oseba za varstvo podatkov dataskyddsombud
gh̄anijiet verwerkingsdoel cel finalidade scop účel namen syften
bażi legali rechtsgrond podstawa prawna fundamento jurídico temei juridic; baza juridică právny základ pravna podlaga rättsliga grunden
ipproċessar verwerking przetwarzanie tratamento prelucrare spracovanie obdelava behandling
interess leġittimu gerechtvaardigde belang uzasadniony interes interesse legítimo interes legitim oprávnené záujmy zakoniti interes berättigade intressen
riċevitur ontvangers odbiorca destinatário destinatar príjemca uporabnik mottagare
pajjiż terz derde land państwo trzecie país terceiro țară terță tretia krajina tretja država tredjeland
perijodu periode okres prazo de conservação perioada doba obdobje period
aċċess toegang dostęp acesso acces prístup dostop tillgång
rettifika rectificatie sprostowanie retificação rectificare oprava popravek rättelse
th̄assir wissen usunięcie apagamento ștergere vymazanie izbris radering
restrizzjoni beperking ograniczenie limitação restricționare obmedzenie omejitev begränsning
oġġezzjoni bezwaar wnoszenie sprzeciwu opor opune právo namietať ugovarjati invända
portabbiltà tad-data gegevens- overdraagbaarheid przenoszenie danych portabilidade dos dados portabilitatea datelor prenosnosť údajov prenosljivost podatkov dataportabilitet
jiġi irtirat il-kunsens toestemming intrekken cofanie zgody retirar consentimento retrage consimțământul súhlas odvolať preklic privolitve återkalla samtycke
ilment klacht skarga reclamação plângere sťažnosť pritožba klagomål
awtorità superviżorja toezichthoudende autoriteit organ nadzorczy autoridade de controlo autoritate de supraveghere dozorný orgán nadzorni organ tillsynsmyndighet
kuntratt overeenkomst umowa contrato contract zmluva pogodba avtal
rekwiżit statutorju wettelijke verplichting wymóg ustawowy obrigação legal obligație legală zákonná požiadavka statutarna obveznost lagstadgat krav
rekwiżit kuntrattwali contractuele verplichting wymóg umowny obrigação contratual obligație contractuală zmluvná požiadavka pogodbena obveznost avtalsenligt krav
konsegwenzi gevolgen konsekwencje consequĕncias consecință následky posledica följder
teh̄id awtomatizzat ta’ deċiżjonijiet geautomatiseerde besluitvorming zautomatyzowane podejmowanie decyzji decisão automatizada process decizional automatizat automatizované rozhodovanie avtomatizirano sprejemanje odločitev automatiserat beslutsfattande
tfassil tal-profil profilering profilowanie definição de perfis crearea de profiluri profilovanie oblikovanje profilov profilering
jipproċessa ulterjorment verdere verwerking dalsze przetwarzanie proceder tratamento porterior prelucrare ulterioară ďalšie spracovanie nadaljnja obdelava ytterligare behandla
kunsens toestemming zgoda consentimento consimțământul súhlas privolitev samtycke
twettiq ta’ kuntratt uitvoering van een overeenkomst wykonanie umowy execução de um contrato executarea unui contract; execut contract plnenie zmluvy izvajanja pogodbe fullgöra ett avtal
obbligu legali wettelijke verplichting obowiązek prawny obrigação jurídica obligație legală zákonná povinnosť zakonska obveznost rättslig förpliktelse
interess vitali vitale belang żywotny interes interesse vital interes vital životne dôležitý záujem življenski interes vitala intresse
interess pubbliku algemeen belang interes publiczny interesse público interes public verejný záujm javni interes allmänt intresse
awtorità uffiċjali openbaar gezag wł adza publiczna autoridade pública autoritate publică; autoritatea oficială verejná moc javna oblast myndighetsutövning
awtorita’ pubblika overheidsinstantie organ publiczny autoridades públicas autoritate publică orgán verejnej moci javni organ offentlig myndighet
Table VIII: List of GDPR Phrases III