The Privacy Oracle: April 2019

Davis Wright Tremaine LLP


The Privacy Oracle consolidates significant US legislative and regulatory developments at the state and federal level into a single publication. In this month’s issue, we offer:

    • An analysis of bills introduced in the 116th Congress that seek to regulate consumer privacy
    • A review of amendments to the CCPA that have recently advanced out of committee in the California legislature
    • Insight into the failure of the Washington Privacy Act and an update on amendments to Washington’s Data Breach Notification Law
    • A high-level round-up of draft state consumer privacy legislations
    • An overview of litigation risk associated with the private right of action for data breach in the CCPA
    • Practical tips on updating contracts to designate external parties as service providers under the CCPA

Federal Privacy Legislation Introduced, but Future Unclear

In the wake of calls for Congress to regulate consumer privacy and prevent a “patchwork” of state legislation, six bills have been introduced that would set forth broad federal obligations regarding the collection, storage, and disclosure of consumer data.[1] Despite bipartisan support for comprehensive privacy legislation, none of the federal consumer privacy bills listed below has progressed since introduction. And more bills may be added to the mix. Sen. Marsha Blackburn (R-TN) reintroduced the BROWSER Act (H.R. 2520 from the 115th Congress), and the Senate Committee on Commerce, Science and Transportation mentioned they are working on proposed legislation of their own, though details and timing are still unknown.

Disagreement over federal preemption of state law may be one factor delaying advancement of any bill. House Speaker Nancy Pelosi (D-CA) recently drew a line in the sand on this issue during a Recode Decode Podcast on April 12, saying “the Republicans would want preemption of state law. Well, that’s just not going to happen. We in California are not going to say, ‘You pass a law that weakens what we did in California.’ That won’t happen.” Sen. Feinstein (D-CA) also made it clear that she would not support a federal bill that weakens California’s Consumer Privacy Act. Sen. Klobuchar (D-MN) said there were “a lot of tears shed about the patchwork of bills across the country” in a Senate Judiciary hearing, yet there is no federal preemption in her co-sponsored bill with Sen. Kennedy (R-LA). Sen. Blumenthal (D-CT) noted that draft proposals sent to the Judiciary Committee often undercut existing state protections by using preemption. On the other hand, Sen. Blackburn and Sen. Tillis (R-NC) voiced support for preemptive privacy legislation.

Federal consumer privacy bills introduced to date in the 116th Congress:

Bill Information Title Description
Introduced Apr. 11
Sen. Markey (D-MA)
Privacy Bill of Rights Would grant consumers rights similar to those under CCPA and require businesses to obtain “opt-in approval” prior to the collection or sale of data, as well as any material changes in practices; contains a private right of action in addition to FTC and state AG enforcement.
H.R. 2013
Introduced Apr. 1
Rep. DelBene (D-WA)
Information Transparency & Personal Data Control Act A revised bill from the 115th Congress. Changes made to some terms and requirements to include options for cross-platform portability, thresholds for audit requirements, and FTC enforcement. The bill also proposes to require the FTC to hire 50 new full-time employees and provides $35M in funding for data privacy and security.
S. 806
Introduced Mar. 14
Sen. Kennedy (R-LA)
Own Your Own
Data Act
Would prohibit the collection of data or information generated on the internet. A short bill that would require social media companies to create a button for users to obtain or export a copy of their data. Data would be provided to the user with any analysis performed by the company on the data. Would also require annual clean, plain language licensing agreements with the user.
Introduced Feb. 27
Sen. Cortez Masto (D-NV)
Digital Accountability and Transparency to Advance (DATA) Privacy Act Would require companies to obtain opt-in consent from individuals to collect their genetic information and to disclose such sensitive data outside of their relationship with the consumer.
Introduced Jan. 17
Sen. Klobuchar (D-MN)
Sen. Kennedy (R-LA)
Social Media Privacy and Consumer
Rights Act
Would protect data privacy of consumers on social media and online platforms. Would require online platforms to provide consumers with greater transparency and control over their data. It would also require notification of an unauthorized disclosure of personal information within 72 hours. This notification requirement would cover disclosure of a broad array of personal information, including email address and location information, and not just sensitive data. In the event of a breach, the consumer would have rights to object to processing by the platform and demand deletion of data. The law would also require online platforms to have a privacy program in place.
Introduced Jan. 16
Sen. Rubio (R-FL)
American Data Dissemination Act (ADD Act) Uses the Privacy Act of 1974 as a framework and would require the FTC to submit recommendations for privacy requirements that Congress can impose on covered providers. It would provide consumers with rights to access, correction, and deletion rights as defined by the FTC. Its sole purpose seems to be pre-emption of state privacy laws and is scant on details.

