# Confidential files sent unasked: stop and escalate | SourceX

Canonical: https://refer.sourcex.si/guides/what-to-do-when-someone-sends-confidential-files-unasked
Last updated: 2026-11-05

Stop where the file landed. Read no further, forward nothing, copy nothing into a CRM, shared drive or AI tool, and never pass any of it to SourceX or hold it for a referral. Send your own policy owner or counsel a short notice of what arrived and let them decide whether it is returned, deleted or preserved. Tell the sender only that you did not need it. Any introduction then runs on what the company's CEO says for that purpose, because SourceX's published process asks partners for no files.

This page is for the person at a fund, family office or advisory firm who gets the call when an unrequested attachment turns up, often a liaison between the deal team and the general counsel's office. It does not tell you what your confidentiality duties are; your own agreements, policy and counsel (or the company's) do.

## A file arriving is not permission to use it

The senders differ; the answer does not.

- A controller who wants to "speed things up" before the CEO has heard of the idea.
- A portfolio founder forwarding a supplier's process manual "to see if they'd fit".
- A co-investor passing along an extract from someone else's sale process.
- A former employee who still holds the old company's files.

The useful question is not "is this helpful?" but "who decided this should leave the company?" For SourceX, the company's CEO decides what the company says and shares. A controller's enthusiasm, a founder's goodwill or an investor's access does not stand in for that decision, and SourceX's who-qualifies page lists introductions made without the decision maker's knowledge among the cases that are usually not a fit.

Permission for an introduction is narrower still: a CEO who agrees to hear from SourceX has agreed to a conversation, not a transfer of records or a story about the company. SourceX's own pages describe a path with no files in the middle. The referral site tells partners: "You do not need to export, upload, or describe confidential records." The company's first step on the main site is "A few questions, no files". SourceX's trust center puts scope with the company: "The supplier decides which systems, records and date ranges are in scope. Everything else stays out." A file a third party pushed to you was never inside that scope.

The sample Channel Partner Agreement says the same from the partner's side. Section 4.2 gives the partner "no authority to share a supplier's inventory, records, raw data or personal information", and section 4.4 says the partner "must not collect or retain supplier dataset copies through the referral program without separate written authorization." Neither clause tells you how to treat a file under your own obligations; that question belongs to your counsel.

## The stop-and-escalate response procedure

Six steps, in order. The first three happen in minutes and need no one's approval; the last three belong to whoever your policy names.

| Step | Who acts | What they do | What they do not do | What the log records |
|---|---|---|---|---|
| 1. Stop | The person who received it | Close the file or thread at the moment they recognize what it is | Scroll on to see what it is, download attachments or follow a shared link | The time they stopped |
| 2. Hold in place | The recipient | Leave it in the inbox, channel or folder where it arrived | Move it to a CRM, deal room, shared drive, phone or AI assistant, or forward it, even internally | Where it sits now |
| 3. Log the envelope | The recipient | Note the sender, date, channel and a neutral description such as "two attachments from the company's finance team" | Summarize the contents, or copy file names that themselves reveal contents | Envelope facts only |
| 4. Escalate | Recipient to the policy owner, often the general counsel's office | Send a notice describing the arrival, and the file itself only if counsel asks for it | Ask colleagues informally what to do, or decide alone | Who was told, and when |
| 5. Answer the sender | The recipient, in words counsel approves | Acknowledge receipt, say it was not needed and has not been passed on | Comment on the contents, thank them for the data, or promise a deletion counsel has not approved | Date of the reply |
| 6. Carry out the decision | Whoever counsel names | Return, delete or preserve as instructed | Keep a quiet copy in case it is useful later | The instruction and the date it was carried out |

Two features matter most. The log describes the envelope, never the letter, so the incident record does not become a second copy. And steps 4 and 6 sit with your policy owner and counsel, not the deal team, because only they can see the obligations that decide between returning, deleting and preserving.

The FTC's guide for businesses on protecting personal information is organized around five principles it names take stock, scale down, lock it, pitch it and plan ahead. In paraphrase of the search excerpt: under scale down it advises keeping only what the business needs, and under plan ahead it recommends a response plan with a senior staff member coordinating it. An unasked file that may contain personal information is a small version of that problem, and naming the coordinator, plus a backup, before anything arrives is the step the rest of this procedure depends on.

A reply the sender cannot misread, adjusted by your counsel:

> Thank you for thinking of us. We didn't need these files and haven't passed them to anyone, SourceX included. Our compliance team will be in touch about how they will be handled. If your CEO would like to talk to SourceX, the company can apply itself and decide what to share.

## Who may see what once a file has arrived

Reduce everything to what the next decision needs. The escalation needs a description of the arrival; an introduction, if one follows, needs only the company's name, the CEO's preferred contact route and the CEO's yes.

| Party | What may reach them | What stays away from them | Why |
|---|---|---|---|
| Your counsel or policy owner | A notice of the arrival; the file if they ask for it | Nothing they ask for | They decide what happens to it |
| The sender | A short acknowledgment | Any remark about the contents | Commentary invites the next attachment |
| The company's CEO | Separately, the question of whether to talk to SourceX; anything about the file only as counsel decides | The contents read back as "what we saw" | The CEO's decision has to rest on the CEO's own knowledge |
| SourceX | If the CEO wants it: company name, contact route and the CEO's yes | Any file, extract, count or system name drawn from the file | The CEO decides what the company tells SourceX |
| Deal team, investment committee, CRM | Nothing | The file and anything learned from it | They are part of neither the escalation nor the introduction |
| AI notetakers and assistants | Nothing | Uploads, summaries or pasted extracts | Each one makes a new copy |

