HHS Overhaul of HIPAA: Summary of New Obligations for Covered Entities and Business Associates

by Baker Donelson

On January 17, 2013, the Department of Health and Human Services (HHS) posted Modifications to the HIPAA Privacy, Security, Enforcement, and Breach Notification Rules [PDF] (the Final Rule) under the authority of the HITECH Act and the Genetic Information Nondiscrimination Act (GINA), as well as under the general authority of HHS. The Final Rule, scheduled to be published in the Federal Register on January 25, 2013, will be effective on March 26, 2013. Thankfully, however, in general covered entities and business associates will have an additional six months, until September 23, 2013, to come into compliance. The Final Rule does not address the Proposed Rule on Accounting for Disclosures [PDF], published May 31, 2011.

This client alert provides an overview of the principal changes in the Final Rule. Look for a complete Ober|Kaler review and analysis of the Final Rule in the coming days. 

Business Associates


In addition to formalizing the inclusion of Patient Safety Organizations and Health Information Organizations (Health Information Exchanges, E-Prescribing Organizations and similar organizations) as business associates, the Final Rule provides important clarification about the status of “conduits” as business associates. Since the inception of HIPAA, service providers such as the post office and telephone companies have been exempt from the business associate requirements as their access to Protected Health Information (PHI), if any, has been on an incidental, as opposed to a routine, basis. As technology has evolved, the application of this test, never a “bright line,” to important health care industry service providers such as cloud service providers of storage or software, has been unclear. The Final Rule articulates a brighter line test. A conduit, whether of paper or electronic PHI, only provides transmission services, including any temporary storage of PHI incidental to the transmission service. By contrast, a service provider that provides storage is a business associate, even if the agreement with the covered entity does not contemplate any access or access only on a random or incidental basis. The test is persistence of custody, not the degree (if any) of access.

Downstream Contractors

A hospital contracts with a billing company. The billing company contracts with a shredding company to dispose of its billing records. The shredding company contracts with a trucking company to bring the hospital’s paper billing records to its shredding facility. Under the Final Rule, each entity would be directly responsible for compliance with the business associate requirements under the Security Rule and the Privacy Rule, even if the parties fail to enter into a written business associate agreement. The trucking company’s responsibility would likely be based on custody, even if it did not view the records, as discussed above. Under the Final Rule, the hospital would only be required to enter into a business associate agreement with the billing company. The business associate or downstream subcontractor would be required to obtain written “satisfactory assurances” from its immediate subcontractor. In the event of a breach of the security of unsecure PHI, the chain of reporting would follow the chain of contracting in reverse: trucking company to shredding company; shredding company to billing company; billing company to hospital. 

Privacy Rule Obligations

The HITECH Act was not specific on the Privacy Rule direct obligations of business associates. The Final Rule specifies that these responsibilities are for limiting uses and disclosures of PHI to what is  provided in the business associate agreement or the Privacy Rule; for disclosing PHI to HHS for an investigation of the business associate’s HIPAA compliance; for disclosing PHI to the covered entity or the subject individual in response to a request for an electronic copy of the individual’s PHI (discussed below); for making reasonable efforts to comply with the minimum necessary requirements of the Privacy Rule, and finally, for entering into a business associate agreement with a subcontractor. 

Transition Provisions

In recognition of the time that will be necessary to renegotiate existing business associate agreements, the Final Rule grandfathers existing business associate agreements for up to one year beyond the compliance date, up to September 23, 2014. In order to qualify, the business associate agreement must have been in existence prior to the publication of the Final Rule, have complied with HIPAA and not be renewed or modified during the grandfather period. An automatic renewal, under a so-called evergreen clause, does not constitute a renewal or modification for purposes of the availability of the grandfather period.

Enforcement Rule

Effective Date

The Enforcement Rule changes are effective on March 26, 2013. The additional 180 days afforded for most of the provisions in the Final Rule apply only to modified standards or implementation specifications.

Investigation and Resolution of Violations 

The Final Rule reflects the requirement of the HITECH Act that HHS will investigate a possible HIPAA violation if, as HHS states, a preliminary review of the facts available from a complaint or compliance review, or from independent inquiry by HHS, indicates the possibility of willful neglect as to HIPAA compliance. The investigation may proceed directly to an enforcement action, particularly but not only, in the case of willful neglect. However, the Final Rule offers reassurance that, absent indications of willful neglect, HHS still will seek compliance through informal, voluntary action in appropriate cases.

Violations Due to Reasonable Cause 

