# Referral success story confidentiality: a test | SourceX

Canonical: https://refer.sourcex.si/guides/the-confidentiality-test-before-publishing-a-network-success-story
Last updated: 2026-11-05

Test a network success story twice before it goes anywhere. First for inference: what could a reader work out from each line, even with no company named? A reward figure lets anyone compute the company's payout, a "we were paid" post dates the company's payment, and a sector-size-region description can pick one company out of a public portfolio. Then for permission: the company's CEO clears facts about the company, SourceX clears in writing anything identifying it as your partner or describing the deal, and nobody in your chain can clear an Acquisition Partner's identity. SourceX's own default for deals is silence.

This guide is for the general counsel liaison who sees the draft after the platform team has written it, usually with a deadline attached. It covers one story about one introduction. Aggregate reporting across many companies has its own review in [publishing network research without exposing companies](/guides/how-to-publish-network-research-without-exposing-companies).

## Why a success story is a confidentiality question before it is a marketing one

Start with what the deal's own parties typically agree. SourceX's process page lists its standard deal terms and, under exclusivity and confidentiality, says: "Neither side publicizes the deal." Its investor page lists Acquisition Partner anonymity as part of its model: "Labs can source data without revealing their roadmap or identity to the market." A fund that publishes the story can make public what the company and SourceX would each normally keep quiet.

Then look at what the fund actually knows, and from whom. Partners sign the Channel Partner Agreement before submitting introductions, and its section 1.6 defines Confidential Information to include "introduced contact identities, introduction records, buyer identities, requirements, pricing, proposed fees, inventories" and more. Section 4.6 says the partner receives information about its own referral "using generic stages or reference codes," and that SourceX "need not reveal confidential Acquisition Partner names, contracts, prices, margin or full acceptance evidence." Section 4.5 says "Neither Party may publicly identify the other as a partner or disclose non-public deal details without written authorization, except as legally required."

So a partner who writes a detailed success story is either repeating confidential information or guessing. Neither belongs in public. What remains publishable is narrow, and the test below finds it.

## Purpose, audience and the information-flow map

Write down what the story is for before testing a word of it: recruiting introducers, showing LPs that the platform team is active, or a conference talk. The purpose decides the minimum content, and the audience decides how far it travels. An LP letter is publication; it gets forwarded.

Then map every piece of information the draft could carry to who holds it, who may receive it and whether it can ever appear in a story.

| Information | Who holds it | Who may receive it | In a public story |
|---|---|---|---|
| That the company considered or chose licensing | The company | Whom its CEO decides | Only with the CEO's written permission for this text |
| What records it has, how many, how old | The company and SourceX | SourceX's process page labels its private data summary "Summaries stay private to you and SourceX." | Only with the CEO's written permission, and never taken from SourceX's summary |
| Deal stage and dates | SourceX, in generic stages or codes | The partner, for its own referral | Only with the CEO's permission and SourceX's written authorization; in practice, leave it out |
| Price, payout, terms | The company and SourceX | The partner sees only what explains its own reward | Never |
| The reward amount and status | The fund, from SourceX | The fund's finance and counsel | Never: it reveals the payout (next section) |
| The Acquisition Partner | SourceX | Nobody in the partner's chain; terms section 7 says partners never receive confidential buyer information | Never |
| What the fund knew from board materials | The fund, under its duties | Nobody outside the duty | Never |
| That the fund introduces CEOs to SourceX and may be paid | The fund | Anyone, once SourceX has authorized it in writing | Yes, with the disclosure |

The last row is usually the whole of what a fund can say.

## The derived-disclosure arithmetic

The reward is not the fund's private number. SourceX's terms publish exactly how it is calculated, so a reward figure carries the company's payout inside it.

In symbols: if SourceX pays the company P on its first qualifying transaction, the fund's reward R is the greater of USD 50,000 plus 5% of P and 15% of P; on a further transaction first agreed inside the 12-month Repeat Window, R is 15% of P. Any reader can reverse it: on a first transaction up to USD 500,000, P equals R minus USD 50,000, divided by 5%; above that, and on every repeat, P equals R divided by 15%. Even a post saying the fund received "the floor" tells readers the company was paid at least the USD 100,000 Minimum Transaction. A company that agreed with SourceX not to publicize its deal would have its payout published by a third party.

Status leaks the same way. SourceX's referral process page says a referral is shown as Paid "only after an actual payout has been recorded," and section 5 of the terms makes a reward payable only after the Acquisition Partner has accepted the dataset, SourceX has received cleared funds and the company has been paid. A post that says the fund's reward arrived dates all three events for anyone who knows the company. Even "an introduction we made is now in final review" tells a reader a deal exists.

Descriptions leak through combination. "A 300-person Midwest freight broker in our portfolio" is anonymous only to readers who have not seen the fund's public portfolio page.

## The publication evidence and permission gate

Every line of the draft passes six gates in order. A line that fails a gate is cut or rewritten, never argued through.

