Comments on CMS Proposed Rule on Medicaid Fiscal Accountability Due Feb. 1, 2020

Holland & Knight LLP
Contact

Holland & Knight LLP

Highlights

  • The Centers for Medicare & Medicaid Services (CMS) has published a proposed Medicaid Fiscal Accountability rule that would significantly amend existing regulations.
  • The amendments would have an impact on 1) base and supplemental payments, 2) Disproportionate Share Hospital (DSH) payments, 3) program financing, and 4) healthcare-related taxes and provider-related donations.
  • The deadline to submit comments in response to the proposed rule is Feb. 1, 2020. It is also foreseeable that Congress may attempt a legislative response to some of the proposed changes.

The Centers for Medicare & Medicaid Services (CMS) on Nov. 18, 2019, published a proposed Medicaid Fiscal Accountability rule that would amend existing regulations related to 1) base and supplemental payments, 2) Disproportionate Share Hospital (DSH) payments, 3) program financing, and 4) healthcare-related taxes and provider-related donations. CMS describes some changes as codifying existing guidance or clarifying current practices while they consider others to impose new procedural or substantive requirements.

The proposed changes are significant, including:

  • explicit delineation of tax and provider-related donation practices that would violate the prohibition on "hold harmless" arrangements
  • limitations on funding sources for intergovernmental transfers (IGTs)
  • limitations on how Certified Public Expenditures (CPEs) can be used
  • substantive change in the definition of entities considered government providers
  • greater stringency in calculating upper payment limits (UPLs) and creation of a new UPL cap applicable to practitioners
  • new and extensive state reporting/justification requirements for supplemental payment programs
  • changes that will constrain the scope of permissible healthcare-related taxes
  • numerous documentation, justification and information reporting requirements

The deadline to submit comments in response to the proposed regulation is Feb. 1, 2020. It is also foreseeable that Congress may attempt a legislative response to some of the proposed changes.

This Holland & Knight alert summarizes CMS' views regarding the need for the proposed changes (as discussed in the preamble to the proposed rules), as well as explains the substance of the proposed changes.

CMS Concerns

A. Supplemental Payments

With regard to supplemental payments (as distinct from base payments), CMS notes that the current ownership-based UPL categories allow individual institutions to receive Medicaid payments above the Medicare reasonable amount. They further note that the same is true of supplemental payments to practitioners because there is no UPL applicable to that group. CMS notes that it does not routinely examine the distribution of supplemental payments to individual providers, as current state reporting vehicles – CMS Form 64, the Medicaid Budget and Expenditure System (MBES) and Transformed Medicaid Statistical Information System (T-MSIS) – do not capture this data, and management reviews and audits are burdensome and not comprehensive. CMS indicates that it seeks to have a better understanding of the relationship between supplemental payments, costs, current UPLs, state financing of the non-federal share of supplemental payments, and the impact of supplemental payments on Medicaid. CMS also notes that the U.S. General Accountability Office (GAO) has recommended establishing facility-level reporting of supplemental payments, and that many such payments seem to target only those who participate in their financing.

B. Disproportionate Share Hospital Payments

CMS considers DSH payments to be neither base payments nor supplemental payments (given their separate statutory status). DSH payments are subject to state allotment limitations and hospital-specific limits enforced by audits. CMS' central concern is that it is often unable to determine if a particular provider was overpaid, the root cause of an overpayment or the amount. It also notes the Office of Inspector General (OIG) recommendation for the need to adjust future DSH payments to reflect actual incurred costs (through a process included in state plan amendments) and to include only allowable costs.

C. Medicaid Program Financing

After discussing the basic rules governing healthcare-related taxes, bona fide donations, IGTs and CPEs, CMS notes that states have become increasingly reliant on the use of these mechanisms by non-state units of government and that this could implicate the statutory requirement that states not lower the amount, duration, scope or quality of services due to the lack of funds from such local sources. CMS specifically calls out its concern regarding the use of complicated, unallowable financing arrangements involving public-private partnerships to mask non-bona fide provider-related donations as allowable IGTs. As discussed below, CMS is therefore proposing to require improved state reporting on supplemental payments and sources of the non-federal share; greater specificity in a variety of regulatory definitions and information to support various financing mechanisms; and addressing "egregious funding schemes that mask non-bona fide donations" by clarifying where indirect hold-harmless arrangements exist and by explicitly prohibiting "supplemental payments that support these schemes."

D. Healthcare-Related Taxes

