What should partners never promise a business owner about data privacy?

What should a partner never promise an owner about privacy?

Never promise absolute outcomes: perfect anonymity, that nobody will ever find out, that a deal will happen, a price or reward amount, or that employees do not need to be told. Replace each with an accurate statement about process. Redaction rules are agreed with the company before any work begins, and nothing is delivered until the agreement is signed and the company authorizes it.

Overpromising hurts the owner, who relies on you, and hurts you, because a promise you cannot keep becomes your problem. This is general information, not legal, tax or financial advice.

Why absolute privacy claims are wrong

Regulators treat privacy and confidentiality promises as enforceable commitments. FTC staff have written that a company's promises not to use customer data for undisclosed purposes, such as training models, are enforceable in the AI context. See the FTC's AI companies privacy and confidentiality commitments. A separate FTC staff post says that quietly adopting more permissive data practices, such as sharing consumers' data with third parties or using it for AI, after promising otherwise may be unfair or deceptive. See the FTC post on changing terms of service.

The lesson for partners: the company's own promises to its customers and staff decide what it can license, and your loose words can lead an owner to assume more than the process provides.

The do-not-say list, with replacements

Checklist before any conversation

• I will describe the process, not outcomes.
• I will not describe, summarize or ask to see any confidential records.
• I will say that nothing is binding until the company agrees terms and signs.
• I will say the company keeps ownership and licenses, not sells, its data.
• I will mention the partner reward only in the standard terms, if asked, without typing or quoting amounts.
• I will point to counsel for anything on privacy law, employee notice or customer contracts.

What you can say with confidence

1. The company keeps ownership; data is licensed, not sold.
2. Redaction and de-identification requirements are agreed before work begins.
3. Data is delivered only after an executed agreement and the company's authorization.
4. The company gets one all-in price, SourceX fee included, paid as a one-time payment, typically within about 60 days of invoicing once the buyer selects the data.
5. Large deliveries stay in the seller's own storage or ship on encrypted drives.

For the longer version of the first point, point the owner to when redaction rules are agreed and whether a sample can be reviewed, and for payment concerns see what happens if the buyer pays late.

Rewards: the one thing to get exactly right

If an owner asks how you are paid, say: partners earn 25% of the eligible platform fees SourceX actually collects, up to $100,000 per referred company, paid only after the buyer pays and SourceX receives its fee. It is never deducted from what the company receives, and no reward is guaranteed. Do not add numbers.

Two scenarios, and how to answer

Illustrative: an owner of a mid-sized logistics firm says, "If my emails go to an AI company, will my customers be able to see them?" A weak answer is "Absolutely not, it is fully private." A better answer is: "Redaction rules are agreed between your company and SourceX before any work begins, and nothing is delivered until you sign and authorize it. Your lawyer should check your customer contracts, because those decide what you can license."

Illustrative: a CFO asks, "How much will we get?" Do not name a number or a range. Say: "Price and terms are agreed between the company and buyers, and nothing is binding until you sign. You receive one all-in price, with SourceX's fee included and no separate charges."

Why the rule protects you personally

A partner who repeats guarantees may be seen as having made representations the program never made. If the owner relies on them, the disagreement may land on you, and counsel can tell you how far that exposure reaches. Sticking to process statements keeps you inside the facts the program can stand behind, and it makes your introductions more credible to careful owners, lawyers and HR leads. The company-side version of the same discipline is in what to say when a customer asks whether you sold their data to AI.

Pressure is also an overpromise

An owner who feels hurried may agree to things they do not understand. Read how to make sure an owner never feels pressured and, for lenders, bankers raising data licensing. A sponsor's view appears in portfolio data licensing and reputational risk.

If you already overpromised

1. Correct it in writing promptly and plainly.
2. Tell the owner to rely on the signed agreement, not on conversation.
3. Pause the introduction until the owner confirms they understand.
4. Use the corrected wording from the table in future conversations.

Next step

Use the table above as a pre-call card. When you are ready, register as a partner, draft a message with the introduction email builder or the software implementation partner email template, and check the referral earnings calculator and FAQ.