Unlocking the EU General Data Protection Regulation: A practical handbook on the EU's new data protection law: Chapter 11: Obligations of processors

White & Case LLP
Contact

Overview

Why does this topic matter to organisations?

Under the GDPR, the concept of a "processor" does not change. Any entity that is a processor under the Directive likely continues to be a processor under the GDPR. However, whereas the Directive generally only imposes direct compliance obligations on controllers, the GDPR imposes direct compliance obligations on both controllers and processors, and both controllers and processors will face direct enforcement and serious penalties if they do not comply with the new EU data protection law. Therefore, it is important that processors understand their obligations under EU data protection law.

What types of organisations are most affected?

The direct legal obligations imposed on processors under the GDPR are of obvious importance to organisations that act as processors. However, they are also important to organisations that act as controllers, and engage processors to process personal data on their behalf.

Under the GDPR, processors (e.g., many outsourced service providers) are likely to face significantly higher costs as a direct result of the increased compliance obligations, and those costs are likely to be passed on to customers. Furthermore, the negotiation of processing agreements is likely to become more complex, as processors become more careful about the terms of the agreement and the scope of the controller's instructions.

What should organisations do to prepare?

Organisations that act as processors, or act as controllers that engage processors, should carefully review the requirements associated with appointing processors. In particular, they should review their existing data processing agreements and consider whether any amendments are required. Any new data processing agreements should be drafted in accordance with the requirements of the GDPR. In addition, each organisation that acts as a processor should:

  • identify the data processing activities for which it is a processor;
  • ensure that it understands its responsibilities as a processor under the GDPR; and
  • ensure that it has appropriate processes and templates in place for identifying, reviewing and (to the extent required) promptly reporting data breaches to the relevant controller.

Icons are used below to clarify the impact of each GDPR change. These GDPR impact icons are explained here.    

Detailed analysis

Issue

The Directive

The GDPR

Impact

blank

Definition of "processor"

In general terms, a "processor" is any entity or individual (other than an employee of a controller) that processes personal data on the controller's behalf.

blank

Art.2(e)

In summary, a "processor" is an entity that processes personal data on behalf of the controller. A full definition is set out in Chapter 5.

does not materially change

Art.4(8)

In summary, a "processor" is an entity that processes personal data on behalf of the controller. A full definition is set out in Chapter 5.

neutral

The concept of a "processor" is essentially unchanged under the GDPR. Any entity that is a processor under the Directive likely continues to be a processor under the GDPR.

blank

Appointment of processors

Organisations that act as controllers commonly appoint service providers to process personal data on their behalf. EU data protection law permits this practice, but imposes certain requirements on organisations that wish to do so.

blank

Art.17(2)-(3)

A controller that wishes to appoint a processor must only use processors that guarantee compliance with national data protection laws which are based on the Directive. The controller must appoint the processor under a binding written agreement, which states that the processor:

  • shall only act on the controller's instructions; and
  • must ensure the security of the personal data that it processes.

materially changes

Rec.81; Art.28(1)-(3)

A controller that wishes to appoint a processor must only use processors that guarantee compliance with the GDPR. The controller must appoint the processor in the form of a binding written agreement, which states that the processor must:

  • only act on the controller's documented instructions;
  • impose confidentiality obligations on all personnel who process the relevant data;
  • must ensure the security of the personal data that it processes;
  • abide by the rules regarding appointment of sub-processors;
  • implement measures to assist the controller in complying with the rights of data subjects;
  • assist the controller in obtaining approval from DPAs where required;
  • at the controller's election, either return or destroy the personal data at the end of the relationship (except as required by EU or Member State law); and
  • provide the controller with all information necessary to demonstrate compliance with the GDPR.

negative

The GDPR imposes significant new requirements that must be included in all data processing agreements. As the GDPR does not contain transitional arrangements addressing this issue, existing agreements are affected as well and may need to be renegotiated. It is likely that processors located outside the EEA will resist the imposition of these new obligations, potentially making it harder for organisations acting as controllers to lawfully appoint their desired processors, and resulting in more complex negotiations of outsourcing agreements.

blank

Application