CMS articulates several concerns related to taxes used to finance Medicaid programs. The first involves situations where a tax arrangement that is not broad-based or uniform nonetheless qualifies as being "generally redistributive" under the applicable regulatory tests – the "P1/P2" test employed for uniform taxes that are not broad-based or the "B1/B2" test for non-uniform taxes. CMS believes that states are implementing tax programs that meet these tests but nonetheless impose an undue burden on Medicaid. A second area of concern is that the regulatory definition of "health care-related tax" is not capturing all tax arrangements that should meet this definition, especially where a differential impact on Medicaid providers or payers is "masked" as part of a broader state revenue scheme. Third, CMS is concerned that states are using provider taxes in combination with various payment arrangements or understandings to violate the hold harmless rules. Finally, CMS is aware that a number of states are taxing health insurers who are not managed care organizations (MCOs) and that the existing permissible classes of healthcare items and services does not include insurers.

Specific Proposed Regulatory Changes

CMS proposes two dozen specific regulatory changes of varying significance.1 Significant items include the following:

A. State Share of Financial Participation: New IGT and CPE Requirements

1. Current Regulations

Title XIX requires that at least 40 percent of the state share of Medicaid financing must be state revenues and the remaining 60 percent can be derived from local sources. Current regulations (42 CFR 443.51) require that the state share be either:

a) funds that are directly appropriated to the state Medicaid agency

b) funds that are transferred from other public agencies to the state Medicaid agency ( (IGTs), or

c) funds that a public agency expends and certifies were used for Medicaid-eligible expenditures (CPEs).

2. IGT-Related Changes

The proposed rule would replace the term "public" with "state and local" and make other IGT-related changes to this section as follows.

  • Local IGT funds would need to derive from state or local taxes (or funds appropriated to a state university teaching hospital). There is no current requirement that a public agency identify the transferred funds to a tax source.
  • An IGT would be considered an impermissible non-bona fide provider-related donation if it is "contingent upon the receipt of funds by, or ... actually replaced in the accounts of the transferring agency" with funds from an unallowable source.

3. CPE-Related Changes

As for CPEs, new specific certification requirements (and substantive use limitations) are imposed under a proposed new regulatory section (42 CFR 447.206). Reimbursement to such providers may not exceed their actual cost using reasonable cost allocation principles that track federal cost accounting rules or Medicare cost principles. The state must establish and implement documentation and audit protocols, and only the certified amount may be claimed for Federal Financial Participation (FFP). In addition, the certifying entity must receive and retain the full amount of the FFP associated with the CPE. Finally, the certifying entity cannot be paid in excess of the amount attributable to services to Medicaid beneficiaries.

B. Bona Fide Donations/Provider Related Donation: Clarifying Existence of Hold Harmless Arrangements

1. Current Regulations

Medicaid regulations (42 CFR 433.54) define the term "bona fide donation" as provider-related donations that are not returned to the donor under a hold harmless arrangement. Among other things, a hold harmless arrangement can exist when the recipient provides to the donor a payment, offset or waiver that directly or indirectly guarantees return of all or a portion of the donation to the donor.

2. Clarifying Existence of Hold Harmless Guarantee

The proposed regulation adds additional language to Section 42 CFR 443.54(c)(3) to make clear that "such a guarantee will be found to exist where, considering the totality of the circumstances, the net effect of an arrangement between [the state or local government] and the provider ... results in a reasonable expectation that the provider, provider class or a related entity will receive a return of all or a portion of the donation ... regardless of whether the arrangement is reduced to writing or is legally enforceable ..."

"Net effect" is defined as "the overall impact of an arrangement, considering the actions of all of the entities participating in the arrangement, including all relevant financial transactions or transfers of value, in cash or in kind, among participating entities." Net effect is to be determined by considering the "totality of the circumstances, including the reasonable expectations of the participating entities, and may include consideration of reciprocal actions without regard to whether the arrangement or a component of the arrangement is reduced to writing or is legally enforceable by any entity" (Proposed 42 CFR 433.52).

3. Clarifying Scope of Activities Comprising Provider-Related Donations

The proposed regulation also substantially amends the existing definition of a "provider-related donation" (42 CFR 422.52) to clarify the scope of captured transactions. The proposed addition indicates that "any transfer of value where a health care provider or provider-related entity assumes an obligation previously held by a governmental entity and the governmental entity does not compensate the private entity at fair market value will be considered a donation made indirectly to the governmental entity." The obligation need not constitute a legally enforceable obligation to be considered a donation. Rather, this will be determined by examining the totality of the circumstances and the arrangement's net effect.

4. Presumption Based on Organizational Revenues

