# Software platform data ownership in referrals | SourceX

Canonical: https://refer.sourcex.si/guides/when-a-company-controls-its-software-but-not-its-content
Last updated: 2026-11-05

Then its software is not its dataset. Owning the code, the hosting and the admin console shows who can operate a platform, not who owns the content inside it. SourceX's published screening treats material that belongs to a company's clients as usually not a fit, so a platform company is screened on the records it created about its own work: engineering history, support playbooks, QA and operations records. Set the customer content aside, then let the CEO decide whether to talk.

This trips up portfolio teams more than any other rights question, because the platform companies in a portfolio are often the ones with the most impressive data story. Investors hear "we process millions of documents a month" and picture a dataset. Whether the company owns any of those documents is a separate fact, and funding stage never settles it.

## Two chains: who runs the software, and who owns what is in it

Every platform company sits on two chains that rarely end at the same owner.

- **The control chain** runs through the code, the hosting, the admin roles and the power to export, migrate or delete. A platform company usually holds all of it.
- **The content chain** runs through who created each record, under which contract, and what that contract says about ownership. It often ends at the customer, the user or an outside creator.

The agreements of well-known platforms state the split in plain words. Atlassian's customer agreement says that, as between the parties, the customer owns all intellectual property and other rights in Customer Data, which it defines as data, content or materials provided by or for the customer through its cloud products, while Atlassian keeps the rights in its products and technology. GitHub's terms of service say users keep ownership of the content they post and grant GitHub a license defined by those terms. In both cases the vendor runs everything and owns the software, and the content belongs to someone else.

Creators outside the payroll add a third twist. The U.S. Copyright Office's Circular 30 explains that a work is "made for hire" when an employee creates it in the course of the job, or when a commissioned work falls into one of nine statutory categories and both sides sign a written agreement saying so. A freelancer's article that meets neither test is not automatically the commissioning company's. A publisher can run the content management system, the site and the audience, and still not own a large share of its archive.

## Pin down the operating entity, and who controls it now

Before sorting records, settle which company you are screening and who speaks for it.

1. **Which entity owns the platform, and which entity employs the people who created the records?** In a group these can differ. The records that matter here are created by employees, so follow the payroll.
2. **Has control changed?** An acquisition can leave inherited systems administered by one entity while the content still belongs to the customers of another; the [tenant control versus data ownership worksheet](/guides/post-merger-tenant-data-ownership-referral) traces that case. In an insolvency, control of software accounts follows legal authority, as SourceX's article on [who controls company software accounts in an ABC, receivership or bankruptcy](https://sourcex.si/insights/who-controls-company-software-accounts-in-an-abc-receivership-or-bankruptcy) sets out.
3. **Who authorizes?** The CEO of the operating company authorizes a licensing discussion and signs for it. A fund's board seat or majority stake does not make the fund the decision-maker.

## Platform-versus-content owner examples (Illustrative)

Six invented companies, each with at least 50 full-time employees at peak and years of operation. The fourth column is what a screen looks at; the third is what it sets aside.

| Case (Illustrative) | What the company controls | Whose content flows through it | Records it likely created itself | Screening call |
|---|---|---|---|---|
| 1. 280-person vertical SaaS for property managers | Code, hosting, admin console | Leases, work orders and tenant messages, owned by its customers under the subscription agreement | Engineering issues and code reviews, incident reviews, internal support playbooks | Screen its own records; customer tenants are out of scope |
| 2. 150-person marketplace for freelance designers | Platform, matching rules, moderation tools | Portfolios and messages posted by users, who keep ownership | Trust and safety policies, moderation guidelines, product specifications | Route: moderation logs that quote user posts need rights review |
| 3. 400-person contact center running client helpdesks in the clients' software | Neither the software nor the tickets | Tickets and calls inside the clients' own systems | QA rubrics, training curricula, staffing and scheduling records | Screen its own training and QA material only |
| 4. 90-person trade publisher | Its content management system and website | Articles by staff, and by freelancers who signed no written assignment | Staff-written archive, style guides, editorial workflow records | Screen staff work and process records; the freelance archive needs rights review |
| 5. 220-person managed IT provider | Its monitoring and ticketing tools | Client environments and client data | Runbooks, change procedures, its own service desk process | Route: tickets that describe client systems are client-confidential |
| 6. 120-person document-processing SaaS for insurers | Extraction models and processing pipeline | Policyholder documents processed inside insurers' tenants | Two years of sparse engineering notes | Stop |