Of the four tiers of penalties specified in the HITECH Act, the required state of mind for the lowest tier (entity did not know, and in the exercise of reasonable diligence would not have known of the violation) and for the highest two tiers (willful neglect) are unchanged under the Final Rule. The state of mind for second tier, violations due to reasonable cause not amounting to willful neglect, was not specified. The second tier is important as a practical matter, because it likely covers many common violations by otherwise generally compliant covered entities and business associates, such as those that occur due to human error, despite workforce training and appropriate policies and procedures. The Final Rule modifies the definition of reasonable cause to specify the state of mind; reasonable cause covers violations in which the entity exercised ordinary business care and prudence to comply with the provision that was violated or in which the entity knew of the violation but lacked “conscious intent or reckless indifference” associated with a violation due to willful neglect.

Upstream Vicarious Liability

As discussed above, under the Final Rule, compliance obligations flow downstream between parties with direct contractual relationships: covered entity to business associate, business associate to subcontractor, and so on. If a business associate or downstream contractor is an agent of the entity with which it contracted under federal common law, civil monetary penalties imposed on the downstream contractor for a HIPAA violation, so long as it is within the scope of the agency, will be attributable to the upstream party with which it contracted. The Final Rule summarizes HHS’s view of federal common law of agency. Determinations will be based on the right or authority of the upstream entity to control the downstream contractor’s conduct in the course of performing the service, even if that right was not actually exercised with respect to the violation for which the CMP is imposed.


In a significant departure from the Proposed Rule, the Final Rule will require an authorization for treatment communications and for communications presently permitted as an exception to the marketing requirement of an authorization under the definition of health care operations, if the covered entity (or, under the Final Rule, a business associate) receives financial remuneration from the third party whose product or service is subject to the communication. Financial remuneration consists of direct or indirect payment to the covered entity or business associate from, or on behalf of, the third party whose product is the subject of the communication. An exception, in accordance with the HITECH Act, is made for subsidized refill reminders or communications about a currently prescribed drug or biological, as long as the subsidy is reasonable in amount. Direct means the payment is paid directly to the entity making the communication and indirect means that it was channeled through a third party to the covered entity or business associate making the communication. Financial remuneration does not include “in-kind” or other nonfinancial subsidies for this purpose. 

HHS reasoned that the Proposed Rule, which required notice and an opt-out for subsidized treatment communications (defined as those sent to an individual) and an authorization for subsidized health care operations communications (defined as those sent to a population of individuals) about treatment or treatment alternatives, health-related products or services available from the covered entity, participants in or benefits available in a provider or health plan network (i.e., the exceptions to the definition of marketing in the definition of health care operations) was impractical to implement, requiring a judgment as to whether a communication pertained to treatment or health care operations and requiring two separate processes for subsidized communications, depending on the answer. In the absence of direct or indirect remuneration, no authorization is required for either the treatment or the health care operations communications. In addition, the exception for face-to-face communications or gifts of nominal value continues, without reference to remuneration from a third party.

Sale of PHI

The HITECH Act required that if a covered entity or business associate received direct or indirect remuneration in exchange for the disclosure of PHI, a so-called “sale” of PHI, an authorization be obtained from each subject individual. Exceptions were specified in the Act for public health activities, research, treatment, the sale or other business consolidation of a covered entity, business associate services requested by the covered entity, fees charges for providing an individual with access to the individual’s PHI, and other purposes designated by HHS. The Final Rule defines sale of PHI as “a disclosure of protected health information by a covered entity or business associate, if applicable, where the covered entity or business associate directly or indirectly receives remuneration from or on behalf of the recipient of the protected health information in exchange for the protected health information.” Disclosure includes granting access directly or through licenses or lease agreements. Remuneration, for this purpose, includes in-kind value.  

In the case of a transfer for public health purposes, the remuneration can be a cost-based fee to cover the costs of preparing and transmitting the data. A similar limitation applies to research. Cost-based fees, however, may include direct and indirect costs, so long as there is no profit factor. Disclosures for treatment and payment activities are exempted, to make it clear that these activities do not constitute a sale. As to disclosures to a business associate, the Final Rule makes it clear that a business associate may recoup reasonable cost-based fees from third parties for preparing or transmitting records on behalf of the covered entity or where otherwise permitted by law, and that remuneration paid by the business associate to a subcontractor for activities performed on behalf of the business associate does not require an authorization. The definition of costs for research purposes applies to the foregoing exemptions, where reasonable cost is specified.


