IRS answers some, but not all, questions in long-awaited cryptocurrency guidance

Proskauer - Tax Talks

Proskauer - Tax Talks

The first official guidance on the taxation of cryptocurrency transactions in more than five years has been issued.

The guidance includes both a Revenue Ruling (Rev. Rul. 2019-24, 2019-44 I.R.B. 1) and answers to Frequently Asked Questions on Virtual Currency Transactions (the “FAQs,” together with Revenue Ruling 2019-24, the “Guidance”) was issued on October 9, 2019 by the U.S. Internal Revenue Service (the “IRS”).  The Guidance provides much sought information concerning the tax consequences of cryptocurrency “hard forks” as well as acceptable methods of determining tax basis for cryptocurrency transactions.  The Guidance also reasserts the IRS’s position, announced in Notice 2014-21, 2014-16 I.R.B. 938, that cryptocurrency is “property” for U.S. federal income tax purposes and provides information on how the rules generally applicable to transactions in property apply in the cryptocurrency context.  However, important questions remain unanswered.  It remains to be seen whether more definitive regulatory or administrative guidance is forthcoming.

The Guidance comes amidst an ongoing campaign by the IRS to increase taxpayer compliance with tax and information reporting obligations in connection with cryptocurrency transactions.  In 2017, a U.S. district court ordered a prominent cryptocurrency exchange platform to turn over information pertaining to thousands of account holders and millions of transactions to the IRS as part of its investigation into suspected widespread underreporting of income related to cryptocurrency transactions.  Earlier this year, the IRS sent more than 10,000 “educational letters” to taxpayers identified as having virtual currency accounts, alerting them to their tax and information reporting obligations and, in certain cases, instructing them to respond with appropriate information or face possible examination.  Schedule 1 of the draft Form 1040 for 2019, released by the IRS shortly after publishing the Guidance, would require taxpayers to indicate whether they received, sold, sent, exchanged, or otherwise acquired virtual currency at any time during 2019.[1]

Taxpayers who own or transact in cryptocurrency or other virtual currency should consider carefully any tax and information reporting obligations they might have.  Please contact the authors of this post or your usual Proskauer tax contact to discuss any aspect of the Guidance.  Read the following post for background and a detailed discussion of the Guidance.

Except where the context indicates otherwise, the tax consequences discussed in this post generally apply to transactions involving cryptocurrency held by a taxpayer as a capital asset.  This post does not consider tax consequences other than U.S. federal income tax consequences.


The Guidance describes a “virtual currency” as “a digital representation of value that functions as a medium of exchange, a unit of account, and a store of value,” other than a representation of the U.S. dollar or the official legal currency of a foreign country (referred to in IRS guidance as “real” currency).  The term “virtual currency” as used in the FAQs includes digital currency, cryptocurrency, and any other asset having “the characteristics of virtual currency,” regardless of name, but is limited to virtual currencies that have an equivalent value in, or act as a substitute for, real currency (referred to as “convertible” virtual currencies).[2]

The Guidance defines a “cryptocurrency” as a virtual currency that uses encryption to secure transactions digitally recorded on a distributed ledger (for example, a blockchain, DAG, or Tempo).  Although this blog specifically considers transactions involving cryptocurrency, certain of the rules discussed may apply to other forms of “convertible” virtual currency.

Tax consequences of “hard forks”: gross income inclusion depends on whether new cryptocurrency units are “received” by the taxpayer

Revenue Ruling 2019-24 specifically addresses the tax implications of a so-called “hard fork,” i.e., a change in the protocol (or software) of a cryptocurrency’s blockchain[3] that causes the new blockchain to permanently split off from the existing or “legacy” blockchain.  Where the protocol on the legacy blockchain continues to be utilized by the legacy cryptocurrency, the result is two unique cryptocurrencies, each with its own blockchain, but sharing a common (pre-“fork”) history.  In some hard forks, units of the new cryptocurrency are distributed to the distributed addresses of some or all of the account holders at the time of the split (referred to here as the “legacy holder”).  The IRS refers to this type of distribution as an “airdrop.”

The immediate tax implications of a hard fork to a legacy holder under the Revenue Ruling depend on whether the holder “receives” units of the new cryptocurrency.  The determination of receipt is based, in turn, on whether the new cryptocurrency has been distributed to the legacy holder and, if so, whether the taxpayer exercises sufficient “dominion and control” over the new units.[4]

