What happens from your first check to getting paid, shown on the platform screens you would actually use.
57 seconds · real platform screens, labelled examples
For companies licensing their business data
02 / How we handle your data
Signed first. De-identified. Used only on your terms.
One controlled line from your application to your payment. Nothing moves until two signatures are in place, your data sits in access-controlled custody on an approved route, de-identification is completed and checked before any commercial use, and the fee is owed to you at Closing whether or not the partner has paid.
01
Supplier portal
apply · inventory only
NO RECORDSNothing moves before two signatures
02
Agreement
Master + Confirmation
2 SIGNATURESMaster once, Confirmation per deal
03
Secure transfer
after your go-ahead
APPROVED ROUTEYour records move (from step 3, only after your go-ahead)
NOTIFIEDthen a Closing Notice within 2 business days
07
Licensed delivery
approved partner only
PERMITTED USENo use outside the Permitted Purpose
08
You are paid
60 days from invoice
OWED AT CLOSINGfrom your valid invoice, not tied to the partner paying
YOUR SIDE · NOTHING HAS MOVEDSOURCEX CUSTODY · RESTRICTED, CHECKED, NOTIFIEDOUTCOME · LICENSED, PAID
Your journeyYour records move (from step 3, only after your go-ahead)Illustrative overview. Your signed Master Supplier Licensing Agreement and Dataset Deal Confirmation govern every specific.
Nine steps, with what happens to your data at each one.
The same nine steps you see in your SourceX account. Records stay with you until step 7. Fee owed at Closing. Paid within 60 days of a valid invoice.
A · Qualify and offerBefore Day 1
B · Sign and set upDays 1–14
C · SellDays 14–30
D · Deliver, close, payDays 30–130
Records stay with you · steps 1 to 6Records move · approved route only · steps 7 to 9
01 / Apply and qualify · Before Day 1
Your application and data inventory. No records are shared.
A few questions, no files, and an indicative estimate. SourceX checks fit, completes the inventory with you and sets the processing route.
What you see
An application confirmation with the Supplier Process Overview, then “under review” once the inventory is in.
What does not happen
No records or samples leave your systems. A mutual NDA is available first if you want one.
Basis · Process Overview step 1 · Master cover: no records or samples yet
01 / 097.5 s per step · click a step · arrow keys
Your records moveYour journeyStandard signature
Day 1 is the Master signature. Day ranges are planning targets; your signed Master and Confirmation govern every specific.
Signatures
2Master once · Confirmation per deal
Records move at
Step 7only when SourceX gives the go-ahead
Review
30 days or lessfrom the review-start event in your Confirmation
Payment
60 daysafter a valid invoice · not conditional on the partner
Nobody outside your deal is named here. Specifics live in your signed agreements.
Inside step 7 · Master Section 3.1
Prepare and deliver, through the approved route.
The route is approved in your Master and named in your Confirmation. Six activities, in the Master’s words, with what you do and what you see on it.
The approved route your Confirmation namesApproved in your Master · named in your Confirmation
ActivityWhat the Master namesWhat you do · what you see
01Extractpackaged exports or approved extraction accessYou provide the export, or the approved accessafter your go-ahead
02Secure transfersecure upload or transfer to the approved locationNothing for you to doreceipt recorded
03Storeapproved storage and processing locations onlyEncrypted · access-controlled · named accessfor as long as it is in SourceX custody
04De-identifyagreed steps to reduce identifying information, if requiredOnly if your Confirmation requires itnothing for you to do unless a signed record says so
05Checkcompleted and checked before commercial useChecked and recordedbefore any commercial use
06Deliverreceipt recorded; starts the Review Period if your Confirmation says soYour review, up to 30 daysthen the Closing Notice within two Business Days
Your Confirmation
It names the route for your deal and whether de-identification is required. Anything outside its approved details needs a signed amendment, with both signatures.
07
What de-identification does to a record
Identifying details are removed or replaced, and the result is checked before any commercial use.
De-identification means applying the agreed steps to reduce identifying information and re-identification risk. Your Confirmation says whether it is required. Where it is, it is completed and checked before commercial use. No method removes every possibility of re-identification, and the Master says so.
SourceX usually pays a one-time fee for the dataset; some agreements set recurring deliveries, each paid as the agreement states. There are no royalties or usage fees. The exact payout is fixed in the signed Dataset Deal Confirmation; an earlier estimate is indicative only. Data that does not reach Closing earns no payment.
02
Two standard sign-offs
One Master Supplier Licensing Agreement, signed once after qualification, and a short Dataset Deal Confirmation for each deal. Returning suppliers reuse the Master and sign a new Confirmation; a material change needs a signed amendment. Closing results in a Closing Notice, not another full contract.
03
You keep ownership
You retain ownership of your original licensed data. Under the signed agreement, SourceX owns the deidentified dataset, subject to your underlying intellectual property rights.
04
Exclusivity and confidentiality
Licenses are exclusive for AI training: you agree not to license the selected data to anyone else for that purpose. The term and any alternatives are set in your Dataset Deal Confirmation. The restriction binds you; SourceX's right to distribute or sublicense the deidentified dataset is unaffected. Neither side publicizes the deal. The term runs from Closing and covers only the selected data; future data and unselected records are not included.
05
Acceptance review and Closing
SourceX reviews the delivered data for up to 30 calendar days from the review-start event set in your Confirmation and may accept sooner. Data that has not closed by the deadline is treated as declined and deleted within 30 days. Buying part of the data needs either fixed-price lots agreed in the Confirmation or a signed amendment.
06
Payment
You invoice after Closing. Payment is due within 60 calendar days after SourceX receives a valid invoice, unless different terms are signed.
07
Permanent license
Once the fee is paid, SourceX's license to the deidentified dataset is permanent and survives termination of the agreement, and models already trained on it aren't retrained or deleted.
08
What you confirm
You have the rights to license the data, personal data was collected lawfully (GDPR/CCPA), it hasn't been licensed for AI training before, and it wasn't created or altered with AI for the sale.
05 / Fit signals
SourceX maps what your company knows to what AI labs and Acquisition Partners need.
We evaluate ten fit signals, not just company size, then turn messy business systems into a private inventory Acquisition Partners can understand.
How Acquisition Partners judge fit
Illustrative example
Volume
Historical depth
Uniqueness
How detailed the work is
Domain expertise
Shows how work ended
Human feedback
Data structure
Clear ownership
Acquisition Partner demand
Not a valuation. Company size alone doesn't determine value; final value depends on actual Acquisition Partner demand and due diligence.
What does each stage of a SourceX deal settle, and what is still open?
An application is an assessment, not a sale. Each stage settles one more question about your data, and nothing before Closing turns a figure into money you can invoice. That is why one deal can carry several numbers: an indicative estimate after the first questions, an indicative range at the offer, an exact payout once the Dataset Deal Confirmation is signed, and an invoice only after Closing.
Keep two other amounts apart from your payout. A referral partner who introduced your company can earn a share of what SourceX actually pays you, under the referral program's own terms. SourceX's income from licensing the de-identified dataset onward, as your agreement allows, is a separate matter.
The table shows what each stage settles, what stays open after it and the record you hold.
What does each stage of a SourceX deal settle, and what is still open?
Stage reached
What it settles
Still open
Record you hold
Application
Your systems, years of history and exports are described; an indicative estimate is shown
Qualification, an offer and any payout
Your application answers
Qualified
Fit is checked, the inventory is completed with you, the rights check is run and a processing route is set
Whether an offer follows
The completed private inventory
Indicative offer agreed
A range proposed from your inventory that you agreed, possibly after a counter
The price, which stays indicative
The agreed indicative range
Master signed
One agreement covering this deal and later ones; the inventory assessment starts
Which dataset, at what payout
Master Supplier Licensing Agreement
Confirmation signed
Exact dataset, payout, rights, processing route and deadlines, including the Closing Deadline
Commercial commitment, delivery and acceptance
Dataset Deal Confirmation
Commercial commitment
SourceX has commitment on the approved terms, signs its onward agreement and gives the go-ahead
Whether the delivered data is accepted
The go-ahead to prepare
Closing
SourceX has accepted the data in writing and every condition is met
Payment
Closing Notice
Paid
Payment against your valid invoice, unless different terms were signed
No payment question; the license and exclusivity continue as signed
Your invoice and the payment
No Closing by the deadline
The data is treated as declined and deleted
No payment for data that did not close
No-deal notice
What information starts the conversation, and who in your company holds it?
Descriptions, not records: fit can be judged without files because the early question is whether your records resemble what buyers look for. As a general guide, that means one system holding tens of thousands of records or more, with years of consistent history, usually at least two; smaller sets can qualify when the work is rare, and every case is assessed deal by deal.
Three kinds of knowledge usually sit with different people, and naming them early saves a round of questions later. One person can hold more than one role; what matters is that each answer has an owner. Gather the following before you apply, without exporting anything:
1The context owner: the manager who knows what the fields and status codes mean and how a piece of work ended, for example how a support ticket was resolved or a purchase order approved.
2The export owner: the administrator who can say whether each system exports the fields you would offer, and in what formats.
3The rights owner: the person who can locate the customer and vendor contracts and privacy notices that govern reuse, and who can sign for the company.
4For each system: its name, the work it records, the first and last year of records, any migration or gap, and a rough record count.
5Whether records show outcomes as well as activity, since how the work ended is one of the fit signals above.
6Limits you already suspect: customer or vendor restrictions, personal or sensitive fields, free-text notes.
7Hold back files, record samples and screenshots: no data upload is needed to see whether your company qualifies.
What happens when scope, permission or context is unclear, as in many older archives?
Unclear points become questions before the deal moves on, and each answer can keep records in, narrow the scope or take records out. The Apply and qualify step above says SourceX completes the inventory with you and runs the rights check; the six gaps in the table are the ones a supplier should expect to clarify there. They are a reader's guide drawn from that step, not a published SourceX checklist.
What happens when scope,…
tap a node
Gap
Scope
Question to expectWhich systems, years and record types are you offering?
What the answer can changeThe inventory, and later the exact dataset in the Confirmation
Each node is a row of the table below.From this section
For older archives, age is not the test; continuity and context are. Ten years of records that span a system migration, renamed status codes or a merger may behave like two shorter datasets, and records nobody can still explain are hard to assess, however old. Historical depth is a fit signal, not a promise that old data qualifies; the guide to licensing ten-plus years of historical records covers older privacy notices and format conversion.
Removing names does not settle the personal-data question either. For EU records, the EU Court of Justice, in Case C-268/21, treated pseudonymised personal data that could be attributed to a person with additional information as information about an identifiable person, so expect questions about IDs and free text after obvious identifiers are gone. This is general information; your counsel decides how it applies to your records.
Each gap, the question to expect and what the answer can change:
What happens when scope, permission or context is unclear, as in many older archives?
Gap
Question to expect
What the answer can change
Scope
Which systems, years and record types are you offering?
The inventory, and later the exact dataset in the Confirmation
Permission
Do customer or vendor contracts, or your privacy notices, limit reuse?
Records stay in, are narrowed or are excluded
Personal data
Where do personal details sit, including IDs and free text?
The processing route, or the exclusion of some records
Continuity
Did a migration, merger or gap break the history?
Which years count as one consistent dataset
Context
Can someone explain the fields, codes and outcomes?
Whether the records can be assessed at all
Export
Can each system export the fields in scope?
Whether access and inputs can be ready for preparation
Who does the preparation work, and what should you check in the Confirmation first?
SourceX runs the preparation, and it starts only after the Confirmation is signed and SourceX gives the go-ahead. Your part is to approve scope and terms, stand behind the confirmations you give in the agreement and provide access and inputs. SourceX either de-identifies the records itself or uses its processing partner, and because it does not host multi-terabyte datasets, large deliveries stay in your own storage or ship on encrypted drives.
Who does the preparation…
tap a node
Task
Approve scope and terms, and sign
WhoYou
WhenBefore any data is delivered
Each node is a row of the table below.From this section
This page names no connectors or self-service tools, so do not assume one exists for your system; the route is the one your Confirmation fixes. Before signing, check each field against your completed inventory, then use the table to see who does what:
Checklist · 6 items
Dataset: the systems, date range, record types and exclusions match the inventory, so nothing is in scope that you did not mean to offer.
Payout: one figure for the whole dataset, or fixed-price lots if only part of the data may be bought; without lots, a partial purchase needs a signed amendment.
Rights: which uses the agreement grants, the exclusivity term, and that future data and unselected records sit outside it. The licensing terms glossary defines training, evaluation and permitted use, but only your signed agreement grants them.
Processing route: who handles the data, and where it sits during preparation.
Deadlines: the Closing Deadline, and that data not closed by then is treated as declined and deleted.
Changes: whether newer records come through recurring deliveries in this agreement or a new Confirmation under the same Master. Any material change needs a signed amendment.
0/6
0 of 6 ticked. Tick each item as you go.
Who does the preparation work, and what should you check in the Confirmation first?
Task
Who
When
Approve scope and terms, and sign
You
Before any data is delivered
Confirm rights, lawful collection, no earlier AI-training license and no records created or altered with AI for the sale
You
In the signed agreement
Complete the inventory, run the rights check and set the processing route
SourceX, with you
During qualification
Provide system access and inputs
You
After the go-ahead
Extract, transfer and de-identify
SourceX through the approved route; de-identification by SourceX or its processing partner
After the go-ahead
Hold large datasets
Your own storage, or encrypted drives
At delivery
Review the delivered data and accept it in writing
SourceX
Before Closing
How should an investor read a qualified status in SourceX materials?
As an early supplier-side gate, not as evidence of demand. A qualified company has passed fit, inventory and rights checks; commercial commitment comes later and acceptance only at Closing, so hold any figure to the stage table above. Ask for movement between stages as counts with a denominator and a cohort date, such as signed Confirmations out of companies qualified in the same month, open cases shown as open. SourceX shares company and commercial metrics with investors directly and publishes none here.
Two limits apply. Qualification can reverse when a rights or personal-data question surfaces after it, and it says nothing about how many buyers stand behind a deal. Licensing income can rest on very few buyers: Reddit's Form 10-Q for the quarter ended March 31, 2026 says that "substantially all of the contract value associated with our licensing revenue is derived from two of our partners".
Whether a plain-language process page helps companies take part on informed terms can be tested rather than assumed. ISO 24495-1:2023 sets governing principles and guidelines for plain-language documents. A test would give first-time readers the stage table and check whether they can say what a qualified status does not mean, find where the payout is fixed and name the record that marks Closing, against readers given the agreements alone. No result is published or claimed.
Methods note. The stage table, gap categories, responsibility split and checklists were written for this page on 2026-10-26 from the process and deal terms above and SourceX's approved public facts; the gap categories are editorial, not an internal SourceX taxonomy. Not measured: how many companies reach each stage, how long stages take and whether these additions improve understanding.
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 for this section
In Case C-268/21 the EU Court of Justice treated pseudonymised personal data that could be attributed to a natural person with additional information as information on an identifiable natural person. Source
Reddit's Form 10-Q for the quarter ended March 31, 2026 says that substantially all of the contract value associated with its licensing revenue is derived from two of its partners. Source
ISO 24495-1:2023 establishes governing principles and guidelines for developing plain-language documents. Source