Skip to content
Outrich Data

Email and chat · SaaS

License a SaaS company's internal chat and email for AI training

A software company's internal chat is a record of engineering and operations work that AI labs value. Outrich Data is a direct buyer that licenses public channel history and role-based mailboxes, checks employee notice and customer terms, and removes direct messages, shared customer channels and secrets. Payment is funded into escrow first.

The records at this intersection

Software companies work in chat. Incidents are run in a dedicated channel from first alert to all-clear. Deployments are announced and rolled back in the open. Support engineers ask product engineers how a feature behaves. Sales engineers ask whether an integration is possible. Product decisions are argued in threads.

This is the most technical workplace conversation there is, and it comes with links to the systems being discussed. It also comes with three complications found together in this industry: staff spread across states and countries, customers present inside shared channels, and credentials pasted into messages during a rushed fix.

A worked example

Consider a cloud software company that has used the same chat workspace since its early days. It has incident channels, a busy engineering help channel and many shared channels with customers.

The export is limited to public channels. Shared channels are identified by their external membership and dropped. Channels for the company's European office are left out on counsel's advice. In the rest, credentials are detected and replaced, employee handles become consistent pseudonyms with a role, and customer names become placeholders. Incident threads keep their order and timestamps, so the sequence from alert to resolution can still be followed.

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

Rules that bite here

What the title search looks at.

Employee monitoring and notice laws
Several states require employers to tell staff about electronic monitoring. New York, Connecticut and Delaware have notice statutes. A written policy that work messages are company records is the usual foundation. Review coverage for every state where staff work.
GDPR for staff outside the US
Messages written by employees in the EU or UK are personal data. Reusing them for a new purpose needs a lawful basis and may call for consultation with employee representatives. Many companies exclude those staff or those channels.
Customer agreements
Shared channels and support threads carry customer confidential information. NDAs, master agreements and DPAs govern it, so shared channels are excluded and customer names are removed elsewhere.
Stored communications
Only communications held on systems the company controls, under policies that cover them, are in scope. Personal accounts and personal devices are not.

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.

  • Direct messages and private channels
  • Shared channels with customers, partners and vendors
  • Customer names, account IDs and quoted customer messages
  • Tokens, passwords and connection strings
  • Employee names, handles and @mentions
  • HR, legal, security disclosure and compensation channels
  • Channels dominated by staff in jurisdictions that are not cleared

Value

What raises or lowers the value.

FactorEffect on value
Incident historyComplete incident threads with a resolution are generally the most sought-after part.
Threaded discussionTeams that reply in threads produce cleaner units than teams that talk in a flat stream.
Notice coverageA clear, long-standing policy on work communications makes more of the history clear to license.
Customer presenceThe more work happens in shared channels, the smaller the licensable set.

Publicly reported deals for context

  • Closed startups and AI labs, workspace data (chat, docs): About $15,000. MIT Technology Review 2026-10-13

Reported by the sources linked. These are other parties' deals, not offers, and not a prediction of what your data is worth.

Questions

Email and chat in saas: what companies ask.

Do we need employee consent?
It depends on where staff work and what your policies say. In much of the US a clear written policy is the starting point, and some states require specific notice. For staff in Europe the position is stricter. Counsel should review before scope is set.
What about former employees' messages?
They are company records if your policy covered them at the time. They are de-identified in the same way as current staff messages. The title search checks which policy version applied during each period.
Can incident channels reveal security weaknesses?
They can. Hostnames, internal URLs and details of unresolved weaknesses are removed, and your security lead approves the rules. Postmortems about security incidents are usually excluded.

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