Finally, the proposed rule, as part of changes to the definition of "provider-related donation" would create a presumption based on the amount of an organization's revenues that are derived from providers and/or provider-related entities. Where such amount exceeds 25 percent of the organization's revenue, the organization always will be considered as acting on behalf of healthcare providers if it makes a donation to the state, and the amount of such donation that will be considered to be a provider-related donation will be based on the percentage of the organization's revenue during the relevant fiscal year that was received as donations from providers or provider-related entities. Where the amount is below 25 percent, donations will not generally be presumed to be provider-related donations. It should be noted that this is not a "safe harbor" provision but merely a presumption.

C. Upper Payment Limit-Related Provisions

The proposed rule makes significant changes related to UPLs. It adds a new Subpart D to 42 CFR 447 (proposed sections 284, 286, 288 and 290) that redefines the hospital groupings used for UPL calculations, imposes new substantive and reporting requirements regarding those calculations, requires extensive reporting on supplemental payments and creates penalties for reporting non-compliance.

1. Changes to Public/Private Hospital Definition

CMS is proposing to revise and tighten the definitions governing public and non-public hospitals (proposed 42 CFR 447.286). Going forward, the three categories of hospitals for UPL purposes would be "state government providers," "non-state government providers" and "private providers." This replaces the existing construct that asks whether the entity is "owned or operated" by a state, locality or private interest. CMS indicates that it is concerned that the existing regulations create ambiguities. It mentions the example of a private nursing home that transfers its deed to a governmental entity, thereby obtains governmental status without any other meaningful change in operations or revenue sources, and then has its lease payments to the government treated as IGTs.

To be considered a non-state government provider, the entity would need to be a "unit of local government ... which has access to and exercises administrative control over [appropriated] state funds and/or local tax revenue including the ability to expend such ... funds." Non-state government provider status will be determined based on the totality of the circumstances, including (but not be limited to) consideration of:

  • whether any entity other than the provider shares the responsibility for ownership or operation of the provider (giving consideration to decision-making authority, legal responsibility for risk from losses, authority over operational revenue, control of personnel (e.g., hiring/dismissal), tax liability and responsibility for payment of malpractice premiums)
  • the "character" of the entity (giving consideration to whether it is described in communications as a unit of government, whether the state considers it governmental solely for Medicaid purposes, and whether it "has access to and exercises control over" appropriated funds and/or local tax revenue)

The considerations applicable to a totality of the circumstances analysis to determine state governmental provider status are very similar.

2. UPL Reasonable Cost Calculations/Reporting

The second major change in the proposed rule affecting UPL is the imposition of new and much more specific requirements governing the calculation of costs for the purpose of determining a reasonable estimate of what Medicare would pay a UPL group of facilities for Medicaid items and services. Under proposed 42 CFR 447.288, the state would be required each year to submit a "demonstration of compliance" with the applicable UPL limit for inpatient, outpatient, skilled nursing facility (SNF), immediate care facility (ICF) and institution for mental disease (IMD) services. The proposed rules would require the use of specific data sources (including for cost purposes either a Medicare cost report, state cost report based on Medicare cost principles or 45 CFR Part 75 cost allocation rules), methodology parameters and acceptable UPL demonstration methodologies (either cost- or payment-based).

3. Supplemental, DSH, Provider Contribution and Related Information Reporting

Additionally, on each quarterly CMS-64, the state must report granular, provider-specific information regarding supplemental payments and, on an annual basis, aggregate provider-specific data on such payments as well as information on provider base payments, total Medicaid payments, total DSH payments, Medicaid units of care furnished and other information. This also includes reporting on provider-specific contributions to supplemental payments, including CPEs, IGTs, donations and healthcare-related taxes.

4. New UPL for Practitioners

As noted above, there is no existing UPL for practitioners, and some states make supplemental payments to practitioners (usually physicians). CMS is proposing to create a new UPL for practitioner services and to limit supplemental payments to practitioners to 50 percent of FFS base payments to the eligible provider, or 75 percent in the case of services provided within a Health Resources and Service Administration (HRSA) Health Professions Shortage Area (HPSA).

D. Supplemental Payments: State Plan Requirements

CMS is proposing to amend existing regulations (42 CFR 447.252) governing state plan amendments (SPAs) to more closely oversee supplemental payments. First, approval of SPAs as they pertain to supplemental payments would be limited to three years after which a renewal would be required. Second, an SPA proposing supplemental payments would need to provide extensive information, including an explanation of consistency with current law, the purpose and intended effects of the payment, and the criteria used to determine provider eligibility for the payment. Additionally, the SPA must include a description of the methodology used to calculate the amount and distribution of the payment to eligible providers that includes information on a list of required items (including the payment amount to each eligible provider, and the specific criteria for service, utilization or cost data used to calculate the amount or distribution of payments). The state must further provide assurances that applicable UPLs will not be exceeded, amonitoring plan and, for renewals, an evaluation of program impacts during the prior approval period.

