An Open Door Gives Away The Secret, But Rule 502 Attracts It Back

March 31, 2009

Pyramid at Night with the All Seeing Eye branded with the latest nonsenseA new case involving the movie The Secret provides excellent analysis of new Evidence Rule 502 while at the same time taking irony to new heights. Heriot v. Byrne, 2009 WL 742769 (N.D. Ill. March 20, 2009).

I do not normally write a blog in the middle of the week, but the sarcastic potential and ironies in Heriot v. Byrne are just too much to resist – sleep can wait. The Law of Attraction compels this exposé. Consider the facts. This is a law suit about a movie called The Secret, where one of the corporate defendants is named The Secret, LLC. All of the parties in this law suit were somehow involved in the conception and making of The Secret. The movie was a huge New Age success. The exalted spiritual masters who conceived and produced The Secret did so, or so they say, to share the secret of the ages as to how to attract success and happiness in your life.

Well, now the real secret is out, these special masters have indeed attracted what they deserve, they have attracted lawyers and fights over money. The plaintiffs claim to own part of The Secret. The defendants deny that and have filed counter-claims of their own. The plaintiffs’ primary goal seems to be their accounting claims where they are trying to find out how much money The Secret has made, which, so far, the defendants have kept secret.

But wait, there’s still more secrets. The defendants accidentally received some of the plaintiffs secret emails to their attorney. They received these secrets because the plaintiffs’ e-discovery vendor made a mistake. The named of the vendor is Open Door Solutions. You cannot make this stuff up. If this were a movie, you would not believe it, which, by the way, appears to have been the judge’s reaction to the movie, but we will get to that in a minute.

Back to the open-door disclosure of the plaintiffs’ secret attorney communications. When these secrets were accidentally disclosed to defense counsel, they denied that they were secrets at all. Alternatively, they said that even if they were once secrets, they were no longer secrets, because the secrets were revealed. They argued that the disclosure of the secrets by handing them over to opposing counsel waived any attorney client privilege that these secrets might have once enjoyed.

Plaintiffs tried to protect their secrets by relying on new Evidence Rule 502. It protects attorney-client secrets and requires clawback of inadvertently disclosed secrets if certain conditions are met. Defendants denied clawback and the applicability of Rule 502. Defendants claimed that the plaintiffs’ disclosure of secrets was not inadvertent. Even if the disclosure was inadvertent, defendants argued that Rule 502 should still not protect the secrets because it only protects secrets where reasonable steps to prevent disclosure were taken. The claimed that the way-too-open-door handling of plaintiffs’ alleged secrets was negligent and thus not protected by Rule 502. Finally, they argued that even if these secrets were protected by Rule 502, they should still be allowed to tell these secrets, and not give them back, because of the crime-fraud exception to the attorney-client privilege. That is the rule where a client cannot keep secret any communications he may have with his attorneys about a crime or fraud that he may commit in the future. (Confidential communications about past crimes and fraud committed in the past can, however, be kept secret.)

Secret Shh!So to summarize, open door mistakes led to a battle between the masters of The Secret over the attorney-client secrets of a man who claimed to own part of The Secret and wanted its secret profits disclosed. The defendants, purported sole owners of The Secret, including  one called The Secret, LLC., wanted to keep their profits secret, but disclose the plaintiffs’ secrets, claiming they were not secrets at all, or if they were, they were bad secrets not entitled to secrecy, or they were waived by a way-too-open door handling of the secrets. (Try saying that real fast.)

Magistrate Judge Martin C. Ashman attracted to himself the task of sorting out this tangled web. As mentioned, Judge Ashman was not too impressed by the movie The Secret, as he begins his opinion by noting:

This case involves a controversy over The Secret, a made-for-television documentary that purports to reveal the “most powerful law in the universe.” The Secret, http://www.thesecret.tv/ (last visited Mar. 17, 2009). As if that declaration was not grandiose enough, the website further claims that, “[b]y applying the knowledge of this law, you can change every aspect of your life.”  

Although Judge Ashman did not think The Secret the parties had created was much of a secret, he did think the plaintiff’s secrets were bona fide and entitled to protection. He upheld the attorney-client privilege by applying Evidence Rule 502. He held that the open-door disclosure was a mistake, and happened in spite of the reasonable steps to prevent disclosure that had been instituted by plaintiff’s attorneys. For that reason, Judge Ashman enforced the clawback provisions of Rule 502 and required that the defendants, including The Secret, LLC., to keep the plaintiffs’ secrets secret.

