United States: Securities And Corporate Governance Litigation Quarterly - November 2015

Decisions Of Interest For Corporate And Transactional Lawyers

Welcome to the fifth issue of Securities and Corporate Governance Litigation Quarterly, Seyfarth's quarterly publication of the Securities & Financial Litigation Group focusing on decisions or other items of interest for corporate and transactional lawyers. Each summary below is followed by key practice takeaways.

Delaware Chancery Court Rejects Majority Stockholder's Attempt To Remove And Replace Officers Through By-Laws Amendments

Gorman v. Salamone (here) involves a long-running dispute over the control of Westech Capital Corp. which arose because a voting agreement was arguably unclear as to whether certain directors were to be elected per capita among certain key shareholders or per share. The majority shareholder, John J. Gorman, IV, largely lost that battle in an earlier case that was decided by the Delaware Supreme Court in late 2014 (here) which left the CEO and Gorman's nemesis, Salamone, in place, together with the board seat to which Salome was entitled as CEO under the voting agreement.

Undeterred, Gorman purported to amend Westech's bylaws by written consent to allow the stockholders — Gorman with the majority of the shares — to remove and replace Westech's officers. The amended bylaw provided:

Section 6.2. Term of Office. The elected officers of the Corporation shall be elected annually by the Board at its first meeting held after each annual meeting of stockholders. All officers elected by the Board shall hold office until the next annual meeting of the Board and until their successors are duly elected and qualified or until their earlier death, resignation, retirement, disqualification or removal from office. Any officer may be removed, with or without cause, at any time by the Board or by the stockholders acting at an annual or special meeting or acting by written consent pursuant to Section 2.8 of these Bylaws. The Board shall, if necessary, immediately implement any such removal of an officer by the stockholders. Any officer appointed by the Chairman of the Board or President may also be removed, with or without cause, by the Chairman of the Board or President, as the case may be, unless the Board otherwise provides. Any vacancy occurring in any elected office of the Corporation may be filled by the Board except that any such vacancy occurring as a result of the removal of an officer by the stockholders shall be filled by the stockholders.

Gorman then attempted to remove Salamone pursuant to Gorman's new purported power and appoint himself as the new CEO. Salamone and other board members refused to recognize Gorman's actions and Gorman commenced a summary proceeding under Section 225 of the Delaware General Corporation Law ("DGCL") to determine whether Salamone had been properly removed. Gorman relied on both Section 142(b) of the DGCL which provides that "[o]fficers shall be chosen in such manner and shall hold their offices for such terms as are prescribed by the bylaws or determined by the board of directors or other governing body" and on Section 109(b) which generally gives the stockholders broad power to adopt and amend the bylaws "relating to the business of the corporation, the conduct of its affairs, and the rights or powers or the rights or powers of its stockholders, directors, officers or employees."

However, the Court found that the general powers given to stockholders were trumped by Section 141(a) which specifies that "[t]he business and affairs of every corporation . . . shall be managed by or under the direction of a board of directors, except as may be otherwise provided in this chapter or in its certification of incorporation." Section 141(a) has been interpreted as a prohibition on stockholders directly managing the business affairs of a corporation, and the issue in Gorman v. Salamone was whether the majority stockholder's removal and replacement of Salamone as CEO was tantamount to "managing" the corporation. The Chancery Court concluded it was because it mandated how the board of directors decided the substantive business decision of removing the corporation's CEO. The Court stated the test for whether a bylaw is proper as whether it defined the "process and procedures" by which a board decision is made or, instead, whether the bylaw mandates how the board should make specific business decisions, which the new bylaw certainly did.

Practice takeaways:

  • Control fights in closely held corporations are sometimes the product of poor drafting of corporate governance documents. Often, however, the lack of clarity and ambiguities in those documents are the product of negotiated compromises and "kicking the can" on potential control issues rather than sloppiness. If the corporate documents governing control go too far, the court may resort to a highly technical reading of the statute to preserve the board's primacy to manage the business and affairs of the corporation, thus leading to unsatisfied expectations, hopeless deadlocks, and potentially lengthy and expensive litigation.
  • Imprecise corporate governance documents and their unintended or intended consequences can seldom be revised after the fact if there are classes of directors elected to protect certain control groups; one or the other of the control groups will object and there is often no way for one group to break the deadlock. Gorman v. Salamone demonstrates one of number of ways that even a majority shareholder cannot break the deadlock.
  • Bylaws are by their nature only "rules of the road" governing process and procedures. All too often stockholders attempt to pack precise corporate control provisions into bylaws and shareholder agreements, and in light of Gorman v. Salamone that approach may not hold up in a judicial challenge.
  • Choice of entity is very important in relation to control and the extent to which stockholders can inject themselves into substantive business decisions. The DGCL already provides an avenue through which stockholders can restrict the discretion of directors and implement stockholder management by electing to treat the corporation as a statutory "close corporation." See DGCL Sections 341 et seq. (including Section 350 (restricting director discretion) and Section 351 (management by stockholders) if close corporation status is elected in the certificate of incorporation). Also, these formalities do not necessary apply to limited liability companies, where member and manager roles can be more freely defined by contract. As the Gorman court noted, "a Delaware corporation is a board-centric entity. Other governance structures can be imposed on other entities, if that is what the stakeholders desire."

