Chapter 12: Impact Assessments, DPOs and Codes of Conduct – Unlocking the EU General Data Protection Regulation

by White & Case LLP
Contact

White & Case LLPWhy does this topic matter to organisations?

A significant aspect of complying with EU data protection law is demonstrating compliance—making it evident to DPAs that an organisation is meeting its obligations. Three of the key ways in which organisations can demonstrate that they are complying with EU data protection laws are:

  • Impact Assessments. Data Protection Impact Assessments ("Impact Assessments") are a tool designed to enable organisations to work out the risks that are inherent in proposed data processing activities before those activities commence. This, in turn, enables organisations to address and mitigate those risks before the processing begins.
  • DPOs. A Data Protection Officer ("DPO") is a person who is formally tasked with ensuring that an organisation is aware of, and complies with, its data protection responsibilities.
  • Codes of Conduct. Organisations within the same industry, or engaging in similar types of processing, are likely to encounter similar data protection issues. Codes of Conduct provide such organisations with useful guidance on industry-standard approaches to these issues. Compliance with a Code of Conduct may provide evidence of compliance with the GDPR.

What types of organisations are most affected?

All organisations that have data protection compliance obligations under the GDPR (whether as controllers or processors) are affected by this issue.

What should organisations do to comply?

Organisations should:

  • Review their existing or planned data processing activities, and consider whether any of them present compliance risks from a data protection perspective. Each current or proposed processing activity that presents such risks should be the subject of an Impact Assessment.
  • Consider whether their core business operations involve: (i) regular and systematic monitoring of data subjects on a large scale; and/or (ii) processing of Sensitive Personal Data on a large scale. Organisations that do either of these things should appoint a DPO.
  • Confer with other organisations that are in the same industry, or are carrying out similar types of processing, to consider whether it might be appropriate to adhere to an existing Code of Conduct, or create a new one.  

Icons to convey information quickly

The following icons are used in the table, to clarify the impact of each change:

Under the GDPR, the position on this issue has materially changed (e.g., the GDPR has introduced a new obligation that did not previously exist).

Under the GDPR, the position on this issue has not materially changed (e.g., although the wording may be different in the GDPR, the nature of the relevant obligation is unchanged).

The impact of the GDPR on this issue is likely positive for most organisations (e.g., because the GDPR provides certainty in relation to a previously unclear issue).

The impact of the GDPR on this issue is likely neutral for most organisations (e.g., because the requirements under the GDPR and the Directive are essentially the same).

The impact of the GDPR on this issue is likely negative for most organisations (e.g., because the GDPR introduced a new obligation on organisations).

The impact of the GDPR on this issue is unknown at this stage (e.g., because the impact on organisations is dependent upon secondary guidance that has not yet been written).

 

Issue The Directive The GDPR Impact

Impact Assessments

In order to assess the potential risks arising out of any new processing activity, EU data protection law requires organisations to conduct an Impact Assessment.

The WP29 has issued Guidelines on Impact Assessments (WP 248) (the "Impact Assessments Guidelines") which provide further clarity on the requirements around Impact Assessments.

Rec. 53

Member States could legislate regarding specific types of processing that were likely to pose high risks. However, the Directive did not expressly require controllers to conduct Impact Assessments.

 Rec.84, 90-94; Art.35; WP29 Impact Assessment Guidelines

Where a new processing activity is proposed (especially where new technologies will be used) resulting in a high degree of risk for data subjects, the controller must first conduct an Impact Assessment. Factors that elevate the level of risk, according to the WP29, include:

  • evaluation of data subjects (e.g., performance at work, health; behaviour; or location);
  • automated decision making with significant effect on a person (e.g., automated refusal of credit);
  • systematic monitoring (especially covert monitoring);
  • processing Sensitive Personal Data;
  • large-scale processing;
  • combining or matching separate datasets;
  • processing affecting vulnerable individuals;
  • processing using untested technology; and
  • Cross-Border Data Transfers.

A single Impact Assessment can cover multiple processing operations that present similar risks. However, the Impact Assessment may need to be an on-going process, depending on the circumstances of the data processing. Any organisation that conducts a DPIA must seek the advice of its DPO (if any).

 The express obligation to conduct Impact Assessments is, in principle, a new burden on controllers. However, even under the Directive, many DPAs expected controllers to conduct Impact Assessments in relation to new, high-risk processing activities.

 By conducting Impact Assessments, controllers may identify and address risks that would otherwise not have been detected. This may help controllers to avoid breaches of the GDPR that might otherwise have occurred.

Prior Consultation

Whenever an organisation is planning to engage in a form of processing that presents particular risks to the rights and freedoms of data subjects, that organisation should consult the relevant DPA(s).

Rec.54; Art.20

Member States were responsible for creating a list of processing operations likely to present specific risks to the rights and freedoms of data subjects. Where a controller intended to engage in a processing activity on such a list, it was first required to consult with the relevant DPA.

 Rec.94-95; Art.35(4)-(6), 36