If cryptocurrency units are distributed to a taxpayer via an airdrop (and the distribution occurs by reason of the taxpayer’s holding of the legacy cryptocurrency at the time of the fork)[5], the taxpayer generally will be considered to receive the units at the same date and time as the associated airdrop is recorded on the new blockchain, provided the taxpayer also has dominion and control over the units at that time.  A taxpayer is considered to exercise dominion and control for this purpose if it has the ability to transfer, sell, exchange, or otherwise dispose of the units.  In contrast, a taxpayer that is unable to transfer, sell, exchange, or dispose of the new units—for example, because the taxpayer’s wallet does not support the new cryptocurrency or the taxpayer holds its units on an exchange platform that does not support the new cryptocurrency—will not have dominion and control (and will not be considered in receipt of the cryptocurrency at the time of the airdrop).  In the event the taxpayer later acquires the ability to transfer, sell, exchange, or dispose of the new cryptocurrency, the taxpayer will be treated as “receiving” the cryptocurrency at that later date.  Although the Revenue Ruling indicates that other types of transfers may cause a taxpayer to be treated as receiving units created in the hard fork, the specific facts of the ruling only consider transfers via airdrop.  The Revenue Ruling similarly indicates that a taxpayer may “constructively receive” cryptocurrency units prior to their airdrop into the legacy holder’s digital wallet, but does not provide any examples.

A legacy holder that does not actually (or constructively) receive units of the new cryptocurrency (i.e., because they are neither airdropped nor otherwise transferred to an account owned or controlled by the taxpayer) is not required to recognize income from a hard fork.

The amount of a taxpayer’s gross income resulting from a hard fork will generally equal the fair market value of the new units at the time they are received by the taxpayer (in general, the time the airdrop is recorded on the new blockchain, provided the taxpayer has dominion and control over the new units).  A taxpayer cannot apply any of its basis in the legacy cryptocurrency to reduce the amount of income recognized on receipt of the new units.  While the Revenue Ruling does not provide guidance as to how fair market value is to be determined for this purpose, the FAQs indicate that the IRS will accept value calculated by a blockchain explorer (such as CoinMarketCap) based on an analysis of worldwide cryptocurrency indices as of a specific date and time.[6]  A taxpayer that does not rely on the value provided by a blockchain explorer will have the burden of establishing value.

The Revenue Ruling also confirms that gross income recognized in a hard fork will be ordinary, without regard to the taxpayer’s holding period in the legacy cryptocurrency units.  While this treatment follows from general tax principles (for example, the taxation of lottery winnings and other forms of “free” money), it may come as a surprise (and a disappointment) to taxpayers expecting all gains or losses from cryptocurrency held as a long-term investment to be capital (and perhaps hoping to use other capital losses to offset any gain recognized as a result of a fork).  The taxpayer’s basis in the new cryptocurrency will equal the units’ fair market value at the time of their receipt (generally, the amount of taxable income reported by the taxpayer).  Although the Revenue Ruling does not specify, presumably the taxpayer’s holding period begins on the day after it is received.[7]

Note that the facts of the Revenue Ruling specifically state that, following the hard fork, transactions involving the legacy cryptocurrency continued to be recorded on the legacy blockchain.[8]  Neither the Revenue Ruling nor the FAQs expressly considers the situation where the hard fork results in all transactions moving to the new blockchain with the protocol of the legacy blockchain then abandoned.  Where only a single blockchain is maintained following the hard fork, it may be more appropriate to treat this as a “soft” fork (i.e., changes in the protocol of a blockchain that do not cause a new cryptocurrency to be formed), which the FAQs indicate would not give rise to taxable income.[9]  Where transactions  actually do continue to occur on the legacy blockchain following the hard fork (as under the facts of Situation 2 of the Revenue Ruling), there is nevertheless a risk of character (and timing) mismatches should the legacy cryptocurrency decline in value as a result of the fork.  Although not inevitable, devaluation of the legacy cryptocurrency, either as a result of perceived dilution or because of doubt about the survival of the legacy protocol, is certainly possible, particularly in the context of a contentious or “experimental” fork.[10]  Whereas a taxpayer would recognize ordinary income upon receipt of the new units (whether or not sold), loss on the legacy units generally would not be recognized until a sale or other disposition, and any such loss would be capital rather than ordinary.

