ESMA’s Final Draft Disclosure Technical Standards

by Cadwalader, Wickersham & Taft LLP

Cadwalader, Wickersham & Taft LLP


On 22 August 2018, the European Securities and Markets Authority (“ESMA”) published its Final Report on the technical standards on disclosure requirements under the EU Securitisation Regulation[1] (the “Final Report”)[2]. This annexed final draft technical standards on the disclosure requirements under the Securitisation Regulation (the “draft Disclosure Technical Standards”) (consisting of draft Disclosure RTS[3] and draft Disclosure ITS[4]).

The December 2017 Consultation

The draft Disclosure Technical Standards follow on from ESMA’s consultation paper dated 19 December 2017 and the draft technical standards annexed to that consultation (the “December Consultation Paper”). They incorporate comments made in feedback to the December Consultation Paper and arising from a public hearing on the proposed technical standards in February 2018.

ESMA has noted that the second part of its December Consultation Paper, relating to operational standards and access conditions for information made available to securitisation repositories, will now be included in a second batch of documents that will deal with ESMA’s mandates regarding securitisation repositories.

Legislative Background

The Securitisation Regulation was published in the Official Journal of the European Union on 28 December 2017 and entered into force on 17 January 2018. The Securitisation Regulation will be directly applicable law across the EU and will apply to securitisations, the securities of which are issued (or where no securities are issued, the securitisation positions of which are created), from 1 January 2019. We commented on the obligations that will arise under the Securitisation Regulation in our Clients and Friends Memorandum dated 26 October 2017[5].

Other Technical Standards prepared under the Securitisation Regulation

ESMA’s draft Disclosure Technical Standards are part of the various technical standards prepared by ESMA and the European Banking Authority (“EBA”) pursuant to mandates contained in the Securitisation Regulation. We commented on the draft Regulatory Technical Standards (“RTS”) published by the EBA in respect of the Securitisation Regulation’s risk retention requirements in our Clients and Friends Memoranda dated 21 December 2017[6] and 31 July 2018.

Transparency Obligations in the Securitisation Regulation

Transparency Obligations in the Securitisation Regulation – reporting entity

Article 7 of the Securitisation Regulation contains the transparency requirements and directs the originator, sponsor and Securitisation Special Purpose Entity (“SSPE”) (i.e. the special purpose vehicle) of a securitisation to make certain prescribed information relating to the securitisation available to investors, national regulators and, upon request, to potential investors. These entities must designate one of them to fulfil the disclosure requirements (the “reporting entity”).

Transparency Obligations in the Securitisation Regulation – Information to be Provided Before Pricing

Under Article 7 the information to be made available includes: (ii) documentation disclosure (i.e. prescribed transaction documentation); (iii) a transaction summary for “private securitisations”[7] (please see below); and (iv) in the case of STS[8] securitisations, the STS notification.

This information is to be made available before pricing[9]. The timing of the transaction documentation disclosure obligation will potentially be problematic given that documents are typically still in draft form, and often incomplete, at the time of pricing. Furthermore, Article 22(5) of the Securitisation Regulation, which relates to STS securitisations only, requires the information to be made “available before pricing at least in draft or initial form”. There does not seem to a clear basis for this apparently less onerous obligation for STS securitisations. In its Final Report, ESMA acknowledges this issue and has said that, although it falls outside ESMA’s technical mandates, it has ensured that this issue has been passed on to the responsible legislative bodies.

Transparency Obligations in the Securitisation Regulation – Ongoing Reporting Obligations

The ongoing reporting obligations include: (i) quarterly[10] asset level disclosure (i.e. information on the underlying exposures) (the “Underlying Exposures”) (ii) quarterly[11] investor reports containing prescribed information (“Investor Reports”); (iii) any inside information relating to the securitisation that the reporting entity[12] is obliged to make public under the Market Abuse Regulation[13] (“Inside Information”); and (iv) even where it is not inside information, any material breach of the obligations laid down in the documents, any material change in the structural features or risk characteristic of the securitisation, or any material amendment to transaction documents (“Significant Events”).

The quarterly Investor Reports must contain: (i) all materially relevant data on the credit quality and performance of underlying exposures; (ii) information on events which trigger changes in the priority of payments or the replacement of any counterparties, and data on the cash flows generated by the underlying exposures and by the liabilities of the securitisation[14]; and (iii) risk retention compliance information.