DPAs are responsible for creating a list of the types of processing that are subject to Impact Assessments. Those lists must be put through the Consistency Mechanism and then sent to the EDPB (see Chapter 15). Where a controller intends to engage in a processing activity on such a list, it must first consult with the relevant DPA.

 The obligation to conduct Impact Assessments imposes a new, and in some cases significant, compliance burden on controllers.

 The requirement to apply the Consistency Mechanism (see Chapter 15) in respect of high risk processing activities should mean that businesses face more consistent enforcement measures from DPAs.

Appointment of a DPO

A DPO is a person who provides the primary contact point for data protection issues within an organisation.

The WP29 has issued Guidelines on Data Protection Officers (WP 243) (the "DPO Guidelines") which provide further clarity on the key terms of Art 37, including "core activities", "large scale" and "regular and systematic monitoring".

N/A

The Directive did not explicitly require organisations to appoint a DPO. In some Member States (e.g., Germany, Sweden) the appointment of a DPO offered certain advantages (e.g., by obviating the need to register with the local DPA). Many organisations in other Member States appointed DPOs simply to ensure that responsibility for data protection compliance was allocated to a specific person, and did not slip through the gaps.

 Rec.97; Art.37; WP29 DPO Guidelines

A controller or processor must appoint a DPO if local laws require it to do so, or if its core data processing activities involve:

  • regular and systematic monitoring of data subjects on a large scale; or
  • processing Sensitive Personal Data on a large scale.

A corporate group may collectively appoint a single DPO.

Organisations that are not required to appoint a DPO are free to do so voluntarily (although the DPO Guidelines note that a voluntary DPO is subject to the same requirements as mandatory DPOs). If a DPO is appointed, the organisation must publish the details of the DPO, and communicate those details to the relevant DPA.

 The obligation to appoint a DPO may impose a significant burden, especially for smaller organisations.

 The DPO Guidelines clarify that a single DPO can be appointed for a corporate group (or several entities within a group) provided that he or she is easily accessible from each business location for which he or she is responsible. Explicit permission to appoint a single DPO for a corporate group is a welcome development for organisations, but it will be important to ensure that such a DPO is provided with sufficient resources to perform the role.

Qualifications of a DPO

A DPO is responsible for data protection compliance. It therefore makes sense for organisations to ensure that their DPOs are suitably qualified for this role.

N/A

The Directive did not specify any minimum qualifications for DPOs.

 Rec.97; Art.37(5)-(6)

A DPO should have expert knowledge of data protection law and practice, and should be capable of performing the functions of a DPO (outlined below). A DPO can be an employee or an outside consultant.

 The DPO Guidelines state that sensitivity, complexity and amount of data processed within an organisation will impact the expertise required for a DPO and a sufficient understanding of operations, as well as information systems, data security and data protection needs of the controller is recommended. For many organisations, it will be challenging to find an existing employee who satisfies the prerequisite requirements of being a DPO. This may mean that such organisations have to engage outside consultants, at potentially significant expense, to fulfil this role.

Role of a DPO

The role of the DPO is to ensure that the relevant organisation achieves data protection compliance.

N/A

The Directive did not set out a specific role for DPOs to fulfil.

 Art.38(1)-(2), (4)-(5)

The DPO must deal with all data protection matters affecting the controller or processor properly and in a timely manner. The controller or processor must provide the DPO with the necessary resources and support. Data subjects may contact the DPO (e.g., to exercise their rights under the GDPR). The DPO must be bound by a confidentiality obligation in relation to his or her work.

 The GDPR formalises requirements not expressly set out in the Directive. However, in most cases this will make little practical difference.

 The DPO Guidelines state that the DPO must be included in all aspects of data processing decisions undertaken within the organisation and that the DPO's opinion on such matters are given weight. If the organisation acts contrary to the DPO's opinion, it should record the reasons for that decision.

Special protection for DPOs

In principle, an organisation should not be able to take disciplinary action against a DPO merely because the DPO makes life harder for the organisation. If an organisation could do so, it would leave the DPO unable to act in a truly independent manner.

N/A

The Directive did not offer DPOs any special protection. However, the laws of several Member States (e.g., Germany) provided that a DPO who is also an employee is protected from almost all disciplinary actions by the employer, making it very difficult to remove the DPO. Consequently, many organisations in these Member States elected to engage an outside consultant as a DPO.

 Art.38(3)

The organisation cannot instruct the DPO in the performance of his or her duties, and cannot terminate the DPO's employment (or take any other disciplinary action) as a result of the performance of the DPO's duties.

 Organisations should consider this issue very carefully, in conjunction with applicable employment laws in the relevant Member States. In practice, some organisations may conclude that it is better to appoint an outside consultant to the role of DPO, as opposed to an employee who will become very difficult to remove from that position. However, the DPO Guidelines state that even external DPOs cannot be "unfairly" removed.

