Open Source Software Licensing

McDonnell Boehnen Hulbert & Berghoff LLP

McDonnell Boehnen Hulbert & Berghoff LLP

For over 30 years, open source software (OSS) has formed the backbone of the technology industry. Today, it is nearly impossible to find a computing device that does not utilize an open source component. For example, the Linux kernel powers well over a billion devices. As the adoption of OSS accelerates, it is increasingly important to understand the history, legal issues, and future challenges of the open source world.

What is OSS?

OSS is computer software that is released under a specialized license that grants users permission to view, change, and redistribute the software. The actual source code of such software is “open” to the public.

The philosophy behind OSS can be traced back to the Free Software Movement of Richard Stallman.[1] A researcher at the MIT Artificial Intelligence Laboratory in the early 1980s, Stallman pioneered the leading open source license of the time: the GNU general public license (GPL).[2] Stallman challenged traditional proprietary licenses through GPL by establishing software that could be developed communally and collaboratively, while guaranteeing the rights of end-users to modify and redistribute the source code.

Shortly after GPL, the Open Source Initiative (OSI) was formed to spread the open source philosophy. OSI developed the “Open Source Definition,”[3] which includes the following core principles:

  1. Free Redistribution: The license shall not restrict any party from selling or giving away the software as a component of an aggregate software distribution containing programs from several different sources.
  2. Source Code: The program must include source code, and must allow distribution in source code as well as compiled form.
  3. Derived Works: The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software.
  4. Integrity of The Author’s Source Code: The license may restrict source-code from being distributed in modified form only if the license allows the distribution of “patch files” with the source code for the purpose of modifying the program at build time.
  5. No Discrimination Against Persons or Groups: The license must not discriminate against any person or group of persons.
  6. No Discrimination Against Fields of Endeavor: The license must not restrict anyone from making use of the program in a specific field of endeavor.
  7. Distribution of License: The rights attached to the program must apply to all to whom the program is redistributed without the need for execution of an additional license by those parties.
  8. License Must Not Be Specific to a Product: The rights attached to the program must not depend on the program’s being part of a particular software distribution.
  9. License Must Not Restrict Other Software: The license must not place restrictions on other software that is distributed along with the licensed software.
  10. License Must Be Technology-Neutral: No provision of the license may be predicated on any individual technology or style of interface.

Today, a wide variety of OSS licenses exist. OSI plays an important role in “verifying” new open source licenses to ensure that each license upholds the core tenants of the OSI definition. While most open source licenses follow OSI’s broad principles of granting users the permission to view, change, and redistribute the software, the way in which each license achieves these principles varies. Open source licenses can be grouped into permissive licenses and copyleft licenses.

Permissive licenses can be considered as “public domain” licenses. These licenses typically grant users the right to do what they please with source code, from repackaging the source code into another open source project to incorporating the source code into proprietary products. The only caveat of a permissive license is that correct attribution must be provided. When an author of an open source project releases their source software under a permissive license the author is given no guarantee for how the source code will be used and/or distributed in the future. Examples of widely-used permissive licenses include the MIT license,[4] the Apache license,[5] and Berkeley Software Distribution (BSD)[6] licenses.

Copyleft licenses allow users to view, change, or redistribute source code, but require that any derivative work from the source code uphold the copyleft license. More specifically, when an author of an open source project releases their software under a copyleft license, the author is given a guarantee that any derivative work of their software will also have a copyleft license. This aspect essentially turns copyleft licenses into a “viral license” in which all derivative works of an original open source project are “infected” and authors and users must adhere to the original license. Examples of widely-used copyleft licenses include the GNU General Public License (GPL).

“Weakly-protective” licenses exist as a compromise between the permissive and copyleft licenses. Weakly protective licenses generally prevent the licensed source code from becoming proprietary on its own, yet allow such source code to be incorporated as part of a larger proprietary program. Examples of widely-used weakly protective licenses include GNU Lesser General Public License (LGPL).[7]

Case Law Involving OSS