## Facts you cannot unlearn

Sometimes the stop comes two pages in, and you now carry a headcount, a system name or an archive's size in your head. Treat each one as unknown. The introduction uses only what the CEO tells you for that purpose, and when the CEO's figure differs from the file, the CEO's figure is the only one that travels. If keeping the two apart feels impossible, that is a reason to hand the introduction to a colleague who never saw the file, and to mention it in your notice to counsel.

Credit and reward never depend on a file. Section 2 of the terms decides credit from dated records such as written introduction evidence; an attachment someone pushed at you is not one and gives you no head start. If a CEO-approved introduction leads to a license, the default reward on the company's first qualifying transaction is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; the USD 50,000 floor applies once per referred company, and further qualifying transactions first agreed within 12 months of the first Closing pay 15% of their Actual Supplier Payout. Section 4 adds that the reward "is paid separately by SourceX and is never deducted from the supplier's agreed compensation", so the company receives the same amount whether or not a partner is involved. Whoever submits the introduction signs the SourceX Channel Partner Agreement first.

## Escalation, withdrawal and publication need separate answers

Each of the three has its own owner, and a yes to one is never a yes to another.

- **Escalation** decides what happens to the file. Your policy and counsel own it, with the company's counsel where they judge that right, and it runs to completion whether or not an introduction ever happens.
- **Withdrawal** covers a sender who asks you to forget it and a CEO who declines the conversation. The introduction stops, the file stays with counsel's instruction, and the CEO's no is recorded with its date and never reopened through the sender. The company remains free to apply to SourceX on its own later.
- **Publication** covers any public trace: a case study, an anonymized example in a newsletter, a count in a pitch. An unasked file never becomes content. A CEO's later yes to a conversation is not a yes to a story, which needs its own written permission from the CEO for specific words.

## Three arrivals (Illustrative)

Illustrative: generic companies and invented events, with no outcome implied.

**The eager controller.** A deal partner mentions SourceX to the CEO of a 180-person freight forwarder. Two days later the controller emails a large export "so you can check whether we fit". The partner stops at the first sheet, logs the envelope and notifies the general counsel's office, which approves a reply and decides about the export. Asked separately, the CEO wants an introduction; the company applies and tells SourceX what it chooses.

**The forwarded manual.** A portfolio founder forwards a supplier's internal process manual: "these guys have tons of data, worth an intro?" The supplier's CEO has never heard the idea. The platform lead leaves the email where it is, notifies the policy owner and tells the founder that the supplier's own CEO is the only route. No introduction exists until that CEO says yes.

**The notetaker capture.** On a video call a company's operations head shares a dashboard, and the fund's AI notetaker saves screenshots into its summary. The liaison treats the summary as an unasked file: held, reported to counsel, and the tool's retention settings reviewed under the fund's policy.

For a founder who wants to send samples before anything has arrived, the [no-upload replies](/guides/how-to-handle-a-founder-who-wants-to-send-data-immediately) come first; for legal matter material, see [keeping privileged material out](/guides/how-to-keep-privileged-material-out-of-data-referral-discussions); for files your own systems filed automatically, use the [CRM attachment review](/guides/how-to-avoid-building-a-shadow-data-room-in-your-crm).

## Where this procedure can fail

- **Slow answers.** The file sits and the sender keeps sending; name a coordinator and a backup in advance.
- **Copies already exist.** Mail servers, sync clients and backups duplicate a file before anyone stops. The procedure limits new copies; it cannot recall old ones.
- **Preservation.** If a dispute or investigation may be in play, deleting can be the wrong answer. That is exactly why the decision sits with counsel.
- **No in-house counsel.** A sole practitioner still needs a decision-maker; use your own outside counsel rather than this page.
- **Relationship cost.** A sender may feel rebuffed; the reply thanks them and offers a better route.

**Methods note.** The procedure was assembled from SourceX's published process and trust pages, the program terms (Version 2026-10-22.2, since replaced by version 2026-11-04), the unsigned sample Channel Partner Agreement and the FTC guide cited below, all checked on 2026-10-28. It has not been tested against outcomes. It is not legal advice, and your own obligations may require different steps or a different order.

## 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.

Once a stray file has gone through escalation and the CEO, asked separately, wants the conversation, [register as a partner](/register), let the CEO compare the company with [who qualifies](/who-qualifies), and read the [program terms](/terms) before anyone contacts SourceX. Related situations are collected in the [guides hub](/guides).

Handling a stray file is referral work; judging whether SourceX itself merits an investment is a separate task, and anyone doing it can request investor materials through the [SourceX investor overview](https://sourcex.si/investors).

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/how-it-works
- https://sourcex.si/how-it-works
- https://sourcex.si/trust
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://www.ftc.gov/business-guidance/resources/protecting-personal-information-guide-business
- https://sourcex.si/investors
