What is the value in adding an email confidentiality notice? The company I work for adds a disclaimer on the bottom of each email. I was wondering if it had any value. I'll list part of it below: CONFIDENTIALITY NOTICE: This e-mail message is for the sole use of the intended recipients. ... may be privileged ... legal restrictions. ... not the intended recipient ... you are hereby notified that ... dissemination... It's redacted above because there may be some restrictions as to what I'm allowed to put in a public forum. Hopefully this is common enough that the gist of it is well known to readers of this question. I just wonder how valuable it is to have on our emails.
This notice has no legal power what so ever. This has been, and is being, used as a legal backup and a scare tactic. For the most part, if someone gets some sort of "sensitive" information in an email, and it was not intended for them - this notice will serve as a scare tactic to make people get rid of it because of the legal sound of the disclaimer. Also, the senders are preparing themselves for a legal battle by having the notice in email’s body. In case that the sender sent some “sensitive” data to the wrong recipient, they can be potentially held liable for privacy breach of information similar stuff. So, when they show up in court they can potentially use the argument that they did everything within their power to protect the information by adding the disclaimer and the fact that the privacy breach happened is due to a natural human error. Basically, there is no disclaimer that can protect against actual libelous or defamatory content. The most a disclaimer can accomplish in this respect is to reduce the responsibility of the company, since it can prove that the company has acted responsibly and done everything in its power to stop employees from committing these offenses. [1] If you as an employee of a company shared sensitive information or personal information by mistake, you, and the company are still liable for your own action. It can be argued in court that the recipient’s email was not verified, that a human error is not an excuse because the information could have been encrypted with a password, the information could have been transmitted via a phone call or in person, and a bunch of other excuses that will hold the company liable for damages. There is no legal doctrine or theory under which an email confidentiality disclaimer is enforceable in a circumstance like this. There is virtually no scholarly analysis of the impact of email disclaimers and very little analysis by non-scholars. One of the few authors who have commented on the subject suggests that the misconception that email disclaimers have validity may arise from the mistaken belief that the Electronic Communications Privacy Act (ECPA) somehow applies. Michael Santarcangelo, “Do Email Disclaimers Matter?,” Sec. Catalyst (Oct. 17, 2007). But, as this author points out, the ECPA prohibits only “intercepting” emails. Emails that arrive at their destination—even if the sender did not intend that destination—are not emails that have been intercepted in transit, and the ECPA is therefore inapplicable. In short, the ECPA is focused on the criminal intent of the interceptor, not the ability of the sender to execute his or her own intentions. With regard to communications with lawyers, the rules are a little different. Model Rule of Professional Conduct 4.4(b) states, “A lawyer who receives a document relating to the representation of the lawyer’s client and knows or reasonably should know that the document was inadvertently sent shall promptly notify the sender.” It is noteworthy that the rule requires only notice and doesn’t require refraining from reading the document or prohibit other use of the document. And a number of states haven’t even adopted Rule 4.4(b), so there may not be a requirement even to notify the sender in certain states. Nonetheless, if a court is examining “fairness” in connection with waiver of privilege, a disclaimer on an email sent to a lawyer might help. [4]
Unless you were operating under a non-disclosure agreement he (and you) can use any information that he learned unless it violates IP law. It sound like what you told him is generic (if expert) views on high-level approaches to software design. That is, you didn't give him slabs of code that you own the copyright for or disclose trade secrets that you own. That sort of advice is freely usable by him. There is a reason that consultants in every field don't give away their advice before signing the contract. Now you know what it is.
"Hearsay" is a term used for statements offered in evidence in court that are not admissible because the person who originally made the statement has not testified to it. The hearsay rule is complex, and has many ramifications and exceptions. Legal texts take hundreds of pages to explain all these complications. But the term is not appropriate unless the statement is offered as evidence in court, or there is a plan to offer it. An ordinary email that no one plans to offer in court is neither hearsay nor not-hearsay, it is just a set of statements that may be true or untrue, accurate or mistaken. If for some reason this email were to be placed in evidence in court, the default procedure would be to call the person who originally wrote it to testify, and ask questions like "Did you write this? When did you write it? was it the truth to the best of your knowledge when you sent it?" If the original sender cannot or will not be a witness, then whether the email will be accepted as evidence will depend on what is sought to be proved by the email, and what evidence there is that the email was sent, and by whom, and was the truth as far as the sender knew. If what you really want to know is whether the email accurately quotes the organization's lawyer, just email or write that lawyer, saying something like "Does the attached email accurately represent an opinion that you gave to {organization} as I have been told it does?"
someone I spoke with said "there is to be no recording of this or any other calls". Must I follow this instruction? Although, in Canada, there is no requirement on you to obtain consent to make recording, this explicit objection creates a hurdle. If you simply ignore the objection and record the conversation anyway without letting the objecting party know, you may give them a ground for a claim under the breach of confidence doctrine. The safest move would be to reply: No. There will be recording of this and any other calls. It will be then up to them to hang up. If they don't, they lose all grounds for any claims.
According to my knowledge I am not allowed to share other people's full name nor phone number nor email address without their permission. That is not correct. According to GDPR Article 2: This Regulation applies to the processing of personal data wholly or partly by automated means and to the processing other than by automated means of personal data which form part of a filing system or are intended to form part of a filing system. This Regulation does not apply to the processing of personal data ... ... (c) by a natural person in the course of a purely personal or household activity; GDPR Recital 18 states in relevant part: (2) Personal or household activities could include correspondence and the holding of addresses, or social networking and online activity undertaken within the context of such activities. Personal data that is not processed by &quot;automated means&quot;, for example data which is transmitted verbally, by hand writing, or by manually sent email, is not covered by the GDPR. Data which is used by a natural person for &quot;personal activities&quot; is also not covered. Consulting one's personal lawyer might well be a personal activity unless it is a business matter. Even if such a transfer of data were in scope for the GDPR, consent of the data subject (DS) is not the only available lawful basis. GDPR article 6 permits any of several possible lawful bases to be used, particularly paragraph 1 point (f) which reads: (f) processing is necessary for the purposes of the legitimate interests pursued by the controller or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject which require protection of personal data, in particular where the data subject is a child. Also possibly relevant is point (c) which reads: processing is necessary for compliance with a legal obligation to which the controller is subject; In short, providing one's personal lawyer with the names and addresses of relevant people in connection with a legal issue is not at all likely to be prohibited by the GDPR, nor to require the consent of the people whose names and contact info are provided. However, a comment by user PMF reads: The Data Protection laws are mostly for companies, not for individuals. This is an overstatement. The laws do apply to natural persons as DCs, although enforcement is largely targeted at businesses, particularly large, for-profit businesses.
The purpose of that disclaimer is not to prevent reprimands or legal action. It's really as simple as it appears -- it's to inform the readers that the tweets in fact contain the opinion of the person who wrote them and are not intended to be understood as the official position as that person's employer. This is especially important for people who occasionally or frequently convey their employer's official position. It's not supposed to be some kind of magic word that causes something to happen. It's just an attempt to convey accurate information and avoid misunderstandings.
The information in telephone books is public. so are postal change-of-address records. So are records of the ownership of real estate. So are vital statistics such as birth records. So are voter registration lists -- i myself purchased a voter registration list (in digital form) for a municipality which showed people's names, addresses, and the years when they voted, when I was a political candidate for local office in NJ. It cost about $100. I believe that many states also make driver's license information available for a fee to marketers. Credit records are available for certain limited purposes, also. No doubt there are other public sources I haven't thought of. If such a site relies on public records, or other publicly available data, it is not illegal. Many such sites offer to remove names on an opt-out basis, but there is no legal requirement that sites do so. This kind of information is not considered nto be "private facts" under US tort law. Aside from opting out, if the sites provide that option, I don't think you have any recourse. One could ask the local legislature to pass a law prohibiting such sites, or making them require consent, similar to the GDPR that the EU has. But I don't know of any such law in the US to date.
I would probably have a legal disclaimer out of an abundance of caution. That being said, you have a right to free speech via First Amendment guarantees. While that right is not absolute and some words “by their very utterance” cause injury or incite an immediate breach of peace, and do not receive constitutional protection, (there is the old adage you do not have the right to shout fire in a crowded movie theater). This (your blog) is not that. To take it to its logical (or illogical) extreme, there are many things on the internet, in magazines, scholarly articles, etc. that could injure someone or cause damage in the event that one who was not qualified or competent to perform the action described undertook to do so. A child could burn themselves following the directions on a mac and cheese box but they shouldn't be cooking in the first place. The same rings true for high voltage electricity - a non-licensed electrician should probably not create a high voltage power supply. But, will some? Yes. But you are not liable for printing a blog about the practice. On another but related note, if you are a licensed electrician your licensing authority may require that you take precautions to ensure you do not inadvertantly direct others to engage in practices of licensed professionals that could cause harm by giving them information. I doubt this but I don't know because I am not an electrician. As far as could you be liable for writing it....under our legal system you can be sued under a theory of negligence for just about any action someone thinks was unsafe or causes injury. And you never know what a jury will do. But I think that to sue someone for simply writing something would be fairly easily dismissed through a motion for summary judgment by a competent attorney in the event you got sued. If everything a person wrote, that if followed by an unqualified person resulted in injury, resulted in liability for damages than it would have a chilling effect on their First Amendment right to free speech. That said, I go back to my original statement that it couldn't hurt to have a simple liability waiver for extra protection. It could be something as simple as: "The information contained herein is not mean to be comprehensive and is for informational purposes only. You should not undertake to perform anything described herein without adequate training and/or supervision. The Author disclaims any responsibility for any injury, damage, or loss as a result of reliance upon the information found on this site/blog." If you do use a liability waiver, make sure it is bold and obvious. Otherwise, it can backfire!