Tsibouris & Associates Home | Practice Areas | Attorneys | Contact | Publications | Clients | Blog Home

Monday, March 08, 2010

Insurance Provider Settles Case Due to Deficiencies in Electronic Signatures, Electronic Evidence, and Contract Drafting

By Mehmet Munur

A District Court in New York recently decided a case where the perfect storm of messy contract drafting, which left a key term undefined and ambiguous, lack of proper evidence to prove the date of formation of the contract, and deficiencies in electronic signatures forced a life insurance provider to settle the case. While the court held that the electronic signatures used to sign the life insurance application survived summary judgment, the definition of the term Participant was vague and could not result in summary judgment for the insurance company. The case highlights the importance of precisely defining terms in a contract, building appropriate procedures for proving the existence of electronic contracts, and procedures for identifying the person electronically signing documents.

Neil Dukoff, an AICPA member, and Shari Dukoff, as his dependent, entered into a group life insurance contract with Prudential Insurance for Mrs. Dukoff using an electronic application in 2004. After Shari Dukoff passed away in May 2006, Prudential refused to honor the insurance contract arguing that the insurance contract was based on material misrepresentations in the application related to Mrs. Dukoff’s cancer surgery. Both sides moved for summary judgment, both motions were denied.

I. Prudential’s Arguments for Summary Judgment

Prudential made two arguments for summary judgment. First, it argued that there was no valid contract because Mr. Dukoff was not a party to the contract. Second, Prudential argued that the contract was procured through fraud and was, therefore, invalid. In both cases, Prudential could have helped resolved the issues by properly defining and using the words “Participant,” “Dependent,” “I,” and “My.”

A. Parties to the Contract

The court denied Prudential’s motion for summary judgment on the ground that Mr. Dukoff was not a party to the contract because there was enough doubt as to whether Mr. Dukoff or Mrs. Dukoff signed the contract. The court also found that the contract was ambiguous as to who was the intended party.

Prudential argued that there was no contract because Mrs. Dukoff was in the hospital recovering from surgery during the time she was to have signed the contract. Prudential offered as evidence a computer printout showing that the contract was submitted on May 15, 2004, the date on which both parties agree that Mrs. Dukoff was recovering from surgery in the hospital. However, Mr. Dukoff stated under oath that the contract was signed around March or April 2004. The court held that this printout was not sufficient to accurately show that the date reflected was the date of submission.

Needless to say, this is far too small a digital footprint for a contract that was formed online. Prudential could have built systems that logged applications submitted on its servers. In this log, Prudential could have recorded the time, location by IP address, unique cookie information, and other information related to the submission of the application and produced this evidence in trial. Prudential could have sent an automatic confirmation email to the email address of the applicant right after the submission of the application online. Finally, Prudential could have shown that a confirmation letter was sent several days after the submission with welcome letters and the signed contract. It is likely that Prudential had one or more of these processes in place. However, Prudential did not present any of more evidence than the printed contract with the date. Counsel for Prudential may have been more worried about the ambiguities in the contract than the proving the exact date of formation of the contract.

The court then turned to the language of the contract to address these ambiguities. In at least one section, “the applicant state[d] that ‘I’ authorize Prudential to access ‘my’ medical records to determine eligibility for insurance.” Considering that Mr. Dukoff did not need to provide his medical records, the court concluded that this language pointed to Mrs. Dukoff as the party to the contract. The certificate of coverage was of no use because it stated both names on it. Adding apparent authority and ratification issues to the mix, the court decided that there was a genuine issue of material fact as to who were the parties to the contract.

B. Procurement through Fraud

The court then turned to Prudential’s second argument for motion for summary judgment: fraud. However, the court did not need to address the admissibility of the evidence related to Mrs. Dukoff medical records and fraud. Once again, there was a genuine issue of material fact as to whether Prudential challenged the validity of the contract in the appropriate time.

Prudential contested the validity of the insurance policy after more than 2 years of its effective date. However, Prudential argued that the contract allowed it to contest its validity using Mrs. Dukoff’s statements 2 years after her death. The court found that the undefined term “Participant” made the language related to challenge within 2 years ambiguous. The contract and the certificate of insurance stated:

Incontestability of Dependents Life Insurance
This limits Prudential’s use of a Participant’s statements in contesting an amount of Dependents Life Insurance for which the Participant is insured with respect to a dependent. These are statements made to persuade Prudential to accept you for insurance.
They will be considered to be made to the best of your knowledge and belief. These rules apply to each statement:
(1) It will not be used in the contest unless:
(a) it is in a written instrument signed by the Participant; and
(b) A copy of that instrument is or has been furnished to the Participant or the Participant’s Beneficiary.
(2) If it relates to the dependents [sic] insurability, it will not be used to contest the validity of Dependents Life Insurance which has been in force, before the contest, for at least two years during the Participant’s lifetime.