[1] There are three more narrowly constructed, consumer-related bills:

  • Blunt (R-MO) and Sen. Schatz (D-HI) introduced S. 847, Commercial Racial Recognition Privacy Act of 2019, on March 14. It would prohibit certain entities from using facial recognition technology to identify or track an end user without obtaining the affirmative consent of the end user. It would also require third party testing of technologies prior to implementation and meeting data security, minimization, and retention standards as determined by the FTC and NIST.
  • Richard Durbin (D-IL) introduced S. 783, Clean Slate for Kids Online Act of 2019, on March 13. It would allow for deletion of PI collected by internet operators of activity prior to age 13.
  • Edward Markey (D-MA) and Sen. Josh Hawley (R-MO) introduced S.748 on March 12. It would amend the Children’s Online Privacy Protection Act of 1998 (COPPA) to strengthen protections relating to the online collection, use, and disclosure of personal information of children and minors.

A Barrage of CCPA Amendments: Can Any Go the Distance?

After months of sparring among politicians, businesses, and privacy advocates, both the California Assembly and Senate have advanced a variety of proposed amendments to the state’s first-in-kind comprehensive privacy statute, the California Consumer Privacy Act or CCPA. But the clearest thing to emerge from this rush to “clarify” CCPA is the multitude of concerns that the statute has raised on each side of the debate.

The majority of bills approved by the Privacy and Consumer Protection Committee of the Assembly (“the Committee”) appear aimed at narrowing the amount and types of data that are subject to CCPA restrictions. For example, California businesses long have asserted that the CCPA should not apply to data collected by employers about their employees and job applicants. AB 25 would amend the CCPA to eliminate the statute’s potential application to data collected in the employment context.  Similarly, two amendments advanced by the Committee (AB 874 and AB 1355) would exclude deidentified or aggregated data from the definition of “personal information.” Another (AB 873) would narrow the definition of personal information further by eliminating the statute’s application to information that identifies only a household, rather than an individual. AB 1146 would exempt vehicle information shared between a motor vehicle dealer and a manufacturer.

One amendment that advanced in the Senate earlier this month would result in a significant change to the enforcement of the law. SB 561, scheduled for a hearing on April 29, 2019, would expand the CCPA’s private right of action to apply to any violation of the statute and eliminate the 30-day period that would allow businesses to cure a violation prior to a plaintiff initiating suit. Far from the narrowing and clarifying measures moving in the Assembly, this Senate initiative would expand exponentially the impact and costs of CCPA compliance for California businesses by allowing class action litigators to drive the interpretation and enforcement of the CCPA at will.

Do not be misled, however—there is no universal agreement in Sacramento that the CCPA must be tamed. Even if all of the Committee’s amendments were to be approved by the full California Assembly, the chances that any of these measures will be approved by the Senate is far from certain.

CCPA Amendments Summary:

Assembly Bills

AB 25: Clarifies that the term “consumer” does not include “a natural person whose personal information has been collected by a business in the course of a person acting as a job applicant to, an employee of, a contractor of, or an agent on behalf of, the business” to the extent that person’s information is collected and used “solely within the context of the person’s role.”

AB 846: Confirms that a “consumer’s voluntary participation” in a loyalty or rewards program is permitted under the statute

AB 873: Amends the definition of “deidentified” to mean information that “does not reasonably identify or link, directly or indirectly, to a particular consumer.” Also amends the definition of “Personal information” to mean “information that identifies, relates to, describes, or could reasonably be linked, directly or indirectly, with a particular consumer” and eliminates reference to information that identifies a household.

AB 874: Amends the definition of “personal information” to exclude deidentified or aggregated consumer data and amends the definition of “publicly available information” to mean information lawfully provided from federal, state, or local government records.

AB 1355: Requires that a business disclose “[t]hat a consumer has the right to request the specific pieces of personal information that the business has collected about that consumer.” Also provides that businesses may disclose the personal information sold to third parties by listing the category of third party, rather than by identifying each third party. Similar to AB 874, amends the definition of “personal information” to exclude deidentified or aggregated consumer information. Requirement that financial incentives and price differentials be reasonably related to the value provided to the business by the consumer’s data, rather than the value provided to the consumer by the consumer’s data.

