# Route a customer's data rights question | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-route-a-customer-s-data-rights-question-to-their-own-team
Last updated: 2026-11-05

Route it; don't answer it. When a customer asks whether it can license its records for AI training, a SaaS vendor's partner team should send each part of the question to the person at the customer who owns it: the CEO for whether to explore licensing at all, counsel for contracts and rights, the system administrator for what exists. The vendor answers only questions about itself, such as its export documentation and its own data use, and introduces the CEO to SourceX only when the customer asks.

The reason is structural. The vendor holds the customer's records under a service contract, may earn a referral reward if a license completes and has no authority over the customer's decision. Answering for the customer would blur all three.

## Why the vendor should hand the question back

Access is not authority. Hosting, supporting and backing up a customer's records gives a vendor technical reach, not a say in what the customer does with them. Where the records include personal data and the customer is the controller, the GDPR makes that division explicit: Article 28(3)(a) requires the processor's contract to stipulate that it processes personal data only on documented instructions from the controller. A vendor that started steering the customer's licensing decision would be acting well outside that role.

The vendor's own promises point the same way. In February 2024, FTC staff wrote that it may be unfair or deceptive for a company to adopt more permissive data practices, such as using data for AI training, and tell consumers only through a surreptitious, retroactive change to its terms. That post concerns a company's own data use, not a customer's license, but it is a good reason to keep the two visibly apart: the vendor's data practices are governed by its terms, and the customer's licensing decision belongs to the customer.

Then there is money. If the partner team is registered as a SourceX referral partner, it may be paid when a license completes. The FTC's Endorsement Guides treat the possibility of being paid as a material connection that must be disclosed clearly and conspicuously when the audience would not expect it. Few customers expect their software vendor to be paid for a recommendation.

## The customer benefit, and who can say yes

The benefit is the customer's, not the vendor's: a customer company may license its own operating records directly to SourceX and be paid under its own agreement. That benefit exists only if the company could qualify: it reached 50 or more full-time employees at peak, contractors not counted; its operating history is documented; it holds the rights to license; and an authorized contact can speak for it. If a 30-person customer asks, the honest answer is that the program does not fit today.

The person who raises the question is rarely the person who decides. It is usually an administrator, an operations leader or a finance lead who noticed years of history in the product. Treat that person as the internal sponsor. The CEO authorizes a licensing discussion and signs for the company, so the routing ends at the CEO, and SourceX's own screening guidance treats an introduction made without the decision maker's knowledge as usually not a fit.

## The owner-led question routing guide

One rule runs through the guide: the vendor answers questions about the vendor, and every question about the customer's records, contracts or decision goes back to the customer.

| Customer question | Who answers at the customer | What the vendor may offer | What the vendor never does |
|---|---|---|---|
| 1. Can we license our data for AI training? | The CEO decides whether to explore; SourceX's review decides fit | Say the decision is theirs; offer an introduction if the CEO wants one | Say yes, no or "probably" |
| 2. Does our contract with you allow this? | Counsel, reading the subscription agreement and any data processing addendum | Point to the relevant clauses and published export documentation | Interpret the contract for them |
| 3. What do we have in your product, and since when? | The system administrator, from the admin console or export tools | Share export documentation and published retention settings | Run exports, pull samples or browse records for this purpose |
| 4. Are records about our own customers ours to license? | Counsel, then SourceX's rights review | Nothing beyond routing | Give an opinion on third-party rights |
| 5. Do you use our data to train AI? | The vendor: this one is about the vendor | A straight answer from current terms, privacy policy and addendum | Answer from memory or change terms quietly |
| 6. Would you be paid if we go ahead? | The vendor | Disclose the referral relationship and that any reward is paid by SourceX, never from the customer's payout | Hide or play down the connection |
| 7. Who do we talk to at SourceX? | The company applies itself, with the CEO's knowledge | A partner-link introduction addressed to the CEO | Submit customer details without consent, or send any records |

Log each question by number, the date, who at the customer received it and what happened next. The log is the evidence that the vendor routed rather than answered, and it becomes the measure for the pilot below.

**Method note.** The guide was built from SourceX's program terms (Version 2026-10-22.2, since replaced by version 2026-11-04) and screening page, GDPR Article 28 and FTC guidance, all checked 2026-10-26. It assigns questions to owners; it does not assess any particular contract, and it is general information, not legal advice. For the contract questions in rows 2 and 4, the customer's counsel decides; [whether SaaS terms let a customer take its data out](/guides/saas-data-export-rights-contract) is a useful starting read for them.

## Three data layers in one product, and whose decision each is

Three kinds of data sit in the same product, and only one of them is the customer's to discuss licensing.