Factual and Procedural Background

Open Door

This saga of secrets began innocently enough with the defendants’ request for production, including  “[a]ll documents relating to United States visa applications filed by or on behalf of Heriot.” The plaintiff, Drew Heriot, happens to be a citizen of Australia, as are most of the other parties to this action.

Since all documents these days are created electronically, this triggered e-discovery, which in turn triggered the attorneys for Heriot to seek the help of an e-discovery vendor, the mentioned Open Door Solutions. Open Door provided electronic scanning, optical character recognition, and other discovery related services.  Here is the court’s description of the process which Open Door (here called the “Vendor”) and Heriot’s attorneys set up for this production:

First, the Vendor created a database of the documents provided to it by Plaintiffs (“Master Database”), which Plaintiffs then could review. (Id. at 3-4.) Second, during April and May of 2008, Plaintiffs “had paralegals and other non-lawyers conduct a preliminary review [of] the documents in the Master Database,” assigning documents “general, pretrial discovery codes.” (Id. at 4.) One general code was “immigration,” which Plaintiffs “used to flag documents (primarily e[-]mails) that had anything to do with Mr. Heriot’s immigration to the United States.”(Id.) (Editors note: the misspelling of “immigration” in the Westlaw transcription was corrected as an obvious error.)

Third, Plaintiffs searched for responsive documents in their Master Database. (Id.) Fourth, once identified, these responsive documents would be “coded for subsequent copying and inclusion in the Production Database.” (Id.) Additionally, Plaintiffs would mark responsive documents “as either Confidential or Highly Confidential under the Stipulated Protective Order.”

Id. at *2. 

This is a pretty standard plan of action, except that I do not see privilege review and logging specifically mentioned.  To comply with the discovery request regarding Heriot’s immigration visa, plaintiffs requested and received a paper copy of the visa file from Heriot’s immigration lawyer. Next, plaintiffs gave the Heriot’s visa application to Open Door with instructions to:

(1) scan and add it to the Master Database, (2) copy the scanned versions to the Production Database, … (3) electronically stamp the application as ‘Highly Confidential’ for production[,] … [ (4) ] Bates Stamp all documents in the Production Database, and … [ (5) ] include Mr. Heriot’s visa application and other sensitive material at the front of the production.

Id. 

Now we come to the mistake of Open Door. (By the way, mistakes like this can and do happen to most everyone sooner or later, but seem to happen more often to some than to others.) Frankly, from the court’s limited description of the facts in the opinion, I cannot understand exactly what the vendor did wrong that supposedly blew the privilege review, but I gather it had to do with mixing the sensitive visa related materials in with the general database and not placing them in the front of the production for review as instructed. The vague description makes me more sympathetic towards Open Door and a little suspicious about the attorneys. All we know for sure is that mistakes were made here and secret emails were unintentionally produced.

On August 25, 2008, plaintiffs produced around 1,499 documents comprised of 6,952 pages. This is a pretty small production by today’s standards. Plaintiffs did not withhold any documents for privilege and so did not produce a privilege log. That does seem odd. Two months later, on October 22, 2008, plaintiffs counsel discovered the mistake in production while preparing for a deposition scheduled for October 24, 2008. The next day, October 23rd, they notified defense counsel of the inadvertent production and demanded the return and destruction of certain documents they claimed were privileged. The defense complied, but kept one copy for use to challenge the claimed privilege protection. The defendants then promptly filed a motion to compel production, including the challenged documents, which were filed under seal. The plaintiffs opposed that motion and filed their own unrelated motions to compel.

Legal Analysis on Waiver

Judge Ashman begins the legal analysis with the following overview of the law (citations omitted):

Ordinarily, disclosure of confidential information to an unprotected third party operates as a waiver.  Under FRE 502, however, disclosure of privileged information will not operate as a waiver when “(1) the disclosure is inadvertent; (2) the holder of the privilege or protection took reasonable steps to prevent disclosure; and (3) the holder promptly took reasonable steps to rectify the error, including (if applicable) following Federal Rule of Civil Procedure 26(b)(5)(B).” FED.R.EVID. 502(b)(1)-(3). All three elements described in FRE 502 must be satisfied to prevent a waiver. Id.

Id. at *5

