AI data asset · anonymous listing
#912
- Potential data value
- Assessment available after diligence
- Licensing readiness
- REVIEW REQUIRED
- Preferred structure
- Non-exclusive, de-identified derivatives
Seller identity is never disclosed at this stage. Introduction requires buyer qualification, seller approval and executed confidentiality.
- Industry
- SaaS
- Region
- European Union
- Company size
- 100–500 employees
- Years operating
- 9+
- Historical data
- 7 years
- Estimated records
- 1.1M+ tickets, issues and deploys
- ERP
- NetSuite
- CRM
- HubSpot
- Approx. employees
- 260
- Support Tickets
- Engineering Workflows
- Customer Relationships
- Tier-1 to tier-3 escalation
- Bug triage to release
- Incident response
- Renewal risk escalation
Cross-system connectivity
Zendesk → Jira → GitHub → Snowflake
Volume
Over a million linked tickets, issues and deploys.
92
weight 12
Historical depth
Seven years, with a support-platform migration in year three.
74
weight 12
Workflow complexity
Escalation paths are well structured but shallow.
72
weight 12
Cross-system connectivity
Ticket-to-issue-to-commit chains are traceable.
90
weight 11
Uniqueness
Support corpora are comparatively well represented.
64
weight 10
Data quality
Consistent taxonomy since the migration.
88
weight 9
Outcome labels
Resolution, reopen and satisfaction outcomes present.
90
weight 9
Industry value
Steady demand for support and coding agent evaluation.
78
weight 8
AI-agent relevance
Ticket-to-code resolution is a canonical agent task.
86
weight 8
Licensing readiness
Customer contracts need confidentiality review.
66
weight 5
Privacy / de-identification complexity
GDPR scope; customer contacts in ticket bodies.
58
weight 4
Why this asset scored 79
Strong linkage is the defining feature here: a customer report can be followed to the issue and the commit that resolved it, which is exactly the chain coding and support agents are evaluated against. Uniqueness is the largest deduction, since support corpora are comparatively well represented on the open market, and GDPR scope adds de-identification work on customer contacts inside ticket bodies.
- •Support deflection
- •Vertical AI agents
- •Evaluation benchmarks
Ownership
Company-owned tenants.
Source systems
Zendesk, Jira, GitHub, Snowflake.
Third-party data
Customer-submitted attachments present.
Customer / client data
Business contact data in ticket bodies.
Employee data
Agent and engineer identities.
Potential PII
GDPR-scope personal data.
Contract restrictions
Customer MSAs include confidentiality terms.
Licensing permissions
Pending rights review.
Retention period
Seven years retained.
Geographic restrictions
EU processing preferred.
Intended AI use
No customer-identifiable outputs.
De-identification requirements
Contact and attachment scrubbing.
Status indicators reflect seller-reported information and SentryRights screening only. No asset is represented as legally licensable until rights and privacy diligence is completed with the seller and, where applicable, its counsel.
Demo data — illustrative sample listings, not live marketplace records
- Volume
- HIGH
- Historical depth
- MODERATE
- Workflow complexity
- MODERATE
- Cross-system connectivity
- HIGH
- Industry uniqueness
- MODERATE
- Data quality
- HIGH
- Outcome labels
- HIGH
- PII risk
- MODERATE
- De-identification difficulty
- MODERATE
- Licensing readiness
- REVIEW REQUIRED
- 1
Buyer submits request
Identity, funding stage and entity are verified before the request moves.
- 2
Buyer provides intended use
Specific model, application and downstream distribution limits stated in writing.
- 3
Platform reviews buyer
SentryRights qualifies the buyer and screens the intended use against seller preferences.
- 4
Seller receives request
Seller sees the buyer profile and intended use while remaining anonymous.
- 5
Seller approves or declines
No identity is disclosed without an explicit seller approval.
- 6
NDA / confidentiality
Mutual confidentiality executed through the platform.
- 7
Identity revealed
Counterparties are introduced only at this point.
- 8
Data diligence begins
Rights review, privacy review and de-identification are coordinated by SentryRights.