A solved ticket is a small, complete record of work: a problem, what was tried and how it ended. That's why support data appears on programme lists. Zendesk is also a clear case of a vendor's terms shaping how data can leave.
Where these records usually live
Help desks
- Zendesk
- Intercom
Freshdesk
ServiceNow
Examples of common tools, to help you find your records. Product names and logos belong to their owners; no affiliation or endorsement.
01What Zendesk's terms say
Two documents do different jobs.
Your ownership. The Customer Agreement says "Customer retains ownership of all Service Data" (s.3.1), and lets you export it during your subscription and for 30 days after (s.3.4), with some exceptions.
What apps can do. The Developer Terms cover anyone using Zendesk's APIs. They limit use of API data, "including creating, training, or improving any general AI model, such as, but not limited to, a large language model" (s.3.6(iii)). They also rule out apps that "allow bulk export of API Data" (s.3.6(iv)), persistent copies (s.3.6(v)), and reselling API data (s.3.3(iv)).
So it matters how tickets leave. A programme's app pulling them through the API looks like what those clauses are about. An export you run yourself is a different question, because the agreement gives you export rights, but whether it covers licensing to a third party is one for your lawyer.
- Ask the programme exactly how it would collect tickets.
- Don't approve an app connection until you've read what it can access.
- Check your own contract. Terms vary by plan and date.
02What to include, and what to leave out
03The customer problem
Every ticket involves a customer. Names and emails are easy to find, but the problem is the free text, where people mention addresses, order numbers, health issues and card details. Attachments and screenshots are worse.
- Consumer customers: see customer data.
- Business customers: check their contracts.
- If you're an outsourcer: tickets you handle for a client are probably theirs to decide on. See customer support.
04How to scope it
- Start with what's yours: macros, triggers and Help Centre articles.
- Choose solved tickets with clear outcomes, by category and date.
- Leave out sensitive categories, such as complaints, legal and billing disputes.
- Sample the free text before you agree anything. See what is a data sample?
- Plan around your contract end. If you're leaving Zendesk, the 30-day export window is short.
This isn't legal advice.
05Questions people ask
Do I own my Zendesk tickets?
Zendesk's Customer Agreement says the customer retains ownership of all Service Data. That's between you and Zendesk: a ticket can still contain someone else's confidential or personal information.
Can a data programme connect to Zendesk?
Be careful. Zendesk's Developer Terms restrict using API data for general AI models, bulk export and resale. Ask the programme how it would collect tickets.
Does Zendesk train AI on my tickets?
Read Zendesk's own AI data-use information for your plan. Its agreement says you instruct it to use Service Data to provide, secure and improve its products.
Sources
- Zendesk Developer Terms (effective 12 August 2025), checked 5 November 2026
- Zendesk Customer Agreement (effective 1 August 2025), checked 5 November 2026
- Zendesk AI Data Use Information, checked 5 November 2026
