The Obama Administration’s Personal Data Notification & Protection Act: An Analysis

by Cadwalader, Wickersham & Taft LLP
Contact

On January 12, 2015, President Obama proposed the Personal Data Notification & Protection Act, which would create a federal standard for data breach notification.1  The proposed bill is part of a more wide-ranging effort by the Obama administration  to shore up the nation’s cybersecurity.2  The measure comes at a time when both the public and private sectors, especially the retail and banking industries, have been under increasing attack by cyber criminals and state actors; the Sony hack attributed to North Korea is only the latest in a series of high-profile cyber incidents. 

The Obama administration’s draft bill follows a long line of legislative proposals that have failed to gain passage despite the rising incidence of high-profile data breaches.  In just the last two years, five data breach notification bills were introduced in the Senate alone, yet none garnered sufficient support for passage.3  However, the public’s heightened interest in the issue, combined with the support of key business groups, might be enough to finally break the gridlock.

Business groups such as the National Retail Federation4 support the Obama administration’s proposed legislation because it creates a single breach notification standard.  These groups—which are likely to have greater sway with Republicans and conservative Democrats—reason that even a tougher federal standard would be simpler to comply with than the current patchwork of 47 different—and often conflicting—state laws.5  Meanwhile, consumer protection groups are concerned because the federal legislation would preempt state data breach notification laws, including those that offer greater protection than the proposed federal standard.6

The proposed legislation’s ultimate success likely will turn on whether both sides can reach agreement on a middle ground and recognize that neither businesses nor privacy advocates will be able to cherry-pick all of their favorite provisions from existing state laws and earlier federal proposals.  The following is a brief analysis of the proposed bill’s key provisions.

Defining Personal Information

The Obama administration’s proposal would require businesses to notify individuals whose sensitive personally identifiable information (“SPII”) has been or is reasonably believed to have been acquired or accessed without authorization unless there is no reasonable risk of harm or fraud to the individual.  The bill defines SPII to include:

(1) an individual’s first and last name or first initial and last name in combination with any two of the following data elements:

(A) home address or telephone number;

(B) Mother’s maiden name;

(C) month, day, and year of birth;

(2) a non-truncated social security number, driver’s license number, passport number, or alien registration number or other government-issued unique identification number;

(3) unique biometric data such as a finger print, voice print, a retina or iris image, or any other unique physical representation;

(4) a unique account identifier, including a financial accounting number or credit or debit card number, electronic identification number, user name, or routing code;

(5) a user name or electronic mail address, in combination with a password or security question and answer that would permit access to an online account; or

(6) any combination of the following data elements:

(A) an individual’s first and last name or first initial and last name;

(B) a unique account identifier, including a financial account number or credit or debit card number, electronic identification number, user name, or routing code; or

(C) any security code, access code, or password, or source code that could be used to generate such codes or passwords.

This definition is more expansive than that which is found in most of the earlier Senate proposals.7  The Obama administration’s proposal also authorizes the Federal Trade Commission (“FTC” or the “Commission”) to use its rulemaking authority to amend the definition of SPII, thereby ensuring that the law will remain relevant as technology evolves, while also introducing some uncertainty about the scope of future breach notification obligations.

Identifying a Data Breach — The Trigger for Notification

The proposed legislation also details when a security breach gives rise to an obligation to notify affected individuals.  The administration’s proposal broadly defines “security breach” to include instances in which there is a reasonable basis to conclude that an unauthorized acquisition of or access to SPII occurred.8  Individual notification generally is required when a security breach occurs, but a risk-based exemption narrows this obligation.  Individual notification is not required where “there is no reasonable risk of harm or fraud” to the individual whose SPII was acquired or accessed.  While relieving businesses of notification obligations in some cases, this exemption is not as broad as that which is found in many state laws and previous federal proposals.  Many states, and several earlier federal proposals, require notification only in cases where substantial harm or a specific kind of harm—identity theft—is likely.  The result is that the proposed legislation likely will require individual notification more often than would be required under many existing state laws and previous legislative proposals.

The bill acknowledges the burden that notification can place on small businesses by requiring only those “businesses that use, access, transmit, store, dispose of, or collect sensitive personally identifiable information about more than 10,000 individuals in any 12-month period” to notify individuals of a security breach that may affect their SPII.9  The proposal also takes into consideration the expanding number of businesses that give vendors access to their SPII.  For example, a retailer might contract with a vendor to maintain its point-of-sale terminals, thereby sharing the SPII found on those terminals with the vendor.  The bill relieves vendors—and other business entities that do not own or license personally identifiable information—of any obligation to notify individuals of a breach of that information unless there is a contractual agreement to the contrary.  Rather, vendors must notify the owners or licensees of SPII in the event of a security breach, and those owners and licensees in turn must provide any required notification.10

Risk Assessments — The Key to Avoiding Unnecessary Notification

