Your Definitive Guide to the ACA Int’l Ruling: The Top 10 Things Every TCPAlander Needs to Know Now

by Dorsey & Whitney LLP
Contact

It’s here! It’s here! It’s finally here!

At last, I no longer need to field the question of “when, oh when, is the D.C. Circuit Court of Appeals going to rule on the ACA Int’l appeal of the FCC’s TCPA Omnibus ruling from 2015?” Now we know the answer: right in the middle of March Madness, of course.

Forced, as I am, to look up from the basketball games, I must now face the biggest TCPA questions of all: What is the current state of the law respecting predictive dialers? Can we use contractual revocation provisions to full effect? Who is the called party? Is the TCPA constitutional?

This is my definitive take on these and other TCPA issues arising out of the big D.C. Circuit ruling of ACA Int’l v. FCC, No. 15-1211, Doc. No. 1722606 (D.C. Cir. Mar. 16, 2018). The truth is, however, that for every TCPA question the D.C. Circuit answered, its ruling raises many more. Indeed, Judge Srinivasan’s opinion poses at least a dozen specific questions back to the Commission to consider on remand. Unfortunately, therefore, we are all a long way from having final answers on most issues. I guess that’s not really much of a surprise, however, since nothing is ever simple in TCPAland. That said, with Chairman Ajit Pai at the helm of the FCC, industry has very good cause to think that real TCPA change is on the horizon.

Before we get into that, some quick background is in order for any reader who isn’t completely conversant with the history here. The Federal Communications Commission (“FCC” or “Commission”) is the government agency responsible for implementing (i.e. interpreting) the Telephone Consumer Protection Act (“TCPA”). The TCPA generally prevents calls to cell phones made using an automated telephone dialing system (“ATDS”) without the express consent of the “called party.” The FCC’s rulings regarding the meaning of vague phrases within the TCPA (like what’s an ATDS?) are binding on courts and private litigants alike. While this sort of arrangement works fine for 99.9% of federal statutes, the TCPA is incomparably vague, regulates a common activity—phone calls—and contains a massive $500.00 per violation minimum statutory penalty that can be privately enforced. This gives the FCC tremendous power to determine the lawfulness of phone calls and, indirectly, the contours of free speech in this country.

More pertinently, whenever the FCC interprets the TCPA in a manner that expands its reach, private lawsuits go through the roof. Prior to President Trump appointing Chairman Pai to lead the FCC—more on him in a moment— the TCPA went through a lengthy expansionary phase under the watchful eye of then-Chairman Tom Wheeler. While Chairman Wheeler seems like a fine fellow, his policies vastly expanded the reach of the TCPA to the point—as the D.C. Circuit points out in the ACA Int’l ruling—that every smartphone in the country became a federally-regulated autodialer. While the FCC’s stated goal in enacting these changes was to give itself the means to aggressively enforce the statute against true bad actors—almost exclusively unscrupulous telemarketers—it turned a blind eye to the explosion of private TCPA lawsuits its policies were enabling against good industry actors, most of whom were just trying to chat with their customers at phone numbers they had been lawfully provided. The crown jewel of the FCC’s former “expand the TCPA so we can go after bad telemarketing guys and we’ll just hope that private litigants don’t abuse it” policy was the Commission’s 2015 TCPA Omnibus ruling. That ruling expanded the reach of the TCPA to regulate virtually any software-enabled dialing device, made the essential express consent defense as fragile as a bubble, and saddled callers with the risk of calling wrong numbers even when a number changed hands without their knowledge. A predictable and instantaneous explosion of private TCPA suits followed—over a quarter of which were class actions seeking capless statutory damage recoveries often ranging into the billions of dollars—prompting some to muse whether TCPA actually stood for “Total Cash for Plaintiff’s Attorneys.”

The 2015 TCPA Omnibus ruling was challenged by a team of Petitioners—lead by the good folks over at ACA International and joined by my friends at CBA—on a duly-authorized appeal to the D.C. Circuit Court of Appeals. Oral argument was held back in October 2016, and ever since then TCPAland has waited, with baited breath, for the D.C. Circuit’s definitive ruling on the lawfulness of the Omnibus.