The Final Rule permits covered entities to combine conditional and unconditional authorizations for research if they differentiate between the two activities and allow for an opt-in of unconditional research activities. Future research studies may now be part of a properly executed authorization, which includes all the required core elements of an authorization. Under the prior rule, covered entities could not combine or condition authorizations for purposes other than research that involves treatment, while a separate authorization was needed for future research or to create or build a central research database or repository. This change brings HIPAA in line with Common Rule requirements related to biospecimens and databases. The only exception applies to authorizations related to psychotherapy notes, which may be combined only with another authorization for the use or disclosure of psychotherapy notes. 

Disclosures about a Decedent to Family Members and Others Involved in Care

Previously, a covered entity could disclose information about a decedent only to a personal representative. Under the Final Rule, a covered entity also is permitted to disclose a decedent’s information to family members and others who were involved in the care or payment for care of the decedent prior to death, unless inconsistent with any prior expressed reference of the individual that is known to the covered entity. This change does not change the authority of a decedent’s personal representative. 

Disclosures of Student Immunization to Schools

Under the Final Rule, covered entitiesmay send immunization records directly to a school without written authorization. Instead, a covered entity may provide immunization records to a school upon the assent by a parent, guardian or person acting in loco parentis. These disclosures must comply with state law regarding the provision of immunization records. Covered entities must document their discussions related to disclosure for student immunization records.


The Privacy Rule permitted a covered entity to use or disclosure PHI to a business associate or related foundation for fundraising purposes without an individual’s authorization. Permitted PHI included:

  • Demographic information related to an individual
  • Dates of health care provided to an individual.

The Final Rule clarifies what constitutes demographic information. It does not modify what constitutes fundraising communication and current opt out requirements, however. Under the Final Rule, covered entities are provided flexibility to decide the method to allow for individuals to opt out and opt back into the use of PHI in fundraising activities. For example, a covered entity could use a toll-free number, email address, other opt-out mechanism or a combination of methods. In addition, under the Final Rule HHS leaves the decision as to the scope of the opt-out related to future fundraising communications to the covered entity. Many covered entities found campaign-specific opt-outs difficult to track for compliance purposes. HHS strengthened the standard related to further communications after individuals opt out from “reasonable efforts” to an outright prohibition.

Notice of Privacy Practices

Covered entities that did modify their Notice of Privacy Practice after the passage of HITECH are now required to  make changes and to distribute the new Notices based on changes required under the Final Rule. For example, the Final Rule requires that a covered entity include uses and disclosures of PHI, but not specify a list of all situations in which an authorization is required. Instead, covered entities can list categories that require authorization, such as:

  • psychotherapy notes (if applicable)
  • marketing purposes
  • sale of PHI

The Notice must also include a statement that other uses and disclosure not described in the Notice of Privacy Practices will be made only with authorization from the individual. The Notice of Privacy Practices must also include a statement related to fundraising communications and the individual’s right to opt out, and the new right to restrict certain disclosures of PHI to a health plan where the individual pays out of pocket in full for the health care item or service. Finally, the Notice of Privacy Practice must include a statement related to a breach of unsecured PHI, although an entity-specific statement is not required.

Right to Request a Restriction of Uses and Disclosures

The Final Rule creates a new right to restrict certain disclosures of PHI to a health plan where the individual or a family member or other person pays out of pocket in full for the health care item or service. Covered entities will be required to develop methods to create notation in an individual’s medical record related to restrictions so that information is not sent to or accessible to health plans. Covered entities still can submit restricted information for required Medicare and Medicaid audits under the “required by law” requirement of the Privacy Rule.

Access of Individuals to Protected Health Information


The Final Rule amends the Privacy Rule to allow individuals to request electronic copies of their PHI that is maintained in an electronic health record (EHR) or other electronic designated record set. Covered entities must provide an electronic, “machine readable copy,” which means digital information stored in a standard format enabling the PHI to be processed and analyzed by a computer. HHS provides flexibility as to the exact format, acknowledging that systems may vary, but requires the covered entity to accommodate individual requests for specific formats, if possible.

Third Parties 

Under the Final Rule, if an individual requests a covered entity send PHI directly to another individual, the covered entity must transmit the copy as requested. This request must:

  • be in writing and signed by the individual, and
  • clearly identify the designated person and where to send the copy of the PHI.

If a covered entity already requires that access request be in writing, the covered entity can use the same request to access the individual’s PHI or require a separate written request. Covered entities will need to implement policies and procedures to verify the identity of the person who requests PHI and safeguards to protect the information that is used or disclosed.