Tasks of a DPO

The DPO's role involves the performance of certain tasks, such as advising the relevant organisation of its data protection compliance obligations.

N/A

The Directive did not specifically oblige DPOs to perform any particular tasks, although the national laws of some Member States allocated particular tasks to DPOs.

 Art.38(6), 39

A DPO must fulfil at least the following tasks:

  • informing and advising the relevant controller or processor (and any employees who process personal data) about their obligations under the GDPR;
  • monitor compliance with the GDPR by the controller or processor;
  • advise on Impact Assessments and prior consultation with DPAs; and
  • cooperate with DPAs and act as a point of contact for DPAs.

 The GDPR obliges organisations to appoint a DPO (where applicable) and requires that DPO to perform certain tasks.

 The fulfilment of those tasks by the DPO should, in theory, mean that the organisation is better able to achieve compliance with the GDPR.

Purpose of Codes of Conduct

Codes of Conduct provide a means for certain industry sectors, or groups of organisations, to create context-specific rules regarding the processing of personal data, in their respective industries, in compliance with EU data protection law.

Rec.26; Art.27

Associations and other industry bodies could prepare Codes of Conduct covering compliance with the Directive in general, as implemented in the laws of the relevant Member States, or specific aspects of those laws.

 Rec.77, 81, 98-99; Art.40(2)

Associations and other industry bodies may prepare Codes of Conduct covering compliance with the GDPR, in respect of general or specific aspects of the GDPR.

 The essential aim of the provisions relating to Codes of Conduct is the same in the Directive and the GDPR. In both cases the creation of Codes of Conduct, to be adhered to by organisations, is encouraged for the purpose of improving overall compliance with EU data protection law.

Encouragement of Codes of Conduct

Creating a Code of Conduct is a laborious undertaking, but one that can help improve compliance. EU data protection law therefore obliges authorities to encourage the creation of Codes of Conduct.

Rec.61; Art.27(1)

The Commission, and Member States, were obliged to encourage the drawing up of Codes of Conduct.

 Rec.98; Art.40(1), 57(1)(m), (p), (o)

Member States, DPAs and the EDPB are all obliged to encourage the drawing up of Codes of Conduct.

 The language in the GDPR makes only minor adjustments to the position as it was set out in the Directive, and these are unlikely to materially affect organisations.

Adherence to Codes of Conduct by non-EEA controllers and processors

One of the core dangers of transferring data out of the EEA is that those data will be subject to lower standards of protection. By adhering to Codes of Conduct, non-EEA controllers and processors can address this risk, and provide a lawful basis for Cross-Border Data Transfers (see Chapter 13).

N/A

The Directive did not specifically provide for non-EEA controllers or processors to sign up to Codes of Conduct.

 Rec.81; Art.40(1)(j), (3), 46(2)(e)

Controllers and processors that are outside the EEA, and that are not subject to the GDPR, may adhere to Codes of Conduct in order to create a framework for providing adequate protection to personal data in third countries. The GDPR specifically allows adherence of non-EEA controllers and processors to an approved Code of Conduct to provide the basis for Cross-Border Data Transfers (see Chapter 13).

 The fact that non-EEA organisations can use adherence to approved Codes of Conduct as a basis for Cross-Border Data Transfers provides a new option for organisations seeking to transfer personal data internationally. It may also make compliance simpler for organisations that frequently exchange data with other organisations in the same industry.

Enforcement of Codes of Conduct

A Code of Conduct only serves a useful purpose to the extent that it is enforceable against entities that sign up to it. The question of who carries out such enforcement, and what powers they have for doing so, is therefore of critical importance to the operation of any Code of Conduct.

Art.27(2)-(3)

DPAs were responsible for reviewing and enforcing Codes of Conduct. Where Codes of Conduct applied in multiple Member States, the WP29 could also have responsibility for reviewing those Codes of Conduct, although enforcement would still have been carried out by DPAs.

 Art.40(4), 41

An independent body may be appointed by the relevant DPA to monitor and enforce a Code of Conduct if it is:

  • independent and has demonstrated its expertise;
  • has established procedures for reviewing and assessing compliance with a Code of Conduct;
  • has established procedures for dealing with complaints or infringements of the Code of Conduct; and
  • can demonstrate that it has no conflicts of interest in this role.

Such a body may be appointed to monitor and enforce compliance with a Code of Conduct. DPAs still retain their own separate enforcement powers.

 An industry body that is already familiar with the processing taking place within that industry may be better placed than a DPA to enforce a Code of Conduct for that industry. That said, such bodies cannot act to the exclusion of DPAs, and it is always open to a DPA to intervene in any such enforcement proceedings.

Advantages of adherence to approved Codes of Conduct

Codes of Conduct clearly need to provide practical advantages for organisations, in order for the effort necessary to create such Codes of Conduct to be worthwhile.

Rec.26, Art.27