E. Healthcare-Related Taxes

CMS proposes tax-related changes in several sections (42 CFR 433.55, 433.56, 433.68, 433.72).

1. Undue Burden

To ensure that a tax is "generally redistributive" under waiver-related tests (42 CFR 433.68), CMS proposes to add a further level of examination to determine whether a tax that is determined to be generally redistributive under existing tests nonetheless imposes an "undue burden" on the Medicaid program. This would essentially be defined as a tax that imposes a higher burden on groups that have higher levels of Medicaid activity than it does on other taxed groups. A tax would be considered to impose undue burden if taxpayers are divided into taxpayer groups and any of the following conditions apply.

  • The tax excludes or places a lower tax rate on any taxpayer group based on a lower level of Medicaid activity.
  • Within each taxpayer group, the tax rate imposed on any Medicaid activity is higher than the tax rate imposed on any non-Medicaid activity (except as a result of excluding from taxation Medicare or Medicaid revenue).
  • The tax imposes a lower tax (or no tax) on a taxpayer group with no Medicaid activity unless all entities within the no-Medicaid activity group either furnish no services within the class in the state, do not charge any payer for services within the class, are federal providers of services or are units of government.
  • The tax imposes a lower tax rate (or no tax) on a group that is defined based on any commonality that CMS "reasonably determines" can serve as a proxy for the group having no or relatively low Medicaid activity.

2. Differential Treatment

CMS is proposing to change the definition of a healthcare-related tax in 42 CFR 433.55(c) to address taxes that are not solely applicable to healthcare entities, providers or payers but where there is some form of "differential treatment" of such healthcare interests. The proposed changes clarify that differential treatment exists in tax programs where some of those providing or paying for healthcare items or services are selectively included but others are not, as well as where some pay more than others. In making these determinations, CMS will look at the parameters of the tax ("the grouping of individuals, entities, items or services" on which the tax is imposed) and the totality of the circumstances. The new regulation would specifically prohibit "selective incorporation" of some healthcare interests but not others, or applying a higher rate to healthcare interests for a generally applicable tax (e.g., a business tax).

3. Hold Harmless Arrangements

To address the relationship between healthcare-related taxes and hold harmless arrangements, CMS would evaluate using a "net effect" standard (see related discussion above pertaining to donations). A direct or indirect hold harmless guarantee would be found to exist where, considering the totality of the circumstances, the net effect of any arrangement between the state or other unit of local government and the tax payer results in a reasonable expectation that the taxpayer would receive a return of some or all of the tax amount. This would apply regardless of whether the arrangement was written or legally enforceable.

4. Health Insurers as a Class

CMS is amending the defined classes of healthcare services and providers (42 CFR 433.56) to permit states and localities to tax the services of health insurers, separately and in addition to the current class of managed care organizations (which may not only be Medicaid MCOs).

F. DSH Audit Reporting Requirements

To improve financial integrity, CMS is proposing that states include a new audit data element as part of the existing requirement for annual DSH reporting (42 CFR 447.299) that requires auditors to quantify the estimated financial impact of any audit finding related to whether a hospital may have received DSH payments in excess of its limit. In addition, states would be required to report identified overpayments in a more timely manner on the CMS-64.

G. Retention of Payments

A new section (proposed 42 CFR 447.207) is added to require that, regardless of the payment methodology used by a state, it must permit the provider to retain the full amount of the total computable payment for services under the state plan (or waiver/demonstration if applicable). In enforcing this provision, the Secretary will examine any "associated transactions" (which may include administrative fees paid to the state for processing claims or IGTs or hold harmless arrangements) to ensure that the state's claimed expenditure is equivalent to its net expenditure. CMS indicates that some states have been charging fees for processing provider Medicaid claims which serves as a de facto provider tax and should be paid for with Medicaid administrative funds.

H. Prohibitions on Varying Provider Reimbursement

A new provision, proposed 42 CFR 447.201(c), would explicitly provide that a state plan could not vary FFS payment to providers for Medicaid services based on a beneficiary's Medicaid eligibility category, enrollment under a waiver or demonstration, or federal matching rate available for services provided to a beneficiary's eligibility category. CMS intends to make clear that variation in payment based on FFP is inequitable and is prohibited. It notes that this does not prohibit variations in payment based on cost considerations.

 

Notes

1 Several minor items are not discussed in this alert.

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.

© Holland & Knight LLP | Attorney Advertising

Written by:

Holland & Knight LLP
Contact
more
less

Holland & Knight 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.