Yes, most people have. A few lines at the bottom of a business email say the message is confidential, may be privileged, and should be deleted by anyone who is not the intended recipient. Those lines are common, but nothing reviewed here establishes that a footer alone binds every person who reads it, and nothing establishes that it is meaningless either. Whether confidentiality wording has legal force depends on specific facts: whether the parties exchanged promises, what the information is, how it reached you, which jurisdiction applies, and whether a public-records law governs the document.
What the typical footer says
A standard confidentiality notice usually does four things. It identifies the intended recipient, states that the message may contain confidential or privileged information, tells anyone who received it in error to notify the sender, and asks them to delete it. A common version reads along these lines: “This message is intended only for the named recipient and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender and delete this message.”
That wording is an instruction and a request. It tells a mistaken recipient what the sender wants. It does not, by itself, settle whether the recipient has taken on a legal duty.
Why a footer alone is not a settled contract
Readers often ask whether reading an email creates a binding agreement. The authorities that address confidentiality promises do not treat a boilerplate footer as the same thing as a negotiated promise. The question turns on the surrounding facts, and the table below lists the circumstances that change the analysis.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
| Situation | What changes | Why it matters |
|---|---|---|
| Footer on an ordinary business email | No exchange of promises is shown | The legal effect is not settled by the footer alone; treat it as a request from the sender |
| Separately signed NDA or confidentiality agreement | Specific promises were made and accepted | Obligations depend on that agreement’s terms and the governing law |
| Misdirected email you did not seek | You are not the intended recipient | The footer’s notify-and-delete request is the sender’s instruction; a universal legal duty is not established |
| Information submitted to a public body | Public-records law may apply | A confidentiality promise may not prevent disclosure (see the Delaware example below) |
| Federal government data release | A specific use and non-disclosure agreement is signed before release | Governed by 48 CFR § 3452.227-72, which covers that release context only |
Where a confidentiality promise does have force
The clearest example of a confidentiality promise producing legal consequences is Cohen v. Cowles Media Co., 501 U.S. 663 (1991). A source gave information to newspapers in exchange for a promise of confidentiality, and the papers broke that promise. The US Supreme Court considered whether the First Amendment barred damages under state promissory-estoppel law. Justice Byron R. White, writing for the Court, stated: “We hold that it does not.” The holding concerns that particular claim, not email footers. What made the case matter was an explicit promise made in exchange for information.
Public bodies cannot always keep records secret by contract
A confidentiality clause also does not reliably hide a government record. In Delaware Opinion 17-IB01, dated February 3, 2017 and published February 8, 2017, the state Attorney General concluded that the City of Dover violated FOIA by refusing access to a settlement agreement because of its confidentiality clause. The opinion found that the City had constructive possession of, or administrative control over, the agreement, and that the confidentiality agreement did not bar disclosure. It also cited earlier Delaware authority holding that a public body cannot make enforceable promises of confidentiality about public records. That conclusion applies to Delaware public-records law and the dispute it addressed.
A 2010 Northern Ireland Assembly Public Accounts Committee report took a policy position on the same kind of clause. Its Recommendation 5 said confidentiality clauses should not be used in public-sector settlement arrangements, and that any exceptional use should receive specified approvals. That is a policy recommendation for one institutional setting, not a general legal rule.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.If you receive one by mistake
When a misdirected email contains sensitive information, the practical steps are the same whatever the footer says:
- Stop reading and do not forward, copy, quote, or post the message or its attachments.
- Notify the sender using a contact method you already trust, rather than replying to an address that may have been part of the error.
- Delete the message if the footer or the sender asks you to, and follow any other instruction the sender gives.
- If the material involves account data, a legal matter, or a dispute, get advice from a lawyer qualified in your jurisdiction before you act further.
If the email arrived through an employer, report it to that employer’s IT or privacy contact as well, so the company can decide what else needs to happen.
The footer tells you what the sender expects. Whether you are bound by it, and what you must do beyond the steps above, depends on facts and local law that a general article cannot settle.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