**Case 6 is the rejected example.** Everything impressive about it, the document volumes, the accuracy figures, the customer logos, sits in the customers' column. The documents belong to insurers and describe their policyholders, which makes them client-owned material and personal data at once. What the company created itself is a thin, two-year set of engineering notes. On today's published criteria there is nothing to introduce, so the platform team records "stop: content owned by customers; own records too thin" and does not raise licensing with the CEO. A warm board relationship does not change who owns a policyholder's file.

Case 3 is the mirror image and the reason software ownership is not a fit test. The contact center owns none of the platforms it works in, yet years of its own QA rubrics, training material and staffing records were written by its employees about its own work. That can be a strong company to introduce. For the general version of this distinction outside platforms, see [company data versus data owned by its customers](/guides/how-to-distinguish-company-data-from-data-owned-by-its-customers).

## Mandate, language and history checks for a platform company

The fit facts still apply once the content question is settled, and platforms fail them in particular ways.

- **History.** A platform may be ten years old while its own engineering records start at the last tracker migration. Ask how far back the company's own records go, not when the product launched.
- **Language.** 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. A platform company based in, say, India is measured on its own records, not on its customers' content.
- **Mandate.** SourceX checks relevance to its current data needs during review, and those needs differ by data category. Engineering and support-process records are one category; a partner names them and does not guess demand.
- **Contracts.** Customer agreements can reach past customer content into aggregated or derived data. The [customer contract restrictions guide](/guides/customer-contract-data-use-restrictions) and the [aggregated-data clause guide](/guides/aggregated-data-clause-saas-agreement) show what counsel reads.

## Six questions that separate the two chains

Ask the founder, at metadata level. No contract copies, no samples, no logins.

1. "What does your standard customer agreement say about who owns customer data: you, the customer, or unsure?"
2. "Which records did your own employees create about your own work, and in which systems?"
3. "Did contractors create any of the material you would consider, and did they sign assignments?"
4. "Do the records you would consider quote or embed customer content, such as tickets that paste customer messages?"
5. "Has control of the company or its systems changed through an acquisition, merger or financing?"
6. "Has the CEO been asked whether they want a conversation about licensing?"

Answers of "unsure" to questions 1, 3 or 4 make the case a route, not a stop. They are exactly the questions SourceX's rights review and the company's counsel exist to answer.

## Sending a mixed case forward without promising anything

Most platform companies land in the middle: real records of their own, mixed in with content they do not own. Describe them that way. The relationship owner tells the CEO that the conversation would be about the company's own engineering, support and operations records, that customer content stays out, and that SourceX and the company's counsel review rights before anything is agreed. Never call it "your platform data", and never imply that customer content can be licensed with enough paperwork. Only a partner who has signed the SourceX Channel Partner Agreement submits the introduction, after the CEO agrees. The [software and SaaS industry page](/industries/software-and-saas) covers what platform companies typically hold.

## Where the platform-content line is harder than it looks

- **Contracts differ.** Some customer agreements give the vendor rights in aggregated or de-identified data; others forbid any reuse. A screen cannot tell which, and a founder's memory of the template is not the signed version.
- **Copyright edges.** The work-for-hire categories in Circular 30 are narrow, and whether some other signed agreement covers a freelancer's work is a question only the paperwork answers. A freelance archive may be cleaner, or messier, than the founder thinks.
- **Embedded content.** Records the company created often quote what it does not own: a support ticket written by staff can paste a customer's message. Volume estimates shrink once that is filtered out.
- **Control can move.** Acquisitions and insolvencies change who administers systems, and with them who can produce records at all.
- **Demand.** A company's own records may simply not match a current program. SourceX checks relevance in review, and a clean case can still be declined.

**How the examples were built.** Each case applies SourceX's published criteria (who-qualifies page updated 20 Oct 2026; program terms Version 2026-10-22.2, since replaced by version 2026-11-04) to an invented company, using the ownership splits stated in Atlassian's customer agreement, GitHub's terms of service and Copyright Office Circular 30, all read on 26 Oct 2026. No real contract was reviewed. The cases measure nothing about demand, volumes or acceptance rates, which SourceX has not published. The [overview for venture platform teams](/for/venture-platform-teams) places this screen in the wider portfolio workflow.

## 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 platform company's own records clear the screen and its CEO wants the conversation, [register for a partner link](/register), compare the case with [who qualifies](/who-qualifies) and read the [program terms](/terms) before the relationship owner makes the ask.

Some readers look at platform economics as prospective investors in SourceX itself. That is a different decision from introducing a company, and those readers can ask for investor materials via 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/terms
- https://refer.sourcex.si/who-qualifies
- https://www.atlassian.com/legal/atlassian-customer-agreement
- https://docs.github.com/en/site-policy/github-terms/github-terms-of-service
- https://www.copyright.gov/circs/circ30.pdf
- https://sourcex.si/investors
