Workflow logs · SaaS
License a SaaS company's workflow logs for AI training
A software company holds two kinds of logs: records of its own staff operating the business, and records of customers using the product. The first kind is far easier to license. Outrich Data is a direct buyer that separates them, checks customer terms on usage data, removes identifiers and pays through escrow.
The records at this intersection
Internal operations at a software company leave detailed traces. Support staff work through admin consoles to issue refunds, reset access and change plans. Engineers follow runbooks during an incident, and the deploy system records each release and rollback. Finance approves credits. Each action is logged with the tool, the step and the result.
Product telemetry is the other body of logs: events generated when customers click, call the API or run jobs. It is larger, and it is mostly the customer's activity under the customer's contract. Treating the two as one dataset is the common mistake at this intersection.
A worked example
Consider a billing software company whose support team resolves most requests through an internal admin tool. Every session is logged: the ticket that prompted it, the screens visited, the actions taken and the final state.
The dataset is built from those sessions. Account identifiers are replaced with pseudonyms, staff with roles and amounts with bands. Each session is joined to the category of the originating request, so a lab sees a task, the steps a trained person took and the outcome. Product telemetry is left out because the customer agreement permits internal use of usage data only. Incident runbook executions are added after the security lead reviews them.
The example is illustrative. It does not describe a completed transaction.
Rules that bite here
What the title search looks at.
- Usage data clauses in customer agreements
- Many SaaS contracts let the vendor use aggregated or de-identified usage data to improve its services. Fewer extend that to licensing it to third parties. The wording decides whether product telemetry can be in scope at all.
- GDPR and online identifiers
- User IDs, IP addresses and device identifiers are personal data under GDPR. Event logs keyed to them remain personal data until those links are broken in a way that prevents re-identification.
- CCPA service provider limits
- When you process end-user data as a service provider, California law and your contract confine you to the stated business purposes. Licensing identifiable event data would fall outside them.
- Audit log commitments
- Security exhibits and SOC 2 descriptions often promise that audit logs are retained and access-controlled. An export should follow your own access procedure and leave the retained logs untouched.
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 account IDs, workspace names and user identifiers
- IP addresses, device identifiers and session tokens
- Request and response payloads containing customer content
- Staff usernames, replaced with role pseudonyms
- Internal hostnames, URLs and credentials in command logs
- Telemetry from customers whose agreements do not allow it
- Security event logs and anything describing a live weakness
Value
What raises or lowers the value.
| Factor | Effect on value |
|---|---|
| Task-level sessions | Logs that tie a sequence of actions to a stated goal and a result are worth more than raw event streams. |
| Cross-system traces | Sessions spanning several internal tools show the kind of work agents are being built to do. |
| Internal versus customer data | Operations logs generated by your own staff are easier to clear than customer telemetry. |
| Schema documentation | Event definitions that explain each action make the logs usable without guesswork. |
Related combinations
Questions
Workflow logs in saas: what companies ask.
Can we license product analytics events?
Why are internal admin logs valuable?
Are application error logs useful?
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.