Under Construction - June 2016

Snell & Wilmer

Letter from the Editor

by James J. Sienicki

Welcome to the June 2016 edition of our Under Construction newsletter. Hope you are staying cool this summer.

Are you legally operating your drone on the construction site? In our Winter 2015 Under Construction newsletter, we highlighted requirements for legal operation of drones for commercial use. The follow-up article in this edition provides additional updates in light of recent developments taken by the FAA and states like Arizona affecting drone operations.

We will also take a look at new legislation and recent court opinions in Arizona affecting the construction industry and how these changes may affect your construction business. Then, we move to California and examine a recent California case evaluating the sufficiency of proof of construction claim damages, including the first case in California discussing home office overhead delay damages and the federal Eichleay formula. We conclude with an article discussing a developing issue in Utah regarding indemnification of board member/developer defendants by HOAs for attorney’s fees and costs.

We hope you will find these articles informative and enlightening. Please let us know if you want us to address a specific construction issue in a future newsletter. Cheers to a wonderful summer!

Jim Sienicki

Are You Legally Operating That Drone on Your Construction Site?

by Jason Ebe

Drones are becoming widely used on construction projects. But the mere purchase and review of the owner’s manual is insufficient for legal operation. In our article in the December 2015 Under Construction, we highlighted requirements for legal operation of drones for commercial use, such as on construction projects. These requirements include: a grant of exemption allowing such commercial use; a Certificate of Waiver or Authorization from the FAA; registration of the drone with the FAA and an FAA certified pilot.

The FAA registration system has been active since December 21, 2015. For drones acquired after that date, registration is required prior to the first outdoor flight. After completing registration, owners will receive a personal registration number which must be identified on the drone. Answers to frequently asked questions regarding the registration process can be found at http://www.faa.gov/uas/registration/faqs/.

Operators must also comply with applicable state laws affecting drone operation. For example, on May 11, 2016, Arizona Governor Doug Ducey approved SB 1449 placing further limitations on drone operation within Arizona. According to the National Conference of State Legislatures, 26 states have enacted laws addressing drone issues and an additional six states have adopted resolutions. Arizona’s law, among other things, prohibits operation of drones to intentionally photograph or loiter over critical facilities such as refineries, water and wastewater facilities, electrical transmission or distribution facilities, electronic communication stations or towers, railroads, courthouses, public safety or emergency operation facilities, military installations, and hospitals with air ambulance services, as well as operations which interfere with first responder operations.

If you are contemplating operation of a drone in your business, or are already doing so, and haven’t complied with the applicable FAA and state requirements, you need to take appropriate corrective action now. Operation in violation of these requirements could result in criminal and/or civil penalties, as well as potential breach of contract claims arising out of your use of the drone, and potential loss of insurance coverage for resultant damage from such use.

For additional information regarding drones and liability issues, check out our colleague Troy Roberts’ frequent posts on Snell & Wilmer’s Into the Breach Blog at http://www/swlaw.com/blog/data-security/.

Arizona Construction: New Legislation and Recent Court Opinions

by James J. Sienicki and Mark Molique

The first half of 2016 had a handful of legislation and court opinions discussing issues affecting the construction industry.

Legislation: House Bill 2268 Regarding 20-Day Notices on Arizona Public Projects

The Arizona legislature weighed in on how subcontractors and suppliers may give the necessary preliminary 20-day notices on public works covered by Arizona’s Little Miller Act (LMA) to preserve their bond claims. The LMA requires that prime contractors on public works projects provide payment bonds to protect subcontractors and suppliers who provide labor and/or materials. The LMA requires that subcontractors and suppliers that do not contract directly with the prime contractor send certain notices to the prime contractor to preserve their bond claim: a written preliminary 20-day notice that complies with certain subsections of A.R.S. § 33-992.01 and a subsequent 90-day notice. Subsection (F) of A.R.S. § 33-992.01(F) provides that preliminary 20-day notices for the purpose of mechanics’ liens may be given by first-class mail sent with a certificate of mailing, registered or certified mail, all postage prepaid, though the LMA referred to A.R.S. § 33-992.01, it did not expressly reference subsection F. Instead, the LMA stated that notices had to be sent by certified or registered mail. Many were under the impression that preliminary 20-day notices on public works projects could be sent by first-class mail with a certificate of mailing to preserve their bond claims.

