The difference sounds obvious until a helpful CEO attaches "a few examples so SourceX can see what we have", or a colleague asks whether the company's customer list counts as contact data. This page is for the fund's general counsel's office, or whoever answers those questions for the platform team, and it gives the answer as a set of worked boundaries rather than a definition.
Two records, two owners
The contact record belongs to the partner. It describes a person and an event: who the CEO is, how to reach them and when they agreed to be introduced. It is still personal information. NIST's glossary, paraphrased, describes personally identifiable information as information that can distinguish or trace an individual's identity, alone or combined with other linked information, and a name with a work email does exactly that. Which privacy obligations attach to it depends on where the fund operates; the fund's counsel decides that, not this page.
The introduction record is part of the contact record. The sample Channel Partner Agreement fixes its minimum: each introduction record "must identify the company, domain, Partner, opportunity, introduction method and timestamps." Credit is decided from dated records like this one, so it earns its place.
The dataset sample belongs to the company. It is a piece of the records the company might license, and the agreement is direct about the partner's position: "This Agreement gives Partner no authority to share a supplier's inventory, records, raw data or personal information, or to access extraction systems." SourceX's trust page puts scope with the company, "The supplier decides which systems, records and date ranges are in scope. Everything else stays out.", and its referral process page tells partners they "do not need to export, upload, or describe confidential records."
| Record | Whose it is | What it is for | Who may receive it |
|---|---|---|---|
| Contact record | The partner's | Reaching the CEO and remembering the relationship | Colleagues who need it for the introduction |
| Introduction record | The partner's, shared once submitted | Proving who introduced whom, when and how | SourceX, after the CEO agrees |
| Dataset sample | The company's | Showing what the records contain | Only SourceX, from the company, when the company chooses |
Why small, redacted or anonymized changes nothing
Size does not change ownership. Three tickets are as much the company's records as three million. Redaction does not change it either. A CEO who blacks out names before emailing a page has not performed SourceX's de-identification, which is a step in SourceX's process under the company's signed agreements, not something an email can do.
The timing makes the point sharper. SourceX's trust page says "Nothing is delivered until the supplier has signed the Master agreement and the deal's Dataset Deal Confirmation and SourceX gives the go-ahead." Even SourceX receives no records before those signatures. A sample that travels through a partner ahead of any agreement runs ahead of SourceX's own process, through someone with no authority to carry it.
Twelve boundary examples
The items are Illustrative, chosen because each one has been mistaken for the other kind.
| Item (Illustrative) | Kind | Why | What the partner does |
|---|---|---|---|
| The CEO's name, title, work email and mobile number | Contact record | Personal information about the person introduced | Keep it in your own system, under your own privacy duties |
| Date and channel of the CEO's yes, in the CEO's words | Introduction record | Evidence of permission | Keep it, dated |
| The company's legal name and web domain | Introduction record | Section 3.3 of the agreement names both | Keep them |
| "About twelve years of support tickets in one system," said by the CEO | A description, not a record | The company describing itself | No need to note it; the company states it in its own application |
| A spreadsheet of the company's customer contacts | Sample | Contact details, but the company's, about third parties | Decline it; do not open further or forward |
| Three "anonymized" tickets pasted into an email | Sample | A piece of the records, whatever was removed | Do not forward; tell the CEO SourceX needs no files at this stage |
| A screenshot of the help desk dashboard | Sample | Shows the content, structure and volume of the records | Do not keep or forward |
| The field list of the company's CRM | Treat as a sample | Describes the records' structure in the company's own terms | Leave it between the company and SourceX |
| A redacted customer contract | Company record, possibly privileged | Rights belong to SourceX's review and the company's counsel | Never take it |
| Your own note: "CEO agreed by phone, 3 October" | Contact record | Your record of your own act | Keep it |
| The CEO's public profile and the company's published headcount | Public signal | Published by them; dated when you read it | Note it with its source and date |
| A figure from a board pack the fund received | Confidential to the fund's seat | Learned through board rights, not given for this purpose | Ask the CEO one question at most; never record or send the figure |
The customer spreadsheet is the row that causes the most confusion, because it is literally a file of contact records. Ownership, not format, decides. Your contact record is about the CEO you introduce; the company's contact records are part of what the company might license, and SourceX's screening page warns that material belonging to a company's clients is usually not a fit anyway.
The last row is a different boundary with the same answer. SourceX's screening page says knowledge from board packs or information rights is a reason to ask the CEO, "never material to pass along".
Cut the record to what the next decision needs
Two decisions follow an introduction. The CEO decides whether to talk, and SourceX decides whether the company's application fits a current program. Neither needs a sample from the partner. SourceX's application describes itself as "Three screens, about 7 minutes, to check your fit." and lists "No files needed", "No passwords or API tokens" and "Nothing licensed or transferred". The company describes its own systems and history there, in its own words.
So the partner's record stops at the rows marked keep above. Anything more is information the fund must then protect, retain, disclose on request or delete, for no benefit to the introduction.
When a sample arrives anyway
Do not open it further, forward it or reply with it attached. Tell the CEO, in one line, that SourceX's application needs no files and that you will not pass anything on. Then handle the file under the fund's own policy and counsel's instruction, and record that it arrived: the date, the kind of item and what was done, never its contents. When the file is a contract or legal memo, the privileged-material guide applies. When files have already spread into a CRM through integrations, run the attachment boundary review. If the company's privacy lead joins the conversation, the referral conversation with a privacy officer sets the agenda.
Escalation, withdrawal and publication, one rule each
- Escalation. If SourceX needs more, it asks the company; section 2.2 of the agreement lets SourceX communicate with a referred company directly. The partner is never the channel for records.
- Withdrawal. If the CEO withdraws, the contact record shrinks to the dated stop. Contact details you no longer need go under the fund's retention policy.
- Publication. A contact record never becomes a public list of introduced companies. The sample agreement restricts publicly identifying the other side as a partner or sharing non-public deal details without written authorization, and the CEO agreed to an introduction, not to being listed.
Risks and limits of these boundaries
- Definitions differ by law. What counts as personal information, and what duties follow, varies by jurisdiction. The fund's counsel settles it.
- Borderline items depend on content. A schema, a summary or an org chart can reveal more than it seems. When unsure, treat it as a sample.
- Tools copy without asking. Email and CRM integrations file attachments automatically, so a boundary held in conversation can fail in software.
- The company's own contracts may limit even descriptions. Customer agreements can restrict what the company may say about its records. That is for SourceX's rights review and the company's counsel.
- Nothing here was measured. How often samples reach partners has not been studied or published.
Method note. The boundary examples apply the sample Channel Partner Agreement (sections 2.2, 3.3, 4.2 and 4.5), SourceX's trust, application and referral process pages, the who-qualifies page and the program terms (version 2026-10-22.2, since replaced by version 2026-11-04), all read on 2026-10-28, with NIST's glossary for the meaning of personal information. Each row was classified by who owns the item and what the next decision needs, not by its file type.
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.
Give the twelve boundary rows to everyone at the fund who makes introductions, then register as a partner, check each company against who qualifies and read the program terms before the first contact record is created.
Deciding what a fund may hold about an introduction is a referral question; anyone weighing SourceX as an investment can ask for investor materials through the SourceX investor overview.
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.