UK: CFTC Adopts Final Rules On Regulatory And Real-Time Reporting; Extends Effective Date For Dodd-Frank Provisions

Last Updated: 16 January 2012
Article by Peter Y. Malyshev and Jonathan T. Ammons

Introduction

On December 20, 2011, the US Commodity Futures Trading Commission (the CFTC or Commission) held an open meeting where it approved two final rules and one final order promulgated under the Dodd-Frank Wall Street Reform and Consumer Protection Act (Dodd-Frank). Both final rules were adopted with unanimous votes and the order was adopted via seriatim vote the day before the meeting. The two rules address how swap data will be reported to regulators and separately to the public; the order clarifies when Dodd- Frank provisions will become effective.

Summary

The first rule adopted on December 20 establishes recordkeeping requirements and a regulatory reporting regime for the swaps market (the Regulatory Reporting Rule). The second final rule establishes a reporting regime for the public dissemination of swap transaction data in real-time (the Real-Time Rule). Both rules affect swap dealers (SDs), major swap participants (MSPs), swap counterparties that are neither SDs nor MSPs, swap data repositories (SDRs), swap execution facilities (SEFs), designated contract markets (DCMs), and derivatives clearing organizations (DCOs). The Commission was also scheduled to vote on a final order extending the temporary relief which was granted on July 14, 2011 from certain provisions of the Commodity Exchange Act (CEA) that otherwise would have taken effect on July 16, 2011 (i.e., the effective date of Dodd- Frank). However, the Commissioners voted in favor of that order via seriatim on December 19, 2011. The rules have not yet been published in the Federal Register but are available on the Commission's website.1

Opening Statements by Commissioners

The Commissioners all expressed their support for the two final rules in their opening statements. Commissioners Sommers and O'Malia, who voted against the proposed real-time reporting rule, both explained that many of their concerns with the proposed rule were addressed in the final Real-Time Rule which allowed them to vote in favor of this final rule.

Final Rule on Swap Data Recordkeeping and Reporting Requirements