Determining basis in units sold or exchanged: specific identification or first-in, first-out (FIFO)

In order to calculate the taxable gain or loss realized upon a sale or exchange of cryptocurrency, a taxpayer must determine its basis in the units sold.  Prior to the release of the Guidance, there was significant uncertainty surrounding the determination of basis and holding period where the taxpayer acquired units of cryptocurrency at different times and/or at different prices.

The FAQs apply rules of identification similar to those applicable to transactions in stocks and securities.  By default, a taxpayer is treated as having sold its earliest-acquired units first, known as the “first-in, first out,” or “FIFO,” method.[11]  However, if the taxpayer is able to “specifically identify” the units that are sold, exchanged, or otherwise disposed of in the transaction and can substantiate the basis in those units, it can use its actual basis in the specific units identified (generally, the cost to acquire those units).[12]  The FAQs indicate that specific identification may be accomplished either by documenting the specific unit’s or units’ unique digital identifier (e.g., a private or public key and an address) or by providing records showing all transaction information for all units of a specific cryptocurrency held in a single account, wallet, or address.  The documentation must show (1) the date and time each unit was acquired, (2) the basis and the fair market value of each unit at the time it was acquired, (3) the date and time each unit was sold, exchanged, or otherwise disposed of, and (4) the fair market value of each unit at the time of its sale, exchange, or other disposition and the amount of money or the value of property received for each unit.[13]  Specific identification will also apply to the determination of the taxpayer’s holding period for purposes of determining whether any capital gain or loss recognized upon the sale or exchange is long-term or short-term.[14]

Guidance concerning determination of fair market value and other issues

Because cryptocurrency is treated as property for tax purposes, the tax consequences of a number of transactions involving cryptocurrency depend on the fair market value of the cryptocurrency.  These include (but are not limited to) the amount of wage or self-employment income a taxpayer reports for compensation received in the form of cryptocurrency, the amount of a taxpayer’s charitable deduction if appreciated cryptocurrency is donated to charity, the amount of gain or loss recognized when cryptocurrency is sold for cash, and the amount of loss recognized by a taxpayer on the sale or disposition of cryptocurrency received as a gift.

The FAQs provide that the fair market value of cryptocurrency received in a transaction over an exchange platform is equal to the amount recorded by the platform for that specific transaction expressed in U.S. dollars.  Where the transaction is “facilitated” by an exchange platform but is not recorded on the blockchain (an “off-chain” transaction), the fair market value is the trading price of the cryptocurrency on that exchange as of the date and time the transaction would have been recorded on the blockchain had it been an “on-chain” transaction.[15]  For other transactions not conducted on an exchange, the taxpayer may rely on the price provided by a blockchain explorer (discussed above) for the applicable date and time, or else must establish that another value is an “accurate representation” of the cryptocurrency’s fair market value.[16]  The fair market value of cryptocurrency received in exchange for property or services that is not traded on any exchange platform and does not have a “published value” is deemed to be equal to the fair market value of the services or property exchanged for the cryptocurrency at the time of the exchange.[17]  While Notice 2014-21 required that a taxpayer determine fair market value as of the date of the transactions, the FAQs indicate that this determination must be made as of the specific date and time of a transaction, a subtle change that may have a material impact given the historic volatility of cryptocurrency trading prices over even the course of a single day.

Notice 2014-21 did not discuss specifically charitable donations of cryptocurrency or the receipt of cryptocurrency as a gift.  The FAQs confirm that, consistent with cryptocurrency’s treatment as property for tax purposes, no gain or loss is recognized by a taxpayer on the donation of cryptocurrency assets to a charitable organization or on the receipt of cryptocurrency as a gift.[18]

The FAQs also confirm that a taxpayer generally will not recognize gain or loss on transfers of cryptocurrency between different wallets or accounts on different exchange platforms that are owned by the same taxpayer.[19]

Additional guidance forthcoming?

