# Security questions before a data referral | SourceX

Canonical: https://refer.sourcex.si/guides/when-security-questions-arrive-before-the-introduction
Last updated: 2026-11-04

Answer what is public, route everything else and keep a way out open. Before an introduction no company records have gone anywhere, and none need to: SourceX's first step is a few questions with no files. Sort the founder's questions into three tiers: what SourceX publishes today, what it shares only after review or writes into the agreement, and what no one can answer until the company applies. Hand that sort over as a one-page packet with the escalation contact and a sentence the founder can use to decline.

A VC operating partner hears these questions at an awkward moment, when the founder has not yet agreed to anything. The packet lets the partner be useful without vouching for SourceX, without speaking for the company's systems and without turning a founder's caution into a sales objection to overcome.

## What an early security question is really asking

A question asked before any introduction is rarely about encryption. It is usually about exposure: what saying yes would commit the company to, who would find out, and whether the partner is putting a reputation behind SourceX. Sort the concern before you look for an answer.

| The question as asked | What it usually means | When an answer exists |
|---|---|---|
| "What would we have to hand over just to find out?" | Exposure before any commitment | Now: the first step is a few questions with no files |
| "Who learns that we're looking at this?" | Confidentiality of the decision itself | Now: the partner and SourceX; partners never see applicant documents |
| "How would SourceX protect our records later?" | The counterparty's controls | Partly now, from SourceX's trust center; the rest in review and the agreement |
| "Has anyone independent checked them?" | Assurance from a third party | Now, from SourceX's own dated status page |
| "Would you stake your name on them?" | The partner's judgment | Now: you have tested nothing, so no |

The first two rows and the last are the partner's to answer in plain words. The middle two belong to SourceX, and the answers should come from SourceX's pages or people, never from the partner's memory of them.

## Introduce first or answer first: what the terms say about order

Sequence matters for one reason the founder will not know about. Section 3 of the terms treats a company SourceX already knows as a duplicate, and it is broad: "A relationship includes any earlier lead, account or email correspondence between SourceX and the company, however it began." Section 2 runs the other way once an introduction exists: "SourceX may communicate directly with a referred company without affecting valid attribution."

So a security email the founder sends before any introduction may make a later introduction a duplicate, while the same email sent after it does not touch attribution. Whether a particular message counts is SourceX's decision from its own records. The partner's position is simpler: the founder's diligence outranks the partner's credit. Offer three honest routes and let the founder pick.

1. **Read first.** The founder reads SourceX's public trust center and process pages. Nothing is sent, and the founder decides afterward.
2. **Introduce with security first on the agenda.** The founder agrees to an introduction whose first item is security, and the questions then go to SourceX directly.
3. **Write first.** The founder contacts SourceX's security team before any introduction. That is the founder's right. Mention the duplicate rule once, as your own interest, and accept the answer.

Never ask a founder to hold a question back to protect a reward. An introduction made by managing what the founder may ask is not one the founder truly agreed to, and SourceX's screening guidance counts introductions made without the decision maker's knowledge as usually not a fit.

## The security-question handoff packet

The packet is one page the partner sends the founder. It answers nothing the partner cannot answer and points to whoever can.

| Packet section | What goes in it | Where the content comes from | Who fills it in |
|---|---|---|---|
| A. The question | The founder's words, verbatim, with who asked and the date | The founder | The partner |
| B. Public now | Dated links to SourceX's trust center and process page, with the two facts that answer most early worries: no files at the first step, and nothing delivered until both agreements are signed and SourceX gives the go-ahead | SourceX's own pages | The partner, as links, not summaries |
| C. After review | Security questionnaire responses, a business continuity overview, the incident escalation process, contract templates, a DPA where applicable, and the subprocessor list on request | SourceX, privately, after review | SourceX |
| D. After applying | Which systems, records and date ranges are in scope, the processing route and how this dataset would be de-identified | SourceX's review with the company | The company and SourceX |
| E. Escalation | SourceX's security contact, or the documentation request on its trust center, where sensitive reports go only to signed-in accounts after approval | SourceX's trust center | The founder |
| F. Decline line | "Not now, please don't follow up," or any wording the founder prefers | The founder | The founder; the partner records the date and stops |
| G. The partner's role | No files, no credentials, no applicant documents reach the partner | Section 7 of the terms | The partner |

Section D is the one founders find most reassuring once they see it. SourceX's trust center leaves scope to the supplier: the company picks the systems, records and date ranges, and nothing outside them is included. A founder worried about the most sensitive system can simply leave it out.

