More Egregious Aggregation Under ERISA in the Sun Capital Partners Case? The District Court Goes Down Yet Another Road

by Dechert LLP
Contact

The recent opinion by the U.S. District Court for the District of Massachusetts on remand from the U.S. Court of Appeals for the First Circuit in the Sun Capital Partners case may be troubling to private equity funds and other investment funds that invest in portfolio companies with significant liabilities under the Employee Retirement Income Security Act of 1974 (“ERISA”). As we previously discussed in a 2013 OnPoint, under the First Circuit’s decision in 2013, an investment fund that owns 80% or more of a portfolio company may effectively be aggregated with the portfolio company for ERISA purposes and share its ERISA liabilities, depending on whether the fund is considered a “trade or business” based on the relevant facts and circumstances. 

Now, under the District Court’s recent decision, even an investment fund that owns less than 80% of a portfolio company may effectively be aggregated with the portfolio company and share its ERISA liabilities if, based on certain relevant facts and circumstances, the fund is deemed to have created a partnership-in-fact with a related fund, such that the funds’ ownership interests are aggregated for purposes of satisfying the 80% threshold. The District Court’s thinking is that the deemed partnership is aggregated with the portfolio company, and then the funds share the liability of the deemed partnership under general partnership principles. 

The District Court’s reliance on this deemed-partnership approach to reach a result that was expressly rejected by the First Circuit on other grounds could be of concern to those private equity funds and other investment funds with similar investment structures and activities as those involved in Sun Capital Partners. However, while the District Court’s rationale is troubling, the decision is from a lower court, and it is not at all clear that a Circuit Court (including the First Circuit) would agree with the District Court’s novel approach.

Background

Private equity and similar funds sometimes invest in portfolio companies that may have significant liabilities under ERISA and the employee-benefits provisions of the Internal Revenue Code of 1986 (the “Code”). For example, a company may have a substantially underfunded defined benefit pension plan or significant potential withdrawal liability under a multiemployer pension plan.

A lurking question that has persisted is whether, if a fund’s ownership interest in a portfolio company exceeds a certain percentage threshold, the fund and the portfolio company are aggregated as a single employer for certain liability and other purposes under ERISA and the Code. ERISA and the Code provide in general terms that the 80%-or-more affiliated group of corporations or “trades or businesses,” commonly referred to as a “controlled group,” may effectively be aggregated and viewed as a single employer.

The aggregation question is a critical one, as liabilities under ERISA and the Code can in some cases be very significant. The effects of aggregation under ERISA and the Code may include, among other things:

  • joint and several liability under the ERISA provisions applicable to defined benefit pension plans governing funding and plan termination and the rules governing withdrawal liability to a multiemployer pension plan;
  • imposition of certain excise taxes on all applicable affiliates jointly and severally;
  • application of nondiscrimination and other rules applicable to employee benefit plans on a controlled-group basis; and
  • responsibility for “COBRA” compliance on a controlled-group basis.

The aggregation question for investment funds has attracted increasing attention ever since the release of a September 26, 2007 letter (the “PBGC Letter”) from the Appeals Board of the Pension Benefit Guaranty Corporation (the “PBGC”). The PBGC has general administrative responsibility under the ERISA provisions applicable to the termination of defined benefit pension plans and withdrawal liability to multiemployer pension plans. 

The specific aggregation provision that applies for purposes of the withdrawal liability rules and which was at issue in Sun Capital Partners is Section 4001(b)(1) of ERISA, which provides that, “under regulations prescribed by the [PBGC], all employees of trades or businesses (whether or not incorporated) which are under common control shall be treated as employed by a single employer and all such trades and businesses as a single employer.” For many funds, the analysis under the withdrawal liability and other ERISA controlled-group rules can turn, in part, on the critical threshold question of whether a particular investment fund is a “trade or business” for these purposes. 

If the fund is not a “trade or business,” aggregation may not be required, regardless of whether the fund has sufficient ownership interest in a portfolio company to be considered to be under “common control” with the portfolio company. The PBGC Letter concluded that the private equity fund there at issue was a “trade or business” under Section 4001(b)(1) of ERISA, and that certain of its subsidiaries should be considered, together with such fund, to be a single employer under ERISA. 

Sun Capital Partners v. N.E. Teamsters and Trucking Industry Pension Fund

