Industries
Software and SaaS: what your operating records are worth to AI research
A software company's unit of work is the ticket, pull request or account change its people close every day. Those records show how a product is built and supported. A license can cover that workflow history only after names, customer details and secrets are removed. A software company still has to pass the fit check.
Up to $150K · $0 cost · 3 days
| Fact | Detail |
|---|---|
| Unit of work | ticket, pull request, or account change |
| First exclusion | end-user account identifiers |
| First rule | The U.S. Copyright Office says copyright protects original works of authorship, including computer software. Copyright does not protect facts, ideas, systems, or methods of operation, although it may protect the way these things are expressed. The same office says copyright law does not protect domain names. U.S. Copyright Office |
| Second rule | Title 17 of the United States Code defines a computer program as a set of statements or instructions to be used directly or indirectly in a computer in order to bring about a certain result. govinfo |
What Software and SaaS operating records look like
Software and SaaS operating records are the ticket, pull request, or account change a team closes, and they are not the customer's login or password.
Reproducing a bug from a ticket shows the steps a person took, the build they named, and how the bug was closed. Reviewing and merging a change shows who approved the diff and what the review asked to fix. Those two trails are the product's working memory. Customer logins, payment profiles, and the text of a private support thread are a different store. A license can talk about the workflow. It does not take the account.
Other sectors are grouped under company data licensing by industry.
The license itself is explained in how to sell company data to AI companies.
Workflows in Software and SaaS that AI research can learn from
AI research can learn how a software team reproduces a bug from a ticket, pull request, or account change, which are three different trails.
- reproducing a bug from a ticket
- reviewing and merging a change
- answering an account escalation
The full history matters because a single merged change, read alone, hides the failed attempts and the rollback. Answering an account escalation is a third trail: the handoff from support into engineering, with the customer's identity already removed. Together they show how a product is run, not who the user is.
For a related sector's records, read fintech company data for AI research or education company data for AI research.
Systems Software and SaaS companies usually run
GitHub, Jira, and Slack are the usual homes of that ticket, pull request, or account change, and each linked system has its own deletion write-up.
Google Workspace often holds the spec and the customer note that sparked the ticket. The table names the system and why that sector's work sits there. A tool with no deletion write-up is still listed, as plain text, so the inventory is honest.
| System | Category | Why it holds this sector's work |
|---|---|---|
| GitHub | Anything else | Pull requests, review comments, and the merge live in the repository. |
| Jira | Project or workflow | Bugs, tasks, and account escalations are tracked as tickets. |
| Slack | Chat | The engineering conversation around a change often starts in chat. |
| Google Workspace | Email and collaboration | Specs and the note that opened a ticket often sit in shared docs. |
What a Software and SaaS license leaves out
End-user account identifiers, customer support personal details, and passwords, keys, and secrets never leave in a license, even when the ticket text looks harmless.
- end-user account identifiers
- customer support personal details
- passwords, keys, and secrets
End-user account identifiers include the login, the user id, and the email on the account. Customer support personal details include the name and phone in the thread. Passwords, keys, and secrets include tokens pasted into a ticket by mistake. Taking those out does not make the company eligible on its own.
The details that never leave any company are listed in what is never shared.
Rules cited for Software and SaaS records
Any note about a ticket, pull request, or account change is a description of a public source, not a statement that a software license meets that rule.
Software has no single federal statute that defines a ticket or a pull request. The notes quote the Copyright Office, the copyright statute, the trade-secret definition, the Export Administration Regulations, and the disclosure rule for a service offered to the public. They describe those sources. They do not say a software company qualifies.
| Rule | What the source says | Source |
|---|---|---|
| What Does Copyright Protect? | The U.S. Copyright Office says copyright protects original works of authorship, including computer software. Copyright does not protect facts, ideas, systems, or methods of operation, although it may protect the way these things are expressed. The same office says copyright law does not protect domain names. | U.S. Copyright Office |
| 17 U.S.C. 101 — Definitions | Title 17 of the United States Code defines a computer program as a set of statements or instructions to be used directly or indirectly in a computer in order to bring about a certain result. | govinfo |
| 17 U.S.C. 117 — Limitations on exclusive rights: Computer programs | Section 117 of the Copyright Act says it is not an infringement for the owner of a copy of a computer program to make another copy or adaptation for archival purposes only, if all archival copies are destroyed when continued possession of the program ceases to be rightful. An exact copy prepared under that section may be leased, sold, or otherwise transferred only as part of the lease, sale, or other transfer of all rights in the program. | govinfo |
| 18 U.S.C. 1839 — Definitions | Under 18 U.S.C. 1839, a trade secret includes programs or codes, whether tangible or intangible, if the owner has taken reasonable measures to keep the information secret and the information derives independent economic value from not being generally known to, and not being readily ascertainable through proper means by, another person who can obtain economic value from its disclosure or use. | govinfo |
| 15 CFR 772.1 — Definitions of terms as used in the Export Administration Regulations | Section 772.1 of the Export Administration Regulations defines software, for terms as used in those regulations, as a collection of one or more programs or microprograms fixed in any tangible medium of expression. The same section defines source code as a convenient expression of one or more processes that may be turned by a programming system into equipment executable form. | eCFR |
| 18 U.S.C. 2702 — Voluntary disclosure of customer communications or records | Except as 18 U.S.C. 2702 provides, a person or entity providing an electronic communication service to the public shall not knowingly divulge the contents of a communication while in electronic storage by that service. A provider of remote computing service to the public shall not knowingly divulge the contents of a communication carried or maintained on that service for a subscriber or customer in the circumstances that section describes. The section allows disclosure with the lawful consent of the originator, an addressee, or an intended recipient, or of the subscriber in the case of remote computing service. | govinfo |
Wind-down specifics for Software and SaaS
Before a software company closes its cloud account, the trail that matters is the export of each ticket, pull request, or account change, not a copy of user passwords.
Canceling the host does not describe how the product was built. Export the tracker and the repository while the account still opens. Leave access tokens and user passwords out of the bundle. A spreadsheet of seat counts is not a substitute for the ticket history.
- Export the ticket history and the repository before the cloud account closes.
- Leave passwords and access tokens out of that export.
- A canceled subscription does not by itself describe how the product was built.
General information only. This is not legal, tax or financial advice.
Related
- Industries
What operating records look like by sector, and what is left out.
- How to sell company data
How to sell or license company data to AI companies, and which route fits.
- What's shared
Which records can be licensed, which details never leave, and what you approve.
- Eligibility
Staff, records, daily-use systems, and the right to license, plus a checker.
- Estimate
US payout bands by staff at peak, and the estimator that uses them.
- Fintech
Payment and credit decisions, with card numbers left out.
- Education
Course runs, with named student records left out.
Questions about software and SaaS company data for AI research
Which end-user account identifiers never leave a software company in a license?
End-user account identifiers never leave a software company in a license. That means the login, the user id, and the email on the account. Customer support personal details and passwords, keys, and secrets stay out with them, including a token someone pasted into a ticket. The ticket, pull request, or account change can remain as workflow history after those fields are removed. Removing them does not by itself mean the company qualifies.
Is a ticket or pull request the record a software company would license?
Yes. The unit of work is the ticket, pull request, or account change a team closes. Reproducing a bug from a ticket, reviewing and merging a change, and answering an account escalation are the three trails. A license can cover that workflow history only after names, customer details, and secrets are removed. The customer's login is not the record. The fit check still decides whether the company qualifies.
Which system write-ups should a SaaS company open before it cancels?
Open the deletion write-ups for GitHub, Jira, Slack, and Google Workspace before you cancel them. GitHub holds the pull request and the merge. Jira holds the ticket and the account escalation. Slack holds the engineering thread. Google Workspace holds the spec that opened the ticket. Export the tracker and the repository while the accounts still open, and leave access tokens and user passwords out of the bundle.
Does shipping software make the company eligible on its own?
No. Shipping software does not replace the staff and records rules. A software company still has to pass the fit check. The write-up describes the ticket, pull request, or account change. It does not say the company qualifies, and it does not price the history. Secrets and end-user account identifiers stay out even when the company asks to include them.
Sources
- U.S. Copyright Office. What Does Copyright Protect?. Checked 2026-11-04
- govinfo. 17 U.S.C. 101 — Definitions. Checked 2026-11-04
- govinfo. 17 U.S.C. 117 — Limitations on exclusive rights: Computer programs. Checked 2026-11-04
- govinfo. 18 U.S.C. 1839 — Definitions. Checked 2026-11-04
- eCFR. 15 CFR 772.1 — Definitions of terms as used in the Export Administration Regulations. Checked 2026-11-04
- govinfo. 18 U.S.C. 2702 — Voluntary disclosure of customer communications or records. Checked 2026-11-04