Approved Codes of Conduct under the Directive could:

  • provide guidance on specific data protection issues (e.g., anonymisation); and
  • provide evidence of compliance with the requirements of the national laws that implement the Directive.

 Rec.77; Art.24(3), 28(5), 35(8), 46(2)(e), Art.83(2)(j)

Adherence to an approved Code of Conduct:

  • may provide guidance on specific compliance issues;
  • may provide evidence of compliance with the GDPR;
  • is a positive factor in an Impact Assessment;
  • may provide the basis for Cross-Border Data Transfers (see Chapter 13); and
  • may affect any fines imposed upon the adherent controller or processor.

 The increased advantages of adherence to an approved Code of Conduct create significant new reasons for organisations to consider creating and implementing Codes of Conduct.

Approval of Codes of Conduct by DPAs

In order for a Code of Conduct to provide the advantages identified immediately above, that Code of Conduct must first be formally approved by DPAs.

Art.27(2)

DPAs had to ascertain, among other things, whether a Code of Conduct was in accordance with the relevant national law that implemented the Directive. The DPA had the power to seek the views of data subjects on the issue.

 Art.40(5), 57(1)(p), 58(3)(d)

Draft Codes of Conduct must be submitted to the competent DPA, which must then:

  • approve the Code of Conduct if it provides sufficient protections in accordance with the GDPR, or amend it if it does not;
  • register and publish approved Codes of Conduct; and
  • publish the criteria for gaining such approval.

If a Code of Conduct affects processing in several Member States, DPAs must review the Code of Conduct in accordance with the Consistency Mechanism (see Chapter 15) and refer it to the EDPB.

 Because the approval criteria must be published, and DPAs must act uniformly under the Consistency Mechanism (see Chapter 15), the approvals process under the GDPR is likely to be more transparent and objective than the process under the Directive.

Approval of Codes of Conduct by the WP29/EDPB

Where organisations seek to implement a Code of Conduct affecting multiple Member States, approval of the Code of Conduct at an EU-level is generally required.

Art.27(3), 30(d)

A draft Code of Conduct could have been submitted to the WP29, which would then have issued an opinion on whether that Code of Conduct complied with the Directive (although, on a literal interpretation of Art.27(3), a Code of Conduct would have to have complied with the national laws of all 28 Member States that implemented the Directive). The WP29 could have sought the views of data subjects. The Commission could also have publicised any approved Codes of Conduct.

 Art.40(8), 64(1)(b)

The EDPB is required to issue an opinion on any draft Code of Conduct before it is approved. The EDPB must also register and publish approved Codes of Conduct.

 Although the GDPR changes the language, the approval format and process, and the body from which approval must be obtained, the overall outcome results in minimal changes for organisations seeking to implement a Code of Conduct affecting multiple Member States.

Purpose of seals and certifications

The primary purpose of seals and certifications is to provide organisations with a formally recognised confirmation of compliance with EU data protection law, typically with an associated visual symbol (e.g., a badge or emblem that can be displayed on published documents and websites, confirming that the organisation satisfies the requirements of the relevant seal or certification).

N/A

The Directive did not specifically address certification. A number of national DPAs and industry bodies created their own certification schemes.

 Rec.77, 81; Art.42, 43

The GDPR provides for a voluntary system of accreditation, under which controllers or processors may adhere to the requirements of a seal or certification scheme, for the purpose of demonstrating compliance with the GDPR.

 Although seals and certifications gain formal recognition under the GDPR, their essential purpose is unchanged: organisations that want a visual badge or emblem that demonstrates their compliance with all, or any aspect, of EU data protection law can apply to the relevant scheme. If they are successful in their application, they earn the right to display the relevant badge or emblem.

Encouragement of seals and certification

Implementing a seal or certification scheme is a difficult and time-consuming exercise, but one that can help improve compliance. EU data protection law therefore obliges DPAs to encourage the creation of seal or certification schemes.

N/A

This issue was not specifically addressed in the Directive.

 Rec.100; Art.42(1), (8)

Member States, DPAs, the EDPB and the Commission are all obliged to encourage the establishment of certification mechanisms, particularly targeting small and medium enterprises. The EDPB is responsible for maintaining and publishing a register of seal and certification schemes.

 By drawing additional attention to the various seal and certification schemes, Member States, DPAs, the EDPB and the Commission may increase the value of such schemes in the eyes of the public, and also in the eyes of organisations.

Adherence to seal or certification schemes

In order to adhere to a seal or certification scheme, an organisation must provide the DPA or independent body that oversees the relevant scheme with all information and access to its processing activities which are necessary to conduct the seal or certification review procedure.

N/A

This issue was not specifically addressed in the Directive.

 Art.42(4), (6)

An organisation may apply for a certification or seal by providing all necessary information and submitting its relevant processing activities to the DPA or independent body that oversees the relevant scheme. Adherence to a certification or seal does not reduce the obligation of a controller or processor to comply with the GDPR.

 Organisations that wish to obtain a seal or certification are able to select the type of seal or certification for which they wish to apply, and must then agree to provide the relevant DPA or independent body with the necessary information and access to their processing activities.