In Sun Capital Partners, a number of affiliated investment funds (collectively, the “Sun Funds”) formed a limited liability company (an “LLC”) to indirectly acquire a particular portfolio company (the “Portfolio Company”). One of the Sun Funds, “Sun Fund III” (which consisted of two parallel funds), owned 30% of the LLC and another Sun Fund, “Sun Fund IV,” owned the other 70%, such that Sun Fund III and Sun Fund IV together indirectly owned 100% of the Portfolio Company. Shortly after the acquisition by the Sun Funds, the Portfolio Company went bankrupt. In connection with its bankruptcy, the Portfolio Company withdrew from the multiemployer plan (the “Multiemployer Plan”) of which it was a member. As a result, the Portfolio Company incurred withdrawal liability to the Multiemployer Plan of approximately US$4.5 million. The Multiemployer Plan sought to collect the liability from both the Portfolio Company and the Sun Funds, based on the ERISA aggregation rules noted above. The Sun Funds filed a declaratory judgment action in federal district court in Massachusetts, seeking a declaration that they were not subject to withdrawal liability to the Multiemployer Plan on the bases that: (i) the Sun Funds were not part of a joint venture or partnership and therefore did not meet the “common control” requirement for ERISA aggregation; and (ii) neither of the Sun Funds was a “trade or business” that could be properly aggregated with the Portfolio Company under ERISA. 

The District Court’s Initial Decision and the First Circuit’s Decision on Appeal

In October 2012, the U.S. District Court for the District of Massachusetts granted summary judgment in favor of the Sun Funds, finding that neither of the Sun Funds was a “trade or business” as intended by ERISA. In doing so, the District Court squarely rejected the PBGC Letter’s approach to the “trade or business” question. The District Court did not need to reach the other condition that must be satisfied to impose withdrawal liability on the Sun Funds, i.e., the question of whether either Sun Fund was under “common control” with the Portfolio Company.  

In July 2013, the First Circuit reversed the District Court’s decision on the “trade or business” issue. The First Circuit held that, when evaluating whether an investment fund is a “trade or business” for purposes of the ERISA aggregation rules, courts should use some form of an “investment plus” analysis that considers a number of factors. However, the First Circuit declined to set forth specific factors that would be included in the “plus” part of the “investment plus” analysis. Applying the “investment plus” standard to the Sun Funds’ investment in the Portfolio Company, the First Circuit determined that Sun Fund IV was a “trade or business” because, in part, its “active involvement in management” provided it with a “direct economic benefit.” Specifically, the fees paid by the Portfolio Company to an affiliate of Sun Fund IV’s general partner for its management services were used to offset management fees that Sun Fund IV otherwise would have owed its general partner. The First Circuit was unable to determine, however, whether Sun Fund III received similar management fee offsets, and remanded the case to the District Court to make that determination. The First Circuit also directed the District Court to determine whether the Sun Funds were under “common control” with the Portfolio Company in order to obligate the Sun Funds for the Portfolio Company’s ERISA withdrawal liability.1

The District Court’s Decision on Remand

On remand, the District Court first addressed whether Sun Fund III was a “trade or business.” After a detailed review of Sun Fund III’s management fee arrangements, the Court determined that the management fees Sun Fund III otherwise would have owed its general partner were indeed offset by the fees that the Portfolio Company paid to an affiliate of the Sun Fund III’s general partner. Therefore, the District Court concluded that the “trade or business” prong of the controlled-group withdrawal liability test under ERISA was satisfied with respect to Sun Fund III. The District Court also rejected the Sun Funds’ contention that the First Circuit had erroneously held that Sun Fund IV was a “trade or business.” 

After determining that both Sun Funds were involved in a “trade or business” for purposes of ERISA, the District Court moved onto the “common control” question. The District Court determined that, although each Sun Fund’s respective ownership stake in the Portfolio Company was under 80%, both Sun Funds were ultimately liable for the Portfolio Company’s withdrawal liability. In order to reach such determination, the District Court proceeded to create a deemed partnership between the two Sun Funds over the LLC, as further discussed below. 

The District Court, using an approach urged by the Multiemployer Plan, determined that the two Sun Funds had together created a partnership-in-fact to invest in the Portfolio Company, even though the Sun Funds had indeed created an actual LLC to acquire the Portfolio Company. In this regard, the District Court found that a partnership-in-fact between the Sun Funds existed largely on the basis that they engaged in “joint activity” prior to deciding to co-invest in the Portfolio Company through an LLC. The District Court noted that this “joint activity” covered “at least the period” before the acquisition was completed and “would appear to extend” through the operation of the Portfolio Company. The District Court also viewed the 70%/30% split between the two Sun Funds as a choice showing “an identity of interest and unity of decisionmaking between the [Sun] Funds rather than independence and mere incidental contractual coordination,” and as an investment structure stemming from “top-down decisions to allocate responsibilities jointly . . . and offer advantages to the Sun Funds group as a whole.” The Court further observed that there was “no meaningful evidence of actual independence” between the Sun Funds in their co-investments because the Sun Funds did not show, for example, that they sometimes co-invested with each other but also co-invested with other unaffiliated entities, or that they had any disagreements with respect to the Portfolio Company’s operations. Rather, the District Court found that the “smooth coordination [was] indicative of a partnership-in-fact sitting atop the LLC: a site of joining together and forming a community of interest.” 