AB 1146: Exempts vehicle information shared between a new motor vehicle dealer and the vehicle’s manufacturer from the statute.

AB 1564: Allows businesses to provide an email address rather than a toll-free number for CCPA requests.

Senate Bills

SB 561: Expands the CCPA private right of action to include any violation of the statute and removes the 30-day cure period prior to filing suit.

Washington State Privacy Act: A Postmortem

For most of March, the Washington Privacy Act (“WPA”) (SB 5367) looked like a sure thing. With Democrats in complete control of the state government, the bill’s nearly unanimous passage in the state Senate, and the support of the technology industry, the WPA seemed poised to join the CCPA as one of the first comprehensive state privacy laws. But the House substantially amended the bill in response to strong opposition from some consumer privacy advocacy groups. Efforts to find a compromise failed, and the bill was shelved for the year.

Although the legislature failed to enact the WPA, it did take some action in the privacy area, amending the state’s data breach law to require companies that have suffered a breach to notify consumers within 30 days of discovering the breach (the previous deadline was 45 days). The law also now requires businesses to inform affected consumers of when the breach occurred and when it was discovered, and, if the breach involved usernames or passwords, to tell consumers to take steps to secure their electronic accounts.

Washington lawmakers agreed on the basic framework of the WPA. Unlike the CCPA and other state privacy bills introduced this year, the bill was based on the EU’s General Data Protection Regulation (“GDPR”). It would have given Washington residents the right to access data that companies held about them (similar to the right contained in the CCPA), to correct inaccurate information about them, to demand deletion of data with only a few exceptions, and to opt out of some uses of their data, such as for targeted advertising. In addition, companies would have been required to conduct “risk assessments” for their processing of consumers’ personal data and to ask for the affirmative consent of consumers before processing their data in ways that posed a high risk of privacy harm. Legislators in both the Senate and House expressed that limiting the use of facial recognition technology by both the private sector and government agencies was a priority; however, they disagreed on how to accomplish this objective.

The Scope of the Law

At the most basic level, there were different opinions on who and what the law should cover. The Senate bill would have applied to entities doing business in Washington who met certain thresholds regarding the number of consumers whose data they controlled and how much of the businesses’ revenue derived from selling personal data; the amended House bill would have removed those thresholds so that all entities doing business in Washington would have been subject to the law by default (though both bills had some exceptions).

There were several other notable differences in scope. The House bill used a broader definition of personal data that would have included data that had already been made public, unlike the Senate’s bill. The House version also offered more guidance on what it meant to de-identify personal data so that it would no longer be subject to the law. And while the Senate bill would have defined a “sale” of personal data as an exchange for monetary consideration to a third party for the purpose of further licensing or selling the data, the House included any exchange or disclosure of personal data to a third party in exchange for anything of value and for any purpose in its definition of a sale.

Trusting Businesses?

Perhaps the most significant difference between the two versions of the WPA was in how they viewed businesses. The Senate bill reflected a relatively positive view of businesses, recognizing that they needed to be regulated in this sphere but also evincing a desire not to overly burden businesses with costly obligations. A belief that businesses might take advantage of consumers at every opportunity and needed to be regulated more strictly, on the other hand, was manifest in the House bill.

This difference in outlook could be seen in how the same GDPR-style rights were implemented. The Senate bill often made exceptions to consumer rights in situations where complying with a request would be cost prohibitive or technically infeasible, would have allowed businesses to retain data a consumer requested to delete if it was necessary for a “business purpose,” and in limited circumstances would have permitted businesses to charge a “reasonable fee” to comply with repetitive consumer requests. The House bill did not include nearly as many exceptions for businesses, only allowed for an analogous exception from the right to deletion if the data was necessary “in relation to the purposes for which it was collected or processed,” and forbid business from ever charging consumers any fees.

Facial Recognition

The differences in the Senate and House approach to facial recognition are a microcosm of the debates over the WPA. The scope of the Senate’s definition of facial recognition, covering only uses for identification, was narrower than the House’s bill, which also regulated its use to detect demographic information or mood. And as it did in other areas, the Senate bill also provided businesses with more latitude to deploy this new technology. The Senate version of the WPA would have permitted the use of facial recognition in decisions that have legal or other significant effects as long as a human reviewed the decision, but the House version prohibited such uses entirely. While the Senate bill would have required companies to allow third parties to test their facial recognition technology for unfair bias, the House bill would have required independent verification that the technology was not biased before it could be deployed. The House similarly put more limits and stricter judicial oversight on the use of facial recognition by government agencies.