Enforcement of seal or certification schemes

A seal or certification scheme only has value if it demonstrates compliance with EU data protection law. Therefore, it must be overseen and enforced, in order to ensure that it achieves that aim.

N/A

This issue was not specifically addressed in the Directive.

 Art.42(5), 43(2)

Seal and certification schemes are overseen and enforced, either by the relevant DPA, or an independent body which has an appropriate level of expertise in relation to data protection and has been accredited by the relevant DPA. An independent body may be appointed to this role for a maximum of five years if it is:

  • independent and has demonstrated its expertise;
  • has established procedures for issuing, reviewing and withdrawing seals or certifications;
  • has established procedures for dealing with complaints or infringements of the seals or certifications; and
  • can demonstrate that it has no conflicts of interest in this role.

Such a body may be appointed to monitor compliance with a seal or certification scheme and withdraw the seal or certification if its requirements are no longer met. DPAs still retain their own separate enforcement powers.

 Organisations that wish to obtain a seal or certification are subject to enforcement by the DPA or independent body that oversees the relevant seal or certification scheme.

Expiry of seals or certifications

Seals or certifications have a maximum shelf life, in order to ensure that organisations keep their compliance responsibilities under review.

N/A

This issue was not specifically addressed in the Directive.

 Art.42(7)

Seals and certifications last for a maximum of three years, and may be renewed provided that the relevant conditions are still met. If the conditions are not met, the seal or certification may be withdrawn.

 Seals and certifications last for a relatively brief period of three years, after which a renewal is necessary. Consequently, seal and certification schemes result in an ongoing, burdensome and potentially expensive process.

Commentary: Conducting an Impact Assessment

Some organisations will be familiar with the concept of an Impact Assessment from their experiences under the Directive, but many will not. In essence, an Impact Assessment is a step-by-step review of the relevant processing activity. It is designed to examine each stage of a processing activity, and help an organisation to ensure that it has identified and addressed all of the risks involved in that activity before it commences.

White & Case has extensive experience with guiding organisations through the process of completing an Impact Assessment. We have developed a clear and thoughtful framework for organisations to follow. In the event that a DPA ever asks any questions about the relevant processing activity, our framework allows organisations to look back at a later date, and use the Impact Assessment to illustrate two important facts to the relevant DPA:

  • All of the material risks were identified. An organisation can only comply with the requirements of data protection law if it has identified the material risks that arise in connection with its processing activities.
  • Appropriate steps were taken to address those risks. In relation to each risk, our framework provides a record of the steps that were taken to resolve or mitigate any danger to the rights and freedoms of data subjects, and provides helpful guidance to organisations on achieving compliance.

Any organisation facing questions from DPAs on these issues can rely on this Impact Assessment framework to provide strong support in addressing those questions.

Example: Appointing a DPO

Q. Under the GDPR, Organisation A is required to appoint a DPO. What steps should Organisation A take in planning for that appointment?

A. Organisation A should consider taking the following steps:

  • Organisation A should analyse the extent to which data processing forms part of its day-to-day business operations. The more personal data Organisation A processes, the greater the likelihood that the role of the DPO needs to be a full-time one, rather than a part-time one.
  • Organisation A should also consider whether it wishes to appoint an internal or an external DPO, bearing in mind: (i) that the GDPR specifically protects the DPO from disciplinary action for tasks performed in his or her capacity as the DPO; and (ii) under the employment laws of some Member States, employees who act as DPOs are afforded additional special protections.
  • Organisation A should also ensure that it adjusts its corporate structures to the extent necessary to provide the DPO with sufficient powers and independence to achieve the requirements of the DPO role under the GDPR.

Commentary: Codes of Conduct, seals and certifications

The GDPR encourages the drawing up of Codes of Conduct by associations and other bodies representing categories of organisations, which should take into account the specific features of the various data processing sectors. Adherence to such Codes of Conduct may be used by controllers and processors to demonstrate compliance with the GDPR requirements. Furthermore, the GDPR encourages the implementation of seals and certifications. Organisations that adhere to either an approved Code of Conduct, or an approved seal or certification scheme, may be able to use such adherence as a means of differentiating themselves from their competitors. For example, an organisation that has achieved a seal that is specific to data protection in its industry is often permitted to display that seal publicly, as a means of demonstrating to individuals that it takes their data protection rights seriously. This, in turn, may persuade those individuals to do business with that organisation rather than with its competitors.

[View source.]

Written by:

White & Case LLP
Contact
more
less

White & Case LLP on:

Readers' Choice 2017
Reporters on Deadline

"My best business intelligence, in one easy email…"

Your first step to building a free, personalized, morning email brief covering pertinent authors and topics on JD Supra:
*By using the service, you signify your acceptance of JD Supra's Privacy Policy.
Custom Email Digest
- hide