The information on Underlying Exposures and in the Investor Reports is to be made available simultaneously each quarter at the latest one month after the due date for the payment of interest[15].

The annex to this memorandum summarises these reporting obligations in diagrammatic form.

Transparency Obligations – Securitisation Repositories

Securitisation repositories are to be established to which prescribed information relating to the securitisation is to be provided by the reporting entity. Those repositories, which are to be registered with ESMA, will collect details of the securitisation and will provide direct and immediate access free of charge to the EU supervisory authorities, to investors and to potential investors. Where no securitisation repository is registered, the reporting entity shall make the information available by means of a website that meets certain prescribed conditions.

Reporting Obligations and Private Securitisations

There is an exemption from reporting to the repository (but not from the rest of the reporting requirements) for “private securitisations” (i.e., those where a Prospectus Directive compliant prospectus has not been drawn up). Recital 13 to the Securitisation Regulation, explains that, in light of the possibility for sensitive commercial information being present in the transaction, private securitisations should be exempted from the requirement to notify information to a securitisation repository. A Prospectus Directive compliant prospectus does not have to be drawn up for admission to trading on markets such as the Irish Global Exchange Market.

In its Final Report ESMA said that it had conducted additional legal analysis and that its interpretation of the Securitisation Regulation was that the technical standards covering the Underlying Exposures and Investor Reports “appear to apply” to all securitisations (i.e. both public and private securitisations). At the same time, ESMA understands that its Article 17 mandates (see below) appear to apply only to public securitisations (which are required to report information to a securitisation repository).

The Draft Disclosure Technical Standards

Legislative Basis of the Disclosure Technical Standards

Article 7(3) of the Securitisation Regulation directs ESMA to develop draft RTS and Implementing Technical Standards (“ITS”)[16] to specify the information that the reporting entity shall provide in order to comply with their reporting obligations.

In addition, Article 17 mandates ESMA to draft technical standards specifying the information and standardised templates that should be provided by the reporting entity to comply with the information requirements of Article 7.

The Securitisation Regulation directed ESMA to submit these draft Disclosure Technical Standards to the European Commission by 18 January 2019. The finalised technical standards are then to be adopted by the Commission by way of a delegated regulation. However, ESMA has recognised that the technical standards need to be adopted by the Commission prior to the date of application of the Securitisation Regulation on 1 January 2019 and has brought this to the Commission’s attention (see also below)[17].

Securitisations subject to the Disclosure Technical Standards

In its December 2017 Consultation Paper, ESMA identified three categories of transactions: (a) securitisations with any securities issued from 1 January 2019 onwards (“new securitisations”); (b) securitisations with all securities issued on or before 31 December 2018, that seek to obtain STS status (“legacy STS securitisations’); and (c) securitisations with all securities issued on or before 31 December 2018, that do not seek to obtain STS status (‘legacy non-STS securitisations’). New securitisations and legacy STS securitisations must comply with the Disclosure Technical Standards[18], However, in its December 2017 Consultation Paper, ESMA notes that legacy non-STS securitisations “appear” to be exempt from disclosure requirements[19].

Concerns Raised in Feedback to the December Consultation Paper

ESMA has highlighted some of the concerns raised in responses to the December Consultation Paper. Respondents raised the jurisdiction issue (discussed below) and the requirement to provide documentation prior to pricing (discussed above). ESMA has made clear that both of these issues are outside the scope of its mandate in preparing the draft Disclosure Technical Standards.

Other points raised in the feedback to the December Consultation Paper related to; (i) the suitability of the templates to non-bank/non-original lender originators; (ii) the potential impact of the transitional provisions; (iii) the need for templates appropriate for CLOs; and (iv) the “no data” options. These points are discussed below.

ESMA’s Draft Disclosure Technical Standards and the Templates

ESMA’s Draft Disclosure Technical Standards consist mainly of extensive reporting templates reflecting the categories of information in the Securitisation Regulations ongoing reporting obligations. There are therefore templates for: (a) Underlying Exposures; (b) Investor Reports; (c) Inside Information; and (d) Significant Events.

ESMA’s Draft Templates for Underlying Exposures

Of these templates, those for Underlying Exposures[20] are likely to have the most significant impact for market participants.

