Salman v. United States (2016): what Delaware LLC founders should know

Case at a glance

• Case name: Salman v. United States
• Year: 2016
• Court: US Supreme Court
• Citation: 580 U.S. 39 (2016)
• Category: Member Disputes

The facts

Federal insider-trading prosecution.

The holding

Personal benefit to tipper can be inferred from gift to relative or friend.

Why this case matters

Insider-trading law.

What this means for Delaware LLC founders

Not directly applicable.

How Salman applies to your LLC

For solo single-member Delaware LLC founders, most fiduciary-duty cases have limited direct application: there is no co-member to owe duties to, and creditor-fiduciary-duty exposure arises only after actual insolvency. The cases become more relevant as the LLC grows:

• Adding co-founders or investors: multi-member LLCs face the full range of fiduciary-duty analysis, though Operating Agreements can modify duties under § 18-1101.
• Manager-managed structures: when non-member managers run the LLC, they owe fiduciary duties to members by default (§ 18-1104).
• Sale or merger transactions: Revlon and Unocal duties translate to LLC change-of-control transactions.
• Member disputes: Court of Chancery jurisdiction over Operating Agreement disputes applies the body of Delaware case law as guidance.

Primary source

The full text of Salman v. United States is available through Westlaw, LexisNexis, and Google Scholar. The Delaware Court of Chancery publishes opinions at courts.delaware.gov/chancery. The Delaware Supreme Court publishes opinions at courts.delaware.gov/supreme.

Related cases and concepts

For broader Delaware corporate and LLC case law context, see our coverage of the business judgment rule, fiduciary duties, Delaware Court of Chancery, and the Delaware LLC Act. The Delaware Limited Liability Company Act sections (6 Del. C. § 18-101 et seq.) interact with the body of Delaware case law to define LLC governance.

See all cases in the Delaware Case Law Library →

What facts gave rise to Salman v. United States?

Salman v. United States, reported at 580 U.S. 39 (2016), arose from a federal insider-trading prosecution. According to the record summarized here, the case sat squarely in the world of securities law rather than in the law of business formation. The factual heart of the matter involved confidential information passing from a person who held it to another person who then traded on it. The relationship between the people involved mattered a great deal, because the chain of information ran through family and personal ties rather than through an arm's-length sale of a tip. That detail, ordinary as it sounds, became the pivot on which the entire appeal turned.

For a non-resident founder reading this for the first time, it helps to set expectations plainly. This is not a Delaware corporate or LLC decision, and the record itself notes that it is not directly applicable to forming or running a Delaware limited liability company. We include it because the underlying idea, that someone entrusted with confidential information owes a duty not to misuse it, echoes themes that do show up in fiduciary and confidentiality questions inside closely held companies. Reading the case carefully lets a founder see how a court reasons about trust, benefit, and the passing of secrets, even when the legal setting is criminal securities enforcement rather than a dispute among LLC members. Treat the connections drawn below as analogy and general background, not as a statement that the holding governs LLC affairs.

What was the precise legal question before the Court?

The narrow question concerned what a prosecutor must show to establish that a person who receives a tip, often called a tippee, can be held liable for trading on it. Earlier doctrine had established that liability depends in part on whether the person who disclosed the information, the tipper, received some personal benefit from the disclosure. The hard part was defining what counts as a personal benefit. If a benefit must always be tangible, such as cash or a kickback, then many disclosures to friends and family would fall outside the rule. If, instead, the benefit can be inferred from the nature of the relationship, then a gift of confidential information to a relative could itself supply the missing element.

That is the question the record captures in compact form. The Court had to decide whether a personal benefit may be inferred when a person gives confidential information as a gift to a trading relative or friend, or whether the government must always point to something the tipper received in exchange. The distinction is not academic. It draws the boundary between conduct that can lead to criminal liability and conduct that, however unappealing, falls outside the statute as interpreted. The case therefore asked the Court to clarify a rule that lower courts had been applying in inconsistent ways, which is a familiar reason for the Supreme Court to take up an appeal at all.

What did the Court actually hold?

Based strictly on the record summarized here, the holding is that a personal benefit to the tipper can be inferred from a gift of confidential information to a relative or friend. In other words, the government does not always need to prove that the tipper pocketed money or received a concrete payment. When someone knowingly hands over confidential information to a close relation who then trades, the gift itself can satisfy the personal-benefit element. The act of giving a valuable secret to a friend or family member is treated as a form of benefit to the giver, because it is much like making the trade and then handing over the proceeds as a present.