Second Circuit Creates Split Regarding Definition Of Whistleblower Under Dodd- Frank's Anti-Retaliation Provisions

On September 10, 2015, the Second Circuit, in Berman v. Neo@Ogilvy LLC (here), split with the Fifth Circuit regarding the reach of Dodd-Frank's whistleblower anti-retaliation provisions. The crux of the debate arises from the interplay between the statutory definition of "whistleblower" and the conduct protected in the Act's anti-retaliation provisions. Specifically, the Act clearly defines "whistleblower" as "any individual who provides . . . information relating to a violation of the securities law to the [SEC]." 15 U.S.C.§ 78u-6(a)(6). The anti-retaliation provisions of the law, however, prohibit retaliation against "whistleblowers" who participate in the following conduct: (i) who raise complaints relating to lawful acts done by a whistleblower in providing information to the SEC; (ii) who participate or assist in any investigation of the SEC based upon such information; and (iii) who make disclosures required or protected under the Sarbanes-Oxley Act and any other law, rule or regulation subject to the jurisdiction of the SEC. See 15 U.S.C. § 78u-6(h)(1)(A)(i)-(iii).

One interpretation of the statute — the one ultimately adopted by the Second Circuit — is that because subsection (iii) above does not expressly condition anti-retaliation protection on an employee having complained to the SEC, a complaint to the SEC is not required by the statute. Under this reading, the protections afforded to a "whistleblower" under subsection (iii) seemingly contradict the clear statutory definition of the term "whistleblower" in the earlier section of the statute, leading a number of district courts, and now the Second Circuit, to conclude that there is sufficient ambiguity in the statute to permit deference to the SEC's subsequent whistleblower regulations defining the term more broadly. Not surprisingly, the SEC's position is that an employee need not report to the SEC in order to benefit from the anti-retaliation provisions of Act. In fact, following oral argument in Berman, the SEC issued an interpretive rule designed to "clarify" that, for purposes of the employment retaliation protections provided by Dodd-Frank, an individual's status as a whistleblower does not depend on reporting information to the SEC. See Interpretation of the SEC's Whistleblower Rules Under Section 21F of the Securities Exchange Act of 1934, Exchange Act Release No. 34-75592 (Aug. 4, 2015).

Not all courts agree with this broad reading of the law. The Fifth Circuit in Asadi v. G.E. Energy (USA), L.L.C. and a number of district courts have held the statutory definition of "whistleblower" is abundantly clear, and notwithstanding the language in subsection (iii), the anti-retaliation provisions support the conclusion that to be a whistleblower, a person must first complain to the SEC. A majority of the panel in Berman disagreed, describing the central issue as whether the "arguable tension between the definitional subsection [] which defines 'whistleblower' to mean an individual who reports violations to the [SEC], and subdivision (iii) . . ., which, unlike subdivisions (i) and (ii), does not within its own terms limit its protection to those who report wrongdoing to the SEC" creates sufficient ambiguity as to require deference to the SEC's rule.

The majority began its analysis by highlighting the purported "tension" between the definition of whistleblower and the language of subsection (iii), observing that if subsection (iii) is meant to protect individuals who complain to the SEC, it will protect only those few individuals who make simultaneous complaints to their employer and to the SEC. The Court further observed that there are categories of potential whistleblowers who cannot report wrongdoing to the SEC until after they have first reported it to their employer (such as auditors and attorneys), and therefore, "apart from the rare example of simultaneous . . . reporting of wrongdoing . . . there would be virtually no situation where an SEC reporting requirement would leave subdivision (iii) with any scope." Consequently, the majority opined the central question is "whether Congress intended to add subdivision (iii) . . . only to achieve such a limited result." Ultimately, the Court determined that the statutory texts are unclear, and found no legislative history that "even hints at an answer." Accordingly, the Court found the "tension" created sufficient ambiguity to allow deference to the SEC's interpretation of the statute.

In its effort to rationalize the apparent unambiguous definition of "whistleblower" set out in the statute, the majority noted, "[w]e recognize that the terms of a definitional subsection are usually to be taken literally. . . and, pertinent to this case, usually applied to all subsections literally covered by the definition, but we have also recognized that 'mechanical use of a statutory definition' is not always warranted." That is, even though the statute provides a clear definition of a term that is later used in other sections of the statute, the majority still concluded that the statute was somehow ambiguous.