Wave byeThe court then considered the issue of whether the new rule superseded prior federal common law concerning waiver of attorney-client privilege. The court basically said it did, unless the prior law (here Judson Atkinson Candies, Inc., v. Latini-Hohberger Dhimantec, 529 F.3d 371, 387-88 (7th Cir.2008)) was not conflicting. Here Judson was not conflicting (it was harmonious) and so the court used Judson to supplement its analysis and articulated the following test (footnote omitted):

This Court therefore adopts the following test. First, a court determines whether the disclosed material is privileged. If it is not, the inquiry ends. If the material is privileged, the court applies FRE 502(b). If the court concludes that disclosing party satisfied all of the elements in FRE 502(b), the privilege is not waived. If, however, the disclosing party fails to satisfy any of the FRE 502 elements, the privilege is waived. In applying FRE 502(b), the court is free to consider any or all of the five Judson factors, provided they are relevant, to evaluate whether each element of FRE 502(b) has been satisfied. This Court applies and explains the details of this test in the following sections.

Id. at *7. Judge Ashman then applied the test where he began by finding that most of the emails in question were privileged. The judge personally reviewed all of the emails and found they contained legal advice to Heriot from his immigration lawyer. A few emails included prior non-privileged communication with a third party. They were to be produced, but with redactions to protect the privileged part of the email chain. A few others had been sent to third parties and, as to them, no privilege was allowed. Id. at *8-*9.

Next the court addressed the Crime-Fraud Exception to the attorney-client privilege. Here is the court’s summary of this law:

Although communications subject to the attorney-client privilege are protected, that protection can be forfeited when, for example, “ ‘the attorney … assist[s] his client to commit a crime or a fraud.’ “ U.S. v. Al-Shahin, 474 F.3d 941, 946 (7th Cir.2007) (quoting Mattenson v. Baxter Healthcare Corp., 438 F.3d 763, 769 (7th Cir.2006)). In other words, “[t]he crime-fraud exception places communications made in furtherance of a crime or fraud outside the attorney-client privilege.” U.S. v. BDO Seidman, LLP, 492 F.3d 806, 818 (7th Cir.2007) (citing U.S. v. Zolin, 491 U.S. 554, 563, 109 S.Ct. 2619, 105 L.Ed.2d 469 (1989)).

Id. at *9. It turns out that the defendant’s arguments here were very weak and there was no basis for a claim of fraud in these emails between Heriot and his immigration attorney. 

Three Part Test of Rule 502(b)

Judge Ashman then moved on to consider whether the three requirements of FRE 502(b) were met wherein disclosure of privileged information will not operate as a waiver when:  

(1) the disclosure is inadvertent;

(2) the holder of the privilege or protection took reasonable steps to prevent disclosure; and

(3) the holder promptly took reasonable steps to rectify the error, including (if applicable) following Federal Rule of Civil Procedure 26(b)(5)(B).”

Rule 502(b)(1)-(3) Fed.R.Evid.

1. Inadvertence

Oops! Shit happens.The court put the burden of proof on the party claiming the privilege in accord with established case law. This is the way it should be. Judge Ashman then found that the first requirement had been met, that the disclosure had been inadvertent. This was the right result, but he labored way-too-hard to get there. In my opinion, it is hard to see how a disclosure like this could be anything but “inadvertent,” taking the normal common sense meaning of the word as “unintentional,” or “not attentive.” Defense counsel here argued in accord with case law that “inadvertent” meant something completely different, that inadvertent here means “not negligent.” The defendants main argument on this point was that the disclosure was “not-inadvertent” because, in their words “Plaintiffs’ counsel … [was] asleep at the switch.” Heriot v. Byrne, supra at *11. Judge Ashman went along with that argument, but then went to great lengths to show they were not quite as asleep as alleged and so the disclosure was inadvertent as required under the rule.

I think this misreads the rule by conflating all three criteria into the first one. This incorrectly resurrects somewhat contra case law that Rule 502 supersedes. Obviously plaintiffs’ counsel was “asleep at the switch” when the production was made and that is exactly what inadvertent means, not attentive or unintentional. For part one of Rule 502(b) three-part test, the party should only have to prove that the disclosure was not done on purpose, that it was a mistake.

Here Judge Ashman made a finding that the disclosure was inadvertent because a variety of factors were met indicating the mistake was understandable and prompt corrective action was taken. These facts are relevant to the second and third prongs of the rule, not the first prong of inadvertence. For that reason I think Judge Ashman made a harmless error in stating:

