Wave 9 settled who may speak about an archive: the custodian checklist for whoever holds it and the litigation hold escalation map for frozen records. This page covers what those leave implicit: the five or six moments in an ordinary introduction where a copy gets made by someone trying to help, and what to do instead.
A copy made to help is still a new copy
SourceX's own guidance on secure reviews draws the line where most people do not expect it: "A secure data review should treat every screenshot, phone photo, copied text and verbatim note as a new copy of the restricted records." The same page separates permission to view, permission to keep a derived copy and the right to license the records later, and calls them three separate questions. A referral touches none of the three, so it has no reason to create anything.
Three things change the moment a copy exists:
- It escapes the original's controls. The archive may sit under a hold, a retention schedule, an access list or a deletion date. A screenshot on a partner's phone sits under none of them.
- It has no clear decider. The controller decides about the archive. Nobody has decided about the forwarded spreadsheet in your inbox.
- It enlarges what must be protected. NIST's guide on personal information gives a whole section to "Minimizing the Use, Collection, and Retention of PII". In paraphrase, it says handling should stay at what is strictly necessary and that holding less reduces the consequences of a breach. A copy made "to be safe" makes the exposure bigger, not smaller.
Whose decision any copy is
Only the party that controls the records can decide that a copy is made, and why. SourceX's screening page defines that party as "Whoever directs that entity now: its board and CEO, an acquirer, or a trustee, receiver or assignee in a formal process," and for a wound-down company routes the question to the estate's controller, with counsel. The CEO alone may not be enough once a formal process starts.
Two legitimate copies can exist, and neither belongs to the referral:
| Copy | Who decides | Who makes it | Does it reach a partner? |
|---|---|---|---|
| A preservation copy for a legal duty | The controller, on counsel's advice | Whoever counsel and the controller engage | No |
| Delivery under a signed deal | The company, by signing its Dataset Deal Confirmation | Approved processing routes, after SourceX's go-ahead | No |
| Anything made "for the referral" | Nobody has authority to want it | Nobody should | It is the problem this page prevents |
The partner agreement says the same thing from the partner's side. Section 4.4 of the sample: "Partner must not collect or retain supplier dataset copies through the referral program without separate written authorization." Section 4.2 adds that the agreement gives a partner no authority to share a supplier's records or to access extraction systems.
The no-copy referral process map
Six stages, each with the copy it tends to invite, the move that replaces it and the only party who could ever approve a copy at that point. Use it as a pre-flight read before each step, not as a form to file.
| Stage | The copy it invites | The no-copy move | Who could ever approve a copy here |
|---|---|---|---|
| 1. You notice the archive | A phone photo of box labels or a server rack; a screenshot of a folder tree | Write one line from memory: what it seems to be, where, who holds it | Nobody, for a referral |
| 2. You ask whoever controls it | Forwarding the custodian's inventory sheet; attaching an index to your email | Name the holder and the date; let the holder send its own status to the controller | The controller, for its own purposes |
| 3. The archive gets described | A sample export "so SourceX can see"; a test restore to check it opens; a file list pasted into a summarizing tool | Pass on only what the controller states: systems, years, rough size, how it knows | The controller, with counsel where a hold may apply |
| 4. You introduce the decider | Attachments, a shared-drive link or a data-room invitation in the introduction | A text-only email to the decider, with a line saying nothing was copied | Nobody: an introduction carries no records |
| 5. The company takes SourceX's first steps | An upload "to speed things up"; records shown on a recorded call | The company lists systems and history; per SourceX, no records are shared at this stage | The company, only after its signed Confirmation and SourceX's go-ahead |
| 6. After a yes, a no or a stop | Notes, screenshots or a stray file kept "just in case" | Keep the decision or stop record only | The controller, for any stray copy |
How to read it. Every row ends with a party that is never the partner. If you find yourself the only person who could approve the copy in front of you, the copy should not exist.
Method note. The rows apply the controller definition and wound-down route on SourceX's who-qualifies page, the first-step and processing descriptions on its how-it-works page, sections 4.2 and 4.4 of the sample Channel Partner Agreement and the copy definition on SourceX's secure-review page, all read on 2026-10-28. The copies listed are common examples, not a full inventory; the map has not been tested on completed introductions.
Transition moments when copies multiply
Restructurings move archives, and each move is a moment when copies appear. Read each against the custody, control and preservation clocks that run beside the referral.
- Migration to cheaper storage. Moving an archive usually means copying it before the old media is retired. If the controller decides to move it, that is the controller's project. Never propose a move to keep a licensing option open.
- A new controller is appointed. Copies made under the old controller's instruction now answer to the new one. Ask whose instruction a copy was made under before mentioning it to anyone.
- The shutdown run-sheet. Final exports scheduled by a wind-down team serve the company's own retention duties. They are not a referral asset, and nobody adds a "spare" export for later.
- A hold is released. A release may come with instructions to return or destroy preserved copies. Where it does, they bind whoever holds the copies, and a licensing conversation does not suspend them.
- The storage contract ends. The end date reaches every copy the provider holds. A partner who sets up a private backup "before it's gone" has made the problem this page exists to prevent.
When a copy already exists
Sometimes the copy arrives before anyone reads this page: a former manager emails a sample, an IT contractor sends a screenshot, a well-meaning colleague uploads an index to a shared folder.
- Stop opening it. Do not forward it, summarize it or show it to SourceX.
- Write down what arrived, from whom, when and where it now sits, without describing its contents.
- Tell the party that controls the company or estate, in writing, and ask what it wants done.
- If a hold could apply, say so in the same note so the controller's counsel can answer; do not delete anything on your own while that question is open.
- Follow the written instruction, then record that you did.
A stray copy does not end the conversation, but it moves the next step to the controller. An introduction made while the partner still holds a stray file looks like the transfer channel it was trying not to be.
Two archives, one rule (Illustrative)
Illustrative. Composites built for this page; no real companies or outcomes.
The receiver and the helpful contractor. A receiver controls the assets of a 180-person freight forwarder, including eleven years of shipment exception records on a server that an IT contractor keeps running. A partner who knows the receiver raises the idea. The contractor offers a test restore "to prove it all still opens". The partner declines and asks the receiver what it already knows. The receiver states the system, the years and that its contractor reports the backups as current. The partner, registered and with the Channel Partner Agreement signed, sends a text-only introduction. The estate applies itself. Copies made for the referral: none.
The screenshot before the hold. A former operations manager of a 95-person clinic group sends a partner screenshots of a scheduling system "to show what's there". The group is in an assignment, and the assignee's counsel has a hold on that system. The partner stops at step 1 of the stray-copy routine, writes to the assignee describing only what arrived and when, and waits. Counsel instructs; the partner complies and records it. The group is also below 50 full-time employees at its peak, which the assignee confirms, so the file closes on fit as well.
Fit, credit and reward with nothing copied
Everything SourceX needs at the start can be said in sentences. Each answer comes from the controller, never from the archive:
- full-time headcount at the company's peak, 50 or more, contractors excluded, and peak rather than today's figure;
- the systems and the years the records cover;
- whether the records are the company's own or belong to clients;
- the controller's name, and the dated record that shows its control;
- where the company is. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.
The partner signs the SourceX Channel Partner Agreement before introducing anyone, as section 1 of the terms requires. Credit is not earned by a click: section 2 gives it to the earliest valid introduction, and only when the company follows with a verified application inside the 90-day window. Any reward is paid by SourceX apart from the company's own payout, which section 4 says is never reduced by it. No value, amount or timing is promised to an estate, and a referral never supplies one. For an offline archive that nobody can open yet, the metadata brief shows how a description is written from labels and invoices without touching the media; for a liquidation, the advisor's inquiry checklist covers the question to the estate.
Where a no-copy rule costs something
- It is slower. A test restore would answer "does it open?" in an hour. The controller's answer may take a week.
- Some archives cannot be described from outside. If nobody can say what an archive holds without looking, the controller decides whether its own people look, for its own reasons. Until then the referral waits, and that is a legitimate stop.
- Copies may already be everywhere. Former staff, vendors and old laptops may hold copies nobody listed. The rule governs what the referral adds, not what already exists.
- Mixed archives multiply the deciders. Where one archive holds several businesses' records, each share has its own controller; the entity separation questions sort that out without opening anything.
- No published results. SourceX has not published how often archive introductions stall for want of a description.
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.
If the controller wants a conversation and every fact you would pass on came from them, create your partner account, hold the controller's answers up against who qualifies and read the program terms before you write; related archive guides are in the guides hub.