This final rule will provide the Commission with its first insight into the true size and depth of the swaps market. While the Commission has historically collected data on physical commodity futures and option contracts traded on DCMs and recently finalized a rule requiring certain large swaps traders to report information about their positions,2 the Commission has never been able to collect a comprehensive data set regarding the swaps market as a whole. The reporting aspect of the rule divides swap data into two categories: creation data (which includes the primary economic terms and confirmation data), and continuation data (which relates to changes occurring during a swap's lifecycle).

Recordkeeping Requirements.3 The recordkeeping requirements are largely unchanged from the proposed rule. In general, the final rule will require SEFs, DCMs, DCOs, and swap counterparties (including non-SD/MSP counterparties) to keep all records required by certain other rules (which, except for the DCO rule,4 have not yet been finalized) in a manner that is readily accessible via real-time electronic access during the life of the swap and for two years thereafter, and in a manner that is retrievable within three business days for two years following that time. The final rule will also require SDRs to maintain all records required by Part 495 for fifteen years. These records must be readily accessible to the SDR and the Commission via real time electronic access for five years following the termination of a swap and in a manner that is retrievable within three business days for ten years thereafter.

Reporting Creation Data.6 In an attempt to ensure that regulatory reporting is performed by the entity which has the easiest, fastest, and cheapest access to the data, the Commission changed several aspects of the creation data reporting requirements from the proposal. In the final rule, the SEF or DCM will have sole responsibility for reporting all creation data for any swap execution on a SEF or DCM. This varies from the proposed rule, where swap counterparties were partially responsible for reporting the primary economic terms and DCOs were responsible for reporting all confirmation data for any cleared swap.

The final rule provides different procedures for the regulatory reporting of off-facility swaps depending on whether the swap is: (i) subject to mandatory clearing; (ii) not subject to mandatory clearing where the reporting counterparty is an SD or MSP; or (iii) not subject to mandatory clearing where the reporting counterparty is a non-SD/MSP. In general, the reporting counterparty (as determined by Rule 45.8) is responsible for reporting the primary economic terms to an SDR unless the swap is submitted for clearing (voluntarily or otherwise) within certain reporting deadlines established by the rule. Contrary to the proposed rule, these reporting deadlines differ based on whether the non-reporting counterparty is an SD or MSP (by providing more time for transactions with non-SD/MSP counterparties) and are phased-in so as to be longer during the first year of reporting than the second or third. DCOs are generally tasked with reporting confirmation data, unless the swap is not cleared or not accepted for clearing, in which case the reporting counterparty must fulfill this obligation.

Reporting Continuation Data.7 Continuation data reporting is meant to ensure that SDRs have data regarding all changes to the primary economic terms of each swap, including changes to a swap's valuation. The Commission originally proposed requiring continuation data in the form of "lifecycle" data, which would only be reported upon the occurrence of certain events, or "snapshot" data, which would require daily reporting, depending on a swap's asset class. Under the final rule, however, continuation data for any swap may be reported via either the lifecycle or the snapshot reporting method. Continuation data for cleared swaps is reported by the DCO, though SD and MSP reporting counterparties must also report valuation data.

Data Standards.8 The Regulatory Reporting Rule provides SDRs with flexibility to use and require a variety of data standards to receive data reported to them. The Commission opted for this method over some requests that there be a uniform reporting format or data standard. The Commission stated that this flexibility is intended to allow a more cost-effective application of evolving data standards.

Type of Reporting

Executed on platform and cleared

Executed on platform and not cleared or not accepted for clearing within reporting deadlines

Not executed on a platform and accepted for clearing within reporting deadlines

Not executed on a platform and not cleared or not accepted for clearing within reporting deadlines

Primary Economic Terms

SEF/DCM reports

SEF/DCM reports

DCO reports if accepted for clearing before the reporting CP reports

Reporting CP reports

Confirmation Data

SEF/DCM reports

SEF/DCM reports

DCO reports

Reporting CP reports

Continuation Data for Credit and Equity Swaps

If Reporting CP is an SD/MSP

DCO (life-cycle or snapshot data)

DCO and SD/MSP (valuation data)

If Reporting CP is an SD/MSP

Reporting CP (all life-cycle or snapshot and valuation data)

If Reporting CP is an SD/MSP

DCO (life-cycle or snapshot data)

DCO and SD/MSP (valuation data)

If Reporting CP is an SD/MSP

Reporting CP (all lifecycle or snapshot and valuation data)

If Reporting CP is a non-SD/MSP

DCO (life-cycle or snapshot and valuation data)

If Reporting CP is a non-SD/MSP

Reporting CP (all life-cycle or snapshot)

If Reporting CP is a non-SD/MSP

DCO (life-cycle or snapshot and valuation data)

If Reporting CP is a non-SD/MSP

Reporting CP (all lifecycle or snapshot and quarterly daily mark)

Continuation Data for Interest Rates, Currency, and other asset classes

If Reporting CP is an SD/MSP

DCO (life-cycle or snapshot data)

DCO and SD/MSP (valuation data)

If Reporting CP is an SD/MSP

Reporting CP (all life-cycle or snapshot and valuation data)

If Reporting CP is an SD/MSP

DCO (life-cycle or snapshot data)

DCO and SD/MSP (valuation data)

If Reporting CP is an SD/MSP

Reporting CP (all lifecycle or snapshot and valuation data)

Continuation Data for Interest Rates, Currency, and other asset classes

If Reporting CP is a non-SD/MSP

DCO (life-cycle or snapshot and valuation data)

If Reporting CP is a non-SD/MSP

Reporting CP (all life-cycle or snapshot)

If Reporting CP is a non-SD/MSP

DCO (life-cycle or snapshot and valuation data)

If Reporting CP is a non-SD/MSP

Reporting CP (all lifecycle or snapshot and quarterly daily mark)

Selection of SDR.9 All data related to a given swap during the life-cycle of the swap must be reported to the same SDR, so the rule sets forth how the SDR for a swap's first report is selected. The SDR for any swap will be selected by whichever party or entity submits the primary economic terms data to an SDR. Therefore, for swaps executed on a SEF or DCM, the SEF or DCM will select the SDR because they will make the first report by reporting the primary economic terms. Even if a party were to report a swap to an SDR before the SEF or DCM, the SDR chosen by a SEF or DCM would be the relevant SDR under the rule.10 For off-facility swaps, the reporting counterparty makes the first report (unless the swap is accepted for clearing before it is reported by the reporting counterparty and within the reporting deadline for primary economic terms data, in which case the DCO makes the first report).

Unique Identifiers.11 The Regulatory Reporting Rule will require the creation and use of three types of unique identifiers: (i) unique swap identifiers (USIs); (ii) legal entity identifiers (LEIs); and (iii) unique product identifiers (UPIs). The USI will be created through a "first-touch" approach, so that the USI is created by SEFs and DCMs for facility-executed swaps, by SDs and MSPs for off-facility swaps in which they are the reporting counterparty, and by SDRs for off-facility swaps between non-SD/MSP counterparties. The LEI must be issued under, and conform to, ISO Standard 17442 which was developed by the International Organization for Standardization, but the Commission has not yet designated a "utility" to provide market participants with LEIs. Until the LEI utility has been designated, registered entities and swap counterparties must use the counterparty identifier created and assigned by an SDR. The Commission also has not yet developed a UPI designation or classification system. Until such a system is established, registered entities and swap counterparties must use their internal product identifier or a product description used by the SDR.

Allocation Issues.12 Several commenters to the proposed rule identified potential complications arising from reporting and assigning a USI to swaps entered into by a firm that acts on behalf of several clients and allocates its side of the swap among the several clients. The final Regulatory Reporting Rule addresses these comments by requiring two sets of reports for allocated swaps. First, the reporting entity must report the primary economic terms of the swap to an SDR, identifying the swap as an allocated swap and utilizing the LEI of the agent instead of the LEIs of the individual clients. Within eight hours of execution, the agent must inform the reporting counterparty of the identity of each client who is the actual counterparty. Second, the reporting counterparty must create a new USI for each individual swap resulting from allocation and report the following to the SDR: (i) an indication that the swap is a post-allocation swap; (ii) the USI of the original transaction; (iii) the USI of the post-allocation swap; (iv) the LEI of the actual counterparty; and (v) the LEI of the agent.

Use of Third Parties.13 Under the Regulatory Reporting Rule, swap counterparties and registered entities (e.g., SEFs and DCMs) are free to contract with third parties to facilitate regulatory reporting. However, the reporting entity remains fully responsible for reporting swap data in a timely and accurate manner.

Final Rule on Real- Time Reporting of Swap Transaction Data

The Real-Time Rule will require swaps data to be reported to a real-time disseminator as soon as technologically practicable after execution. The real-time disseminator must then publicly disseminate the data as soon as technologically practicable after receiving the data unless a time delay applies. Time delays will apply to block trades, large notional swaps, and swaps without an established minimum block size. Because no swap will initially have a minimum block size, a time delay will initially apply to any swap which requires real-time reporting (i.e., until the block sizes are established).

Transactions Subject to Real-Time Public Dissemination.14 Swap transactions will need to be reported and publicly disseminated in real-time if they are: (1) executed as an arm's-length transaction between two parties and result in a corresponding change in the market risk position between the two parties; or (2) a termination, assignment, novation, exchange, transfer, amendment, conveyance, or extinguishment of rights or obligations of a swap that changes the pricing of the swap. In order to be reportable, then, initial transactions must create a change in market risk between the parties, and life-cycle events must result in a change of price for the swap.

The Commission noted that this is a change from the proposed rule, which required public reporting of a wider range of swaps. This change is intended to ensure that certain inter-affiliate swaps and life-cycle events are not required to be reported. Specifically, if an inter-affiliate swap merely moves risk within an entity without creating credit exposure to the other party, it would not be required to be reported because it is not an arm's-length transaction and does not result in a change in the market risk between the parties. As an example, the final rule states that a transaction between wholly-owned subsidiaries of the same parent would not need to be publicly disseminated. As one Commissioner noted, however, the rule does not explain how swaps between entities that are partially controlled by the same parent would be treated. Lifecycle events will not have to be reported unless they affect the price of a swap.

Real-Time Reporting Required for Bespoke Swaps.15 Although many commenters argued that the Commission should not require real-time reporting for uncleared or bespoke swaps, the final rule will require real-time reporting and public dissemination for all swaps as long as they are reportable swaps as defined above. This includes enduser to end-user swaps. While real-time reporting is required of these swaps, the Commission granted certain bespoke swaps and swaps between certain counterparties a longer reporting delay than others, as explained below.

One exception from this requirement relates to off-facility swaps in the "other asset class" (i.e., swaps not in the interest rate, credit, forex, or equity asset classes). For these swaps, realtime reporting will initially only be required for: (i) swaps that reference one of 28 enumerated contracts (which correspond to the Reference Contracts in the final position limits rule); (ii) swaps that are "economically related" to such contracts; and (iii) swaps that reference Brent Crude Oil. The Commission plans to adopt rules regarding real-time reporting for the remaining swaps in the "other asset class" at a later date. Until that time, the Real-Time Rule does not require real-time reporting of such swaps.16 Time Delays for Public Dissemination.17 The Real-Time Rule establishes two types of time delays: (1) interim time delays applicable to all swaps (including non-block trades); and (2) time delays which will apply to blocks and large notional off-facility swaps. The Real- Time Rule does not establish the size for block trades (this aspect of the proposed rule will be re-proposed), but does specify the time delays that will apply to block trades and large notional swaps.

Until block sizes are established, all swaps (including nonblocks) will be subject to certain time delays. Once block sizes are established, non-block swaps must be reported and disseminated as soon as technologically practicable. Until block sizes are established, all swaps executed on a SEF or DCM will be subject to a 30 minute dissemination delay during the first year and 15 minutes during the second year. For offfacility swaps, this interim time delay varies based on: (i) whether or not the swap is subject to mandatory clearing; (ii) whether one, both, or none of the counterparties are SDs or MSPs; and (iii) the swap's asset class. The time delays for these off-facility swaps range from 30 minutes to 48 business hours after execution (during the first year after mandatory compliance) depending on these factors. For swaps where at least one counterparty is an SD or MSP, however, the longest delay is 4 hours after execution. These time delays are all reduced during the second year after mandatory compliance. Once block sizes are established, they will be subject to similarly-varying time delays based on the same factors.

Implementation.18 The final rule sets forth a schedule for phasing-in the reporting requirements, which varies between asset classes, and delays mandatory real-time reporting for reporting counterparties who are non-SD/MSPs for six months. This implementation schedule must be read in conjunction with the time delays set forth above to determine when and how quickly public dissemination is required. For example, during the first year, SEF-executed swaps on interest rates must be publicly disseminated within 30 minutes of execution beginning on the compliance date, SEF-executed swaps on foreign exchange products must be reported within 30 minutes of execution beginning 90 days after the initial compliance date, and offfacility swaps between two non-SD/ MSP counterparties in any asset class must be reported within 48 hours of execution beginning 180 days after the initial compliance date. The Commission published a chart demonstrating the interaction between the time delays and phased implementation of the final rule.19

Foreign Exchange (Forex) Swaps and Forex Forwards May Be Exempted.20 The final rule clarifies that, if the Treasury Department determines that forex swaps and forex forwards should not be regulated as swaps, they will not be subject to real-time reporting requirements. However, they would not be excluded from regulatory reporting obligations even if the Treasury Department makes such determination.

Reporting Party and Limited Use of Third Parties. For swaps executed on a SEF or DCM, the SEF or DCM will report the swap to an SDR and the swap counterparties have no responsibility or power to control such reporting. This includes off-facility block trades executed pursuant to the rules of a SEF or DCM. For off-facility swaps not executed pursuant to the rules of a SEF or DCM, the Real-Time Rule maintains the proposed hierarchy for determining the reporting party, but also permits the parties to agree that either one should be the reporting party.

The final rule has several limitations on the use of third-party providers for realtime reporting.21 For swaps executed on or subject to the rules of a SEF or DCM, the parties cannot opt to use a third-party provider to transmit data to an SDR; instead, the SEF or DCM is solely responsible for reporting such transactions to an SDR. However, SEFs and DCMs may enter into a contractual relationship with third party service providers to transmit transaction data to an SDR. For off-facility swaps, the rule appears to permit parties to use third parties to transmit swap data to an SDR.22 Notably, however, unlike the proposed rule, the final rule explicitly eliminates the ability for third-party providers to act as real-time disseminators. Therefore, SEFs, DCMs, and counterparties can only send data to an SDR for public dissemination (even if they use a third party for transmitting such data to the SDR). Nonetheless, the Commission stated that SDRs can "ensure public dissemination" by contracting with a third-party to "assist in public dissemination."23

Anonymity of the Parties.24 Many commenters urged the Commission to protect the anonymity of the parties to a swap and prevent trading ahead and other types of manipulation. In response, the Real-Time Rule does not require public dissemination of the actual underlying asset(s) for swaps in the "other" asset class which are not: (i) one of the 28 enumerated contracts described above; (ii) economically related to such contracts; (iii) swaps that reference Brent Crude Oil; or (iv) executed on a SEF or DCM. For all other contracts, including any reportable swap in the interest rate, credit, equity, and forex asset classes, SDRs must publicly disseminate the actual underlying asset(s).

Final Order Regarding the Effective Date for Swap Regulation

On December 19, 2011, the Commission issued an Order amending an earlier order which, among other things, extended the effective date for certain self-effectuating provisions of Dodd- Frank while the Commission and the SEC continued their rulemaking process. The December 19 Order provides temporary exemptive relief by: (1) extending the potential latest expiration date of the earlier exemptive relief from December 31, 2011 to July 16, 2012; and (2) adding provisions to account for the repeal and replacement (as of December 31, 2011) of Part 35 of the CFTC's regulations.

Extension of Relief. On July 14, 2011, the Commission granted exemptive relief from certain provisions of the CEA which would have become effective on July 16, 2011 (Dodd-Frank's general effective date) until December 31, 2011 (the July 14 Order). Regarding provisions of the CEA which reference terms which have yet to be defined by the CFTC and SEC, the December 19 Order re-extends this relief until the earlier of: (i) July 16, 2012; or (ii) the effective date of the applicable final rule defining the relevant terms. Regarding other provisions of the CEA which derive from self-effectuating provisions of Dodd-Frank, the December 19 Order re-extends this relief until the earlier of: (i) July 16, 2012; or (ii) such other compliance date as may be determined by the Commission.

Part 35 Exempt and Excluded Commodities. In the July 14 Order, the Commission stated that transactions in exempt or excluded commodities, which were addressed in Part 35 of the CFTC's regulations,25 and persons offering or entering into them would generally be temporarily exempt from provisions of the CEA, notwithstanding the fact that certain requirements in Part 35 may not have been met.26 Under the July 14 Order, this relief was to expire upon the earlier of: (1) the repeal, withdrawal or replacement of Part 35; or (2) December 31, 2011. In order to ensure that certain markets can continue operating, the December 19 Order re-extends the exemptive relief available under the July 14 Order. Additionally, because the Commission recently promulgated a rule which repealed Part 35 on December 31, 2011,27 the Commission amended the July 14 Order to explicitly incorporate by reference Part 35 to ensure that all transactions fully meeting the requirements of Part 35 prior to December 31, 2011 will continue to be exempted from certain provisions of the CEA.

Applicability to Agricultural Swaps. The recent rule which repealed Part 35 as of December 31, 2011 adds new § 35.1, which generally permits persons to transact agricultural swaps subject to the laws applicable to all other swaps. While the Part 35 in effect prior to December 31, 2011 permitted certain persons to transact exempt and excluded commodities on exempt commercial markets ("ECMs") and exempt boards of trade ("EBOTs"), respectively, the Commission clarified that the December 19 Order does not permit agricultural swaps to transact on ECMs or EBOTs. Instead, only exempt and excluded commodities can continue to trade on ECMs and EBOTs under the new Order.

Footnotes

1 Available at http://www.cftc.gov/PressRoom/ Events/opaevent_cftcdoddfrank122011 (last visited Dec. 30, 2011).

2 See Large Trader Reporting for Physical Commodity Swaps, 76 Fed. Reg. 43851 (July 22, 2011).

3 See Regulatory Reporting Rule, pp. 220-223.

4 See Derivatives Clearing Organization General Provisions and Core Principles, 76 Fed. Reg. 69334, 69446 (to be codified at 17 C.F.R. § 39.20) (Nov. 8, 2011).

5 See Swap Data Repositories: Registration Standards, Duties and Core Principles, 76 Fed. Reg. 54538, 54580 (to be codified at 17 C.F.R. § 49.12) (Sept. 1, 2011).

6 See Regulatory Reporting Rule, pp. 224-235.

7 See id. at 235-239.

8 See id. at 114-115.

9 See id. at 261-265.

10 See id. at 261-262.

11 See id. at 73-101.

12 See id. at 77.

13 See id. at 108.

14 See Real-Time Rule, pp. 17-18.

15 See id. at 18-21.

16 See id. at 153.

17 See id. at 215-222.

18 See id. at 146-153.

19 See http://www.cftc.gov/ucm/groups/public/@ newsroom/documents/file/phasein_realtime.pdf (last visited Dec. 30, 2011).

20 See Real-Time Rule, pp. 21-22.

21 None of the restrictions or permissions regarding the use of third parties appear in the actual final rule, but only in the preamble accompanying the rule.

22 The preamble explicitly states that reporting parties to off-facility swaps which are uncleared should be able to use third parties for such services, see Real-Time Rule, p. 55, and later states that "allowing reporting parties to contract with third parties should allay concerns regarding the potential disproportionate cost burden placed on end-users. See id. at 57. However, the rule does not explicitly address the use of third party service providers for bilaterally-executed and voluntarily cleared swaps.

23 See Real-Time Rule, p. 64.

24 See id. at 95-96.

25 Part 35 exempted "swap agreements," from most of the provisions of the CEA if: (1) they were entered into by "eligible swap participants" (ESPs); (2) they were not part of a fungible class of agreements standardized as to their material economic terms; (3) the credit-worthiness of any party having an actual or potential obligation under the swap agreement would have been a material consideration in entering into or determining the terms of the swap agreement, including pricing, cost, or credit enhancement terms; and (4) they were not entered into or traded on a multilateral transaction execution facility. See 17 C.F.R. 35.1 et seq.

26 I.e., the transactions were exempt notwithstanding the fact that: (1) the transaction may be executed on a multilateral transaction execution facility; (2) the transaction may be cleared; (3) persons offering or entering into the transaction may be eligible contract participants as defined in the CEA (prior to the enactment of the Dodd-Frank Act); (4) the transaction may be part of a fungible class of agreements that are standardized as to their material economic terms; and/or (5) no more than one of the parties to the transaction is entering into the transaction in conjunction with its line of business, but is neither an eligible contract participant nor an ESP, and the transaction was not and is not marketed to the public.

27 See Agricultural Swaps, 76 Fed. Reg. 49291 (Aug. 10, 2011).

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

Authors
 
In association with
Up-coming Events Search
Tools
Print
Font Size:
Translation
Channels
Mondaq on Twitter
 
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
 
Email Address
Company Name
Password
Confirm Password
Position
Mondaq Topics -- Select your Interests
 Accounting
 Anti-trust
 Commercial
 Compliance
 Consumer
 Criminal
 Employment
 Energy
 Environment
 Family
 Finance
 Government
 Healthcare
 Immigration
 Insolvency
 Insurance
 International
 IP
 Law Performance
 Law Practice
 Litigation
 Media & IT
 Privacy
 Real Estate
 Strategy
 Tax
 Technology
 Transport
 Wealth Mgt
Regions
Africa
Asia
Asia Pacific
Australasia
Canada
Caribbean
Europe
European Union
Latin America
Middle East
U.K.
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.

Disclaimer

Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.

Registration

Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.

Cookies

A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.

Links

This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.

Mail-A-Friend

If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.

Security

This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.