As discussed above, the bill’s core proposition is that, absent an exception, a business must notify customers of any security breach, regardless of whether that breach involves one individual’s driver’s license number or the credit files of millions of individuals.  The broad reach of this general rule, however, is tempered by several exceptions.  The principal exception allows businesses to avoid the individual notification requirement in instances where “there is no reasonable risk of harm or fraud” to the individual whose SPII was acquired or accessed.11  The only way to make that determination and avoid the notice requirement is to conduct a post-breach risk assessment.

There is a narrow window for a business to conduct a risk assessment after it learns of a security breach.  Within 30 days after discovering a security breach, a business must notify the FTC of the results of the risk assessment and the business’s decision to invoke the risk assessment exemption.

The risk assessment must be conducted “in a reasonable manner or according to standards generally accepted by experts in the field of information security.”  The assessment must also include, to the extent available, at least six months of data that logs every “communication or attempted communication with a database or data system containing sensitive personally identifiable information.”  The logs must contain “all log-in information associated with databases or data systems containing sensitive personally identifiable information, including both administrator and user log-in information.”  This data is more granular—and far more sensitive—than the information that any comparable state law or federal legislative proposal requires a business to turn over to the government.

When and How to Provide Notice

Under the proposal, businesses must make required notifications “without unreasonable delay,” which shall not exceed 30 days unless the entity demonstrates to the FTC that additional time is necessary, or the government delays notification for the purposes of law enforcement or national security.  Individual notice may be provided by mail, telephone, or e-mail (if the individual has consented to receive notice by e-mail).  In addition, a business must provide notice to the media when the number of affected individuals in any one state exceeds 5,000.  Notably absent is a provision in many state laws and earlier federal legislative proposals that allows for substitute notification through the media alone when individual contact information is not available or the cost of providing individual notice is excessive.  The content of a notice, regardless of the method by which it is transmitted, must include a description of the categories of SPII acquired or accessed, a toll-free number that an individual can call to find out what types of SPII a company maintains about him or her, and contact information for the major credit reporting agencies and the FTC.12

Notifying the Government of a Data Breach

In addition to ensuring that individuals receive timely notice of security breaches that affect their SPII, the bill also obligates businesses to report security breaches to the federal government when certain criteria are met.  Government notice may be required even if a risk assessment determines that no individual notification is required.  The Secretary of Homeland Security is directed to designate the entity that will receive this information and disseminate it to the U.S. Secret Service, the FBI, and the FTC.  The bill also sets the criteria that trigger the government reporting obligation.  The obligation to report arises when the SPII of more than 5,000 individuals is accessed, the breach involves a database containing such information about more than 500,000 individuals, or the breach involves federal government databases or the SPII of individuals known to the business to be federal employees or contractors involved in national security or law enforcement.   Notably, just as the FTC can use its rulemaking authority to change the definition of SPII, it can also promulgate regulations to amend the thresholds for when government notice must be provided.  The timeline for notifying the government is even more compressed than for individual notification, with government notice being required at least 72 hours before individual notice, or 10 days after discovery of the security breach—whichever comes first.

Enforcement by the FTC and State Attorneys General

The proposal provides for enforcement of the bill’s breach notification requirements at both the federal and state level.  At the federal level, compliance is enforced by the FTC under the Federal Trade Commission Act (“FTCA”).  Any violation of the bill is defined to be an unfair or deceptive trade practice that is subject to the jurisdiction of the Commission, even if the business entity does not meet the other jurisdictional requirements under the FTCA.13

In addition to enforcement by the FTC, state attorneys general are empowered to bring civil actions seeking injunctive relief or civil penalties of up to $1,000 per day for each individual whose SPII was compromised—up to $1 million per violation.  However, there is no cap on the civil penalties that state attorneys general can recover when the business entity is found to have acted willfully or intentionally.  Before filing an action, a state must provide written notice to the Attorney General and the FTC, which in turn may move to stay the action, intervene in the action, initiate its own action, or file petitions for appeal.  Once the Commission institutes an action, state attorneys general cannot file subsequent parallel actions.  The proposal does not include a private right of action.

Conclusion

There is mounting pressure on the federal government to do more to protect Americans from cyber attacks and computer crime.  However, the success of the Obama administration’s proposal is not a foregone conclusion, especially if consumer protection groups advocate strongly against a law that preempts what they believe are stronger consumer protections included in some existing state laws.  Agreeing on the details will be challenging for Congress, but the growing consensus that a national standard is needed makes this one of the more promising areas in which the new Congress could make real progress.

In the midst of this debate over the need for a national data breach notification law, businesses must keep the bigger cybersecurity picture in mind.  Indeed, businesses do not need to wait for legislation before implementing the most critical aspects of an effective cybersecurity strategy.  Minimizing the occurrence and severity of cyber attacks and data breaches fundamentally depends on creating a corporate culture in which individual users, from line workers to chief executives, exercise discipline in how they use technology every time they log on.14  Legislation alone cannot promote good information security hygiene.  More than any other area of business risk, cybersecurity requires a proactive approach that focuses not only on compliance with existing laws and regulations, but also on implementing and continuously refining best practices and technological solutions to address an ever-evolving threat.