To determine whether a disclosure was inadvertent, “this Court has … look[ed] to factors such as the total number of documents reviewed, the procedures used to review the documents before they were produced, and the actions of producing party after discovering that the documents had been produced.” WunderlichMalech Sys., Inc. v. Eisenmann Corp. (Eisenmann II), No. 05-C-4343, 2007 WL 3086006, at *3 (N.D.Ill. Oct. 18, 2007) (citing Wunderlich-Malech Sys., Inc. v. Eisenmann Corp. (Eisenmann I), No. 05-C-4343, 2006 WL 3370700, at *3 (N.D.Ill. Nov. 17, 2006)). This Court can find no reason to discard these factors, which aptly address the issue of whether a party inadvertently disclosed confidential information.

Id. at *11. The plain language of the rule is good reason enough for me. The court should have disregarded these prior case law factors, at least in so far as the determination of  the “inadvertence” test is concerned. All a party should have to prove to meet the first part of the test is that the disclosure was not intentional. If someone intentionally made the disclosure, and then just changed their mind for some reason, like perhaps new counsel was retained, then you would fail the first test. But if the disclosure was a mistake, an unintentional accident, then according to the normal commonsense meaning of the word, it was inadvertent, and you move on to the next two steps. 

This is, by the way, the only mistake I see in this opinion, which undertakes the difficult task of interpreting and applying a new rule with very little prior case law. This is otherwise a well reasoned opinion demonstrating excellent scholarship. I just hope that the many future cases that are likely to cite this decision do not make the same mistake of conflating the three criteria in Rule 502(b).

2. Reasonable Steps to Prevent

bank-vaultThe next thing to be proved under the Rule is that “the holder of the privilege or protection took reasonable steps to prevent disclosure.” Now we get into the facts and circumstances incorrectly considered by Judge Ashby in the determination of the first step. The defendants here argued that it was unreasonable for plaintiffs not to review the ESI after it was readied for production. They made this argument, even though plaintiffs’ counsel they had already reviewed the email and other documents before they were delivered to the vendor, here Open Door, for final processing and production. The defendants’ position would require either a double review, or review only after processing by a vendor. Either alternative is not acceptable in most circumstances, although I for one do not like a vendor to make direct productions, and where possible would prefer to make a final quick overview myself before production, just to be sure obvious errors were not made. Judge Ashby wisely rejected defendants contention and held:

… a pre-copy review procedure is not per se unreasonable. The procedure used here-where Plaintiffs reviewed the documents and then provided them to the Vendor for production-was reasonable; no disclosure would have occurred but for the Vendor’s error. 

Id. at *14. Of course, had plaintiffs counsel made a quick inspection before turning over the CD, this error might well have been caught. But whether mistakes were made is not the issue. Of course mistakes were made, or the unintentional disclosure would not have occurred. The issue is whether there was a reasonable procedure in place. Here the judge said there was and I do not disagree.

3. Reasonable Steps to Rectify

The third and final test under Rule 502(b) is whether the party that made the unintentional disclosure “promptly took reasonable steps to rectify the error.” Here there was a two week gap between the time of the production and the time the disclosure was noticed. Plaintiffs notified defendants the very next day after the mistake was discovered, so the defendant had to argue that the two month delay was not prompt or reasonable. This means they had to argue for the necessity of a post-production review.  I know that some attorneys and judges contend this is the intent of Rule 502: that you have to look again at documents already produced to verify that you caught and logged all privileged documents; that to do otherwise is not reasonable and constitutes a violation of Procedure Rule 26(b)(5), which requires that all withheld privileged documents be logged. This same people are at a loss to explain the Rules Commentary that expressly states:

The rule does not require the producing party to engage in a post-production review to determine whether any protected communication or information has been produced by mistake.

I agree with Judge Ashman who held:

Plaintiffs had no duty to re-review the documents after providing them to the Vendor. Id. That would be duplicative, wasteful, and against the spirit of FRE 502. Additionally, imposing on disclosing parties a duty to re-review would chill the use of e-vendors, which parties commonly employ to comply with onerous electronic discovery. Against this grain the Court cannot cut.

Heriot v. Byrne supra at *13.