The disagreements between the two chambers’ bills regarding enforcement reflected the same worldviews. The House wanted to provide significantly broader enforcement mechanisms for the law—and do so sooner—than the Senate. One of the biggest points of disagreement between the two bills was whether to provide a private right of action. The Senate would have limited enforcement actions to those brought by the state Attorney General, while the House would also have allowed consumers to sue companies who allegedly violated the law directly. Further, the Senate bill provided for a 30-day opportunity to cure violations before becoming liable under the WPA; the House removed that provision. And the House was in a bigger hurry to start enforcing the law: its version would have gone into effect at the end of July 2020, while the Senate would have given businesses an extra year to get into compliance.

Too Far Apart

With the exception of the House providing for a private right of action, the differences between the Senate and the House versions of the WPA were arguably of degree, not kind. It is possible that each issue standing alone would not have been a deal breaker during negotiations. But cumulatively, there was too much daylight between the two drafts to reach a compromise—especially with time running short at the end of the legislative session. The failure of Washington to pass the WPA is a warning to other states trying to pass similar legislation that they too will have to wrestle with these questions about how broad a scope such a law should have, the leeway given to businesses, and how to enforce consumer privacy rights.

State Consumer Privacy Law Roundup

The following chart summarizes the current status of comprehensive consumer privacy reforms that have been introduced at the state level since the passage of the CCPA. This chart details states that are considering broad laws that would apply across industies. In addition to the draft laws noted below, Maine is considering a consumer privacy law that has been introduced but would apply only to data collected by ISPs—stay tuned for future coverage!

map showing status of consumer privacy legislation in different states within the U.S.








Update from LitLand: A Review of Data Breach Litigation Risk

LitLand is a monthly feature that reviews developments in litigation as they relate to privacy matters and highlight any past, current, and future cases about which you should know.

Welcome to LitLand! In recognition of the fact that the Privacy Oracle was born from demand to track developments such as California’s passage of the CCPA, it seemed only appropriate that our first LitLand feature pay homage to our humble beginnings.

The California legislature earlier this month advanced A.B. 561, an amendment that would expand the private right of action under the Consumer Privacy Act. As it stands, the CCPA limits the private right of action to breaches in which “a consumer’s nonencrypted or nonredacted personal information is subjected to unauthorized access and exfiltration, theft, or disclosure as a result of the business’s failure to maintain reasonable security procedures to institute a civil action for various damages.” If the amendment passes, consumers would have a private right of action for any violation of their rights under the CCPA. This includes the failure of a business to provide required disclosures on its website or honor a deletion or access request. Statutory damages continue to be set at not less than $100 and not greater than $750 per incident or actual damages per violation, whichever is greater, even when plaintiffs do not show harm from the violation. In many cases, including security breaches, each consumer affected would be considered one violation, and 3-figure damages could easily become 7- and 8- figure damages.

Even if defeated, the private right of action provision that is currently in the statute arguably lowers the procedural bar for plaintiffs who have historically faced standing hurdles by making failure to notify regarding a breach a “harm” that would confer standing. A look at the largest consumer data breach class actions implicating California residents in recent years (as reported in the California Office of the Attorney General (“California AG”) 2016 Data Breach Report) provides some insight into the scope of the risk that companies doing business in California will face as of next January:

  1. Anthem
    Nationwide Consumer Settlement: $115 Million
    Potential CCPA Statutory Fine: $1.3B – $7.8T

Anthem suffered a cyberattack in 2015 that resulted in the exposure of 78.8 million consumer records, including their names, addresses, Social Security numbers, dates of birth, and employment histories. 10.4 million California residents were affected.

  1. Target
    Nationwide Consumer Settlement: $10 Million
    Potential CCPA Statutory Fine: $750M – $5.6B

During the holidays in 2013, hackers accessed Target’s point-of-sale reader using credentials stolen from a third-party vendor. The breach exposed the credit and debit cards of approximately 40 million shoppers who had visited Target stores. 7.5 million California residents were affected.

  1. LivingSocial
    Nationwide Consumer Settlement: $4.5 Million
    Potential CCPA Statutory Fine: $750M – $5.6B