The templates are based on previous work in this area. In 2014 ESMA prepared draft RTS (subsequently adopted) containing loan-level requirements for specified ABS[21] pursuant to the CRA3 Regulation[22]. The European Central Bank (“ECB”) has also already prepared templates as part of it ABS loan-level initiative[23]. These existing ECB templates were used as a starting point for ESMA’s templates.

The Underlying Exposures template distinguish between ABCP and non-ABCP securitisations. For the latter, ESMA’s Underlying Exposure templates cover the following underlying exposure types: (a) residential mortgages; (b) commercial real estate; (c) corporate exposures (including loans to SMEs as well as large corporates); (d) auto loans/leases; (e), consumer loans; (f) credit card receivables; and (g) leasing. ESMA has developed a further template for “esoteric” underlying exposures that do not fall within any of these categories. ESMA has also developed an additional add-on template for non-performing exposure (“NPE”) securitisations. Another template exists for ABCP securitisations.

Reporting for CLOs

Many respondents to the December Consultation Paper proposed that a separate reporting template be prepared for CLOs[24], or that the Corporate Underlying Exposures template be modified so as to make it appropriate for CLOs. It was pointed out that the templates should be appropriate for non-bank originators, as well as for bank originators, and that the templates should be suitable for reporting entities who are not original lenders (please see below). ESMA has taken this feedback on board and has taken the view that the Corporate Underlying Exposures template should be adapted for CLOs.

ESMA commented on respondents’ concerns that some information would not be available to CLO managers, as it would only be held by the original lender such as the jurisdiction of the originator/original lender, origination channel of a loan, its origination date, and its original principal balance. ESMA is of the view that such information[25] is important for potential investors to perform their due diligence, as well as for investors and public authorities to meet their monitoring tasks and, therefore, should always be available. ESMA said that “although such information may be challenging to retrieve at first, then by the time that the reporting requirements fully apply, it appears that this information would be able to be made available in a sufficiently broad manner”.

In its Final Report, ESMA explained that it had set out the following arrangements in its draft Disclosure Technical Standards regarding CLO securitisations:

  1. CLO securitisations should complete the applicable Underlying Exposure template for each underlying exposure in the pool (this would normally be the Corporate Underlying Exposures template);
  2. CLO securitisations should also complete an additional securitisation information section, which contains fields of particular relevance for due diligence and monitoring of CLO securitisations. These include information on the type of CLO, on the current stage of the CLO securitisation (e.g. warehousing, ramp-up, reinvestment, post-reinvestment/wind-down), as well as numerous fields to capture in a standardised manner key possible restrictions on the CLO manager’s actions.
  3. CLO securitisations should also complete an additional CLO manager information template, for each CLO manager, including information on the size of the CLO manager in terms of assets under management, capital, employees, as well as its operational arrangements (e.g. pricing frequency and time needed for settlement) and the performance of its CLO securitisation-related investments in recent years.
  4. There is not a separate template for CLOs, but the draft template for Significant Events annexed to the draft Disclosure Technical Standards contains a “CLO Securitisation information section” and a “CLO Manager information section”.

ESMA’s Draft Templates for Investor Reports

Separate Investor Report templates have been created for ABCP and for non-ABCP securitisations.

ESMA’s Draft Templates for Inside Information and Significant Events

As part of the information to be made available for all “public securitisations” (as opposed to that for “all securitisations”) under the draft Disclosure RTS, reference is made to templates for the Inside Information that the reporting entity has made public and for the information on Significant Events that the reporting entity is to make available under the Securitisation Regulation[26]. It therefore appears that these reporting templates do not apply to private securitisations. For the Significant Event templates, ESMA has stated that it has placed particular emphasis on the need to report further details regarding a change in the structural features of the securitisation, or a change in its risk characteristics or its underlying exposures.

Concerns Raised in Feedback Regarding Non-Bank/Non-Original Lender Originators

An important concern raised by respondents to the Consultation was that many of the data fields in the templates annexed to the December Consultation Paper were written in terms that assumed that the originator is a bank. This will not always be the case. Originators may also be entities that have purchased loans on the secondary market and have then securitised them (known as “limb (b) originators”) in the context of the risk retention obligation). It was pointed out that compliance with the reporting obligations in the templates should be practicable for reporting entities who are not original lenders and that the templates should be designed so that all types of originator can comply, and not solely bank originators.