In one of the first major cases involving an OSS license, Jacobsen v. Katzer, the United States Court of Appeals for the Federal Circuit (CAFC) ruled that an open source “Artistic License” to copyrighted program code for controlling model trains was enforceable and the underlying copyright was infringed.[8] Furthermore, the CAFC held generally in Jacobsen that copyright holders who engage in open source licensing have the right to control the modification and distribution of the copyrighted material.[9]

More recently, in Artifex Software, Inc. v. Hancom, Inc., the Northern District of California cited Jacobsen as a basis to establish that royalty-free licensing under open source conditions does not preclude a claim for damages with a decision that stated a “jury can use the value of the commercial license as a basis for any damages determination.”[10] Additionally, in Artifex, the district court ruled that GPL-licensed code can be treated like a legal contract, and developers can sue if the obligations of these licenses are not followed.[11]

Such decisions have supported the enforceability of OSS licenses and suggest that potential copyright infringers ignore the terms of such licenses at their peril.

OSS and Patents

In the United States, OSS can be protected under both copyright and patent law. Whereas copyright protects the underlying expression of source code (i.e., the originality and creativity underlying the way the source code is written), patents can protect the source code’s functionality and the utility and/or design in which it influences the outside world. Because OSS licenses grant user rights under copyright, open source licenses do not inherently bar an original author (or a secondary author using the source code provided by the original author) from obtaining protection on patentable aspects of the source code.

However, in light of the decisions described above, why would one want to obtain a patent on OSS or derivative software that carries a corresponding OSS license? As an example, an original author may desire to assert patent rights against infringers who are not using OSS subject to the OSS license, but different, independently created, software that is nonetheless infringing the author’s patent right. Accordingly, a patent holder could potentially assert patent rights against an infringer who uses independently-developed software that utilizes a patented concept, regardless of whether the source code is subject to an open source license.

Additionally, the original author may desire to market or provide a non-open source licensed version of a software product, such as many dual-license software products.[12] For example, such software products may be released under a proprietary license and an open source license. The open source version can be provided for free, with the aforementioned caveat that any subsequent product using the software must include the open source license. The proprietary version may be sold to businesses looking to incorporate the software into their own proprietary products.

In an effort to protect contributors from such legal discrepancies between copyrights and patents, many open source licenses have explicit clauses that address would-be patentees. For example, the GNU GPL[13] explicitly states:

You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.

In such cases, under the purported terms of the license, an inventor who distributes source code under the GNU GPL cannot assert her own patent rights against subsequent users of the GNU GPL source code.

In a further effort to deter would-be patentees, some open source licenses include clauses that terminate a licensee’s rights to use the OSS if the licensee asserts a patent infringement claim relating to the use of the OSS. Such provisions are often referred to as “patent retaliation clauses.” As an example, Section 8 of the Apache 2.0 license states:[14]

If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

Due to the complexity of modern software projects, patent holders may be completely unaware of OSS embedded into their systems. Accordingly, such patent retaliation clauses can become a substantial risk for patentees intending to assert their software patent. For example, suppose that an enterprise constructs a product that is a derivative of software covered by an open source license with a patent retaliation clause. Then, suppose that the enterprise obtains a patent on the features they added to the derivative work. If the enterprise sues a third-party for patent infringement, the license to distribute the enterprise’s own software (a derivative work of the original software covered by the open source license with a patent retaliation clause) could be revoked under the terms of the OSS license because the enterprise asserted their patent on their derivative work. Under such a hypothetical scenario, the enterprise who merely attempted to assert their patent right may lose the right to distribute their own product.

The Future of OSS

OSS has created enormous value throughout the software industry. One open source project’s success has become the bedrock of another project’s innovation. However, for the OSS model to continue, viable business models must exist to reward creators and maintainers of OSS.