In April of 2015, Division Two of the Arizona Court of Appeals held that Arizona Revised Statutes (A.R.S.) section 34-223(A) did not allow a written preliminary 20-day notice to be sent by first-class mail with a certificate of registration because 34-223 referenced specific sections of 33-992.01 but subsection (F) was not one of them. Thus, the mailing requirements of 34-223, which only authorized registered or certified mail, was required to preserve a bond claim under the LMA.

This year, the Arizona legislature passed House Bill 2268, effective August 6, 2016, amending A.R.S. § 34-223 of the LMA. The amendments provide that the preliminary notice can be sent by any method provided in A.R.S. § 33-992.01(F), which allows the notice to “be given by mailing the notice by first-class mail sent with a certificate of mailing, registered or certified mail, postage prepaid in all cases, addressed to the person to whom notice is to be given at the person's residence or business address.” The subsequent 90-day notice also required by the LMA can now “be given by any means that provides written, third-party verification of delivery to the contractor at any place the contractor maintains an office or conducts business, or at the contractor's residence.” 2016 Ariz. Legis. Serv. Ch. 237 § 1 (H.B. 2268). Until House Bill 2268 becomes effective, preliminary 20-day notices on public projects need to be sent via certified or registered mail.

Appellate cases:

In S&S Paving & Const., Inc. v. Berkley Reg'l Ins. Co., No. 1 CA-CV 15-0239, __ Ariz. __, __ P.3d __, 2016 WL 2756428, at *3 (App. May 12, 2016), the Arizona Court of Appeals held that a subcontractor, S & S Paving and Construction, Inc. (S & S), could not pursue a claim of bad faith against a surety that issued a payment bond pursuant to the Little Miller Act. S & S sent a demand letter to the surety and, at the surety’s request, filled out a proof of claim. The surety informed the subcontractor that it would investigate the claim, including discussing the claim with the prime contractor. The correspondence from the surety included the typical language included by sureties that nothing in the correspondence tolled the statute of limitations. The surety never communicated with S & S again. The statute of limitations for bringing a claim against the bond passed. S & S then sued the surety, bringing claims for breach of contract and bad faith, alleging that the surety had a duty to investigate whether S & S’s claim was valid.

The Arizona Court of Appeals held that the surety could not be liable for bad faith on a public project because the Little Miller Act was the statutory remedy that provided S & S with “a complete and valid remedy.” The court distinguished the result in Dodge v. Fidelity & Deposit Co. of Maryland, 161 Ariz. 344, 778 P.2d 1240 (1989) which held that the surety that issued a performance bond on a private, residential project could be liable to the homeowner for the tort of bad faith for failing to pay a valid claim when the project’s contractor failed to complete the job. Unlike the private project in Dodge, the Little Miller Act was “a carefully crafted statutory scheme that seeks to balance the competing interests inherent in public works projects.” S&S Paving & Const., 2016 WL 2756428, at *3. Nothing in the statute required the surety to do any pre-litigation investigation of the validity of the claim. S & S was required to bring its suit against the surety within the limitations period provided by the statute. For public works controlled by the Little Miller Act, that limitations period is “one year from the date on which the last of the labor was performed or materials were supplied .. . . .” A.R.S. § 34-223(B).

In City of Phoenix v. Glenayre Elecs., Inc., 1 CA-CV 14-0739, 2016 WL 2912619, at *1, __ Ariz. __, __ P.3d __ (App. May 19, 2016), a worker who performed pipe installation and repair for the City of Phoenix developed mesothelioma allegedly as a result of exposure to asbestos years earlier when performing the work. He sued the City of Phoenix, who in turn brought claims for defense and indemnity against the various developers and contractors responsible for planning, designing and constructing the projects.

The Arizona Court of Appeals affirmed the superior court’s dismissal of the City’s claims, holding that the eight-year statute of repose found in A.R.S. § 12-552 barred the claims. The statute of repose bars any action or arbitration based in contract against a person who sells real property or performs design or construction services improving real property. The City of Phoenix argued that A.R.S. § 12-510 exempts governmental entities from the limitations periods and thus, the statute of repose in A.R.S. § 12-552 did not apply. The Court of Appeals noted that the beginning phrase in A.R.S. § 12-552 provides that the statute of repose applied “notwithstanding any other statute.” Thus, the statute of repose in § 12-552 trumped the governmental exemption of limitations in § 12-510. While the statute of repose protects the contracting parties, subcontractors and suppliers are not so protected. Owners sued by third parties for wrongs for which the owner alleges it is free from fault may pursue subcontractors or material suppliers without direct contractual relationships with the owner based on common law indemnity principles. See, e.g., Evans Withycombe, Inc. v. W. Innovations, Inc., 215 Ariz. 237, 243, ¶ 24, 159 P.3d 547, 553 (App. 2006).