ESMA’s response in its Final Report noted the need to ensure that the securitisation disclosure requirements sufficiently catered for the features of non-bank originators. ESMA made certain adjustments to take this into account. ESMA also noted its view that securitisation disclosure requirements should preserve a level playing field between non-bank originators (particularly those having purchased loan portfolios from original lenders) and bank originators.

“No Data” Options in the Templates

Several respondents to the December Consultation Paper suggested additional “no data” options for the templates. ESMA rejected these suggestions and confirmed that there are five “no data” options in the templates:

  1. ND1: data not collected as not required by the lending or underwriting criteria;
  2. ND2: data collected on underlying exposure application but not loaded into the originator’s reporting system;
  3. ND3: data collected on underlying exposure application but loaded onto a separate system from the originator’s reporting system;
  4. ND4 - data collected but will only be available from specified date; and
  5. ND5: “not applicable”.As regards information not being available because it has been transferred from the original lender to the originator, ESMA considers it important that original lenders make sufficient efforts to collect similar information on loans to avoid risks of circumvention of these reporting requirements via the use of original lenders.
  6. Similarly, ESMA considers that allowing loans originated prior to the entry into force of the Disclosure Technical Standards to avoid reporting certain fields would also not be sufficient to capture the requirements in the Securitisation Regulation. As regards “new securitisations”[28], ESMA considers that the draft Disclosure Technical Standards are being published with a sufficient lead time to allow originating banks to begin collecting the necessary information with a view to issuing securitisation transactions from 1 January 2019 and that, consequently, the case for a “no data” option in this situation is not strong.
  7. ESMA has clarified that the use of the “no data” options should be limited to certain fields in the templates. It has said that the ND1 to ND4 “no data” options should only be used in legitimate cases of information not being available. ESMA has said that the use of these options in reporting underlying exposures information in a securitisation “is expected to be extremely limited” and that under no circumstance should they be used as an exemption from the reporting requirements. “No data” options ND1 to ND4 could potentially be used in certain fields in the Underlying Exposure templates, but not in the remaining templates (i.e., the Investor Reports, Inside Information, and Significant Events templates). ESMA has said that greater flexibility is given on the use of the ND5 “no data” option (i.e. “not applicable”) throughout all of the templates[27], although there are also specific fields where there appears to be no reasonable case for the required information to be “not applicable”.

Transitional Issues

Concerns on the Securitisation Regulation’s Transitional Provisions

The Final Report said that respondents had highlighted that the draft Disclosure Technical Standards need to be adopted prior to the 1 January 2019 application date of the Securitisation Regulation so as to reduce the possibility of the Securitisation Regulation’s transitional provisions[29] applying, which would result in market participants having to implement two sets of templates: i.e., those under the Disclosure Technical Standards and those under Article 8b of the CRA3 Regulation. As noted above, ESMA has already alerted the Commission to this issue.

ESMA’s Proposed Transitional Period for Implementation

ESMA has noted that respondents have emphasised the need for sufficient time to adapt to the proposed reporting requirements. ESMA has said that it does not have a legal mandate to propose a transitional period for the implementation of the Disclosure Technical Standards. However, ESMA understands that compliance with the Disclosure Technical Standards may require substantial time and effort. Although ESMA makes clear that is a matter for the Commission, it proposes a transition period for the implementation of the Disclosure Technical Standards so that they could apply in a gradually increasing manner. ESMA considers that 15-18 months appear to be necessary as a transition period. This is a welcome proposal for market participants who would otherwise have very little time to develop the reporting systems necessary to comply with these requirements. We will need to see if the Commission acts on ESMA’s proposal.

The Jurisdictional Scope of the Transparency Obligations

The Jurisdictional Scope of the Obligations in the Securitisation Regulation

The transparency obligations are not expressly stated to be restricted to EU-established originators, sponsors and SSPEs and so appear to have a potential extra-territorial effect (in that they could apply to non-EU established originators, sponsors and SSPEs). Furthermore, these obligations may apply on a consolidated basis to non-EU subsidiaries as a result of the consolidation provisions in the Capital Requirements Regulation[30] (“CRR”) (please see below).