Under the Privacy Rule, covered entities can charge reasonable cost-based fees. The Final Rule allows the labor cost for copying PHI to be separately identified in both paper and electronic form as a factor in cost-based fees. HHS acknowledged that the labor cost for search and retrieval of PHI in electronic form are more than negligible. Covered entities may also include the supply cost for both paper and electronic copies, including CDs or UBS flash drives, along with postage for sending portable media at the request of the individual. Fees related to maintaining systems, infrastructure and storage are not considered reasonable, cost-based fees. Covered entities should check state law related to fee restrictions and requirements. 


The Final Rule removes the 60-day timeframe for retrieval of records held off site, leaving covered entities with 30 days to provide access to records to individuals in all circumstance with a one-time 30-day extension. This change was made due to the increase reliance on electronic records and to encourage covered entities to provide access to records sooner. Covered entities should check state law related to more stringent timeliness requirements and modify current policies and procedures.

Modifications to the Breach Notification Rule (Or, “Goodbye, Harm Standard”)

The Interim Final Breach Notification Rule [PDF] (the Breach Rule), published August 24, 2009, has been finalized mostly without change with one significant exception – the definition of a breach was “clarified” through the removal of the “harm standard” and a shift to a more objective test of whether PHI has been “compromised.” Importantly, this means two things: First, that following the clarification, more breaches will need to be disclosed and reported. Second, because these changes are characterized as a “clarification,” the changes to how covered entities and business associates analyze and report breaches take effect immediately. In fact, the clarification begs the question of whether entities that had relied on a lack of perceived harm to avoid making a breach report will need to reanalyze those incidents and perhaps make (late) disclosures. Most sections of the Interim Final Rule were adopted with minor, or no, changes. Each section of the Breach Rule adopted with noteworthy changes or guidance is addressed below.

Definition of Breach (including the harm standard) 

Of the 85 public comments received on the definition of breach, 70 addressed the harm standard. Of those 70 comments, 60 supported the existing harm standard, but 10 (from members of Congress and consumer advocacy organizations) argued for its modification or elimination. The Office for Civil Rights (OCR) apparently found those 10 comments persuasive.

In short, OCR explained that it believes that the “language [defining breach and explaining the harm standard] used in the interim final rule and its preamble could be construed and implemented in manners we had not intended.” As a result, in the Final Rule, OCR clarifies its “position that breach notification is necessary in all situations except those in which the covered entity or business associate, as applicable, demonstrates that there is a low probability that the protected health information is compromised.” 

This clarification was undertaken in two steps: First, language was added to the definition of a breach to “clarify that an impermissible use or disclosure of protected health information is presumed to be a breach” unless the responsible entity can demonstrate that “there is a low probability that the protected health information has been compromised.” Second, the harm standard was removed and modifications were made to the risk assessment portion of the Breach Rule to require the use of a more objective risk assessment.

In practice, the two changes function together. The following regulatory language was eliminated:

(1)(i) For purposes of this definition, compromises the security or privacy of the protected health information means poses a significant risk of financial, reputational, or other harm to the individual.

(ii) A use or disclosure of protected health information that does not include the identifiers listed at § 164.514(e)(2), date of birth, and zip code does not compromise the security or privacy of the protected health information.

And the following new section of text was added:

(2) Except as provided in [the existing exceptions to the definition of breach], an acquisition, access, use, or disclosure of protected health information in a manner not permitted under subpart E is presumed to be a breach unless the covered entity or business associate, as applicable, demonstrates that here is a low probability that the protected health information has been compromised based on a risk assessment of at least the following factors:

(i) The nature and extent of the protected health information involved, including the types of identifiers and the likelihood of re-identification;

(ii) The unauthorized person who used the protected health information or to whom the disclosure was made;

(iii) Whether the protected health information was actually acquired or viewed; and

(iv) The extent to which the risk to the protected health information has been mitigated.

