SourceX's own terms page shows the problem in one line. It says SourceX Inc. is headquartered in Los Angeles, California, and gives its legal and mailing address in Lewes, Delaware. That is two locations for one company before anyone asks where a single file is kept. A platform manager who reads one address and announces a residency answer has answered a question nobody asked and skipped the one that was.
Six location facts that one address blurs
Treat every cross-border row as six separate cells. Each has a different owner, and a partner fills in only the first one alone.
| Location fact | What it answers | What it cannot answer | Who knows |
|---|---|---|---|
| The partner's own location | Whether SourceX can work with you | Anything about the company | You, checked against SourceX's page |
| Head office | Where the company is run from | Where records sit or who holds them | Public sources, the CEO |
| The entity that holds the records | Which company would license, and whose CEO decides | Where its systems store data | The CEO |
| Where each system stores its data | The physical or cloud region, system by system | Whether the company is inside the published geography | The company's IT lead |
| Language of the records | Whether the English condition is met where it applies | Storage, ownership or rights | The company's own count |
| Commitments about storage and processing | What law, customer contracts or internal policy require | Whether SourceX accepts the company | The company's counsel or privacy lead |
SourceX's glossary defines data residency as a requirement or commitment that data is stored and processed in a specific country or region, and says it can come from law, customer contracts or internal policy (paraphrase). Every one of those sources sits inside the company. That is why the last two rows belong to the company and never to the introducer.
What SourceX publishes about location, and where it stops
The published location test is one sentence on who qualifies: 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. How the English share is counted, system by system, is set out in English-language data referral eligibility.
Three more published facts bound the question:
- Partner location is separate. Partners can join from most countries, but SourceX cannot work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists.
- Programs differ. SourceX applies each program's own criteria, which vary in size, history, geography, language and data category.
- The CEO decides. Opening a licensing discussion and signing for the company fall to the CEO of the company that would license.
SourceX publishes nothing on where a referred company's data must be stored, whether data may cross a border, or how storage location affects a deal. Do not fill that silence with a rule of your own, and do not describe how SourceX or anyone else will protect, store or move the data. Those answers belong in the company's own conversation with SourceX and its own advisers.
Storage location is a setting, not an address
Where a system keeps data is usually chosen when it is set up, and it can differ from system to system inside one company. Amazon Web Services tells its customers: "You determine the geographic region where your customer content will be stored and the type of storage." It adds that content can be replicated and backed up in more than one region. Microsoft's data location FAQ for Microsoft 365 says an administrator can see, for each service, a current geography where data is stored now and a committed geography, and that where data is provisioned depends on the tenant's default geography and where each service is deployed (paraphrase).
Two consequences follow for anyone mapping a network. A head office move does not move a single system. And a company with a helpdesk, a document library and an old on-premises archive may have three storage answers, none of which matches its address. The partner does not need any of them to make an introduction, and should not guess them.
The location distinction question set
Ten questions, asked in order, each to the person who can answer it. The partner writes down the answer as given, with a date, or writes "unknown".
| # | Question | Asked of | The partner records | Never |
|---|---|---|---|---|
| 1 | Can SourceX work with a partner based where I am? | SourceX's published page; SourceX if unsure | Yes, or the date you asked | Assume from your passport or your fund's domicile |
| 2 | Which legal entity holds the records the CEO might license? | The CEO or the relationship holder | The entity's name as the CEO gives it | Substitute the brand or the head office |
| 3 | Where is that company based, in the words of the published sentence? | Public facts, confirmed by the CEO | The place, quoted against the sentence | Promise that the place qualifies |
| 4 | If the English condition applies, has the company counted its English share? | The CEO's team | Counted, not counted, or unknown | Estimate it from the website's language |
| 5 | Is the entity part of a group? | The CEO | Group name, if any | Treat sister companies as separate caps |
| 6 | Who is the CEO of that entity today, and do they want the conversation? | The relationship holder, then the CEO | The CEO's name and the date of the yes | Accept a yes from a board, an investor or a manager |
| 7 | Does the company know where each relevant system stores its data? | The CEO, who may ask the IT lead | Yes, no or unknown; never the regions themselves | Ask for exports, screenshots or logins |
| 8 | Do law, customer contracts or internal policy limit where data may be stored or processed? | The CEO, with counsel | That the question has been raised | Give an opinion on the answer |
| 9 | Which open questions are SourceX's to answer? | You, from the published pages | The list, sent with the CEO's agreement | Answer them on SourceX's behalf |
| 10 | What is the dated outcome? | You | One of the outcome codes below | Leave the row without a date |
Questions 7 and 8 exist to be asked, not answered by you. Their only job is to make sure the CEO knows residency is a real question and raises it with SourceX directly. For languages, a fuller evidence note sits in stating data language without guessing from headquarters.
A multinational row with its unknowns left in (Illustrative)
Illustrative: a generic company and invented facts, with no outcome implied. A 260-person industrial inspection group has its head office in Dublin. Most inspection reports are written by an operating subsidiary in Singapore. The platform manager's first note read "Irish company, EU data." Run through the question set, the row looks like this.
| Question | Answer as recorded | Status |
|---|---|---|
| 2. Entity holding the records | Unknown: the group CEO says reports sit with the Singapore subsidiary, but some are filed by the Irish parent | For the CEO |
| 3. Where based | Head office Dublin (EU); report-writing subsidiary Singapore, a place where the English condition applies | Both recorded; which applies depends on which entity would license |
| 4. English share | Not counted | For the CEO's team |
| 5. Group | Parent and subsidiary: one company for the reward cap | Known |
| 6. CEO and consent | Group CEO in Dublin, yes on 21 October | Known |
| 7. Storage | Reporting system hosted in a cloud region the CEO did not know; document library moved in 2023 | Unknown, raised |
| 8. Commitments | Some client contracts mention data location | Raised with the company's counsel |
| 9. For SourceX | Which entity's records fit a current program; how storage location bears on any deal | Listed for the CEO's conversation with SourceX |
The first note was wrong twice: the head office did not settle which entity holds the records, and it said nothing about where any system stores them. Outcome: introduce once the CEO confirms the entity and the English count, with questions 7 to 9 travelling with the introduction as the CEO's own questions for SourceX.
Send jurisdiction questions to the person who owns them
| If the question is | It belongs to | What the partner says |
|---|---|---|
| May our records leave this country? | The company's counsel or privacy lead | "That is for your advisers; please raise it with SourceX directly" |
| Do our customer contracts restrict where data goes? | The company's counsel | Nothing beyond noting it was raised |
| Is a company based here within the program? | The published sentence; SourceX where it is silent | Quote the sentence; never extend it |
| Where would licensed data be stored after delivery? | SourceX, in the company's own conversation | "SourceX answers that; I cannot" |
| What tax or registration applies to my reward? | Your own adviser | Nothing to the company |
A partner gives no legal, tax or regulatory advice here and makes no data-protection promise for SourceX. The useful work is routing: the right question, to the right person, with a date.
Record a next step or a no-fit
Every row ends in one dated code.
- Ask the CEO. The relationship holder has agreed to ask, and questions 2 to 6 are pending.
- Introduce. The CEO wants the conversation, the entity is named and the published sentence is met as far as known; residency questions travel as the CEO's questions.
- Ask SourceX first. The place or the partner's own location is not clearly covered by a published page.
- Outside the published sentence. Record the place and the date, and do not introduce.
- Revisit on a trigger. A named event would change the answer, such as an English count or a restructuring.
Run the company fit checker only as the preliminary screen it says it is. For the wider geography gates, see why geography is only one part of referral qualification and checking language coverage before suggesting global fit.
Where this question set can mislead
- Programs move. Criteria follow each program and can change. A row checked in October is a row checked in October; date it.
- Storage moves. Migrations change where data sits without changing the address. A "known" storage answer from last year is a new "unknown".
- Confidential knowledge. A fund partner who knows a company's hosting from board packs learned it under a duty. It may prompt one question to that company's CEO and goes nowhere else.
- An answer can harden into a promise. "The data is in Germany", repeated twice, becomes something a CEO thinks SourceX accepted. Keep residency facts in the company's words, attributed and dated.
- Funding status is irrelevant. A celebrated portfolio company and an owner-run firm face the same sentence and the same unknowns.
Method note. The six location facts and ten questions come from SourceX's who-qualifies page and program terms (version 2026-10-22.2, since replaced by version 2026-11-04), SourceX's data residency glossary entry, and two cloud providers' published statements on storage location, all read on 2026-10-27. Nothing here measures how often head office and storage location differ; no such figures have been published. The question set tests no company's data and assesses no legal question.
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.
When a row reaches "Introduce" with the entity named and the residency questions written down as the CEO's own, register as a partner, check the place once more against who qualifies and read the program terms before the CEO hears from SourceX. Other location and language methods are collected in the guides hub.
Mapping where a company keeps its records is referral work; deciding whether SourceX itself is worth investing in is a different task, and readers weighing that can request 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.