| Gate | Question | Fails when | Who can clear it | Evidence to file |
|---|---|---|---|---|
| 1. Source | Do we know this firsthand, or did it reach us in confidence? | It came from a SourceX update, a board pack or the CEO in private | Nobody can launder it; rewrite from public facts | Note of where each fact came from |
| 2. Inference | Could a reader derive a confidential fact from it, alone or with public information? | Amounts, dates, statuses, distinctive descriptors | Nobody; cut or coarsen until nothing can be derived | The coarsened wording and why |
| 3. Company | Has the company's CEO approved this exact text, channel and period in writing? | Approval is verbal, general or borrowed from the introduction consent | The CEO; after an acquisition, the acquirer's CEO; in a formal process, possibly the estate's controller rather than the former CEO | The written approval |
| 4. SourceX | Does it identify SourceX as your partner or describe the deal or SourceX's process? | "Our partner SourceX", "closed with SourceX in six weeks" | SourceX, in writing (section 4.5) | SourceX's dated written authorization |
| 5. Buyer | Does it name, hint at or characterize the Acquisition Partner? | "A leading AI lab", "a household-name model developer" | Nobody in your chain | Not applicable: cut |
| 6. Interest | Does it say the fund could be paid, plainly and where readers will see it? | The reward is unmentioned or buried | The fund, on counsel's advice | The disclosure text and placement |

Gate 6 rests on a general principle rather than a SourceX rule. Section 255.5 of the FTC's Endorsement Guides, in our paraphrase of the search excerpt we read, says a connection a reader would not expect and that could affect how much weight they give an endorsement, payment included, should be disclosed clearly and conspicuously. Whether the Guides apply to a fund's story is for your counsel. A useful line is: "SourceX may pay the fund if a company we introduce licenses data to it; the company is paid the same either way." The second clause rests on section 4 of the terms: the reward "is paid separately by SourceX and is never deducted from the supplier's agreed compensation."

**Method note.** The gate was built for this guide from SourceX's terms (version 2026-10-22.2, since replaced by version 2026-11-04), the sample Channel Partner Agreement (sections 1.6, 1.9, 4.5 and 4.6), SourceX's process, referral-process and investor pages, the who-qualifies page and 16 CFR 255.5, all read on 28 October 2026. It has not been tested against real drafts, and no data on how often success stories expose companies has been published.

## One draft through the gate (Illustrative)

Illustrative. An invented fund, an invented company and invented wording.

The draft LinkedIn post: "Proud that one of our portfolio companies, a 300-person Midwest freight broker, just licensed its dispatch history to a leading AI lab through our partner SourceX. Our platform team's introduction earned the fund a reward in the first payment."

| Line | Gates failed | Outcome |
|---|---|---|
| "a 300-person Midwest freight broker" | 2, 3 | Identifiable from the public portfolio page; no written CEO approval. Cut |
| "licensed its dispatch history" | 1, 2, 3 | Describes the company's records and confirms a deal. Cut |
| "a leading AI lab" | 5 | Characterizes the buyer. Cut |
| "our partner SourceX" | 4 | Needs SourceX's written authorization. Held until it arrives |
| "earned the fund a reward in the first payment" | 2 | Reveals the payout and dates the company's payment. Cut |

What survives, posted after SourceX authorized the fund in writing to name it: "Our platform team now introduces interested portfolio CEOs to SourceX, which licenses business records directly from companies for AI training. SourceX may pay the fund if an introduction leads to a license; the company is paid the same either way. We do not discuss any company's decision." No company, no outcome, no money. It is less exciting than the draft, and it is the version that does not need anyone else's secret.

## Escalation, withdrawal and later publication requests

- **The CEO withdraws approval.** Take the story down that day, chase the copies in newsletters and decks, and file the date. The approval was for a period; withdrawal ends it early.
- **The company wants to announce its own deal.** That is its decision under its own agreement, and SourceX's [guidance on announcing a data license](/questions/should-we-announce-data-licensing-deal) starts from that agreement. If the founder wants the buyer named, the [public buyer name guide](/guides/what-if-the-founder-wants-a-public-buyer-name) explains why that stays confidential. The fund does not amplify an announcement until the company has made it.
- **SourceX publishes its own case study.** That is SourceX's material; sharing it follows [the rules for an approved referral case study](/guides/how-to-use-an-approved-referral-case-study-without-promising-the-same-result), not this gate.
- **Declined, withdrawn or stalled introductions.** Never a story. That a company looked and stopped is its business.
- **Investment talk.** A success story about a referral is not a statement about SourceX as an investment; keep the two apart, as [separating a referral from an investment introduction](/guides/separate-a-company-referral-from-an-investment-introduction) describes.

Material gathered for a story that never runs follows the same end-of-life rules as the rest of the file; see the [retention review for closed referral records](/guides/a-retention-review-for-closed-referral-records), and the [guides hub](/guides) for related fund guides.

## Where this test can be wrong

- **Inference you cannot foresee.** A reader with industry knowledge can combine facts you thought were harmless. When in doubt, coarsen further or do not publish.
- **A CEO's yes may exceed what the company can give.** The company's own agreement with SourceX may restrict publicity; its CEO should check it with the company's counsel before approving.
- **People post on their own.** A team member's personal post can undo the fund's careful one. Brief everyone who touched the referral.
- **No legal advice here.** Confidentiality duties to the company, to SourceX and under securities or privacy law vary; this page gives none. Route questions to your own counsel or the company's.
- **Nothing to measure yet.** Whether a narrow process story recruits introducers as well as a detailed one has not been studied. Do not let that gap become a reason to publish more.

Publishing about referrals is a referral decision. Readers evaluating SourceX itself as an investment can request investor materials through the [SourceX investor overview](https://sourcex.si/investors).

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

Put the six gates in front of your next story draft, [register as a partner](/register) before the fund says anything public about SourceX, point readers to [who qualifies](/who-qualifies) instead of describing companies and rest every money statement on the [program terms](/terms).

This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.

## Sources

- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://sourcex.si/how-it-works
- https://refer.sourcex.si/how-it-works
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/investors
- https://www.ecfr.gov/current/title-16/chapter-I/subchapter-B/part-255/section-255.5