EU data protection law applies across all sectors to all organisations that are subject to the law. Whereas the Directive generally only imposes direct legal compliance obligations on controllers, the GDPR imposes direct legal compliance obligations on processors as well.

blank

Art.4(1)

Each Member State is required to implement national data protection laws that impose direct legal compliance obligations on controllers that fall within the scope of the Directive (as implemented in the national law of the relevant Member State).

materially changes

Rec.22; Art.3(1)

The GDPR applies to the processing of personal data by a controller or a processor that falls within the scope of the GDPR (regardless of whether the relevant processing takes place in the EU or not).

negative

The Directive only imposes direct compliance obligations on controllers (with processors generally only having contractual obligations, not direct legal compliance obligations). The GDPR, however, imposes legal compliance obligations directly on controllers and processors.

blank

Conflicts between the controller's instructions and applicable (EU) law

The defining feature of a processor is that a processor acts in accordance with the controller's instructions. However, a processor might face conflicting requirements between the controller's instructions and applicable law, which leads to obvious difficulties.

blank

N/A

The Directive does not specifically address scenarios in which a processor cannot comply with the controller's instructions for legal reasons.

materially changes

Art.28(3)(h)

In the event that a processor believes that the controller's instructions conflict with the requirements of the GDPR or other EU or Member State laws, the processor must immediately inform the controller.

positive

The GDPR provides a sensible solution, requiring the processor to inform the controller that it cannot comply with the controller's instructions where those instructions conflict with applicable (EU) law. It is then for the controller to issue revised instructions that are consistent with applicable law.

 

unknown at this stage

The GDPR provides no clear guidance on what should happen if the controller's instructions place the processor in breach of the national laws of a jurisdiction outside the EU. Presumably, this will be an issue for negotiation between the parties.

blank

Appointment of sub‑processors

Processors may only appoint sub-processors with the permission of the controller.

blank

Art.16

Sub-processors must only process personal data in accordance with the instructions of the controller or the requirements of applicable law. However, the Directive does not provide clear rules for the appointment of sub‑processors.

materially changes

Art.28(2), (4)

The processor must not appoint a sub-processor without the prior written consent of the controller. Where the controller agrees to the appointment of sub-processors, those sub‑processors must be appointed on the same terms as are set out in the contract between the controller and the processor, and in any case in accordance with Art.28(1)‑(2) (see above).

neutral

Although the Directive does not directly address this issue, DPAs have generally interpreted the Directive as requiring sub-processors to be appointed on the same terms that apply to the processor, and subject to the controller's approval. Consequently, the new language in the GDPR is unlikely to make very much practical difference.

blank

Processor's obligation of confidentiality

Processors must ensure that the personal data that they process are kept confidential.

blank

Art.16

Processors must keep personal data confidential except on instructions from the controller, unless the processor is required by law to process those data.

materially changes

Art.28(3)(b), 29

The processor must ensure that any personal data that it processes are kept confidential. The contract between the controller and the processor must require the processor to ensure that all persons authorised to process the personal data are under an appropriate obligation of confidentiality.

neutral

Art.29 of the GDPR follows the provisions of Art.16 of the Directive. Despite the new requirements regarding contractual protections, there is little practical change for either controllers or processors in this context.

blank

Compliance with the controller's instructions

The relationship between the controller and processor is based on the principle that the processor will only process data in accordance with the controller's instructions.

blank

Art.16

Processors must not process personal data, except in accordance with the instructions of the controller or the requirements of applicable law.

does not materially change

Art.29

Processors (and any subprocessors) shall not process personal data, except in accordance with the instructions of the controller, or the requirements of EU law or the national laws of Member States.

neutral

The GDPR essentially preserves the position set out in the Directive.

blank

Failure to comply with the controller's instructions

It is foreseeable that a processor might depart from the controller's instructions and begin making decisions regarding the purposes for which and means by which personal data are processed.

blank

N/A

The Directive does not specifically address the question of what happens when a processor departs from the controller's instructions.

materially changes

Art.28(10)