MTR Builders, Inc. v. Jahan Realty Mgmt. Corp., 1 CA-CV 14-0650, 2016 WL 1425797, at *4 (Ariz. App. Apr. 12, 2016) is an unreported case that involves a recurring fact pattern between owners and contractors. A contractor sought payment from the owner prior to obtaining a third-party inspection and a certificate of completion on a job as the parties’ contract required. The owner objected to the payment application on these grounds. Ultimately, the inspection was successfully conducted and the certificate obtained but the contractor did not resubmit the payment application. The owner did not make payment and the contractor sued the owner for breach of contract and violation of the Prompt Pay Act. Owner countersued for breach of contract alleging deficiencies in the work. While this decision does not establish new precedent, it does provide some insight into the interplay of several interrelated construction issues involving Arizona’s private Prompt Pay Act, A.R.S.§ 33-992.01, et seq., breach of contract claims, and the result in American Continental Life Insurance Co. v. Ranier Construction Co., 125 Ariz. 53 (1980), a case decided before Arizona passed the Prompt Pay Act. Arizona’s Supreme Court held in American Continental that a contractor’s failure to seek a final certificate of payment, which the contractor understood to be futile, was made a condition precedent in the parties’ contract and barred the contractor’s recovery against the owner for work performed, despite the fact that the contractor had reached substantial completion.

In MTR Builders, Inc. the owner moved for judgment as a matter of law based on the result in American Continental because the contractor sought final payment prior to obtaining the inspector’s final approval or the necessary certificate of completion. The superior court denied this motion. The superior court did, however, grant the owner’s motion for summary judgment on the contractor’s Prompt Pay claim. After the jury returned a verdict in favor of the contractor, the parties cross-appealed the superior court’s rulings on these motions.

The appellate court held that an owner may be liable for breach of contract even though the owner did not violate the private Prompt Pay Act in A.R.S. § 32-1129.01. The court reasoned that the Prompt Pay Act did not replace traditional contractual remedies. In doing so, the court rejected the owner’s argument that the superior court’s decision that the owner had not violated the Prompt Pay Act meant that, as a matter of law, the owner had not breached the parties’ contract. The appellate court affirmed the dismissal of the contractor’s Prompt Pay Act claim because the contractor had submitted the payment application prior to obtaining inspection and the certificate of completion, steps contemplated by the parties’ contract and the Prompt Pay Act.

The appellate court also distinguished the result in American Continental. The court held that the contract in American Continental made obtaining the certificate of final payment a condition precedent to the contractor’s right to payment. The court reasoned that “the contract language [in MTR Builders], when viewed as a whole, is not a strict condition precedent contract.” Instead, the appellate court determined that the contract provided the contractor an express remedy to recover for work it actually performed to the inspector’s satisfaction and allowed the contractor to seek damages in the event of owner’s breach of the obligation to pay. The fact that the contractor sought payment before obtaining the inspection and the certificate of completion did not bar the contractor’s recovery.

The case provides important lessons for owners and contractors, both in crafting effective contract language and complying with the obligations contained in the contracts as they are written. Owners need to timely object to any written request for payment coming from a contractor so as to not violate the Prompt Pay Act. Owners also need to take care that any objection they raise provides them an adequate legal protection before deciding to not pay for work that a contractor actually performs. Owners should be cautious in relying solely on the result in American Continental to avoid paying for work a contractor actually performs. In light of the Arizona Prompt Pay Act, courts may distinguish or overrule American Continental or limit it to its unique facts and specific contractual language.

Contractors should be sure to resubmit payment applications once they clear up any objections raised by an owner to a payment application. Ultimately, whether you are an owner or a contractor, it is critical to read and understand your contract, comply with its express obligations, and also understand the Arizona Prompt Payment Act. Here, the jury ended up awarding the contractor $50,000 for the work the jury found the contractor performed, and the superior court awarded the contractor over $100,000 in attorney’s fees because it prevailed at trial. That’s an expensive lesson.

California Court Reviews Sufficiency of Proof of Construction Claim Damages and Adopts Eichleay

by Michael J. Baker