JD Supra Privacy Policy

Updated: May 25, 2018:

JD Supra is a legal publishing service that connects experts and their content with broader audiences of professionals, journalists and associations.

This Privacy Policy describes how JD Supra, LLC ("JD Supra" or "we," "us," or "our") collects, uses and shares personal data collected from visitors to our website (located at www.jdsupra.com) (our "Website") who view only publicly-available content as well as subscribers to our services (such as our email digests or author tools)(our "Services"). By using our Website and registering for one of our Services, you are agreeing to the terms of this Privacy Policy.

Please note that if you subscribe to one of our Services, you can make choices about how we collect, use and share your information through our Privacy Center under the "My Account" dashboard (available if you are logged into your JD Supra account).

Collection of Information

Registration Information. When you register with JD Supra for our Website and Services, either as an author or as a subscriber, you will be asked to provide identifying information to create your JD Supra account ("Registration Data"), such as your:

  • Email
  • First Name
  • Last Name
  • Company Name
  • Company Industry
  • Title
  • Country

Other Information: We also collect other information you may voluntarily provide. This may include content you provide for publication. We may also receive your communications with others through our Website and Services (such as contacting an author through our Website) or communications directly with us (such as through email, feedback or other forms or social media). If you are a subscribed user, we will also collect your user preferences, such as the types of articles you would like to read.

Information from third parties (such as, from your employer or LinkedIn): We may also receive information about you from third party sources. For example, your employer may provide your information to us, such as in connection with an article submitted by your employer for publication. If you choose to use LinkedIn to subscribe to our Website and Services, we also collect information related to your LinkedIn account and profile.

Your interactions with our Website and Services: As is true of most websites, we gather certain information automatically. This information includes IP addresses, browser type, Internet service provider (ISP), referring/exit pages, operating system, date/time stamp and clickstream data. We use this information to analyze trends, to administer the Website and our Services, to improve the content and performance of our Website and Services, and to track users' movements around the site. We may also link this automatically-collected data to personal information, for example, to inform authors about who has read their articles. Some of this data is collected through information sent by your web browser. We also use cookies and other tracking technologies to collect this information. To learn more about cookies and other tracking technologies that JD Supra may use on our Website and Services please see our "Cookies Guide" page.

How do we use this information?

We use the information and data we collect principally in order to provide our Website and Services. More specifically, we may use your personal information to:

  • Operate our Website and Services and publish content;
  • Distribute content to you in accordance with your preferences as well as to provide other notifications to you (for example, updates about our policies and terms);
  • Measure readership and usage of the Website and Services;
  • Communicate with you regarding your questions and requests;
  • Authenticate users and to provide for the safety and security of our Website and Services;
  • Conduct research and similar activities to improve our Website and Services; and
  • Comply with our legal and regulatory responsibilities and to enforce our rights.

How is your information shared?

  • Content and other public information (such as an author profile) is shared on our Website and Services, including via email digests and social media feeds, and is accessible to the general public.
  • If you choose to use our Website and Services to communicate directly with a company or individual, such communication may be shared accordingly.
  • Readership information is provided to publishing law firms and authors of content to give them insight into their readership and to help them to improve their content.
  • Our Website may offer you the opportunity to share information through our Website, such as through Facebook's "Like" or Twitter's "Tweet" button. We offer this functionality to help generate interest in our Website and content and to permit you to recommend content to your contacts. You should be aware that sharing through such functionality may result in information being collected by the applicable social media network and possibly being made publicly available (for example, through a search engine). Any such information collection would be subject to such third party social media network's privacy policy.
  • Your information may also be shared to parties who support our business, such as professional advisors as well as web-hosting providers, analytics providers and other information technology providers.
  • Any court, governmental authority, law enforcement agency or other third party where we believe disclosure is necessary to comply with a legal or regulatory obligation, or otherwise to protect our rights, the rights of any third party or individuals' personal safety, or to detect, prevent, or otherwise address fraud, security or safety issues.
  • To our affiliated entities and in connection with the sale, assignment or other transfer of our company or our business.

How We Protect Your Information

JD Supra takes reasonable and appropriate precautions to insure that user information is protected from loss, misuse and unauthorized access, disclosure, alteration and destruction. We restrict access to user information to those individuals who reasonably need access to perform their job functions, such as our third party email service, customer service personnel and technical staff. You should keep in mind that no Internet transmission is ever 100% secure or error-free. Where you use log-in credentials (usernames, passwords) on our Website, please remember that it is your responsibility to safeguard them. If you believe that your log-in credentials have been compromised, please contact us at privacy@jdsupra.com.

Children's Information

Our Website and Services are not directed at children under the age of 16 and we do not knowingly collect personal information from children under the age of 16 through our Website and/or Services. If you have reason to believe that a child under the age of 16 has provided personal information to us, please contact us, and we will endeavor to delete that information from our databases.

Links to Other Websites