I think it is clear that Rule 502 does not require another review after production, just to make double-sure that a mistake was not made and privileged documents inadvertently disclosed. If your preproduction steps to prevent disclosure were reasonable, then you are done and should not have to do anything more to search for privileged documents. Your only remaining duty should be to rectify, if and when you happen to discover a mistake while doing something else, like in this case, reviewing documents to prepare for a deposition, or you are advised of the mistake by opposing counsel. Many times when the later happens, opposing counsel will cooperate and just notify you of the mistake and send it back. This is especially true in circumstances where the vendor or law firm make a big mistake, like mislabeling a CD and turning over information to the wrong party. This kind of thing can easily happen despite all kinds of reasonable precautions and good intentions. When it does, most opposing counsel are very polite about, as they should be, and they tell but don’t look. After all, we all know that “Where discovery is extensive, mistakes are inevitable ….” In re Sulfuric Acid Antitrust Litig., 235 F.R.D. 407, 417 (N.D. Ill. 2006), quoted with approval in Heriot at *11.

Conclusion

This case, much like the movie, shows just how much time and money can be wasted over a few garden variety secrets. The parties would have been much better off practicing what their movie preaches. Of course, if that were true, there would have been no lawsuit and these secrets of 502 would not have been revealed. At least, not in such an ironically attractive manner.


New 4th Circuit Ruling on Illegal e-Discovery Adds Teeth to Federal Anti-Hacker Email Privacy Law

March 29, 2009

Hacker - misguided IT experts, often extremely smart and immatureThe Fourth Circuit Court of Appeals has strengthened federal anti-hacker email privacy law by allowing a civil suit for punitive damages alone, even when there are no actual damages. Van Alstyne v. Electronic Scriptorium, _F.3d_, 2009 WL 692512 (4th Cir. March 18, 2009). The Court recognized that the intentional taking of email stored online was a violation of the  Stored Communications Act (“SCA”), 18 U.S.C. §2707, allowing a victim to sue for monetary damages to punish the hacker and deter such future conduct.

This is a significant advance in privacy protection law because previously, punitive damage awards under the SCA were not allowed without proof of actual damages. Id. at pg. 16. People Helpers Found., Inc. v. City of Richmond, 12 F.3d 1321, 1326 (4th Cir. 1993). This is in accord with the general rule that punitive damages are never allowed without proof of actual damages unless a statute expressly allows it. Id. The Court found such authority in the civil enforcement section of the SCA, which states:

If the violation is willful or intentional, the court may assess punitive damages.

18 U.S.C. §2707(c). This is the first time the SCA has been so interpreted by a Circuit Court of Appeals and the first time punitive damages, costs, and attorney fees for an SCA violation have been allowed without proof of damages.

It is a Crime to Hack Into an Online Email Account

The unauthorized access of an AOL account in Van Alstyne constituted a violation of the SCA, which is part of the Electronics Communications Privacy Act (“ECPA”), 18 U.S.C. §2510, et seq. As the opinion at page 8 explains:

Section 2701 of the SCA creates a criminal offense for whoever “intentionally accesses without authorization a facility through which an electronic communication service is provided” or “intentionally exceeds an authorization to access that facility,” and by doing so “obtains, alters, or prevents authorized access to a wire or electronic communication while it is in electronic storage in such system.” 18 U.S.C.A. §2701(a)(1-2).

As background, Bonnie Van Alstyne was employed as Director of Marketing for Electronic Scriptorium, a small data-conversion company. She claimed she was fired after rejecting sexual advances from the CEO, Edward Leonard. At that point, Leonard did a little self-help e-discovery (we presume without any assistance from his lawyer) and hacked into Van Alstyne’s AOL email account.

AOL's old logo modified to look sadThis AOL account, like any online email service, is considered ”a facility through which an electronic communication service is provided” covered by the SCA. Leonard had somehow discovered Van Alstyne’s AOL password. We are not told how he did that, but he could have lawfully discovered it by looking on company computers. Regardless, Van Alstyne had never authorized Leonard to access her AOL account. Leonard used her AOL user-name and password to read her email. We do not know all of the nefarious motives behind this invasion of privacy, but certainly one motive was to try and find something that he could use against Van Alstyne to defend the sexual harassment claims. He found a few emails he liked, downloaded them, and provided them to his lawyer. The lawyer in turn surprised Van Alstyne with these emails during her deposition.

