Skip to content
Outrich Data

Support tickets · SaaS

License SaaS support tickets for AI training

A software company can often license its support tickets when its customer agreements allow use of de-identified data. Outrich Data is a direct buyer that reads your DPAs and terms, removes customer identities, logs and credentials from each ticket, and pays through escrow. Tickets from customers whose contracts forbid it are excluded.

The records at this intersection

SaaS support tickets are technical. Customers paste error messages, stack traces, API requests and configuration files. Agents reply with diagnostic steps, and hard cases escalate to engineering through a linked bug. The ticket closes with a fix, a workaround or a product change.

That makes them different from consumer support. A single ticket can hold a reproduction, a root cause and a verified resolution for a real software problem. The same ticket can also hold a customer's API key, a sample of their end users' data and a confidential description of what they are building.

A worked example

Think of a developer tools company with years of tickets across a self-serve tier and an enterprise tier. The title search finds that the self-serve terms permit use of de-identified data, while a group of enterprise contracts prohibit any secondary use.

The enterprise accounts in that group are filtered out by account ID before anything else happens. In the remaining tickets, keys and tokens are detected and replaced, customer names become placeholders, and pasted payloads are reduced to their structure. Each ticket keeps its category, its internal notes, the linked bug status and whether the customer confirmed the fix.

The example is illustrative. It does not describe a completed transaction.

Rules that bite here

What the title search looks at.

Data processing agreements
For content a customer submits, a SaaS vendor usually acts as a processor under GDPR Article 28 and may only process it on the customer's instructions. Many DPAs carve out de-identified or aggregated data. Some do not. Each agreement has to be read.
Confidentiality clauses
Master agreements and NDAs commonly treat the customer's technical information as confidential. De-identification removes who the customer is. Counsel should confirm that is enough under your wording.
CCPA service provider terms
When you are a service provider under California law, your contract limits you to the business purposes it lists. Using customer personal information for another purpose can break that status.
SOC 2 and security commitments
A SOC 2 report is an attestation, not a law, but your trust page and security exhibits make promises about how customer data is handled. The licensing plan should be consistent with them.

This page is general information, not legal advice. Whether your company can license a given dataset depends on your contracts, your privacy notices and the law where you and your customers are. Review it with your own counsel before signing anything.

Removed before licensing

What comes out first.

  • Customer company names, domains, workspace IDs and account numbers
  • Requester names, emails and signatures
  • API keys, tokens, passwords and connection strings
  • Pasted logs and payloads containing end-user personal data
  • Screenshots and attachments
  • Descriptions of a customer's unreleased product or internal architecture
  • Tickets from customers whose agreements prohibit secondary use

Value

What raises or lowers the value.

FactorEffect on value
Verified resolutionsTickets where the customer confirmed the fix, or a linked bug was closed, are generally worth more.
Technical depthDeveloper-facing products produce diagnostic conversations that are scarce in public data.
Contract coverageThe share of customers whose terms allow de-identified use sets the size of the dataset.
Link to engineeringTickets joined to the bug tracker show the path from report to code change.

Questions

Support tickets in saas: what companies ask.

Our DPA says we only process data on customer instructions. Is that the end of it?
Not always. Many agreements separately permit the vendor to create and use de-identified or aggregated data. If yours do not, the options are customer consent or an amendment. The title search reports this customer by customer.
What happens to API keys customers pasted into tickets?
They are detected and replaced before packaging, whether or not they are still valid. A sample is then reviewed by a person, because pattern matching can miss unusual formats.
Can we include tickets from free users?
Often, yes. Free and self-serve users accept your standard terms, which you control and can read in one place. Whether those terms cover this use is the first thing checked.

Find out if your data qualifies.

Eleven questions, about five minutes, no call required. You get an answer on screen and a written follow-up.

esc