Time鈥檚 up for tracking tools 鈥 so don鈥檛 get caught with your hand in the cookie jar, warn Sean O鈥橠onnell and Kelly Mackey
The Data Protection Commission鈥檚 (DPC) six-month grace period for websites and apps to comply with the law governing the use of cookies and similar tracking technologies expired on 6 October 2020.
The deadline was announced in the DPC鈥檚 guidance note, published on 6 April 2020. The guidance sets out measures that data controllers can take to comply with their consent and transparency obligations, and was produced following a 鈥榗ookie sweep鈥 in autumn 2019.
A sample of 38 websites were surveyed in the sweep, representing a range of organisational size and sectors. This included media and publishing, retail, restaurants and food-ordering services, insurance, sport and leisure, and the public sector. Of the 38 organisations surveyed, only two were found to be in substantial compliance.
One-quarter of the websites used pre-ticked boxes for consent to cookies, a practice expressly disavowed by the Court of Justice of the European Union (CJEU) in (C-673/17) in October 2019.
Overall, the DPC identified compliance issues in the majority of those examined, due to cookies being deployed without any engagement with the user, classifying cookies as being exempt from consent requirements where this was not the case, and reliance on implied consent.
In March 2020, the DPC stated in its that its renewed focus on compliance in this area emanates from 鈥渢he pervasive nature and scope of online tracking, and the inextricable links between such cookies and tracking technologies and adtech鈥 (p50).
Cookies are small data files stored on the user鈥檚 device that can identify and track users as they browse the web. They are typically classified according to their purpose (for example, functionality, performance, analytics, social media, etc), duration (for example, expiry at the end of the browsing session, after three months, etc), and origin (that is, first party or third party).
Cookies are one of a number of device-based tracking technologies. Other examples include local storage objects (LSOs), software development kits (SDKs), pixel trackers or pixel gifs, 鈥榣ike鈥 and social-sharing buttons, and device fingerprinting technologies.
These tools can serve as short-term memory aids between pages or visits to enhance the user鈥檚 online experience but, left unchecked, can also be used to build behavioural profiles on users. Many EU supervisory authorities recently scrutinised their use in COVID-19 contact tracing apps.
Two pieces of legislation apply to cookies and similar tracking technologies:
Regulation 5(3) of the ePrivacy Regulations specifies that tracking technologies can only be used where the subscriber or user has:
The GDPR and Data Protection Act also apply where cookies contain identifiers that may be used to target a specific individual, or where information is derived from tracking technologies that may be used to target or profile individuals ( and of the GDPR).
On the interplay between the ePrivacy Directive and the GDPR, the European Data Protection Board (EDPB) has opined they are intended to coexist and are governed by the principle of lex specialis derogate legi generali 鈥 special provisions prevail over general rules.
In practice, this means that the directive and, by extension, the regulations, serve to particularise and to complement the provisions of the GDPR in circumstances where both apply (, pp 13-14.)
The CJEU clarified in Planet49 that the standard for consent under the ePrivacy Directive is that found in the GDPR 鈥 that is, website operators wishing to store cookies on a user鈥檚 device must obtain active, freely given, specific, informed and unambiguous consent, indicated by a statement or clear affirmative action, and such consent must be as easy to withdraw as it was to give (article 4(11) and 7 of the GDPR).
The court further noted that the directive does not distinguish between personal and non-personal data where consent is required and noted its purpose is 鈥渢o protect the user from interference with his or her private sphere, regardless of whether or not that interference involves personal data鈥.
As such, the act of storing or gaining access to information on a user鈥檚 device by a tracking tool requires GDPR-standard consent, regardless of whether the information involved is personal data.
The guidance reinforces the requirement for the GDPR standard of consent and provides practical direction on how to achieve it when implementing cookie banners or consent management platforms.
Consent must be:
There are two exemptions from the requirement to obtain consent and provide clear and comprehensive information under regulation 5(5) of the ePrivacy Regulations. These are known as the 鈥榗ommunications鈥 exemption and the 鈥榮trictly necessary鈥 exemption.
The communications exemption applies to cookies whose sole purpose is for carrying out the transmission of a communication over a network. The 鈥榮trictly necessary鈥 exemption applies to an online service that has been explicitly requested by the user, and the use of the cookie must be restricted to what is strictly necessary to provide that service.
These exemptions are narrowly defined and do not avail many categories of cookies. In its guidance, the DPC clarified that analytics cookies always require consent 鈥 a position that differs from that taken by supervisory authorities in France and Germany. An example of strictly necessary cookies could include those that record a user鈥檚 country or language preference.
In its guidance, the DPC stressed that the duration of any cookie must always be proportionate to its purpose. For instance, a cookie required for remembering information in a user鈥檚 online shopping cart should not have an indefinite expiry date and should be set to expire once it has served its function or shortly afterwards.
In its July 2019 judgment in (C-210/16), the CJEU held that web operators could be joint controllers of any data, such as IP and browser-related data, that constitutes personal data gathered on a website and disclosed to third parties whose plugins, buttons, or trackers are hosted on the website. Operators are advised to assess their relationship with all third parties whose assets are used on their website or app.
Regulation 17(4) of the ePrivacy Regulations provides the DPC with the power to issue enforcement notices. The DPC is empowered to pursue summary prosecution of web operators that fail to comply with an enforcement notice, and a successful prosecution can result in a Class A fine (up to 鈧5,000).
Where compliance with the regulations is the responsibility of a body corporate then, pursuant to regulation 25, an officer of the organisation may also be prosecuted where an offence has been committed with that officer鈥檚 consent or connivance or due to neglect on their part. 鈥極fficer鈥 includes a director, secretary, manager or anyone purporting to act in such capacity, and members where they manage the affairs of the corporate entity.
These powers have not been invoked previously in relation to cookies, but the DPC has used this same power to prosecute offences of unsolicited marketing on ten occasions in 2018 and 2019.
Elsewhere in Europe, there are examples of significant fines being issued for cookie infractions. For example, the Spanish supervisory authority fined the airline Vueling 鈧30,000 in October 2019 for failing to provide users with options to accept, reject or withdraw consent to cookies in a granular way.
Similarly, the Belgian supervisory authority fined a legal news website 鈧15,000 in December 2019 for insufficient provision of information about cookies and failure to obtain consent for certain non-essential cookies.
If an operator uses any cookies that access users鈥 personal data, the DPC also has recourse to its extensive powers under the Data Protection Act 2018 and the GDPR in order to enforce compliance.
These include inspections, audits, investigations, and requiring the suspension of personal data processing under the act, while non-cooperation with the DPC can be met with a fine of up to 2% of global turnover or 鈧10 million under article 31 of the GDPR.
As costly to any website controller is the risk of reputational damage and negative publicity. Controllers that do not comply with enforcement notices from the DPC are likely to find identifying details of their non-compliance published in the DPC鈥檚 annual report.
The law concerning cookies and other tracking technologies is not harmonised across the EU, and reform in that regard has been rumbling along for some years. The much-anticipated EU ePrivacy Regulation has been the subject of intense lobbying, and it is not yet clear when it will be introduced or what its final text will say 鈥 the most recent draft would introduce a 鈥榣egitimate interest鈥 ground for using cookies in addition to the consent ground.
In its guidance, the DPC warns operators from taking guidance from laws not yet agreed or enacted and underscores that, for now, the ePrivacy Regulations remain the touchstone for tracking technologies and cookie compliance in Ireland.