The downloading of emails from Van Alstyne’s AOL account without authorization constituted “obtaining … a electronic communication while it is in electronic storage in such system” and thus a clear violation of the SCA was established. The Court held that if the SCA is intentionally violated, then punitive damages, costs, and fees can be awarded, even though no damages were caused by the taking of the electronic communication.

Court Requires Actual Damages to Trigger the Statutory Minimum

The Court did, however, draw the line at the automatic award of the minimum statutory damages of $1,000 per unauthorized access. It held that it is not permitted under the statute without proof of some damages. In so doing, it followed the Supreme Court in Doe v. Chao, 540 U.S. 614, 627 (2004). The Supreme Court in Doe considered nearly identical language in the Privacy Act, 5 U.S.C. §552a (g)(4), and held that the $1,000 minimum statutory damages award was available “only to plaintiffs who suffered some actual damages.”

The Fourth Circuit considered itself to be bound by Doe, but reportedly five district courts in five different circuits did not. They had previously held to the contrary that proof of actual damages was not required to receive the statutory minimum award under the SCA. For this reason, some consider Van Alstyne to be a setback for privacy law, and indeed it is, to a degree. Still, this is a slight setback and pales in comparison to a Circuit Court of Appeal allowing punitive damages under the SCA without proof of actual damages.

Here is the Court’s summary, at page 8, of the civil action of damages allowed under the SCA:

Section 2707 provides a private cause of action for “any . . . other person aggrieved” by a violation of § 2701. 18 U.S.C.A. §2707(a). Under § 2707, a district court may award equitable or declaratory relief, a reasonable attorney’s fee and other costs, and “damages under subsection (c).” 18 U.S.C.A. §2707(b). Subsection (c) provides:

The court may assess as damages in a civil action under this section the sum of the actual damages suffered by the plaintiff and any profits made by the violator as a result of the violation, but in no case shall a person entitled to recover receive less than the sum of $1,000. If the violation is willful or intentional, the court may assess punitive damages. In the case of a successful action to enforce liability under this section, the court may assess the costs of the action, together with reasonable attorney fees determined by the court.

The Court rejected plaintiff’s arguments that the reference to a minimum award meant that you should receive $1,000 for every violation, even if there were no “actual damages.” I found the Court’s argument on that point persuasive and even forgetting Doe, which of course you cannot do, I do not see how five district courts were persuaded to rule to the contrary. If Congress had intended to allow a minimum statutory damage award absent proof of actual damages, it could easily have said so in the statute. For instance, The Wiretap Act, which like the SCA is found within the ECPA, does exactly that:

In any other action under this section, the court may assess as damages whichever is the greater of . . . the sum of the actual damages suffered by the plaintiff and any profits made by the violator . . . or . . . statutory damages of whichever is the greater of $100 a day for each day of violation or $10,000.

18 U.S.C. §2520(c)(2). I would support an amendment to the Stored Communications Act to provide for an automatic award of damages in an amount even greater than $1,000 per violation, but regardless, we now have incentive enough from actual and punitive damages to sue to enforce this important law.

Lesson For Hackers: Computer Privacy Law Now Has More Teeth

Hacker animation

Although this case arises out of an employer context, and involves other claims of sexual discrimination and wrongful discharge (thus the search for her email), this is not really an employment case, but rather an individual privacy rights case. This decision strengthens the protection of the Electronics Communications Privacy Act by encouraging civil suits to enforce the SCA email protection segments of this law.

Since it is often difficult or impossible to prove actual damages from an invasion of email privacy, there is little encouragement for victims to sue under the Stored Communications Act if the suit requires proof of damages. Further, as Van Alstyne argues in this case, if you do try to prove damages, such as emotional distress, you often open yourself up to very invasive discovery of all aspects of your personal life. This is something that most people, including Van Alstyne, are unwilling to do. The net result is that the hacker often walks, undeterred from doing it again to the next victim.

If a person is just embarrassed and annoyed by the interception and theft of their email and other electronic messages, and they cannot easily prove actual hard dollar damages, they had no incentive to sue the perpetrator. (They might be able to get an injunction or declaration, but so what.) If you must prove actual damages, then the victim’s only real hope to try to punish and deter a computer hacker is though the criminal system. A victim could file a complaint and hope the prosecutor would bring criminal charges. But as a practical matter, unless money is involved, few prosecutors have the time, money, expertise, or inclination to prosecute such computer privacy cases. The reluctance to prosecute non-monetary hacker cases is especially true in situations such as in this case, where there is ongoing civil litigation between private parties.