In his dissent, Judge Jacobs harshly criticizes the majority for re-writing the statute, misreading its clear terms ("a bad misreading, tantamount to a misquotation") and for placing the Second Circuit on the "wrong side" of a circuit split. Relying heavily on Asadi, Judge Jacobs observed that "[p]ersons who report certain violations of the securities laws are protected from retaliation under (at least) two federal statutes. [SOX] protects employees who blow a whistle to management or to regulatory agencies; Dodd-Frank protects "whistleblowers," defined as persons who report violations "to the [SEC]." He then criticized the majority for "assum[ing] its own conclusion," ignoring the distinction between SOX and Dodd-Frank, and for "look[ing] here, there and everywhere — except to the statutory text" for the meaning of the term "whistleblower." Judge Jacobs next attacked the majority's conclusion that subsection (iii) would have a limited effect, and more so, for its holding that when a plain reading of a statute gives it an "extremely limited" effect, the statutory provision is therefore "impaired or ambiguous."

Practice Takeaway:

  • With a clear circuit split, as well as strong dissent in its own Circuit, this issue seems destined for resolution by the Supreme Court. Indeed, the Second Circuit agreed on October 14, 2015 to put its mandate on hold while Neo@Ogilvy seeks Supreme Court review. Until the Supreme Court resolves the circuit split, the broader restriction on retaliation under the Second Circuit's construction should guide employers' reaction to "whistleblowers" whether or not they report to the SEC.

Recent SEC Enforcement Action Highlights Cybersecurity Risks

On September 22, 2015, the Securities and Exchange Commission ("SEC") announced (here) that R. T. Jones Capital Equities Management, an investment adviser, agreed to settle charges that it failed to establish required cybersecurity policies and procedures before its web server was attacked by a hacker (traced to China). The breach resulted in the compromise of personally identifiable information ("PII") of 100,000 persons, including thousands of the firm's clients.

The adviser was alleged to have violated the "safeguards rule" (here) which requires investment advisers to adopt written policies and procedures designed to protect customer information. Here, the adviser stored sensitive PII on a server hosted by a third party and the adviser failed to conduct periodic risk assessments, implement a firewall, encrypt PII stored on the server, and maintain a response plan in case of cyberattacks.

After the attack, the adviser notified each individual whose PII was compromised and offered free identity theft monitoring. Although the adviser received no reports of a client suffering financial harm from the breach, the SEC faulted the adviser for failing to adopt written policies and to have clear procedures in place before a breach occurs as required by the safeguards rule. The Co-Chief of the SEC's Enforcement Division stated "[I]t is important to enforce the safeguards rule even in cases like this when there is no apparent financial harm to clients."

The SEC's focus on cybersecurity is reflected in the results of a Cybersecurity Examination Sweep Survey (here) by its Office of Compliance Inspections and Examinations ("OCIE"). This survey was designed to inform the SEC's Staff about the level of preparedness of the broker-dealers and investment advisers that were examined. Among other things, the OCIE survey showed that:

  • A significant majority of the broker-dealers and advisers have adopted written information security policies and conduct periodic risk assessments to identify cybersecurity vulnerabilities.
  • Most of the examined firms have been the subject of a cyber-related incident, and about a quarter had sustained losses caused by employees not following authentication procedures for fraudulent emails seeking to transfer funds.
  • The firms' cybersecurity risk policies for their vendors varied in implementation. While most incorporate some form of requirements in their vendor contracts, a much smaller number provide training for vendors and business partners authorized to access their networks.
  • Just over a majority of broker-dealers, and only a small number of advisers, have insurance for cybersecurity incidents.

Practice takeaways:

We anticipate that the SEC's interest in the management of cybersecurity risk will increase among firms in the business of holding and managing clients' information, such as broker-dealers and investment advisers, and will also spread laterally to other entities whose activities are covered by SEC regulation:

  • Cybersecurity threats — whether from nation-state actors, criminal organizations or competitive businesses — are not likely to abate in the future. In order to maintain competitive advantage as a good business partner as well as to avoid or mitigate potential liability, it will become increasingly important for companies to demonstrate that they have sound and constantly updated policies in place. As the R. T. Jones enforcement action demonstrates, having and following a reasonable cybersecurity policy can be as important as the consequences of an actual data breach.
  • The data elicited from the OCIE survey indicates that, for the industry segment covered, practices are moving toward a number of common elements. This reflects an emerging "standard of care" that will inform regulatory expectations and trends in private litigation for information security breaches.
  • Cybersecurity policies should cover security practices, asset management and data flow. They should be designed to identify the business' systems and needs, develop and implement safeguards, detect security threats and events, respond to events with an action plan, and restore normal operations after an incident.
  • The standard of care will constantly evolve as the threats become more sophisticated. In the future, cybersecurity is likely to become predictive based on hacker behavior, rather than reactive by adjusting to past threats.
  • Covered firms should explore insurance options for covering cybersecurity risks.
  • While the OCIE survey was confined to covered broker-dealers, the SEC appears to be directing increased attention to public companies in certain industries that have been targeted by hackers seeking material non-public information on which to trade. While regulatory action specifically directed to cybersecurity risks for public companies in general does not appear imminent, any cybersecurity vulnerabilities that a public company generating material non-public news has may expose it to investigations for insider trading. If those vulnerabilities compromise the company's financial reporting functions, there may also be exposure to claims of inadequate financial controls, deficient disclosure in management's discussion and analysis, and scrutiny of the adequacy of financial reserves for contingencies.