The court held that the term Participant was not expressly defined and could refer to either Mr. Dukoff or Mrs. Dukoff. On the one hand, the terms “Participant Insurance” and “Dependent Insurance” appropriately and respectively referred to Mr. Dukoff and Mrs. Dukoff. On the other hand, the sentence above relating to “statements made to persuade Prudential accept you for insurance” suggested that Mrs. Dukoff was the Participant.

Most importantly, the last statement quoted from the contract above suggested that the Participant’s statements would not be used to contest validity of the Dependent’s life insurance for at least two years during the Participant’s lifetime. However, the lack of definition of the words “Dependent” and “Participant” resulted in ambiguity in deciding whose words could be used against whom. Therefore, the court returned to basic contract interpretation and sought extrinsic evidence, considered the New York statute where the language was supposed to have come from, and lacking additional evidence to the parties’ intent, rejected Prudential’s motion for summary judgment.

Such key terms should have been appropriately and clearly defined, especially if they were capitalized. Additionally, Prudential might have been better served by inserting the required language directly from the statute, which referred to “statements made by any person” instead of the complex Participant and Dependent scheme that Prudential created.

II. Mr. Dukoff’s Arguments for Summary Judgment

In its motion for summary judgment, Mr. Dukoff argued, among other things, that the statements related to Mrs. Dukoff’s health were not signed due to the failure of the electronic signatures scheme that Prudential used. The court held that particular information used in the application was sufficient to identify her as the person signing the application; therefore, Mr. Dukoff was not entitled to summary judgment on the issue.

The insurance contract prohibited the use of statements made by the insured that was not “in a written instrument signed by the [insured]” to contest the contract. Thus, Mr. Dukoff argued that Mrs. Dukoff did not sign her statements. In return, Prudential argued that the electronic signature on the application satisfied the NY Electronic Signatures and Records Act as well as the contractual requirement for written statement and signature. The New York law states that electronic signature “shall have the same validity and effect as a signature affixed by hand.” The law also defines electronic signature as “an electronic sound, symbol, or process, attached to or logically associated with an electronic record and executed or adopted by a person with the intent to sign the document.” The court then turned to Prudential’s application process to determine whether it complied with NY law.

Prudential used a “standard” click through that included the following language at the end:

*I agree By submitting this form, I hereby request coverage under the CPA Spouse Life Insurance Plan. I have read the Conditions Applicable to This Subscription on this web site and agree to those statements and conditions. I also hereby subscribe to the AICPA Insurance Trust in accordance with Member’s Subscription and agree to the applicable conditions.

The applicants also had to enter home address and social security numbers. Prudential argued that this click-through agreement and the use of the identifiers satisfied the definition of electronic signature under NY law.

Not finding any case that invalidated a contract based on electronic signatures, the court turned to State of New York Insurance Department opinions. One particular Opinion stated that, generally speaking, a checked box on an electronic form on the Internet constitutes a valid electronic signature so long as it abides by the definition of electronic signature under the New York law. However, the opinion then added that such technology must be “capable of verifying that the person providing the electronic signature is actually the party to be charged. “ The Opinion further stated that “without such verification measure in place, the Department would not consider a checked box to be a valid signature.” Based on this Opinion, Mr. Dukoff argued that Prudential did not have the means to verify the identity of the person electronically signing the document.

The court deferred to the Opinion but it seemed puzzled by one finding. The NY legislature had removed a reference to a requirement for the electronic signature to include a unique identifier capable of verification from the law several years ago. More specifically, the NY law used to require a unique identifier “capable of verification, under the sole control of the person using it, attached to or associated with data in a manner that authenticates the attachment of the signature to particular data.” The court must have felt that the Opinion inserted back this unique identifier and verification requirement. Therefore, in its interpretation, the court changed the “actual identification” language of the Opinion to “reasonable identification” of the person. However, this being a motion for summary judgment, the court’s finding that “it is at least possible that Prudential satisfied this requirement” by using identifying information, such as address, social security number, and physical description, is excusable.

However, considering that the electronic signature in this case was supposed to be able to distinguish between a husband and a wife signing an application for a $500,000 life insurance, the click-through could not have satisfied the standard created by the Opinion. Under the circumstances, provision of the three pieces of information cannot actually identify the person signing the document. The technology supporting the electronic signature was required to identify the person signing the application to a higher degree of certainty than reasonable identification. Here, Prudential did not have the technology or the processes in place to ensure that Mrs. Dukoff and not Mr. Dukoff electronically signed the application. Considering the amount of money at stake, Prudential could have authenticated the signature by sending a password via text message to her cell-phone, via email to her email address, via mail to her home address, or using any other similar method. The first two methods would likely help distinguish between a husband and a wife signing a document under most circumstances. However, it is unlikely that any of these circumstances would help distinguish between the two when one of them is in the hospital recovering from surgery. This is probably one reason that other life insurance companies require applicants to sign their applications over the phone using a voice signature.