In a wide-ranging review of proving construction delay and impact damages, the California Court of Appeal in the case of JMR Construction Corp. V. Environmental Assessment and Remediation Management, Inc. (EAR), 198 Cal.Rptr. 3rd 47 (2015), evaluated whether it was appropriate to use a modified total cost calculation to prove construction delay and disruption damages, evaluated what is sufficient evidence for an appropriate allocation of delay damages for extended field overhead, analyzed the impact of concurrent delay without a construction schedule analysis in assessing those damages; and, for the first time in a California published decision, adopted the Federal Eichleay formula to calculate home office overhead delay damages.

The dispute arose from a public works project involving the construction of a dental clinic at the Presidio of Monterey. The owner, the United States Army Corps of Engineers, retained JMR Construction Corp. (JMR) as general contractor for the project. JMR, in turn, entered into various subcontracts, including separate electrical and plumbing subcontracts with EAR. While the project was ongoing, JMR (1) communicated with EAR about alleged delays, deficient and late submittals, and improper plumbing work, and (2) retained certain funds otherwise due to EAR under the subcontract. After the project was completed, JMR filed suit against EAR and its surety for breach of contract and for breach of the performance bonds. JMR alleged it was damaged as a result of EAR's failure to perform under the two subcontracts. EAR filed a cross-complaint for recovery of retention funds withheld under the two subcontracts. After a court trial, JMR was awarded damages which included an offset for retention funds JMR withheld under the two subcontracts. On appeal, EAR argued that there was no substantial evidence supporting the trial court's finding that it was liable to JMR for delay on the project and argued that the court erred by using the Federal Eichleay method of calculating extended home office overhead damages. EAR also argued that the court erred by utilizing the modified total cost method of calculating disruption and delay damages. The Appellate Court upheld the trial court.

This case is significant in that it identifies and discusses what is sufficient substantial evidence to support and prove recovery of delay damages and an allocation of such damages among the parties. Here, the court allowed a modified total cost recovery so long as there was substantial evidence of a causal relationship between the extra costs incurred by JMR, general contractor, and the breach of contract by EAR, the subcontractor. The court applied the four-part test for total cost recovery (1) the impracticability of proving actual losses directly; (2) the contractor's bid was reasonable; (3) the contractor's actual costs were reasonable; and (4) the contractor was not responsible for the added cost. The court noted and emphasized that recovery should be applied only to the smallest affected portion of the contractual relationship that can be clearly identified. Here, the general contractor established through expert testimony specific portions of mechanical and electrical work which impacted the general contractor's drywall work in almost every room of the project and the trial court found this testimony to be credible and permitted a modified cost recovery. The Appellate Court accepted that an exact causal relationship was not necessary to establish impact but instead impact was established by the totality of the circumstances through testimony of percipient witnesses and experts. It is important to note here that the subcontractor did not have an opposing expert witness testify at trial.

The court also affirmed damages regarding the apportionment of overhead based on something as simple as an expert assigning percentages of delay to various parties without any definitive construction schedule analysis. The court let stand the general contractor's and its expert’s opinion that the subcontractor, EAR, was responsible for 75 percent of 142 days of delay shared between the subcontractor EAR and another subcontractor. This calculation was accepted by both the trial and appellate courts without the aid of expert schedule analysis. This is a significant shift in the typical accepted approach, i.e., it now appears that an exact schedule analysis may not be necessary after all. Moreover, as if the departure from using a schedule analysis was not enough of a surprise, the court also allowed and upheld an award of general delay damages to the general contractor based on a (speculation?) amount it would have allegedly won from the owner but for the subcontractor's delays. Therefore, the subcontractor was responsible for the general contractor's delay costs.

In another interesting twist, in determining and assigning responsibility for the allocable cost of overhead to the multiple entities responsible for the extended time of performance, the court accepted the general contractor’s expert’s calculation of assessing the damages based on a ratio of outstanding submittals per entity. Remarkably, the trial court accepted that whoever submitted the most submittals likely caused most of the delay. The appellate court affirmed that this analysis was sufficient to support the damages. This runs counter to the industry consensus opinion that there is not necessarily a causal connection between the quantity of submittals and length of delay. Nevertheless, this type of calculation was upheld here. It is obvious to most everyone in the industry that one crucial submittal by one subcontractor could be much more impactful than 15 or more insignificant submittals from a different subcontractor, but the general contractor was able to employ this method here and convince the trial court. Again, it is important to note that the subcontractor here did not offer any opposing experts and thus the general contractor’s and its expert’s testimony was unopposed.

