Tag: Affiliates

  • NDA Essentials, Part 5: Who Can See Your Confidential Information, and Who Answers for Them

    NDA Essentials, Part 5: Who Can See Your Confidential Information, and Who Answers for Them

    You sign an NDA with a company’s U.S. subsidiary. The NDA lets the subsidiary share your information with its “Affiliates,” so the German parent company gets a look. When you ask whether the parent should sign its own NDA, one of its people tells you not to bother, because everyone is already covered. A year later the talks are dead, and you believe the parent is trying to build your product on its own. You sue the parent for breaching the NDA. You lose, because the parent never signed it.

    That’s close to what happened in Knight Capital Partners Corp. v. Henkel AG & Co., KGaA, 930 F.3d 775 (6th Cir. 2019).

    The bottom line: the recipients clause in your NDA answers two questions. Who on the other side may see your information, and who you can hold responsible when one of them misuses it. The answer to the second is usually the company that signed and nobody else, so the clause has to make that company answer for everyone it shares with.

    Part 1 of this series covered this provision in two short paragraphs, and Part 4 promised the longer version. Here it is.

    Two Lists and a Sentence

    The first list says who counts, usually through a defined term, “Representatives,” covering some mix of affiliates, directors, officers, employees, agents, advisors, contractors, and sometimes financing sources. The second list says what has to be true before any of them sees anything: a need to know for the permitted purpose, notice that the information is confidential, and, in better drafts, written confidentiality obligations at least as protective as the NDA.

    Then comes the sentence that matters most when something goes wrong: the receiving party is responsible for any breach by its Representatives.

    Recipients usually want the first list long and the second one short. Disclosers want the reverse. The responsibility sentence is where both sides should slow down, and Knight Capital shows why.

    The Affiliate Who Could See Everything and Signed Nothing

    Knight Capital Partners (“KCP”) was set up to broker a distribution deal for a novel citrus-based cleaning product. In 2014 it signed an NDA with Henkel Corporation, the U.S. subsidiary of Germany’s Henkel AG & Co., KGaA. The NDA let Henkel Corporation share KCP’s information with its “Affiliates,” defined to include any entity that controlled it, which put the German parent squarely inside the definition. Any affiliate that received information became a “Receiving Party,” limited to using it for the purpose of the NDA.

    The deal never happened. KCP sued only the parent, claiming it used KCP’s information to try to develop the product itself. A parent company employee told KCP’s CEO that no second NDA was needed because they were covered by the one already signed, and he later testified that he was bound by the NDA as an affiliate.

    The Sixth Circuit, applying Connecticut law under the NDA’s choice-of-law clause, held that none of it made the parent a party. Only parties are liable for breach of contract. The NDA named KCP and Henkel Corporation as the parties, only they signed it, and it gave affiliates a role as recipients without making them contracting parties. The court read the parent’s “we’re bound” statements as reaffirming its obligations as a Receiving Party, not as joining the contract.

    For a discloser, the lesson is simple: the company that signs is the company you’ll sue, so make it answer for every recipient as if each breach were its own. If one affiliate matters more than the rest, like a parent with its own product development group, ask that affiliate to sign a joinder or the NDA itself.

    Contractors, Vendors, and the Word “Agents”: An Oklahoma Example

    In CMI Roadbuilding, Inc. v. SpecSys, Inc., No. CIV-18-1245-G, 2021 WL 2189222 (W.D. Okla. May 28, 2021), CMI hired SpecSys to manufacture mobile equipment and provide engineering services. Their NDA let SpecSys share CMI’s information with “Representatives” who needed to know it, had been given a copy of the NDA, and had agreed to be bound by the same or similar terms. “Representatives” meant SpecSys’s directors, officers, employees, agents, or advisors.

    SpecSys sent CMI’s engineering documents to at least four parts vendors. CMI called that an unauthorized disclosure. SpecSys said the vendors were its agents or advisors, and that CMI had authorized the disclosures anyway through a letter it gave SpecSys for buying CMI’s proprietary components. Judge Goodwin wrote that the vendors arguably qualified as agents or advisors, declined to decide that contract question without real argument from either side, and found genuine fact disputes on both points. CMI’s own position was that it didn’t object to drawings going to vendors that already had NDAs with CMI.

    This is an unreported trial-court order, and it decided nothing about what “agents” means. That’s the point. Both companies plainly expected vendors to see the drawings, their recipients list didn’t say so, and more than two years into the lawsuit a federal judge couldn’t tell from the contract who was allowed to see what.

    SaaS deals are full of the same people: the offshore development shop, the implementation partner, the contract engineer, the hosting provider. Most of them aren’t anyone’s “agent” in the legal sense. If you’re receiving, name the categories you’ll actually use. If you’re disclosing, decide which ones you’re comfortable with and say so. And if your team plans to paste the other side’s information into an AI tool, ask whether that tool’s vendor is on the list at all.

    Affiliates and Financing Sources Need Their Own Lines

    “Affiliates” is usually defined by control, so a recipient with a large corporate family can share your information with entities you’ve never heard of, including some that compete with you. A blanket affiliate grant is likely overbroad. Limit it to controlled affiliates, named affiliates, or affiliates that need the information for the deal, and keep the signing party responsible for all of them.

    Financing sources come up mostly in acquisitions, where sellers worry that a buyer’s equity co-investor is really another bidder. As an example, the New York City Bar’s model NDA keeps equity sources out unless the seller consents in writing. That default works for commercial deals too: anyone outside the agreed categories sees nothing without your written consent.

    The Statutes Help, but Only So Far

    If the information is a trade secret, a downstream recipient may have statutory exposure without signing anything. Under the Oklahoma Uniform Trade Secrets Act, disclosing or using a trade secret without consent is misappropriation when the person knew or had reason to know it was “derived from or through a person who owed a duty to the person seeking relief to maintain its secrecy or limit its use.” 78 Oklahoma Statutes § 86(2)(b)(2)(c). The federal Defend Trade Secrets Act uses nearly identical language. 18 U.S.C. § 1839(5)(B)(ii)(III).

    That’s a narrower path than a contract claim. You have to prove the information is a trade secret, which much of what an NDA covers isn’t, and prove what the recipient knew. Trade secret status also depends on “efforts that are reasonable under the circumstances to maintain its secrecy,” 78 Oklahoma Statutes § 86(4)(b), and a court weighing those efforts will want to know who you let see the information and on what terms. A tight recipients list helps you there too.

    Who’s on Your List?

    • Find the definition that controls who may receive. It may be “Representatives,” or it may be folded into the definition of “Receiving Party,” as it was in Knight Capital.
    • If you’re receiving, add the categories you actually use: contractors, subcontractors, implementation partners, specific affiliates. Don’t rely on “agents.”
    • If you’re disclosing, require a need to know, notice of confidentiality, and written obligations at least as protective as the NDA, plus your written consent for anyone outside the list.
    • Find the responsibility sentence, and add one if it’s missing. Expect a recipient to ask that it apply only where the recipient failed to use reasonable care in choosing and supervising the person. Decide in advance whether you’ll accept that.
    • If one affiliate matters more than the others, get its signature on a joinder or on the NDA itself.
    • Keep a dated list of who received what. It’s the record Part 4 recommended, with names added.

    Something close to this handles most of that list: “The Receiving Party may disclose Confidential Information only to those of its and its controlled Affiliates’ directors, officers, employees, contractors, and professional advisors who need to know it for the Purpose, have been told its confidential nature, and are bound by written confidentiality obligations at least as protective as this Agreement. The Receiving Party is responsible for any act or omission of any person to whom it discloses Confidential Information that would breach this Agreement if done by the Receiving Party.” If you usually receive, check those categories against how your company actually works before you sign.

    Part 6 of this series turns to the standard of care: what “reasonable care” requires of the recipient, and why the recipient’s own security practices end up setting the floor.

    This post is provided for general informational purposes only and does not constitute legal advice. Reading this post does not create an attorney-client relationship. Contact Ken McConkey to discuss your company’s specific confidentiality agreements.