Our Website and Services may contain links to other websites. The operators of such other websites may collect information about you, including through cookies or other technologies. If you are using our Website or Services and click a link to another site, you will leave our Website and this Policy will not apply to your use of and activity on those other sites. We encourage you to read the legal notices posted on those sites, including their privacy policies. We are not responsible for the data collection and use practices of such other sites. This Policy applies solely to the information collected in connection with your use of our Website and Services and does not apply to any practices conducted offline or in connection with any other websites.

Information for EU and Swiss Residents

JD Supra's principal place of business is in the United States. By subscribing to our website, you expressly consent to your information being processed in the United States.

  • Our Legal Basis for Processing: Generally, we rely on our legitimate interests in order to process your personal information. For example, we rely on this legal ground if we use your personal information to manage your Registration Data and administer our relationship with you; to deliver our Website and Services; understand and improve our Website and Services; report reader analytics to our authors; to personalize your experience on our Website and Services; and where necessary to protect or defend our or another's rights or property, or to detect, prevent, or otherwise address fraud, security, safety or privacy issues. Please see Article 6(1)(f) of the E.U. General Data Protection Regulation ("GDPR") In addition, there may be other situations where other grounds for processing may exist, such as where processing is a result of legal requirements (GDPR Article 6(1)(c)) or for reasons of public interest (GDPR Article 6(1)(e)). Please see the "Your Rights" section of this Privacy Policy immediately below for more information about how you may request that we limit or refrain from processing your personal information.
  • Your Rights
    • Right of Access/Portability: You can ask to review details about the information we hold about you and how that information has been used and disclosed. Note that we may request to verify your identification before fulfilling your request. You can also request that your personal information is provided to you in a commonly used electronic format so that you can share it with other organizations.
    • Right to Correct Information: You may ask that we make corrections to any information we hold, if you believe such correction to be necessary.
    • Right to Restrict Our Processing or Erasure of Information: You also have the right in certain circumstances to ask us to restrict processing of your personal information or to erase your personal information. Where you have consented to our use of your personal information, you can withdraw your consent at any time.

You can make a request to exercise any of these rights by emailing us at privacy@jdsupra.com or by writing to us at:

Privacy Officer
JD Supra, LLC
10 Liberty Ship Way, Suite 300
Sausalito, California 94965

You can also manage your profile and subscriptions through our Privacy Center under the "My Account" dashboard.

We will make all practical efforts to respect your wishes. There may be times, however, where we are not able to fulfill your request, for example, if applicable law prohibits our compliance. Please note that JD Supra does not use "automatic decision making" or "profiling" as those terms are defined in the GDPR.

  • Timeframe for retaining your personal information: We will retain your personal information in a form that identifies you only for as long as it serves the purpose(s) for which it was initially collected as stated in this Privacy Policy, or subsequently authorized. We may continue processing your personal information for longer periods, but only for the time and to the extent such processing reasonably serves the purposes of archiving in the public interest, journalism, literature and art, scientific or historical research and statistical analysis, and subject to the protection of this Privacy Policy. For example, if you are an author, your personal information may continue to be published in connection with your article indefinitely. When we have no ongoing legitimate business need to process your personal information, we will either delete or anonymize it, or, if this is not possible (for example, because your personal information has been stored in backup archives), then we will securely store your personal information and isolate it from any further processing until deletion is possible.
  • Onward Transfer to Third Parties: As noted in the "How We Share Your Data" Section above, JD Supra may share your information with third parties. When JD Supra discloses your personal information to third parties, we have ensured that such third parties have either certified under the EU-U.S. or Swiss Privacy Shield Framework and will process all personal data received from EU member states/Switzerland in reliance on the applicable Privacy Shield Framework or that they have been subjected to strict contractual provisions in their contract with us to guarantee an adequate level of data protection for your data.

California Privacy Rights

Pursuant to Section 1798.83 of the California Civil Code, our customers who are California residents have the right to request certain information regarding our disclosure of personal information to third parties for their direct marketing purposes.

You can make a request for this information by emailing us at privacy@jdsupra.com or by writing to us at:

Privacy Officer
JD Supra, LLC
10 Liberty Ship Way, Suite 300
Sausalito, California 94965

Some browsers have incorporated a Do Not Track (DNT) feature. These features, when turned on, send a signal that you prefer that the website you are visiting not collect and use data regarding your online searching and browsing activities. As there is not yet a common understanding on how to interpret the DNT signal, we currently do not respond to DNT signals on our site.

Access/Correct/Update/Delete Personal Information

For non-EU/Swiss residents, if you would like to know what personal information we have about you, you can send an e-mail to privacy@jdsupra.com. We will be in contact with you (by mail or otherwise) to verify your identity and provide you the information you request. We will respond within 30 days to your request for access to your personal information. In some cases, we may not be able to remove your personal information, in which case we will let you know if we are unable to do so and why. If you would like to correct or update your personal information, you can manage your profile and subscriptions through our Privacy Center under the "My Account" dashboard. If you would like to delete your account or remove your information from our Website and Services, send an e-mail to privacy@jdsupra.com.