So now that the ACA Int’l ruling has been handed down, it falls to me—as the self-declared Czar of the TCPA—to speak definitively as to its impact on the litigation landscape and upon the fate of all who dwell within TCPAland. Accordingly, here are the 10 things you need to know right now:

  1. Chairman Pai is Going to Get His Chance to Make a Mark on the TCPA and I Can’t Wait to See What He Does With It. Since Ajit Pai was elevated by the Trump administration from mere Commissioner to Intergalactic Overlord and Chairman of the FCC, he has set about unwinding most of the work performed by his predecessor, Chairman Wheeler, especially in the net neutrality space. There has been a deafening silence on TCPA-related issues from the Commission, however. Indeed, despite a current glut of petitions that now nearly rivals the count of petitions that had piled up ahead of the Omnibus ruling, the Commission has seemed steadfastly uninterested in unwinding the expansionist policies of the prior administration. Presumably, this was out of due respect for the pending petition before the D.C. Circuit, and a desire not to create havoc in the appellate court system by issuing serial rulings that would wind their way through independent appellate reviews before the same circuit court of appeals that had yet to speak on the Omnibus. Now that the D.C. Circuit has given its nod to the FCC to start over again on a number of key TCPA issues, however, you can bet that Chairman Pai—who once famously called the TCPA a “statutory-rifle shot” when remarking on how limited Congress had intended the statute to be—will take the ball and run with it. Indeed, as shown below, the ACA Int’l ruling is something of a lob pass to the Commission on several key TCPA issues, and we can expect Chairman Pai to finish that alley-oop with a two-handed slam dunk that will get industry onlookers up out of their seats and roaring their applause.
  2. The D.C. Circuit Panel Thinks the Petitioners Missed a Major Issue Regarding the Scope of the TCPA—the Statute Might Only Apply to Calls Made Using a Dialer’s Automatic Capacity! At oral argument back in October 2016, Chief Judge Edwards was heard to forcefully chastise Petitioners’ counsel for conceding that any call made using an ATDS was subject to the statute, even if the call itself was made manually. “Good heavens, that’s your strongest argument and you just conceded it away,” he remarked at the time. The statement was one of a number of remarkable exchanges between bench and bar that played out at the oral argument, and you can read more about the hearing here. It appears that Chief Judge Edwards swayed the panel into his way of thinking, as the ACA Int’l ruling repeatedly makes mention of the Petitioners’ failure to challenge whether calls made without leveraging a device’s “capacity” to operate as an autodialer—more on “capacity” next—are even subject to the TCPA to begin with. As the opinion notes, if not, then “[e]ven if the definition encompasses any device capable of gaining autodialer functionality through the downloading of software, the mere possibility of adding those features would not matter unless they were downloaded and used to make calls.” ACA Int’l at 30-31. The opinion directs the Commission to take this issue into account when reconsidering the petitions. (Notably, however, the Petitioners might have been conceding like a fox—it is precisely because the Court was made to assume that all calls made from an ATDS were subject to the TCPA that it was forced to strike down the TCPA’s interpretation as overly broad, as explained in the next section. Pretty clever, if that was Petitioners’ plan all along.)
  3. The Quibble over “Present” Versus “Future” Capacity was a Complete Red Herring—What Mattered to the Court was the FCC’s Focus on Software-Enabled Dialing Devices. For years now (literally), I’ve had to endure, and sometimes even unwillingly engage in, a more-than-academic debate over whether equipment has current or potential capacity to operate as an ATDS. As the D.C. Circuit points out, however, that entire semantic debate is hogwash: “[v]irtually any understanding of ‘capacity’ [] contemplates some future functioning state, along with some modifying act to bring that state about.” ACA Int’l at 13. But so what? The real issue is whether the FCC’s ruling faithfully tracks Congressional intent with respect to the reach of the statute. And while the D.C. Circuit Court was respectful of the FCC’s authority to delineate those limits, it could not abide by the Commission’s expansion of the statute “several fold” over what Congress intended. As the D.C. Circuit views matters, smartphones are absolutely within the reach of the Omnibus ruling. This is no surprise, as I wrote back in August 2016: “Now, any piece of dialer equipment is governed by the TCPA so long as it can be converted into an autodialer ‘through [future] software changes or updates.’ As demonstrated in the second paragraph of this article, this definition now plainly includes that piece of sophisticated dialing equipment sitting right in your pocket—your smartphone.” Although the D.C. Circuit did not credit me for the analysis, it reached the exact same conclusion and for the exact same reason. The ACA Int’l opinion explains: “[t]he [Omnibus] ruling states that equipment’s ‘functional capacity’ includes ‘features that can be added…through software changes or updates’…[so] ‘a piece of equipment can possess the requisite “capacity” to satisfy the statutory definition of an “autodialer” even if, for example, it requires the addition of software to actually perform the functions described in the definition.'” ACA In’tl at 14-15. It concludes that such a definition necessarily encompasses smartphone technology. And since smartphones are used by hundreds of millions of Americans, but the TCPA—based on the legislative history—was only designed to regulate “hundreds of thousands” of unlawful callers, the FCC’s expansion of the TCPA went far beyond what Congress intended in enacting the statute. On that basis, the FCC’s interpretation of “capacity” was struck down as unreasonable.
  4. The FCC Ran But It Couldn’t Hide on Whether Smartphones Were Within the Scope of the Omnibus Ruling. In its opinion, the D.C. Circuit noted that the FCC refused to concede that smartphones were within the reach of the Omnibus. Its lawyers repeatedly argued that the Omnibus never reached that specific issue, which was reserved for a future petition. The D.C. Circuit was unmoved, and determined that the Omnibus ruling’s failure to address the issue was in and of itself an arbitrary and capricious act. Specifically, in the D.C. Circuit’s view, if the Omnibus does not include smartphones, then the ruling fails to “articulate a comprehensible standard.” See ACA Int’l at 21-23.
  5. The Court Directs the FCC to Clarify Whether the Use of a Random or Sequential Number Generator is a Necessary Feature of an ATDS—and the Fate of Predictive Dialers Hangs in the Balance. And this is where things get very interesting. In the D.C. Circuit’s view, the Omnibus does not answer the crucial question of what capacity is required to make a device an ATDS. Although the Omnibus affirms previous orders suggesting that predictive dialers are within the scope of the ATDS definition, the Omnibus also suggests that a dialer is only an ATDS if it has the capacity to generate random or sequential numbers. These two positions, the Court finds, are irreconcilable because the record plainly demonstrates that not all predictive dialers have the capacity to dial randomly or sequentially. Thus, the D.C. Circuit tees up a crucial issue: “A basic question raised by the statutory definition is whether a device must itself have the ability to generate random or sequential telephone numbers to be dialed. Or is it enough if the device can call from a database of telephone numbers generated elsewhere?ACA Int’l at 25. But the D.C. Circuit refuses to answer the question for the Commission and instead does exactly the opposite, finding, “It might be permissible for the Commission to adopt either interpretation.ACA Int’l at 27. Wow! So the D.C. Circuit just handed the keys to defining an ATDS—which sits at the very heart of the application of the TCPA—to Chairman Pai, who is already on record as stating, “In short, we should read the TCPA to mean what it says: Equipment that cannot store, produce, or dial a random or sequential telephone number does not qualify as an automatic telephone dialing system because it does not have the capacity to store, produce, or dial a random or sequential telephone number.” So maybe, just maybe, the final reversal of the TCPA’s application to predictive dialers—and other dialers that call based upon lists of numbers—is in the cards. Then again, the D.C. Circuit made quite clear that if the FCC wishes to depart from the statutory requirement that an ATDS must make use of a random or sequential number generator, then the D.C. Circuit is likely to bless that too! So an epic showdown is set up before the Commission.
  6. What About Human Intervention? The Court Suggests that It Only Matters if the Commission Chooses to Depart from the Requirement of a Random or Sequential Number Generator. In the D.C. Circuit’s view, the FCC’s after-the-fact pronouncement that an ATDS is something that dials without human intervention and can dial thousands of numbers at a time is just not very useful. As the opinion notes, the Commission has never clarified what human intervention is required, and what dialing thousands of numbers at a time really means. The Court also cannot square the Commission’s observation that a lack of human intervention is the hallmark of an ATDS with the Commission’s subsequent denial of a petition seeking clarification that an ATDS must operate without human intervention. The D.C. Circuit also does not understand what weight is to be given to these seemingly invented attributes of an ATDS, and how they correspond to the statutory requirements. On reconsideration of the issue, therefore, the FCC must—if it chooses to depart from the statutory requirement of using a random or sequential number generator—explain how and when a dialer operates without human intervention, and within just how much time must a dialer be able to dial all those thousands of numbers the Commission keeps mentioning. Again, however, these only seem to be questions that the Commission must answer if it wishes to depart from the statutory requirement of random or sequential number generator.
  7. Reasonable Reliance Is Now the Touchstone of Express Consent—and This is a Very Big Deal. Although the ATDS portions of the ruling are going to get top billing, the most important piece of the ruling, from my perspective, is the D.C. Circuit’s adoption of the FCC’s “reasonable reliance” approach to express consent. The ACA Int’l ruling repeatedly—nearly obsessively—references the FCC’s determination that callers must be able to reasonably rely on consent provided by former subscribers. Indeed, it was this loophole—intended by the FCC to justify nothing more than a one-attempt safe harbor—that the D.C. Circuit ultimately used to reverse that portion of the ruling as arbitrary and capricious. Specifically, the ACA Int’l ruling finds that it was arbitrary and capricious for the FCC—at least on the record before it—to conclude that one attempt was likely to afford a caller reasonable notice that a number had changed hands. As a result, the D.C. Circuit sets aside the one-call safe harbor and instructs the FCC to try again. More importantly to companies being sued in reassigned number suits, the D.C. Circuit has blessed the idea that a caller can reasonably rely on consent afforded by a previous subscriber, which leads to the next point…
  8. The FCC’s Definition of “Called Party” Was Set Aside—and “Intended Recipient” is Still in Play! It’s easy to get confused by the opinion with respect to whether the D.C. Circuit approves of the FCC’s definition of “called party.” Some may say that the D.C. Circuit affirmed the FCC’s determination that “called party” does not mean “intended recipient.” But that is just flat not true. What the ruling did was first determine that the FCC was not required to rule that the “called party” was the “intended recipient” on the record before it. But then, after determining that the FCC’s one-call safe harbor could not be squared with its determination that a caller is permitted to reasonably rely on consent provided by a former subscriber, it set aside the FCC’s “called party” determination because that would impose strict liability for reassigned calls, which is a result that the Commission specifically stated it did not want to embrace. The key language appears at pages 39-40 of the opinion: “If we were to excise the Commission’s one-call safe harbor alone, that would leave in place the Commission’s interpretation that ‘called party’ refers to the new subscriber…We cannot be certain that the agency would have adopted that rule in the first instance…[and] as a result, we must set aside the Commission’s treatment of reassigned numbers [including its definition of called party] as a whole.” So, on remand, the issues to be addressed are: (1) who is the called party?; and (2) if it is still the subscriber, then to what extent may a caller reasonably rely on the consent of the former “called party”?  
  9. Consumers Can Revoke Their Consent by Any Reasonable Means—but Not “Creatively” and Not if Their Contract Says Otherwise! While the revocation piece of the ACA Int’l ruling is big news, it is hardly surprising. Readers of this blog know that I have been saying for over a year now that contractual revocation clauses are enforceable. Sure enough, the D.C. Circuit affirms that “[n]othing in the Commission’s order [] should be understood to speak to parties’ ability to agree upon revocation procedures.” ACA Int’l at 43. More generally, the Court upholds the FCC’s determination that consumers can revoke consent using “reasonable” means. The D.C. Circuit articulates a totality-of-the-circumstances test. One factor to consider is “whether the caller could have implemented mechanisms to effectuate a requested revocation without incurring undue burdens.”Another is “whether the consumer had a reasonable expectation that he or she could effectively communicate his or her request…in that circumstance.” ACA Int’l at 41. One piece of the ruling that is sure to have industry buzzing is the suggestion that a call recipient’s decision not to take advantage of a reasonable revocation paradigm that is offered by the caller might be evidence that the revocation effort was not reasonable. In particular, the Court suggests that “creative” revocation efforts might not be permissible—a clear shot at the unfortunate tactic of some litigants who manufacture TCPA lawsuits by evading known opt-out mechanisms.
  10. No Mention of the First Amendment or the Constitution Is Made in the Ruling. While others may not find this surprising, I am actually shocked by the panel’s silence on constitutional issues. The TCPA has been subjected to strict scrutiny on five separate occasions now—this means that the statute is unconstitutional unless it is narrowly tailored to further a compelling governmental interest. But given the panel’s finding that the FCC Order literally expanded the TCPA to apply to every smartphone in the country and, alternatively, that any other reading of the Omnibus would fail to “articulate a comprehensible standard,” I don’t see how the statute passes strict scrutiny muster. The TCPA—as applied by the FCC—is necessarily either unconstitutionally overbroad, or unconstitutionally vague for want of any discernable scope.

Written by:

Dorsey & Whitney LLP
Contact
more
less

Dorsey & Whitney 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.