Where a processor, in breach of the GDPR, determines the purposes and means of any processing activity (i.e., if the processor makes its own decisions, rather than following the controller's instructions), that processor is treated as a controller in respect of that processing activity.

negative

Organisations acting as processors should be extremely cautious of this provision. In essence, any time that such an organisation processes personal data for its own purposes, rather than the purposes of the controller, that organisation becomes a controller, and is subject to the full compliance obligations of a controller in relation to that processing.

blank

Records of processing activities

In order to ensure compliance, EU data protection law requires processors to ensure that they keep records of their data processing activities, and that the information in those records is provided to (or is available on request by) DPAs.

blank

N/A

The Directive does not specifically require processors to maintain records of any kind. In almost all Member States (other than the Republic of Ireland) there is no obligation on processors to register with the DPA.

materially changes

Rec.82; Art.30(2)

Each processor (and its representative, if any) must keep records of its processing activities performed on behalf of the controller, including:

  • the details of the controller/processor and any representatives/DPO;
  • the categories of processing activities performed;
  • information regarding Cross-Border Data Transfers; and
  • a general description of the security measures implemented in respect of the processed data.

negative

Organisations acting as processors (or their representatives) are subject to this new obligation of maintaining records of processing activities in order to provide, upon request, the recorded information to the DPA. This is likely to require significant investment by processors in record-keeping functions.

blank

Cooperation with DPAs

DPAs are responsible for implementing and regulating EU data protection law.

blank

N/A

The Directive does not require processors to cooperate with DPAs. Instead, the national laws of Member States require controllers to cooperate with DPAs, and the Directive requires processors to act on the instructions of those controllers (see above).

materially changes

Art.31

Processors (and their representatives, if any) are required to cooperate, on request, with DPAs in the performance of their tasks.

negative

The GDPR fundamentally changes the obligations of processors in this regard. Whereas, processors typically have no direct interaction with DPAs under the Directive, they are obliged to interact with and assist DPAs under the GDPR.

blank

Data security

EU data protection law obliges processors to ensure the security of personal data that they process.

blank

N/A

The Directive requires controllers to implement contracts that oblige processors to ensure the security of any personal data they process. However, the Directive does not impose any data security obligations directly on processors.

materially changes

Art.28(1), (3)(e), (4), 32

Processors must implement appropriate technical and organisational security measures to protect personal data against accidental or unlawful destruction or loss, alteration, unauthorised disclosure or access. Depending on the nature of the processing, these may include:

  • encryption of the personal data;
  • on-going reviews of security measures;
  • redundancy and back-up facilities; and
  • regular security testing.

Adherence to an approved Code of Conduct (see Chapter 12) may provide evidence that the processor has met these obligations.

negative

The Directive requires controllers to contractually impose data security requirements on processors. However, the GDPR imposes these requirements directly upon processors, and exposes processors to fines, penalties and compensation claims for failure to satisfy those requirements. Consequently, the level of risk faced by processors under the GDPR is significantly elevated.

blank

Data breach reporting

One of the key issues in maintaining the security of personal data is ensuring that the relevant decision-makers are aware of any data breaches and are able to react accordingly.

blank

N/A

The Directive is silent on the issue of data breach reporting by processors.

materially changes

Art.33(2)

Processors must notify any data breach to the controller without undue delay.

negative

For processors, this obligation creates an additional burden.

 

positive

For controllers, this obligation provides an extra layer of assurance that data breaches will be properly reported.

blank

Obligation to appoint a DPO

In certain circumstances, EU data protection law requires a person to be formally appointed to the role of DPO, in order to oversee an organisation's data protection compliance (see Chapter 12).

blank

N/A

The Directive does not require processors to appoint DPOs.

materially changes

Art.37

To the extent that the GDPR requires the appointment of a DPO (see Chapter 12), that requirement applies to processors.

negative

Some organisations that act as processors are likely to consider this to be a burdensome requirement and an expense.

 

positive

Over the long-term, the appointment of a DPO may help to reduce the risk of non‑compliance with the GDPR.

blank

Restrictions on Cross-Border Data Transfers

EU data protection law restricts Cross-Border Data Transfers unless the transfer is to an Adequate Jurisdiction, a lawful transfer mechanism exists, or an exemption or derogation applies (see Chapter 13).

blank

N/A

The Directive does not directly address the issue of Cross-Border Data Transfers performed by processors (on the basis that the controller bears responsibility for the processor's actions, the processor can only act on the controller's instructions, and the controller is subject to the relevant restrictions).

materially changes

Art.44

Under the GDPR, the obligations regarding Cross‑Border Data Transfers (see Chapter 13) apply directly to processors.

negative

In theory, processors should already be complying with the rules regarding Cross-Border Data Transfers (on the basis of the instructions issues by the relevant controller). However, in practice, the possibility of direct statutory liability for processors (as well as contractual liability of processors to controllers) creates a new category of risk for processors that engage in such transfers.

blank

Liability of processors

EU data protection law recognises the possibility that processors may be liable for breaches of their legal or contractual obligations.

blank

N/A

Where a processor breaches a contract with the controller, it may have contractual liability to the controller. However, processors have no direct liability under the Directive, and data subjects cannot bring claims directly against processors.

materially changes

Rec.146; Art.82(1)-(2)

Data subjects can bring claims directly against processors. However, a processor is liable for the damage caused by its processing activities only where it has:

  • not complied with obligations under the GDPR that are specifically directed to processors; or
  • acted outside or contrary to lawful instructions of the controller.

negative

For processors, the possibility of direct liability is a new risk to grapple with.

 

positive

For controllers, the fact that processors may be directly liable for their own breaches may mean that a controller (if it is not also in breach of the GDPR) may, in some cases, avoid liability for breaches committed by its processors (provided that the controller is not at fault).

Further analysis

Commentary: Processors and the law

Under the Directive, a processor's obligations and liabilities are governed almost exclusively by the processor's contract with the controller. The Directive only permits claims by data subjects to be brought against processors in very limited circumstances.

The GDPR introduces a paradigm shift in the relationship between processors and EU data protection law. In particular, processors are subject to fines and penalties for breaches of the GDPR, which can be up to the greater of €20 million or four percent of annual worldwide turnover (see Chapter 16). In addition, data subjects may bring claims for compensation directly against processors. As a result, many organisations that act as processors will need to completely re-think their approach to data protection compliance.

Example: Data processing agreements

Q. Organisation A is a controller. It wishes to appoint a processor, Service Provider B, to process personal data on its behalf. Organisation A already has a standard data processing agreement that addresses the requirements under the Directive. How does Organisation A's standard processing agreement need to change in order to satisfy the requirements of the GDPR?

A. Many existing "pro-controller" processing agreements already contain some (or all) of the requirements specified in Art.28(3) of the GDPR. Organisation A will need to:

  • review its standard data processing agreement and determine whether that agreement addresses all of the requirements specified in Art.28(3) of the GDPR; and
  • to the extent that the standard data processing agreement does not address all of those requirements, it will need to be amended.

Example: Changes to the controller's instructions

Q. Organisation X is a controller. It wishes to appoint a processor, Service Provider Y, to process personal data on its behalf. The data processing agreement states (in accordance with the GDPR) that Service Provider Y must process the relevant personal data in accordance with Organisation X's instructions. Service Provider Y objects to this language, on the grounds that Organisation X may change its instructions in a way that, while compliant with the law, costs Service Provider Y more money to implement. How should the parties address this issue?

A. This issue is a common point of disagreement between controllers and processors. In most cases, it can be addressed by including in the agreement provisions along the following lines:

  • Service Provider Y shall only process the relevant personal data in accordance with Organisation X's instructions;
  • to the extent that Service Provider Y cannot comply with a change to Organisation X's instructions without incurring material additional costs, Service Provider Y shall: (i) immediately inform Organisation X, giving full details of the problem; and (ii) cease all processing of the affected data (other than securely storing those data) until revised instructions are received; and
  • any changes in Organisation X's instructions that affect the pricing structure or commercial relationship between the parties should go through an appropriate change control procedure.

DISCLAIMER: Because of the generality of this update, the information provided herein may not be applicable in all situations and should not be acted upon without specific legal advice based on particular situations.

© White & Case LLP | Attorney Advertising

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.