It is worth noting that this change also eliminates the existing regulatory exception for limited data sets that do not contain any dates of birth or zip codes. In the event of a breach including a limited data set, whether the data set contains dates of birth or zip codes is immaterial (though the type of information disclosed may play a role in the above-delineated risk assessment.

The Final Rule’s preamble provides ample discussion of each of the new risk assessment factors, along with examples. It is clear from the examples, however, that the OCR intends for the vast majority of breaches to be disclosed. In each explanation/example (which are too voluminous to list here) the guidance provided simultaneously refuses to provide “bright line” rules while also indicating that the standard of a “low probability that the protected health information is compromised” will be very difficult to meet. Finally, it is worth noting that the Final Rule does not provide a definition for compromised (which may make entities’ determination of the likelihood of compromise difficult indeed).

Notification to Individuals

The Final Rule retains the Interim Final Rule’s requirements for breach notifications without modification, but, provides some clarification on some of the finer points of when a breach is “discovered,” the timeliness of notification, methods of notification, the content of the notice, and other sub-topics. Important clarifications include:

  • The Final Rule noted that a covered entity that is acting as a business associate (by, for instance, providing billing or other services to another covered entity) should respond to a breach as a business associate. In these situations, the obligation to disclose will rest with the covered entity whose PHI is compromised.
  • The Final Rule clarified several points regarding alternative notice and made explicit that notice has not been given if a written notice is returned as undeliverable. Covered entities responding to a breach with more than 10 notifications returned as undeliverable may take some reasonable time to search for correct, current addresses for the affected individuals, but must provide substitute notice “as soon as reasonably possible” and within the original 60-day time frame for notifications.

Notifications to the Media

The Breach Rule’s treatment of media notifications is finalized with only a minimal change; since the definition of state was broadened to include American Samoa and the Northern Mariana Islands, the Breach Rule no longer references them directly. In addition, OCR clarified several points regarding media notifications, including:

  • Covered entities are not obligated to incur the cost of any media broadcast regarding the breach in question.
  • Media outlets are not obligated to publicize each and every breach notice they receive (and a failure to publicize does not render the notice provided insufficient).
  • Entities must deliver a press release directly to the media outlet being notified. Posting a general press release on a website, for instance, is insufficient.

Response to Additional Public Comments

Though it did not result in a change to any regulatory text, the Final Rule noted that “[b]ecause every breach of unsecured protected health information must have an underlying impermissible use or disclosure under the Privacy Rule, OCR also has the authority to impose a civil money penalty for the underlying Privacy Rule violation, even in cases where all breach notifications were [timely, compliantly] provided.” This statement clarifies that every breach carries with it the potential for OCR enforcement and civil penalties, regardless of the size or circumstances – a statement that may indicate more stringent enforcement activities to come.

Modifications to the HIPAA Privacy Rule Under GINA

The Final Rule finalizes proposed regulatory provisions implementing changes to HIPAA as a result of the Genetic Nondiscrimination Act of 2008 (GINA). These rule changes were first proposed in October 2009. The proposed rule is, for the most part, adopted without changes, with one rather large exception: the proposed rule’s expansion of entities covered by the changes (which included all health plans subject to the Privacy Rule) has been modified to exclude issuers of long-term-care policies. This change apparently reflects the fact that several comments were received indicating that long-term-care insurance may become financially infeasible without a reliance on genetic information to predict future health conditions. Each regulatory section adopted with noteworthy changes or guidance is discussed below.

Extension of Required Protections to All Health Plans Subject to the HIPAA Privacy Rule

As noted above, the Final Rule adopts the expanded application of the GINA provisions to all health plans subject to HIPAA but notably excludes issuers of long-term-care insurance. OCR responded specifically to claims that such an expansion was beyond its authority, noting that it has broad authority to regulate the use and disclosure of health information, including genetic information, in the interest of individuals’ privacy. The current decision to exclude long-term-care issuers, however, may not be permanent; the Final Rule notes that OCR will be conducting additional studies of the issue, including a study by the National Association of Insurance Commissioners (NAIC), and will reassess the inclusion of long-term-care issuers in the future.

Prohibition on use of Genetic Information for Underwriting

The underwriting prohibition is adopted without modification, save for the exemption of issuers of long-term-care insurance discussed above. Helpfully, the Final Rule includes several examples of how the prohibition would apply. 

Notice of Privacy Practices

The Final Rule adopts the provision obligating health plans that perform underwriting to include in their Notice of Privacy Practices a statement that the health plan is prohibited from using or disclosing genetic information for underwriting purposes. This change does not apply to issuers of long-term-care policies who for now, are exempted from the underwriting prohibition.

Response to Additional Public Comments

In addition to the above specific changes, OCR explained, in response to a public comment, that providers should understand that it is the responsibility of the health plan to abide by the underwriting prohibition. Providers who, for instance, are asked for information that meets the definition of genetic information are not obligated to confirm or ensure that the information will not be used for underwriting purposes. OCR noted, however, that the information requested by health plans remains subject to the minimum necessary standard.

Written by:

Baker Donelson

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