The District Court proceeded to determine that the partnership-in-fact was a “trade or business” for ERISA purposes. To characterize the partnership as a “trade or business,” the District Court relied on the same facts that led to its finding that the Sun Funds were trades or businesses, stating:

Like the Sun Funds, the partnership’s purpose is to make a profit, an important factor in determining “trade or business” status, although an insufficient one. Additionally, the partnership was involved in the active management of the portfolio companies that the First Circuit found critical. For example, the First Circuit found it important that the Sun Funds’ purpose is “to seek out potential portfolio companies that are in need of extensive intervention” and that “restructuring and operating plans are developed for a target portfolio company even before it is acquired.” This period of joint investigation and action prior to the formation of an LLC is central to the work of the partnership itself – it is an important piece of why I find a partnership-in-fact to exist – and so is highly indicative of that partnership being a trade or business. 

. . . . 

For precisely the same reasons as the Sun Funds are trades or businesses, the partnership or joint venture formed between them is so as well. 

Having held that the deemed partnership with respect to the Sun Funds was a trade or business, which owned 100% of the Portfolio Company, the deemed partnership then became aggregated with the Portfolio Company for ERISA purposes, thereby causing the deemed partnership to be jointly and severally responsible for the LLC’s ERISA liability, and in turn, for the Portfolio Company’s withdrawal liability. Having now gotten the withdrawal liability to the deemed partnership, the District Court then pushed the liability up to Sun Fund III and Sun Fund IV under general partnership principles, as they were partners in the deemed partnership that the District Court had discovered.

It is worth noting that the First Circuit in its 2013 decision expressly rejected the Multiemployer Plan’s claim under Section 4212(c) of ERISA that the Sun Funds had engaged in a transaction to evade or avoid withdrawal liability and that, therefore, the 70%/30% split should be disregarded for purposes of ERISA aggregation. In relevant part, the First Circuit stated:

This is simply not a case about an entity with a controlling stake of 80% or more under the MPPAA seeking to shed its controlling status to avoid withdrawal liability. As such, disregarding the agreement to divide ownership of [the LLC] would not leave us with Sun Fund IV holding a controlling 80% stake in [the Portfolio Company]. The Sun Funds are not subject to liability pursuant to [Section 4212(c) of ERISA] and the district court's conclusion that they are not is affirmed. 

The District Court’s finding of a partnership-in-fact under its “common control” analysis is a new analytical route to cause each Sun Fund to be responsible for the ERISA liability of the Portfolio Company, notwithstanding that neither Sun Fund reached the 80% ownership threshold.2

Conclusion

By inserting a partnership-in-fact in the investment structure specifically designed to avoid the 80% threshold, the District Court creates the possibility that any number of affiliated funds could be deemed to have created a partnership and effectively be subject to the ERISA liabilities of their portfolio companies. Unfortunately, the District Court decision is a high-profile case that does impose responsibility on investment funds for the ERISA liabilities of a company in which the funds invest. As a result, funds and their sponsors may want to consider the District Court’s approach in Sun Capital Partners as they structure their investments where the portfolio companies in which they invest are 80%-or-more owned by affiliated funds. However, the decision is merely one at the District Court level, and indeed, is being appealed and may be reversed. Additionally, courts in other circuits that have not yet considered this issue may well be presented in the future with the opportunity to analyze the issue for themselves, and otherwise to give the matter their own careful and critical review. Thus, it should not by any means be assumed that the novel rationale put forth by the District Court in Sun Capital Partners will ultimately carry the day.

Footnotes

1) It is noted that both the District Court and the First Circuit on appeal collapsed the two parallel sub-funds comprising Sun Fund III as a single fund for purposes of addressing the issues involved in the decisions. The collapsing of these two sub-funds as such could potentially be of significant concern to sponsors of similarly structured fund complexes.

2) Under a straight ERISA-driven aggregation analysis, the concern is that both the fund (if a trade or business) and its 80%-or-more portfolio companies all share the ERISA liabilities of each of the 80%-or-more portfolio companies. It is interesting to note that, under the District Court’s view, since the funds’ liability is under general partnership law, the various portfolio companies might not share each other’s ERISA liabilities, unless any one fund owns 80% or more of the multiple portfolio companies.

 

Written by:

Dechert LLP
Contact
more
less

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