Changes in Our Privacy Policy

We reserve the right to change this Privacy Policy at any time. Please refer to the date at the top of this page to determine when this Policy was last revised. Any changes to our Privacy Policy will become effective upon posting of the revised policy on the Website. By continuing to use our Website and Services following such changes, you will be deemed to have agreed to such changes.

Contacting JD Supra

If you have any questions about this Privacy Policy, the practices of this site, your dealings with our Website or Services, or if you would like to change any of the information you have provided to us, please contact us at: privacy@jdsupra.com.

JD Supra Cookie Guide

As with many websites, JD Supra's website (located at www.jdsupra.com) (our "Website") and our services (such as our email article digests)(our "Services") use a standard technology called a "cookie" and other similar technologies (such as, pixels and web beacons), which are small data files that are transferred to your computer when you use our Website and Services. These technologies automatically identify your browser whenever you interact with our Website and Services.

How We Use Cookies and Other Tracking Technologies

We use cookies and other tracking technologies to:

  1. Improve the user experience on our Website and Services;
  2. Store the authorization token that users receive when they login to the private areas of our Website. This token is specific to a user's login session and requires a valid username and password to obtain. It is required to access the user's profile information, subscriptions, and analytics;
  3. Track anonymous site usage; and
  4. Permit connectivity with social media networks to permit content sharing.

There are different types of cookies and other technologies used our Website, notably:

  • "Session cookies" - These cookies only last as long as your online session, and disappear from your computer or device when you close your browser (like Internet Explorer, Google Chrome or Safari).
  • "Persistent cookies" - These cookies stay on your computer or device after your browser has been closed and last for a time specified in the cookie. We use persistent cookies when we need to know who you are for more than one browsing session. For example, we use them to remember your preferences for the next time you visit.
  • "Web Beacons/Pixels" - Some of our web pages and emails may also contain small electronic images known as web beacons, clear GIFs or single-pixel GIFs. These images are placed on a web page or email and typically work in conjunction with cookies to collect data. We use these images to identify our users and user behavior, such as counting the number of users who have visited a web page or acted upon one of our email digests.

JD Supra Cookies. We place our own cookies on your computer to track certain information about you while you are using our Website and Services. For example, we place a session cookie on your computer each time you visit our Website. We use these cookies to allow you to log-in to your subscriber account. In addition, through these cookies we are able to collect information about how you use the Website, including what browser you may be using, your IP address, and the URL address you came from upon visiting our Website and the URL you next visit (even if those URLs are not on our Website). We also utilize email web beacons to monitor whether our emails are being delivered and read. We also use these tools to help deliver reader analytics to our authors to give them insight into their readership and help them to improve their content, so that it is most useful for our users.

Analytics/Performance Cookies. JD Supra also uses the following analytic tools to help us analyze the performance of our Website and Services as well as how visitors use our Website and Services:

  • HubSpot - For more information about HubSpot cookies, please visit legal.hubspot.com/privacy-policy.
  • New Relic - For more information on New Relic cookies, please visit www.newrelic.com/privacy.
  • Google Analytics - For more information on Google Analytics cookies, visit www.google.com/policies. To opt-out of being tracked by Google Analytics across all websites visit http://tools.google.com/dlpage/gaoptout. This will allow you to download and install a Google Analytics cookie-free web browser.

Facebook, Twitter and other Social Network Cookies. Our content pages allow you to share content appearing on our Website and Services to your social media accounts through the "Like," "Tweet," or similar buttons displayed on such pages. To accomplish this Service, we embed code that such third party social networks provide and that we do not control. These buttons know that you are logged in to your social network account and therefore such social networks could also know that you are viewing the JD Supra Website.

Controlling and Deleting Cookies

If you would like to change how a browser uses cookies, including blocking or deleting cookies from the JD Supra Website and Services you can do so by changing the settings in your web browser. To control cookies, most browsers allow you to either accept or reject all cookies, only accept certain types of cookies, or prompt you every time a site wishes to save a cookie. It's also easy to delete cookies that are already saved on your device by a browser.

The processes for controlling and deleting cookies vary depending on which browser you use. To find out how to do so with a particular browser, you can use your browser's "Help" function or alternatively, you can visit http://www.aboutcookies.org which explains, step-by-step, how to control and delete cookies in most browsers.

Updates to This Policy

We may update this cookie policy and our Privacy Policy from time-to-time, particularly as technology changes. You can always check this page for the latest version. We may also notify you of changes to our privacy policy by email.

Contacting JD Supra

If you have any questions about how we use cookies and other tracking technologies, please contact us at: privacy@jdsupra.com.

- hide

This website uses cookies to improve user experience, track anonymous site usage, store authorization tokens and permit sharing on social media networks. By continuing to browse this website you accept the use of cookies. Click here to read more about how we use cookies.