The personal information of more than 50 million people, including names, email addresses, encrypted passwords, and some users’ dates of birth were compromised in a cyberattack on LivingSocial in 2013. 7.5 million California residents were affected.

  1. UCLA Health
    Nationwide Consumer Settlement: $7.5 Million
    Potential CCPA Statutory Fine: $450M – $3.4B

In 2014, hackers breached the hospital’s networks, resulting in the unauthorized access of the personal health information of 4.5 million California residents.

  1. PNI Digital Media (Costco/RiteAid/CVS)
    Nationwide Consumer Settlement: $250 per person
    Potential CCPA Statutory Fine: $280M – $2.1B

The company was targeted in a cyberattack between 2014 and 2015, where payments processed online by Costco, CVS, or Rite Aid were affected. The personally identifiable information and credit cards of 2.8 million California residents were affected.

  1. T-Mobile USA, Inc. (Experian)
    Nationwide Consumer Settlement: $22 Million
    Potential CCPA Statutory Fine: $210M – $1.6B

Fifteen million T-Mobile customers were potentially affected when credit check bureau Experian was hacked in 2015, exposing the customers’ names, addresses, dates of birth, social security numbers, and driver’s license numbers. Over two million California residents may have been affected.

Practitioners’ Corner

Practitioner’s Corner is a monthly focus on topics of interest to in-house counsel in the implementation of their privacy programs.t’s in a CCPA-compliant service provider contract?

You could start by diving right into the relevant definitions and obligations, but we urge you to take a step back. Ask yourself: do I need to establish a service provider relationship in the first place?

The CCPA allows consumers to opt out of a business’s “sale” of personal information to a third party. When consumers exercise that right, they effectively cut off the flow of their personal information between the business and the third party. Businesses can avoid this outcome in certain cases by executing a contract with the third party, making it the business’s “service provider” and immunizing the relationship and data flows from the consumer’s opt-out choice.

The trade-off is that service providers are restricted from “retaining, using, or disclosing the personal information for any purpose other than for the specific purpose of performing the services specified in the contract for the business,” meaning that it is more difficult for service providers to freely use personal information.

The question is whether creating the service provider relationship is necessary in every situation. The CCPA does not compel businesses and service providers to contract when they exchange personal information between them, unlike the controller-processor relationship in the General Data Protection Regulation (GDPR).

Some situations unquestionably call for service provider contracts because the consequence of an opt-out choice is unacceptable to the business. For example, if you use a cloud service provider to store personal information, a consumer’s opt-out choice would, in effect, prevent you from storing that consumer’s personal information with that cloud service provider. Giving individual consumers control in this manner is likely untenable from a technical system architecture perspective and may actually jeopardize the security of the data.

Here is another consequential scenario: savvy CCPA lawyers will know that two entities in the same corporate group are considered a single “business,” if they control or are controlled by one another and they share common branding. This means that, if two entities in the same corporate group exchange personal information, but are not similarly branded, that exchange could be a “sale.” In this case, having an intra-group service provider contract is critical because it prevents a potentially significant business interruption.

In other cases, you may find it acceptable not to create a service provider relationship because the costs of creating that relationship outweigh the benefits. For example:

  • Your service does not depend on a transfer of personal information to a third party.
  • You have alternative arrangements that can be used in the event of a consumer’s opt-out choice.
  • You expect that consumers will seldom exercise their opt-out choice, so the impact of consumer opt-out requests is lessened.
  • It is not feasible for the service provider’s uses of personal information to be constrained by contract.

In addition to these factors, you should also consider whether your existing contracts have language that is compatible with the CCPA’s requirements for creating the service provider relationship. If the recipient of personal information is effectively a service provider already, you may not need to take further action. Alternatively, updating your contracts for CCPA compliance may not present significant challenges.

Your decision whether to transform third parties into service providers is unique to your circumstances. As with all CCPA compliance efforts, that decision begins with knowing your data flows. In Part 2, we will discuss the language that must be present in CCPA service provider contracts if you decide to create them.

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.

© Davis Wright Tremaine LLP | Attorney Advertising

Written by:

Davis Wright Tremaine LLP

Davis Wright Tremaine 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 (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

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 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 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 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

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:

JD Supra Cookie Guide

As with many websites, JD Supra's website (located at (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
  • New Relic - For more information on New Relic cookies, please visit
  • Google Analytics - For more information on Google Analytics cookies, visit To opt-out of being tracked by Google Analytics across all websites visit 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 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:

- 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.