| Layer | Examples | Whose decision | Place in an introduction |
|---|---|---|---|
| Customer content | Tickets, CRM records, project histories the customer's staff created | The customer, through its CEO and counsel | The possible subject of the customer's own license; the vendor never moves it |
| Personal data inside that content | Names, emails, call notes about individuals | The customer as controller; the vendor processes on documented instructions | Handled in SourceX's rights and privacy review with the customer |
| Vendor product analytics | Usage events, feature telemetry, performance logs | The vendor, within its own terms and promises | Not part of the customer's question at all |
| The introduction itself | A partner link and one disclosed email | The vendor | The only thing the vendor contributes |

Ownership in SaaS is set by the actual agreement, which is why the answers in [who owns data in SaaS tools](/questions/who-owns-data-in-saas) and [whether a SaaS company can license customer data](/questions/saas-customer-data-ai-training-rights) both start with the contract. A customer worried about the vendor's own AI use can work through [whether its SaaS vendor is training AI on its data](/questions/is-my-saas-vendor-training-ai-on-my-data); the vendor answers that one directly, under row 5.

Co-sell programs already treat customer contacts this way. Microsoft's Partner Center documentation says customer contact details are needed only when a partner invites Microsoft sales to help, and tells partners to get the customer's consent before sharing them, because Microsoft may contact the customer directly. An introduction to a data licensing counterparty deserves at least the same consent.

## Three questions routed (Illustrative)

Illustrative. Generic companies and invented facts.

**An owner-led yes.** A 230-person property management company asks its maintenance-ticketing vendor whether its 12 years of work orders could be licensed. The account manager logs it as row 1, tells the operations director that the decision is the company's, links the published export documentation (row 3) and asks whether the CEO would like an introduction. The CEO says yes. The partner manager, who has signed the SourceX Channel Partner Agreement, sends the partner link with a one-line disclosure (row 6). The vendor's part ends there.

**An intermediary and a rights question.** A 140-person accounting firm's IT director asks the same of its document-management vendor. Most stored documents are client files, which SourceX's screening guidance treats as usually not a fit. The vendor routes row 4 to the firm's counsel and row 1 to its CEO, and mentions nothing else. If the firm has its own methodology guides and review notes, the CEO can raise them with SourceX directly; the IT director remains the internal sponsor.

**A no-fit counterexample.** A 30-person design studio asks. Its peak full-time headcount is below 50 and much of its work product belongs to clients. The vendor answers honestly that the program does not fit today, makes no introduction and records the question in the log.

## Pilot the routing guide with customers who raise the topic

Run a small, opt-in pilot before announcing anything widely.

1. **Opt-in only.** Respond to customers who raise the topic. If you send anything proactive, make it one neutral, disclosed note to administrators, with no follow-up sequence.
2. **No lists.** Never pass customer names, usage figures or account data to SourceX. Only a CEO who has agreed to a conversation is introduced.
3. **Disclose first.** Put the referral relationship in the first message, not in a footer.
4. **Log everything.** Use the seven question numbers above.
5. **Stop on a complaint.** Any complaint that the vendor overstepped pauses the pilot until it is reviewed.

Measure five things over the pilot: questions received, questions by routing row, CEO-requested introductions, complaints or opt-outs, and answers to two feedback questions (was the routing clear, and did the vendor stay out of the decision). SourceX has not published figures from any SaaS partner pilot, so these are measures to collect, not benchmarks to hit.

## What stays unknown until SourceX reviews it

Introduced companies need 50+ full-time employees at peak, documented operating history, rights to license and an authorized contact. 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. Whether the customer's contracts allow licensing, whether its records match current demand and what a license would cover are settled only in SourceX's review and the customer's own agreement. The vendor never sees, prepares or delivers the records.

Rewards follow the program terms. Illustrative: if SourceX pays the customer USD 100,000 of Actual Supplier Payout, the partner's reward is USD 55,000; at USD 800,000 it is USD 120,000, because 15% is then worth more than USD 50,000 plus 5%. There is no cap. The reward is paid separately by SourceX and is never deducted from the customer's payout. SourceX pays the reward within 60 calendar days of whichever comes later: completed handoff, or final written acceptance of the complete, validated dataset by the Acquisition Partner; other conditions in the terms apply. More software-sector material sits on the [software and SaaS industry page](/industries/software-and-saas) and in the [guides library](/guides).

## 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 customer's CEO asks to be introduced after the routing is done, [register for a partner link](/register), confirm the company against [who qualifies](/who-qualifies), read the [program terms](/terms), and use the [FTC disclosure examples](/resources/ftc-disclosure-examples-referral) for the first message.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://eur-lex.europa.eu/eli/reg/2016/679/art_28/oj
- https://www.ftc.gov/policy/advocacy-research/tech-at-ftc/2024/02/ai-other-companies-quietly-changing-your-terms-service-could-be-unfair-or-deceptive
- https://www.ecfr.gov/current/title-16/chapter-I/subchapter-B/part-255/section-255.5
- https://learn.microsoft.com/en-us/partner-center/referrals/manage-co-sell-opportunities