In sum, this perfect storm of electronic signatures that barely survived legal scrutiny, lack of evidence proving the date on which the contract was signed, and contract terms that were confusing even to the court to interpret resulted in Prudential having to settle the case shortly after it lost its motion for summary judgment. This case is just another reminder that companies must continue to pay attention to the fundamentals of contract drafting while at the same time paying particular attention to electronic signatures and electronic evidence relating to those contracts.

The case is Prudential Ins. Co. of Am. v. Dukoff, No: 2:07-cv-01080-ADS-MLO (E.D.N.Y. Dec. 18, 2009).

Labels: ,

Read More...

Monday, November 10, 2008

Google Updates IP Address Log Retention Policy

By Dino Tsibouris & Mehmet Munur

On September 8, 2008, Google announced that it will reduce the amount of time it retains distinct IP addresses from 18 months to 9 months due to pressure from European regulators. This is not the first time, and likely not the last time, Google will have to amend its IP log retention period in order to comply with the European regulators’ strict policies.

In June of 2007, Google had to reduce the amount of time it retained distinct IP addresses from 24 months to 18 months, due to pressure from the EU Article 29 Data Protection Working Party. After 18 months of obtaining the IP addresses, Google anonymized its IP logs by replacing the last byte of the IP address with hashes (for example 216.54.106.###). Then, Google “firmly reject[ed] any suggestions that [it] could meet [its] legitimate interests in security, innovation and anti-fraud efforts with any retention period shorter than 18 months.”

This recent change in IP log retention policy is certainly in part due to the Working Party’s Opinion on Data Protection Issues Related to Search Engines released in March 2008. The Working Party suggested that the “retention of personal data and the corresponding retention period must always be justified (with concrete and relevant arguments) and reduced to a minimum, to improve transparency to ensure fair processing, and to guarantee proportionality with the purpose that justifies such retention.” More importantly, if “search engine providers retain personal data longer than 6 months, they will have to demonstrate comprehensively that it is strictly necessary for the service.” The Working party then concluded that “[i]n view of the initial explanations given by search engine providers on the possible purposes for collecting personal data, the Working Party does not see a basis for a retention period beyond 6 months.” It appears that Google’s rejection was not firm enough.

Before issuing this opinion, the Working Party sent questionnaires to many search engines. Undoubtedly, Google was one of the search engines that received a questionnaire. Google must have predicted that the Working Party would issue an opinion on IP addresses and cookie use as a result of this questionnaire. Google probably provided all the justifications that it could, but the Working Party was not satisfied. Considering that the Working Party concluded that logs should be retained for 6 months—not 9—Google either has a better justification, or another revision to its privacy policy awaits Google in the near future.

Google may also have problems with the methods it uses to anonymize the logs. The Working Party opinion also commented on Google’s anonymization methods and suggested that they may not be satisfactory under all circumstances. “Currently, some search engine providers truncate IPv4 addresses by removing the final [byte], thus in effect retaining information about the user's ISP or subnet, but not directly identifying the individual. The activity could then originate from any of 254 IP addresses. This may not always be enough to guarantee anonymisation.”

Furthermore, Google has not finalized the methods it is going to use to anonymize IP addresses. In its recent announcement, Google stated that it had not “sorted out all of the implementation details, and [it] may not be able to use precisely the same methods for anonymizing as [it] d[id] after 18 months . . . .” In other words, the anonymization used after 18 months and anonymization used after 9 months are different methods of anonymization. Considering that the Working Party is not satisfied with the first method under all circumstances, arguably, the Working Party may not be satisfied with the new method, either.

One reason for this continuous disagreement over Google’s privacy policy may be about how Google and the European regulators think about privacy. IP address logs are an invaluable source of competitive information for Google; therefore, it would like to retain them unless they are shown to be personal data. In other words, presume the data to be non-personal unless proven otherwise. To support this view, Peter Fleischer, Google’s Global Privacy Counsel, argued in NY Times Bits and in his own blog that he did not think that IP addresses were private data under all circumstances. Both Mr. Fleischer and a Google engineer stressed that IP addresses did not always return to a unique individual but could shared among many users.

The Working Party disagreed. The Working Party opinion stated that “increasing number of ISPs distribute fixed IP addresses to individual users.” Then, the Working Party turned the presumption on its head by stating that “unless the [Search Engine] is in a position to distinguish with absolute certainty that the data correspond to users that cannot be identified, it will have to treat all IP information as personal data, to be on the safe side.” In sum, Google would like a sliding scale approach to IP addresses privacy while the Working Party sees all IP addresses as personal data. This stark difference in approach to privacy is likely to result in more revisions for Google’s IP address logs.

Certainly, Google appears to be taking a serious approach to privacy by creating Google Privacy Channel on YouTube, and drafting a reader friendly Terms of Use. Despite all its efforts, Google’s actions are likely to stay on the spotlight for some time to come. One cannot expect Google to give up so easily on IP address logs that allow Google to provide better services and get the upper hand on its competitors.


Labels: ,

Read More...