Finally, in a matter of first impression, we now have a case in California which accepts the Federal Eichleay formula as a measure of extended home office overhead, subject to the Federal Eichleay conditions. The court set forth the three Eichleay requirements for its application. The contractor must establish: (1) a government cause a delay; (2) that the contractor was on "standby"; and (3) that the contractor was unable to take on other work. Note, the court required conformance with all three elements, most notably the requirement to prove that but for the delay, the general contractor could not go after new work. While the case is one of first impression in California regarding Eichleay, use of the formula is still debated because to recover the contractor has to open up their financials and prove that it could not get work.

This case is both a benefit and a burden. On the one hand the Court’s approval of the method here of proving damages using a modified total cost method and apportioning delay damages among contractors is helpful and instructive as to what constitutes substantial evidence to support such damages; however, on the other hand, if you are defending one of these claims it has just become more difficult, particularly with the relaxation of proving causation and apportionment of delay without schedule analysis.

Indemnification of Defendant by HOA for Attorney’s Fees and Costs in Utah Construction Defect Litigation

by Elisabeth M. McOmber

Articles of Incorporation and other governing documents for a homeowner’s association (HOA) often contain indemnification provisions for HOA board members and former board members providing that the HOA will indemnify board members that are made party to a suit. These provisions are put in place early in a development project and often contain broad terms. It pays to consider the long-term consequences that may result from these provisions should an HOA later bring a construction defect case against the original developer.

Utah trial courts have recently been granting motions for indemnification filed by developer defendants against plaintiff HOAs based on the terms of the HOA’s Articles of Incorporation or other governing documents. The cases involve breach of fiduciary duty claims by an HOA against developer defendants who were original board members of the HOA during the development of the given project. Upon prevailing at trial or via dispositive motion, defendants have asserted that, because the court has found the developer defendant not liable for breach of any fiduciary duty while a member of the HOA, the HOA must indemnify the defendant for the attorney’s fees and costs incurred in defending against the HOA’s construction defect claims. Some Utah courts have agreed. Applying traditional rules of contract construction, Utah courts have found that broad indemnification provisions are unambiguous and apply to HOA board members/developers for a suit brought against the member by the HOA where the board member/developer was determined not to be negligent or to have engaged in misconduct. The courts have accordingly held that the HOA must indemnify the board member/developer for fees and costs incurred in the lawsuit brought by the HOA. Not surprisingly, such rulings can result in a considerable award against the HOA, with one recent trial court judgment including over $300,000 in fees and costs.

In sum, while it is likely this issue will eventually be clarified by appellate court decisions, awareness of this developing issue can help guide HOAs, owners, and developers to best position themselves both prior to and in the course of construction defect litigation.

DISCLAIMER: Because of the generality of this update, the information provided herein may not be applicable in all situations and should not be acted upon without specific legal advice based on particular situations.

© Snell & Wilmer | Attorney Advertising

Written by:

Snell & Wilmer

Snell & Wilmer on:

Readers' Choice 2017
Reporters on Deadline

Related Case Law

"My best business intelligence, in one easy email…"

Your first step to building a free, personalized, morning email brief covering pertinent authors and topics on JD Supra:
*By using the service, you signify your acceptance of JD Supra's Privacy Policy.
Custom Email Digest
- hide

JD Supra Privacy Policy

Updated: May 25, 2018:

JD Supra is a legal publishing service that connects experts and their content with broader audiences of professionals, journalists and associations.

This Privacy Policy describes how JD Supra, LLC ("JD Supra" or "we," "us," or "our") collects, uses and shares personal data collected from visitors to our website (located at www.jdsupra.com) (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 privacy@jdsupra.com.

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 privacy@jdsupra.com 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 privacy@jdsupra.com 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 privacy@jdsupra.com. 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 privacy@jdsupra.com.

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: privacy@jdsupra.com.

JD Supra Cookie Guide

As with many websites, JD Supra's website (located at www.jdsupra.com) (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 legal.hubspot.com/privacy-policy.
  • New Relic - For more information on New Relic cookies, please visit www.newrelic.com/privacy.
  • Google Analytics - For more information on Google Analytics cookies, visit www.google.com/policies. To opt-out of being tracked by Google Analytics across all websites visit http://tools.google.com/dlpage/gaoptout. 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 http://www.aboutcookies.org 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: privacy@jdsupra.com.

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