There is an argument that Article (5)(1)(e) of the Securitisation Regulation, which requires investors to verify compliance with the transparency obligations, does not apply where there is no EU originator, sponsor, original lender or SSPE (“non-EU Securitisation”) because arguably such originator, sponsor, original lender and SSPE do not have an obligation to provide such information pursuant to Article 7 of the Securitisation Regulation. However, even if the market view is that Article 5(1)(e) of the Securitisation Regulation does not apply to an EU institutional investor investing in a non-EU securitisation, EU institutional investors are still required to carry out a due diligence assessment under Article 5(3) of the Securitisation Regulation and to satisfy their continuing obligations under Article 5(4) of Securitisation Regulation. The receipt of information corresponding to that to be provided under Article 7 of the Securitisation Regulation is something that an EU institutional investor may look for in that regard. Effectively, the increased reporting required by Article 7 of the Securitisation Regulation in respect of EU securitisations will likely increase the level of information that EU institutional investors need to consider prior to investing in a non-EU securitisation.

Jurisdictional Consequences of the Consolidated Application of the CRR

We mentioned in our Clients and Friends Memoranda dated 26 October 2017 and 31 July 2018 that an issue that has caused widespread concern in the industry is the extent of the applicability of certain obligations (including the transparency requirements) in the Securitisation Regulation as a result of changes to the CRR. Article 14 of the CRR as amended by Article 1(11) of the CRR Amendment Regulation[31] applies the transparency requirements (as well as the risk retention, due diligence, the “criteria for credit-granting” obligations, and the ban on re-securitisation) under the Securitisation Regulation to EU institutions subject to the CRR, on a consolidated basis. As a result of this amendment to Article 14 of the CRR, the transparency requirements could therefore apply on a consolidated basis to a non-EU subsidiary of an EU bank. Such a subsidiary would have to comply both with the EU transparency requirements and with any locally applicable rules. Those requirements could have significant implications for EU banks operating in third countries through subsidiaries.

It appears that the application of such requirements to non-EU subsidiaries of EU banks was an unforeseen consequence of the changes to the CRR. It looks likely that further amendments will be made to the CRR, the effect of which would be that Article 14 of the CRR would only apply the Securitisation Regulation’s due diligence requirements (and not its transparency requirements or other obligations) on a consolidated basis. However, these further changes to Article 14 of the CRR would be made as part of the overall package to amend the CRR known as “CRR II”, and it is currently not clear that these further amendments would apply from the application date of the Securitisation Regulation, 1 January 2019.

ESMA’s Comments on the Jurisdictional Issues in its Final Report

In its Final Report, ESMA referred to these jurisdictional points having been raised in the feedback to its December Consultation Paper. ESMA is aware of the issues concerning the geographical scope of the disclosure requirements, where the originator, sponsor, and/or original lender[32] is located outside of the EU and the application of disclosure requirements to consolidated entities outside of the EU as a result of the amendments to Article 14 of the CRR. ESMA has said that, although these points fall outside its technical mandates, it has ensured that these issues have been passed on to the responsible legislative bodies.

Next Steps and Conclusion

The draft Disclosure Technical Standards will now be submitted to the Commission, who will adopt the Disclosure Technical Standards by way of delegated EU legislation.

ESMA has listened to the concerns of market participants as regards the contents of the draft Disclosure Technical Standards. Nevertheless, the practical difficulties of complying with these new reporting obligations are likely to be significant and the relevant reporting entities will have to start preparing both their back-office function and their advisors to address those reporting changes. Some market participants have questioned whether the benefits to be gained from the collection of this vast amount of data (a net increase of 516 reporting fields compared with current ECB templates[33]) will justify the resulting compliance costs and will indeed be used by investors.

As noted above, ESMA has highlighted the need for the technical standards to be adopted by the Commission as soon as possible, in view of the transitional provisions of the Securitisation Regulation, to avoid market participants having to implement two sets of templates[34]. ESMA has also proposed a 15-18 month transition period for implementation. It is to be hoped that the Commission will follow ESMA’s advice on these points.

Cadwalader has assisted the Loan Market Association in engaging with ESMA as regards issues arising from the December draft of the Disclosure Technical Standards and will continue to engage with ESMA and the EU legislative institutions as regards concerns with the Securitisation Regulation’s transparency regime.



The originator, sponsor and SSPE of a securitisation are required to make the following disclosures to holders of a securitisation position, competent authorities and, upon request, to potential investors.


Originator, sponsor and SSPE are to designate one of them to fulfil the disclosure requirements.