The Guidance is silent on a number of topics, including of the tax consequences of transactions involving non-currency blockchain assets and “simple agreement for future token,” or “SAFT” arrangements, initial coin offerings, and token-based compensation awards; the tax treatment of mining activities, including the circumstances in which mining will constitute a trade or business; the tax consequences to an “issuer” of cryptocurrency in a hard fork; the tax and reporting consequences to non-US persons investing in, or engaging in other transactions involving, cryptocurrency; or the treatment of cryptocurrency assets and transactions under the subpart F or passive foreign investment company rules.  It is also unclear whether the “receipt” principle announced in Revenue Ruling 2019-24 applies to cryptocurrency airdrops outside of the hard fork context—for example, unsolicited or “promotional” airdrops distributed to holders of other cryptocurrencies as part of a marketing campaign.

The Guidance notably does not contain a “de minimis” threshold for reporting gain or loss from cryptocurrency transactions.  Absent such a threshold, taxpayers may find cryptocurrency unappealing or impractical as a medium of exchange for spot transactions, such as buying a cup of coffee or leaving a tip for a server, all of which would have to be reported to the IRS (and may result in taxable income to the consumer) under the existing guidance.

[1]              IRS Form 14457, “Voluntary Disclosure Practice Preclearance Request and Application” (March 2019), also contains a box for taxpayers to indicate if the disclosure involves “Virtual Currency Issues.”

[2]              Examples of convertible virtual currencies identified by the IRS include Bitcoin, Ether, Roblox, and V-bucks.  See

[3]              Although we use the term “blockchain,” the concepts discussed should apply to any type of distributed ledger technology.  The facts of the Revenue Ruling do not specify the type of distributed ledger used.

[4]              See also Commissioner v. Glenshaw Glass Co., 348 U.S. 426 (1955) (generally defining “income” as an accession to wealth that is clearly realized and over which a taxpayer has complete dominion and control); section 61(a)(3).

[5]              The facts of Situation 2 of the Revenue Ruling state that the taxpayer received the new cryptocurrency “solely because” of its ownership of the legacy cryptocurrency at the time of the fork.

[6]              If the taxpayer held its legacy units on an exchange platform at the time of the airdrop of new units (and assuming the taxpayer has the requisite dominion and control for this to be a “receipt” of those units), it may be appropriate to use the closest exchange price reported by the platform, if available.  See FAQs, Question 25 (the fair market value of cryptocurrency received in a transaction over an exchange platform is the amount recorded in U.S. dollars by the platform).

[7]              See FAQs, Question 28 (holding period for cryptocurrency begins the day after it is “received”); Fogel v. Commissioner, 203 F.2d 347 (5h Cir. 1953) (a taxpayer’s holding period excludes the date of acquisition).

[8]              Question 21 of the FAQs is similarly limited to hard forks that result in the creation of a new cryptocurrency “in addition to” the legacy cryptocurrency.

[9]              See FAQs, Question 29.  This is consistent with the nonrecognition rule applicable to exchanges of common stock for common stock in the same corporation.  See section 1036(a) of the Code; Treas. Reg. § 1.1036-1(a).

[10]             In 2016, the developers of Ethereum caused a hard fork in the Ethereum protocol after a glitch enabled the theft of 3.6 million units of its cryptocurrency, Ether.  Most (but not all) users abandoned the legacy protocol, with the result that within hours, legacy Ether (renamed Ether Classic) was trading at only 1/10 of the trading price of “new” Ether.  As of this writing, transactions continue to occur on both the new and legacy blockchains.

[11]             FAQs, Question 38.

[12]             FAQs, Question 36.

[13]             FAQs, Question 37.

[14]             FAQs, Question 37.

[15]             FAQs, Question 25.

[16]             FAQs, Question 26.

[17]             FAQs, Question 27.  If cryptocurrency is used by a taxpayer to pay for services or property, the FAQs confirm that the gain or loss recognized by the taxpayer on the exchange will generally equal the difference between the taxpayer’s basis in the units exchanged and the fair market value of the property or services received in the exchange.  See FAQs, Questions 14, 16.

[18]             See FAQs, Questions 30-34.

[19]             FAQs, Question 35.

[View source.]

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.

© Proskauer - Tax Talks | Attorney Advertising

Written by:

Proskauer - Tax Talks

Proskauer - Tax Talks 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 (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.