Aside from cases where there are actual damages, such as credit card or medical information hacker cases, criminal prosecutions for breach of computer privacy alone are few are far between. The only exception is the high profile case, such as 2008 Republican Vice presidential candidate Sarah Palin, whose Yahoo email account was hacked into during the election. A college student accessed her email account by guessing the answers to her security questions, and then publicly bragged about it. You betcha he was tracked down and indicted under the SCA. But even there, the student has not yet been convicted and there may be problems with the SCA criminal case.

Sarah Palin

Although many people use online email, it is far from secure. It is all too too easy to discover a person’s online email account password and “hack” into their email or other cloud computing accounts, including social media accounts such as Facebook. The ease of such computer intrusion or hacking is shown by this case and the Sara Palin case. This is especially true if you know the person, or they are a public figure and you can guess their password security questions as the Palin case shows. It is also easy to do if you have access to the person’s work computer and can trace their Internet use history, something most employers today can do.

There are many other instances of email hacking going on today that you never hear about, particularly in divorce or harassment cases. Thanks to Van Alstyne, in the future you will to start to hear about this much more often. The Fourth Circuit has strengthened the rights of computer users to privacy by adding punitive damage teeth to the Stored Communications Act. Since cloud computing has now become so pervasive, this is an important decision for everyone’s privacy rights, including corporations at risk for having their own computers and email systems hacked. Hackers beware! You may not only go to jail, but be sued for punitive damages and fees by everyone you hack.

Apparently this change in the law may also help plaintiffs in class-actions cases that allege SCA violations, such as suits against service providers like AT&T for turning over private email to the government without a valid subpoena. It will make it easier to state a cause of action under the SCA because you will no longer have to plead damages, just an intentional violation. According to class-action attorneys Al Gidari and Ryan Mrazik in their article on the Van Alstyne decision in Digestible Law:

Practically, this case actually makes it easier for plaintiffs to survive motions to dismiss for failure to plead actual damages because they now can assert the conduct was “willful or intentional” and discovery will be required to determine if punitive damages are warranted. And, because whether conduct is willful or intentional is a question of fact, it will be difficult for defendants to win summary judgment after discovery as well. In sum, the Fourth Circuit’s decision may open the door to much more SCA litigation.

Attorneys Gidari and Mrazik recommend that:

Companies should carefully consider when and whether to access, use, or disclose stored communications or customer information and ensure their conduct comports with SCA-authorized activities to avoid the now higher risk of litigation.

That is good advice for companies, spammers,  Gladys Kravitz-types, and hackers alike.

Lessons for e-Discovery Lawyers:
Beware of Illegally Hacked Email

Beware: Email Privacy Law now has some TeethThere are important lessons here for e-discovery lawyers too. The unauthorized access of a person’s private email account to discover and retrieve their email is a crime. Just because you know a person’s user name and password, does not give you the right to use it. This kind of self-help e-discovery is not only unethical, it is criminal. You must employ a request for production or subpoena. You cannot hack into their private email accounts or home computers any more than you can break into their house and steal papers.

Of course, this is different from a situation where you look at the contents of the employee’s office, or office computer, or office email account. See IT Workers Read Your Personal Email and U.S. Law is Generally OK with That. An employer can use an employee’s password to access their company computer and company email because they have authority to do that. But I have never seen an employment agreement or policy which provides an employer with authority to access an employee’s private email account, such as AOL, Yahoo, or Gmail, or hack into their home computer systems, regardless of whether they may sometimes use these computers and email services for business.  Also See: Quon v. Arch Wireless 529 F.3d 892, 2008 WL 2440559 (9th Cir., June 18, 2008), which I wrote about in More “Must Read” 2008 Cases. In Quon the Ninth Circuit held that a company’s disclosure of text messages to the employer, who was the “subscriber” and not “an addressee or intended recipient of such communication,” violated the SCA.

Van Alstyne sends a clear signal to the computer-savvy-Bar. You cannot use self-help in the guise of discovery or employee monitoring to hack a person’s private email account. Yes, I know it is ridiculously easy to hack into these online email and social media accounts. It might be a simple way get at the truth, expose liars, and win the case. It could be done surreptitiously and never disclosed. But don’t do it. This kind of self-help e-discovery is a crime. You could go to jail (up to five years), be fined, and lose your license. Also, as this case holds, you could face a civil suit and a jury with the power to punish the “bad lawyer” with damages. The CEO in Van Alstyne got tagged with a $100,000 punitive damage award. How much do you think a jury might award to punish a lawyer hacker or his or her law firm? It is an easy button to be sure, but don’t press it, and don’t allow your staff, hired detectives, or vendors to do it either.