Disclosure obligations are satisfied by submitting information to a registered “securitisation repository” the identity of which must be disclosed in the securitisation documentation (save for “private securitisations” i.e. where no Prospectus Directive compliant prospectus is required).

Disclosure obligations are to comply with national and EU law governing the protection of confidentiality (but competent authorities may request such information). Obligations also take account of contractual confidentiality requirements.

ESMA has developed draft technical standards for asset level disclosure, quarterly/monthly reporting, inside information and significant events.


[1]   Regulation (EU) 2017/2402 of the European Parliament and of the Council of 12 December 2017 laying down a general framework for securitisation and creating a specific framework for simple, transparent and standardised securitisation, and amending Directives 2009/65/EC, 2009/138/EC and 2011/61/EU and Regulations (EC) No 1060/2009 and (EU) No 648/2012.


[3]  Draft regulatory technical standards specifying the information and the details of a securitisation to be made available by the originator, sponsor and SSPE.

[4]   Draft implementing technical standards with regard to the format and standardised templates for making available information and details of a securitisation by the originator, sponsor and SSPE.



[7]   Also known as “private transactions”

[8]   “Simple, transparent and standardised”

[9]    Although please see below for STS securitisations

[10] Monthly for asset-backed commercial paper (ABCP).

[11] Monthly for ABCP

[12] The originator, sponsor or SSPE.

[13] Regulation (EU) No 596/2014 of the European Parliament and of the Council of 16 April 2014 on market abuse (market abuse regulation) and repealing Directive 2003/6/EC of the European Parliament and of the Council and Commission Directives 2003/124/EC, 2003/125/EC and 2004/72/EC.

[14] For non-ABCP securitisations.

[15] In the case of ABCP transactions, at the latest one month after the end of the period the report covers.

[16]   The RTS supplement the Securitisation Regulation, while ITS specify how the details are to be implemented (eg through standard templates).

[17] In the letter from Steven Maijoor of ESMA to the Commission dated 24 April 2018.

[18] Article 43 of the Securitisation Regulation

[19] ESMA explains that this is because the Securitisation Regulation stipulates that, until the Commission adopts ESMA’s draft RTS on disclosure, the reporting templates set out in the RTS adopted as per Article 8b of the CRA3 Regulation (Regulation (EU) No 462/2013) will apply. At the same time, the Securitisation Regulation states elsewhere that Article 8b of the CRA3 Regulation is “deleted”.

[20] As noted in the Recitals to the draft Disclosure RTS, the term “underlying exposure” is generally understood to refer to any loan, lease, debt, credit, or other cash-flow generating receivable.

[21] Asset-Backed Securities

[22] Regulation (EU) No 462/2013 of the European Parliament and of the Council of 21 May 2013 amending Regulation (EC) No 1060/2009 on credit rating agencies

[23] The ECB ABS loan-level initiative established loan-by-loan information requirements for ABS accepted as collateral in Eurosystem credit operations.

[24] Collateralised Loan Obligations

[25] Such as the jurisdiction of the originator/original lender, origination channel of a loan, its origination date, and its original principal balance

[26] There are separate templates for ABCP and non-ABCP securitisations

[27] ESMA has said that it considers that the ND5 ‘No data’ option (i.e. ‘not applicable’) appears to remain valid and necessary to allow in fields in each of the templates, given the heterogeneity of securitisations, the variety of various underlying exposure products that may still be classified under the same type (e.g. ‘residential mortgages’) and also the prevalence of different originator and jurisdictional practices.

[28] Securitisations the securities of which are issued on or after 1 January 2019 – please see above.

[29] Article 43(8) of the Securitisation Regulation

[30] Regulation (EU) No 575/2013 of the European Parliament and of the Council of 26 June 2013 on prudential requirements for credit institutions and investment firms and amending Regulation (EU) No 648/2012.

[31] Regulation (EU) 2017/2401 of the European Parliament and of the Council of 12 December 2017 amending Regulation (EU) No 575/2013 on prudential requirements for credit institutions and investment firms.

[32] “Original lender” inadvertently omitted from the Final Report

[33] an extra 959 mandatory fields being offset by a reduction of 443 unnecessary optional fields.

[34] i.e. both the present technical standards as well as the templates developed under Article 8b of the CRA3 Regulation.

Written by:

Cadwalader, Wickersham & Taft LLP

Cadwalader, Wickersham & Taft 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 (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.