The packet also puts verification where it belongs. The FTC's guidance for businesses that rely on service providers advises setting security expectations before hiring, writing the requirements into the contract and then checking that they are met (a paraphrase of the FTC's guide). That is work the company does with SourceX in sections C and D. A partner's reassurance in section B is not part of it. For the questions a company puts to a data buyer before delivery, SourceX's own article on [security questions before delivery](https://sourcex.si/insights/what-security-questions-to-ask-an-ai-data-buyer-before-delivery) lists them.

## Known, conditional and not yet reviewed

| Status | Statement | Basis |
|---|---|---|
| Known | No records are shared at the first step | SourceX's process page |
| Known | Nothing is delivered until the Master agreement and the deal's Confirmation are signed and SourceX gives the go-ahead | SourceX's trust center, controls in place today |
| Known | The company decides which systems, records and date ranges are in scope | SourceX's trust center |
| Known | Partners never receive applicant documents | Section 7 of the terms |
| Known | SourceX lists an audit report and two certifications as in progress, with none issued | SourceX's trust center, checked 27 October 2026 |
| Conditional | Questionnaire responses, the DPA and the incident escalation process | Shared privately after review |
| Not yet reviewed | Anything about the company's own systems | Starts only after the company applies |
| Not yet reviewed | Whether the partner considers SourceX secure | The partner has tested nothing and says so |

The audit line deserves care. It is precise and dated, and it is exactly the kind of statement that turns into "they're certified" after two retellings. Send the link rather than a summary.

## A founder who wants answers first (Illustrative)

Illustrative. An invented portfolio company; the exchange shows a method, not an outcome.

A 175-person accounts-receivable outsourcing firm sits in a fund's portfolio. After the operating partner mentions SourceX at a board dinner, the founder writes: "Before you put us in touch with anyone, I need to know how they'd handle our clients' remittance files, and whether you'd vouch for them."

The partner's reply, in full:

> Nothing of yours goes to SourceX for a first look: it's a few questions, no files. Their trust center lists what is in place today and what is still in progress, and they share questionnaire answers and contract terms privately once a company is in review. Your clients' remittance files may never be in scope, since material that belongs to clients is usually not a fit; the firm's own exception queues and procedures are the likelier conversation. I haven't tested their controls and won't vouch for them. If you'd rather ask them first, their security contact will answer you directly. If the answer is not now, say so and I'll stop.

Attached is the packet, with sections A, B and G filled in and C to F pointing to SourceX and to the founder. The founder replies that audit season comes first. The partner records the date and the reason, sets no reminder to chase, and leaves the next move with the founder.

The remittance point changed the conversation. The records the founder feared most were the ones least likely to be in scope, because material belonging to clients rarely is.

## Where an early answer goes wrong

- **Status moves.** SourceX's trust center lists planned items, such as dedicated data rooms and independent security assessments, beside current controls. A link sent today can describe a different state next quarter, so date every link.
- **De-identification is not perfect.** SourceX's trust center says so itself: the supplier agreement records that re-identification may still be possible. A partner who says "it's anonymized" has promised more than SourceX does.
- **The partner's inside knowledge.** Board materials describe a portfolio company's systems in detail. None of it becomes an answer to anyone, in either direction.
- **The credit temptation.** Section 3 gives the partner a reason to prefer route 2. Name that interest openly or not at all, and never act on it by steering the founder.
- **The real worry is elsewhere.** "Are they secure?" can stand in for an incident, a customer contract or a regulator's order. Point the founder to counsel and leave the detail with the company; [how data is secured in licensing](/proof/what-is-data-security-in-licensing) and [MSP client data licensing security](/guides/msp-client-data-licensing-security) cover the contract side, and [whether a company needs an audit report to license data](/questions/do-we-need-soc-2-to-license-data) answers the most common follow-up.

**Methods note.** The packet was assembled on 27 October 2026 from SourceX's trust center and process pages, the program's home page, its screening guidance, sections 2, 3 and 7 of the program terms and the FTC's Start with Security guide. It does not measure how often security questions delay an introduction or how founders respond to the packet; no such figures have been published. To test it, log each early security question for a quarter by tier, and count how many founders chose each route and how many declined.

## 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 the founder has the packet, has chosen a route and still wants the conversation, [register as a partner](/register), look at the company against [the screening profile](/who-qualifies) and read [the terms](/terms) on attribution and duplicates before you submit. Platform teams running this across a portfolio can start with the [overview for venture platform teams](/for/venture-platform-teams) or the step-by-step [process](/how-it-works), and the full [guide library](/guides) covers related questions.

Handing a founder a security packet is referral work; judging SourceX as a possible holding is diligence of another kind, and investors can request 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/
- https://refer.sourcex.si/who-qualifies
- https://refer.sourcex.si/terms
- https://sourcex.si/trust
- https://sourcex.si/how-it-works
- https://www.ftc.gov/business-guidance/resources/start-security-guide-business
- https://sourcex.si/investors