Delaware Chancery Court Issues A Reminder of The Limitations That May Exist In Your Director and Officer Indemnification

The Delaware Chancery Court's recent decision in Charney v. American Apparel, Inc., (here) highlights some potential pitfalls that may exist in many standard Delaware indemnification and advancement provisions for directors and officers. In American Apparel, the company's founder and former CEO and Chairman, Dov Charney, sued to recover advancement of legal expenses he was incurring in another litigation filed by the company. In that other case, the company was suing Charney for breach of a Standstill Agreement the parties had entered into the previous year while Charney was still at the company. The court held that Charney was not entitled to advancement under the company's charter and his indemnification agreement because the suit over the Standstill Agreement was not "related to the fact" that Charney was a director or officer.

In June 2014, Charney was suspended as CEO by the board of directors, pending an investigation into alleged misconduct by Charney. In July 2014, Charney and the company entered into the Standstill Agreement, under which Charney was prohibited from taking certain actions, including seeking removal of members of the board and making disparaging comments about the company to third parties. The Standstill Agreement also governed the terms by which Charney might return to the company, depending on the outcome of the investigation. In December 2014, following the investigation, Charney was terminated for cause based on his misconduct prior to June 2014.

Following his termination, Charney allegedly engaged in a variety of hostile actions that the company believed violated the Standstill Agreement. On May 15, 2015, the company filed its lawsuit over these alleged violations, claiming that Charney was attempting a potential takeover, had expressed anti-board sentiments at employee meetings, made negative statements to third parties, and submitted a declaration in opposition to the board in an unrelated legal proceeding. Charney made a prompt demand on the company for advancement of his legal fees incurred in the Standstill Agreement case under his indemnification agreement and company's by-laws. The Company rejected Charney's demand on May 26, 2015.

Charney filed his suit for advancement of fees on June 4, 2015. Charney argued that the company's advancement obligations are defined by and flow from its indemnification obligations such that he is entitled to advancement expenses incurred in the Standstill Proceeding under Delaware law. The court disagreed and held that while rights to advancement and indemnification are related, they are "discrete and independent." As such, Delaware courts have refused to recognize claims for advancement absent specific language that permits it under the applicable circumstances. Similarly, the court rejected Charney's argument that he was entitled to advancement under the company's charter. The court held that under the charter, only current officers and directors of the company are entitled to advancement. Finally, the court rejected Charney's argument that his fees were incurred "as a result of" his position as a director and/or officer of the company. The court held that while Charney's position exacerbated the magnitude of his actions, there was no causal connection and all of his actions could have been undertaken whether or not he served as a director or officer. Moreover, each of the alleged actions the company was challenging occurred after he had been terminated an officer or director.

Practice Takeaways

  • Review the language of the company's indemnification obligations under the by-laws, charter or in separate agreements with its officers and directors. While most standard indemnification provisions cover both former and current officers and directors, the advancement obligations may not apply to former officers and directors.
  • Pay particular attention to the triggering language of the indemnification obligations. If it is limited to claims brought "by reason of the fact" that one is an officer or director (the language used in section 145 of the Delaware Gen Corp. law), there may be no coverage for contract disputes, like the one here in American Apparel, which may arise out of one's role as a director but may not "arise by reason of the fact" of that role.
  • Recognize that generally there will not be indemnification or advancement coverage for claims that do not have a causal connection to the claimant's actions or inactions as an officer or director, or which do not relate to his or her exercise of judgment, discretion, or decision-making authority on behalf of the corporation.

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
Related Video
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
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 you may opt out by clicking here

    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.

    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.

    Emails

    From time to time Mondaq may send you emails promoting Mondaq services including new services. You may opt out of receiving such emails by clicking below.

    *** If you do not wish to receive any future announcements of services offered by Mondaq you may opt out by clicking here .

    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.

    By clicking Register you state you have read and agree to our Terms and Conditions