It is worth stating what the holding does not do, to avoid reading too much into it. It does not abolish the personal-benefit requirement. It does not say that every disclosure is unlawful. It refines how that requirement can be met in a common family scenario. For a careful reader, the takeaway is that the law looks through the form of a transaction to its substance. A gift dressed up as generosity can still carry legal weight when the thing being given is confidential information that the recipient is expected to trade on. That instinct, looking at substance over label, is one of the few threads that genuinely connects this securities decision to the way courts examine conduct inside business entities.

Which doctrine does the decision rest on?

The decision applies the personal-benefit doctrine that governs tipper and tippee liability under federal securities law. That doctrine grew out of the idea that a person who possesses confidential information by virtue of a position of trust may not exploit it for personal advantage, and may not hand it to someone else to exploit when the disclosure brings the tipper a benefit. Salman did not invent this framework. It clarified one corner of it by holding that the benefit can be inferred from a gift to a relative or friend rather than always requiring proof of a tangible exchange.

Understanding the doctrine helps explain why the case is grouped under member disputes in this collection even though its facts are about securities trading. The common ingredient is breach of a duty owed because of a relationship of trust. In securities law the duty runs to the source of the information and ultimately to the market. In the law of business associations the duty runs among owners and managers who depend on one another. The mechanism differs and the consequences differ, yet both bodies of law share a structural concern with people who hold confidential or sensitive information and the conditions under which sharing it becomes wrongful. Keeping that distinction in mind prevents the analogy from being stretched past what it can bear.

Why does a Delaware company collection include a securities case?

Delaware is the home of choice for a large share of US business entities, and founders who study Delaware law quickly learn that questions of trust and loyalty run through it. Although Salman v. United States is a federal securities decision rather than a product of the Delaware Court of Chancery or the Delaware Supreme Court, it earns a place in a founder-facing collection because it sharpens intuitions about confidential information and the duties that attach to it. A founder who internalizes the lesson that giving away a secret can itself be a benefit is better prepared to think clearly about information control inside a company.

The honest framing, which the record supports, is that this case did not shape Delaware corporate or LLC law in any direct doctrinal sense. It is most useful as a lens. When a Delaware company has members who possess sensitive information, such as customer lists, pricing models, or pending deals, the way courts in other contexts reason about misuse of secrets can inform how an operating agreement is drafted and how members behave. The connection is one of principle and habit of mind, not of binding precedent. Anyone presenting this case to founders should be candid about that boundary, because overstating the link would mislead readers about what the decision can and cannot do for them.

How does the gift principle map onto a Delaware LLC?

Inside a Delaware LLC, members and managers frequently come to hold information that the company treats as confidential. The principle that surfaces in Salman, that quietly passing a valuable secret to a relative or friend can count as a benefit to the person who passes it, translates into a practical warning about loose handling of company information. A member who shares a confidential customer list with a relative who then competes, or who tips a friend about a pending acquisition, is not committing the same offense that the securities laws address, but the underlying behavior may still breach duties owed to the company and its other members.

The mapping is imperfect on purpose, and it is worth listing where the analogy holds and where it breaks:

• It holds where the concern is misuse of confidential information obtained through a position of trust.
• It holds where a court looks at the substance of a transfer rather than its friendly label.
• It breaks because LLC disputes are civil and contractual, not criminal securities matters.
• It breaks because the personal-benefit test is a securities-law construct, not part of the Delaware LLC Act.
• It breaks because remedies in an LLC dispute turn on the operating agreement and on default fiduciary rules, not on federal trading statutes.

What can an operating agreement do with this lesson?

An operating agreement is the central contract of a Delaware LLC, and the Delaware Limited Liability Company Act gives the members wide room to set their own terms. One sensible application of the Salman lesson is to write clear confidentiality provisions that define what counts as company information, who may access it, and what members may not do with it after they leave. Because the statute favors freedom of contract, members can spell out that disclosing sensitive information to outsiders, including relatives and friends, is a breach even when no money changes hands. That mirrors the case's insight that a gift of information can carry real weight.

Drafting around this point tends to be more effective than relying on background principles alone. Useful clauses often address the following:

• A definition of confidential information broad enough to cover customer data, financial models, and deal activity.
• Restrictions on sharing such information with third parties, framed without a money-changing-hands requirement.
• Obligations that survive a member's exit so that secrets cannot be gifted on the way out.
• Stated consequences for breach, which may include damages or removal where the statute and the agreement allow.
• A clear allocation of who decides whether disclosure was authorized.

How does the case relate to fiduciary duties in an LLC?

Fiduciary duties, chiefly the duty of loyalty and the duty of care, sit at the center of how members and managers must treat a Delaware LLC and one another. Salman does not state Delaware fiduciary law, yet its concern with a person who exploits confidential information for the benefit of someone close to them speaks to the same worry that the duty of loyalty addresses. A manager who diverts the company's confidential opportunities to a friend is acting against the interests they are bound to serve, which is the kind of conduct loyalty principles are meant to police.

There is an important Delaware-specific wrinkle. The Delaware Limited Liability Company Act permits members to expand, restrict, or even eliminate fiduciary duties in the operating agreement, subject to the implied contractual covenant of good faith and fair dealing, which cannot be waived. This means the loyalty intuition that Salman gestures toward is, in an LLC, partly a matter of contract design rather than a fixed background rule. Founders who care about preventing the quiet gifting of company secrets are well served by addressing it expressly, because they cannot assume a court will supply a strong duty that the agreement has narrowed. The freedom the statute grants cuts both ways, and silence can leave gaps that careful drafting would have closed.

What is the link to contractual freedom under the LLC Act?

The animating policy of the Delaware Limited Liability Company Act is to give maximum effect to the principle of freedom of contract and to the enforceability of operating agreements. That policy is the bridge between a securities decision like Salman and the everyday work of running an LLC. Where Salman tells us that the law can treat a gift of information as a benefit, the LLC Act tells founders that they may design their own rules about information, loyalty, and consequences, so long as they respect the non-waivable covenant of good faith and fair dealing.

For a founder, the practical implication is that the protections one wants should be written down rather than assumed. Contractual freedom is a tool, and a tool is only as good as the use made of it. If an operating agreement is silent on confidential information, the members fall back on whatever default duties remain after any modifications, and those defaults may be thinner than expected. If the agreement speaks clearly, the members gain predictability about what happens when someone passes a secret to a relative or competitor. The lesson from the case, filtered through the LLC Act, is that the substance of conduct matters and that founders have the authority to define which conduct their company will not tolerate.

What should a non-resident founder take from this in practice?

A founder living outside the United States who forms a Delaware LLC should treat Salman v. United States as background reading that sharpens judgment rather than as a rule that governs the company. The decision is about federal insider-trading liability, and the record is explicit that it is not directly applicable to LLC formation or operation. With that caveat firmly in place, the case still offers a durable habit of mind, namely that confidential information has value and that passing it along, even as a friendly favor, can be treated by the law as a benefit to the person who passed it.

Translated into action, that habit points toward a few sensible steps:

• Decide early what information the company will treat as confidential and write it into the operating agreement.
• Set expectations with co-founders and managers about not sharing sensitive information with outside relatives or friends.
• Recognize that the Delaware LLC Act lets the members shape fiduciary and confidentiality terms, so silence is itself a choice.
• Keep records of who has access to sensitive information and why.
• Seek qualified counsel before relying on any analogy between securities cases and LLC governance, since the bodies of law differ.

What are the limits of reading too much into this case?

It is tempting to stretch a memorable decision into a general theory, but doing so would misstate the law. Salman resolved a specific question about the personal-benefit element in tipper and tippee liability under securities law. It did not address how a Delaware LLC allocates duties, how members resolve disputes, or how an operating agreement should be drafted. The honest reading, consistent with the record, is that the case is informative by analogy and is not a source of authority for company governance. Anyone who tells a founder that this decision controls their LLC affairs is overreaching.

The right posture is calm and modest. Use the case to reinforce a sound instinct about confidential information and the duties that attach to positions of trust, and then turn to the actual sources of LLC law, which are the Delaware Limited Liability Company Act, the operating agreement, and the decisions of the Delaware courts, for rules that genuinely govern a company. This page offers general legal information and not legal advice, and a founder facing a real question about confidentiality, fiduciary duty, or any dispute among members would benefit from consulting a qualified Delaware attorney who can apply the law to the specific facts at hand.