Currently, the software industry is experiencing a shift towards a software as a service (SaaS) paradigm. Above all, the shift has ushered in the era of cloud providers: large organizations who offer computational resources to run the software in production environments. With this paradigm, owning hardware, not software, becomes the engine of wealth creation. So, rather than paying a maintainer of an open source project, the price of using OSS is now more closely tied to the price of paying a cloud provider to execute the OSS. For this reason, many cloud providers are now “open source friendly” (and even belong to a non-aggression Open Invention Network[15]) because they directly benefit from the use of OSS in their cloud environments without having to bear any of the engineering costs of maintaining or upgrading the OSS. However, the open source authors do not directly benefit and typically rely on revenue from “enterprise tier” infrastructure solutions to fund operations and the continued development of OSS.

Many organizations are creating specialized open source licenses to address these issues. MongoDB, a database software company that “open sources” most of their products, has shifted to a Server Side Public License (SSPL)[16] to exclude cloud providers. Specifically, the SSPL requires that those who provide an SSPL product in a hosted platform must also make available their infrastructure code for the hosted platform available under an open source license. This infrastructure code would include things such as provisioning systems or anything that might be required for another company to create a clone of the hosting service. Similarly, Redis Labs, another database software company, has shifted to the Redis Source Available License (RSAL), which precludes Redis software from being used as a database, a caching engine, a stream processing engine, a search engine, an indexing engine, or a machine learning/deep learning/artificial intelligence serving engine. [17]

As the dominance of cloud providers continues, we can expect to see more new open source licenses that focus on fair compensation for the creators and maintainers of OSS.


OSS has evolved to fit the various and disparate needs of the technology industry. OSS licenses have provided a way for its authors and innovators to control how the OSS will be used in the future. With only a few court cases decided relating to OSS licenses, this will be an interesting area of law to follow moving forward.

Additionally, the rise of cloud providers has drastically changed open source models for many technology companies. With the next waves of technological change coming along soon, such as autonomous vehicles, Blockchain, and IoT, newer, more complex open source licenses may be drafted, and argued in the courts, to protect the interests of software innovators and the OSS community.

[1] Brian W. Carver, Share and Share Alike: Understanding and Enforcing Open Source and Free Software Licenses, 20 Berkeley Tech. L.J. 443, 443 (2005).

[2] Id. at 447; see also What is GNU?, GNU Operating System, (last updated May 7, 2019).

[3] See Carver, supra note 1, at 449; see also The Open Source Definition, Open Source Initiative, (last updated Mar. 22, 2007).

[4] The MIT License, Open Source Initiative, (last visited May 23, 2019).

[5] Apache License, Version 2.0, Apache, (last visited May 23, 2019) (hereinafter “Apache License”).

[6] The 3-Clause BSD License, Open Source Initiative, (last visited May 23, 2019).

[7] GNU Lesser General Public License, GNU Operating System, (last updated Nov. 18, 2016).

[8] Jacobsen v. Katzer, 535 F.3d 1373, 1381 (Fed. Cir. 2008).

[9] Id.

[10] Artifex Software, Inc. v. Hancom, Inc., No. 16-CV-06982-JSC, 2017 WL 4005508, at *3 (N.D. Cal. Sept. 12, 2017).

[11] Id. at *6.

[12] Multi-licensing, Wikipedia, (last updated Feb. 8, 2019).

[13] GNU General Public License, GNU Operating System, (last updated Nov. 18, 2016).

[14] See Apache License, supra note 5.

[15] Members, Open Invention Network, (last visited May 23, 2019).

[16] Server Side Public License, mongoDB (Oct. 16, 2018),

[17] Redis Source Available License Agreement, Redis Labs, at 1 (Mar. 20, 2019), available at

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.

© McDonnell Boehnen Hulbert & Berghoff LLP | Attorney Advertising

Written by:

McDonnell Boehnen Hulbert & Berghoff LLP

McDonnell Boehnen Hulbert & Berghoff LLP on:

Readers' Choice 2017
Reporters on Deadline

Related Case Law

"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 (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

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

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:

JD Supra Cookie Guide

As with many websites, JD Supra's website (located at (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
  • New Relic - For more information on New Relic cookies, please visit
  • Google Analytics - For more information on Google Analytics cookies, visit To opt-out of being tracked by Google Analytics across all websites visit 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 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:

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