Van Alstyne also sends a clear signal to the computer-challenged-Bar. Consider the facts in Van Alstyne as stated in the opinion. Van Alstyne was shown several emails during her deposition. They were presented to her in paper form and had apparently not been disclosed to her attorney before the deposition. She had written these emails before she was fired and she recognized them. Apparently they were all work related in some way and hurt her case.

Van Alstyne had primarily used her employer’s Outlook email for work, but would sometime also use her personal AOL email account. She suspected that some of the emails shown to her during the deposition were from her AOL account, not her Outlook account. (I do not know why this was just a suspicion, instead of obvious from the email address, but perhaps the emails all just showed the same user name or perhaps that portion of the email was not included on the papers shown to her). Here is the Court’s explanation of what happened after the deposition:

Van Alstyne believed that these exhibits were actually taken from her AOL account and not her company account. With her suspicions aroused, Van Alstyne began pursuing the possibility that Leonard and ESL had broken into that private account. Sure enough, during a June 2006 deposition, Leonard admitted that he accessed Van Alstyne’s AOL account after she left the company. He further testified that the emails produced during the deposition represented the only occasions on which he had accessed her account.

It turns out that Leonard, the alleged sexual harasser, was not entirely truthful during his deposition testimony. He had far more of Van Alstyne’s AOL emails than that. In truth, he had accessed her AOL account many, many times. In later depositions Leonard admitted the truth. Here are the Court words in footnote 2 about Leonard’s false testimony in his first deposition:

These statements were not entirely true. Indeed, Leonard ultimately admitted to accessing Van Alstyne’s AOL account at all hours of the day, from home and internet cafes, and from locales as diverse as London, Paris, and Hong Kong. During discovery, Leonard produced copies of 258 different emails he had taken from Van Alstyne’s AOL account.

Internet Cafe in Paris

A tad obsessive, wouldn’t you say? In any event, after contradictory testimony like that, Leonard’s credibility is shot. It is no surprise that the jury awarded $100,000 in punitive damages alone, just for these unauthorized intrusions into Van Alstyne’s AOL account.

But what about Leonard’s attorney? Did he or she ask Leonard where he got the emails they were going to use for the deposition of Van Alstyne? I would hope so, and hope that the client lied to his attorneys and said they were all from his company’s computers. Still, it would seem that a diligent investigation and supervision of the discovery process would have revealed the true origin of these emails.

Sergeant Schultz of Hogan's HerosThe lesson to be learned here by attorneys is to always ask and be sure you understand where and how your client obtained email that they turn over to you. Especially in a heated case like this with allegations of sexual harassment, you need to be sure the emails were obtained legally. This is now a common problem in divorce cases. If your client has hacked into someone’s private email to get the evidence, they may well have committed a crime, as this case shows. They should be counseled accordingly. You cannot simply act like Sergeant Schultz in Hogan’s Heros and say “I know nothing!” The dumb as you want to be defense will not work with savvy opposing counsel or judges. You have a duty to inquire and cannot simply look the other way. If you learn the evidence is tainted, you do not use it and just hope that nobody notices.

Don't look a gift horse in the mouthI am not suggesting that is what happened here. I do not know; but the facts stated in the opinion raise some disturbing questions. Clearly we should all exercise caution in the discovery of an adversaries’ email and other personal computer information. When it comes to private email we should forget the common proverb; we should carefully look a gift horse in the mouth.

Conclusion

Everyone who uses email in the clouds can now rest a little safer, thanks to this important ruling of the Fourth Circuit. We can only hope that other Circuits will follow Van Alstyne and allow punitive damage, cost, and fee awards for unlawful invasion of email privacy without proof of actual damages. This will encourage active enforcement by private parties in civil lawsuits. If a jury is mad at the hacker, be they a young student, like in Palin, or the CEO of the company, as in Van Alstyne, we could see quite a few six figure punitive damage awards (assuming the judge does not reduce the size of the award as unreasonably high; see Abner v. The Kansas City So RR , 513 F.3d. 154 (5th Cir. 2008)). Nobody likes to have their email privacy invaded and now we have another way to fight back.