1 See The Personal Data Notification & Protection Act, available at http://www.whitehouse.gov/sites/default/files/omb/legislative/letters/updated-data-breach-notification.pdf.

2 This effort also includes legislation that would facilitate greater information sharing between the private sector and the federal government and, separately, update law enforcement provisions related to the prosecution of computer crime.  See Updated Department of Homeland Security Cybersecurity Authority and Information Sharing Proposal, available at http://www.whitehouse.gov/sites/default/files/omb/legislative/letters/updated-information-sharing-legislative-proposal.pdf; Updated Law Enforcement Provisions Related to Computer Security, available at http://www.whitehouse.gov/sites/default/files/omb/legislative/letters/updated-law-enforcement-tools.pdf.

3 See Data Security Act of 2014, S. 1927, 113th Cong. (Sens. Carper & Blunt); Data Security and Breach Notification Act of 2014, S. 1976, 113th Cong. (Sen. Rockefeller); Personal Data Privacy and Security Act of 2014, S. 1897, 113th Cong. (Sen. Leahy); Personal Data Protection and Breach Accountability Act of 2014, S. 1995, 113th Cong. (Sen. Blumenthal); Data Security and Breach Notification Act of 2013, S. 1193, 113th Cong. (Sen. Toomey).

4 See Retailers Renew Call for Federal Data Breach Notification Law, National Retail Federation (Jan. 12, 2015), https://nrf.com/media/press-releases/retailers-renew-call-federal-data-breach-notification-law.

5 See Brendan Sasso, Why Businesses Love Obama’s Push for Security Regulation, National Journal (Jan. 12, 2015), http://www.nationaljournal.com/tech/why-businesses-love-obama-s-push-for-security-regulation-20150112.

6 See G.S. Hans, White House Data Breach Legislation Must Be Augmented to Improve Consumer Protection, Center for Democracy & Technology (January 16, 2015), https://cdt.org/blog/white-house-data-breach-legislation-must-be-augmented-to-improve-consumer-protection/.

7 Senator Toomey’s bill, for example, would have included only names, social security numbers, government identification numbers, and financial account numbers with required security codes.  At the other end of the spectrum, the definition of “sensitive personally identifiable information” in Senator Blumenthal’s bill included everything in the Obama proposal and added an individual’s medical history.

8 See § 1(g) (“The term ‘security breach’ means a compromise of the security, confidentiality, or integrity of, or the loss of, computerized data that results in, or there is a reasonable basis to conclude has resulted in – (A) the unauthorized acquisition of sensitive personally identifiable information; or (B) access to sensitive personally identifiable information that is for an unauthorized purpose, or in excess of authorization.”).

9 At the same time, this provision would appear to require businesses to track at least monthly their use, access, transmission, disposal, or collection of SPII, so that in the case of a breach, they can determine whether the 10,000 number has been reached.

10 The bill also provides limited exemptions to the individual notification requirement for breaches affecting credit card data and certain HIPAA-covered entities.

11 The bill provides an even greater incentive for businesses to take a proactive approach to safeguarding personal information by creating a rebuttable presumption that no reasonable risk of harm exists when the information subject to a security breach is encrypted.  See § 102(b)(1)(A) (“If the data at issue was rendered unusable, unreadable, or indecipherable through a security technology or methodology generally accepted by experts in the field of information security, there shall be a presumption that no reasonable risk exists.”).

12 In a provision favored by consumer advocates, the bill allows a state to require that a notice include additional information about the state’s victim protection assistance.  For example, California requires individual notice of a data breach to offer identity-theft prevention products.  This is the only instance in which the administration’s proposal does not preempt state data breach notification laws.

13 For example, under the FTCA, the FTC does not have jurisdiction over specific types of entities such as banks, credit unions, and certain nonprofit organizations.  However, the proposed bill would allow the FTC to regulate even those entities’ compliance with the federal breach notification standard.  Despite this broad enforcement authority, a handful of checks limit the Commission’s investigative power.  The Commission must consult with the Attorney General before beginning an investigation, and in certain instances, must coordinate its investigations with the Federal Communications Commission or the Consumer Financial Protection Bureau.

14 See generally Ponemon Inst. LLC, 2015 State of the Endpoint Report:  User-Centric Risk 1 (2015), available at http://www.ponemon.org/local/upload/file/2015%20State%20of%20Endpoint%20Risk%20FINAL.pdf (“The biggest problem identified in this year’s research is the negligent or careless employee with multiple mobile devices using commercial cloud apps and working outside the office.”).

 

 

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.

© Cadwalader, Wickersham & Taft LLP | Attorney Advertising

Written by:

Cadwalader, Wickersham & Taft LLP
Contact
more
less

Cadwalader, Wickersham & Taft 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.