Under the Zendesk Customer Agreement the customer retains ownership of all Service Data, and five programs name Zendesk among the systems they want (Zendesk documents read November 16, 2026; program terms checked November 9, 2026).
Zendesk is one source system in AI training data licensing, and its plans, formats and agreements decide what a company can hand over. Zendesk's own AI terms leave one question unanswered, whether Zendesk trains its own models on Service Data, and this page says so rather than guess.
DataPacts Editorial Team: how we source, date and check every figure. Zendesk documents were read on November 16, 2026; program terms were checked on November 9, 2026.
What a Zendesk Account Holds and What a License Can Cover
A Zendesk account holds tickets with their public replies and internal notes, the users and organizations behind them, and, where used, help center articles and live chat, and a license can cover any of these that the company controls.
Zendesk defines Service Data in section 12 of the Zendesk Customer Agreement as all data, text, messages, communications or other information submitted to and stored within the Services, and it excludes customer and agent account information.
The ticket is the unit buyers name. A ticket combines the requester's first message, the replies, internal notes, status fields, tags and custom fields, and the export format decides how much of that dialogue survives. AI agent tickets, which Zendesk's export article says cannot be exported, never leave the account this way at all.
Buyer demand and the value of support records are covered on the page about selling customer support tickets and chats for AI training; this page stays on Zendesk's own mechanics and terms.
Who Controls Zendesk Ticket Data in a License
Four parties shape what a company can license from Zendesk: the company as the customer that owns Service Data, Zendesk as the provider with its own use rights, app developers bound by the API terms, and the customers and agents whose words fill the tickets. Zendesk, Inc. is a Delaware corporation according to section 12 of the Customer Agreement.
The Zendesk Customer Agreement: Ownership, Use and Export Window
The Zendesk Customer Agreement, effective for new customers from August 1, 2025, states that the customer retains ownership of all Service Data. Changes took effect for existing customers on September 1, 2025. In the same section 3.1 the customer instructs Zendesk to use Service Data to "provide, secure, and improve" Zendesk's products and services.
Ownership is the starting point of the rights audit of the data to be licensed. Section 2.2(i) bars the customer from renting, leasing, selling, distributing, transferring or sublicensing the Services, but it names the Services and not Service Data.
Section 3.4 gives a right to export Service Data during the term and for 30 days after it, with exceptions for deleted, unlawfully created or legally restricted data.
Zendesk's improvement use sits beside any buyer's no-prior-grant warranty, for example section 5.1 of the micro1 Data License Master Terms (version of November 12, 2026, read November 16, 2026), which also takes an irrevocable, perpetual grant.
Whether the two collide is a question for the buyer and counsel to raise, not a conclusion this page draws.
Zendesk AI: What the AI Services Addendum Says About Service Data
Zendesk's AI Services Addendum bars LLM Providers from using Service Data for any purpose other than providing and securing the AI Services (section 3.1), and it names the customer as sole owner of AI Input and AI Output.
Section 1.2 lets the customer disable generative AI services at any time. The page shows no contractual effective date.
The documents read (the Customer Agreement, the Addendum and "How We Protect Your Service Data" of June 1, 2022) do not state whether Zendesk trains its own models on Service Data, and they describe no opt-out. Nothing more is claimed here.
Zendesk Apps and the API License Agreement
Zendesk's Application Developer and API License Agreement, effective June 3, 2025, bars apps from repackaging or reselling Service Data (section 3.3(d)) and from using it for anything other than the app's functionality without the customer's express authorization (section 5(d)).
Section 5(d)(ii) bars disclosure to third parties on the same condition, and section 3.5 applies rate limits.
These terms bind the app developer, so a connector app run by a buyer is bound by them, and the company's own export runs under the Customer Agreement. The difference is set out under buyer connectors vs native exports.
How Zendesk Tickets Leave the Account
Zendesk tickets leave an account by one of three routes: the account export in CSV, JSON or XML, the REST API, or a read-only connection run by a program. Which route fits depends on plan, ticket count and what the buyer needs from each ticket.
Table: the three routes by who runs them and what the record shows, as of November 16, 2026.
| Route | Who runs it | What the record shows | Source |
|---|---|---|---|
| Account export (CSV, JSON, XML) | account admin after the owner's enablement request | named plans only; limits per format | support.zendesk.com, read 2026-11-16 |
| REST API | the company or an app | usable on Team plan; rate limits apply, values not recorded here | support.zendesk.com; API License Agreement |
| Read-only connection or in-environment preparation | program (examples Centific, Scale AI) | read-only connection with exclusions in extraction code (Centific); anonymized before extraction (Scale AI) | centific.com, scale.com, checked 2026-11-09 |
Plans, Enablement and the Team Plan
Zendesk's export tools are available on Suite Growth, Professional, Enterprise and Enterprise Plus and on Support Professional or Enterprise, not on Team, and they stay off until the account owner asks Zendesk Customer Support to enable them. The record on those tools (checked November 9, 2026 and re-read November 16, 2026) shows three points.
- Plans: the export article lists the plans above and excludes Team.
- Enablement: exports are off by default, and the owner's request to Zendesk Customer Support gives the account subdomain.
- Team plan: customers can still use the REST API, and admins can be restricted from exporting.
Zendesk's own export tools carry no separate price on record; export apps are not reviewed here.
Formats and What Each Leaves Out
Each Zendesk export format drops something a buyer may expect, so the format decides how complete a licensed ticket archive is. The table compares the three formats, as of November 16, 2026, from Zendesk's export article.
| Format | Holds ticket comments | What it leaves out or caps | Source |
|---|---|---|---|
| CSV | no | deleted tickets, ticket comments, ticket descriptions; multi-line, multi-select and custom date fields; dates in the account's time zone | Zendesk support |
| JSON | yes, except tickets over 1 MB | comments of any ticket over 1 MB, listed in a separate error file; items stamped within 6 minutes of the request; recommended above 200,000 tickets; above 1,000,000 tickets downloaded in 31-day increments | Zendesk support |
| XML | yes | file capped at 500 MB, about 200,000 tickets; not available above 200,000 tickets; custom ticket, user and organization fields omitted | Zendesk support |
| All formats | n/a | AI agent tickets cannot be exported; JSON and CSV not available in sandbox; order not guaranteed; export link valid at least three days | Zendesk support |
The data manifest lists the format and its gaps, so a buyer that asks for "all tickets" knows what the archive holds. No price effect of these gaps is stated.
The REST API and Read-Only Connections
The Zendesk REST API is the route for Team plan accounts and for scripted exports, and it runs under rate limits whose values are not recorded here. Public scripts that export tickets through the API exist; this page is not a tutorial.
Some programs read in place instead. Centific states that in-scope systems are connected read-only with exclusions enforced in extraction code, and Scale AI states that it anonymizes inside the company's environment before extraction (both checked November 9, 2026).
What to Remove From Zendesk Tickets Before Delivery
Zendesk tickets carry personal data in fixed fields and in free text, so removal works through the requester and agent fields first and the comments, notes and attachments last. Method is covered under PII removal and de-identification; the Zendesk-specific places to look are these.
- Requester name, email and phone number.
- CCs and followers added to a ticket.
- Agent names and signatures in every reply.
- Internal notes, which often hold account details.
- Custom fields with order or account IDs.
- Attachments and screenshots.
Corpus Bridge's illustrative draft replaces names, emails and IDs, Nyne states that it removes identifying details, and Turing states that it covers de-identification, cleanup and packaging costs (all checked November 9, 2026, Turing re-checked November 16, 2026).
Tickets can also hold special-category data such as health details, which under Article 9(1) of Regulation (EU) 2016/679 (applying since May 25, 2018) needs an Article 9(2) exception in addition to an Article 6 basis.
Reusing customer-service records for AI training or sale also needs a compatibility assessment unless it rests on consent or Union or Member State law; see purpose compatibility under Article 6(4) of the same regulation.
What Programs Name When They Ask for Zendesk Data
Five programs and intermediaries name Zendesk among the systems they want, each with its own terms, checked November 9, 2026, with Turing re-checked November 16, 2026. The table lists them alphabetically, as of November 16, 2026, and every value is the program's own statement.
| Program | Role | Zendesk named as | Terms that matter for Zendesk data | Source |
|---|---|---|---|---|
| Centific Enterprise Data | licensee (data vendor) | "Salesforce, Workday, ServiceNow, SAP, HubSpot, Zendesk" | read-only connection; "You license your data. You never hand it over."; payment after acceptance | centific.com |
| Corpus Bridge | introducer (intermediary; a brokerage partner approaches labs) | "Salesforce/HubSpot/Zendesk"; illustrative 96,000 Zendesk tickets | draft: model training only, no resale, names, emails and IDs replaced, three years, non-exclusive, USD 64,200; seller pays a success fee after closing, percentage not published | corpusbridge.com |
| Nyne data partnerships | licensee that delivers to frontier AI labs, none named | "Salesforce, HubSpot, Workday, ServiceNow, SAP, Zendesk" | removes identifying details; training and evaluation only, not published; 20+ US W-2 employees | nyne.ai |
| Scale Data Partnerships | program (human-data platform) | "Salesforce, HubSpot, Workday, ServiceNow, SAP, Zendesk" | anonymizes inside the company's environment; per-package approval; 40+ employees preferred | scale.com |
| Turing Project Lazarus | program (sells the record on, revenue share) | helpdesk: Zendesk, Intercom, Freshdesk | license to Turing exclusive for the first 6 months; Turing may license the record to more than one lab in that term; covers de-identification costs | lazarus.turing.com |
The only Zendesk-specific figure is Corpus Bridge's illustrative draft, USD 64,200 for 96,000 Zendesk tickets from 2015 to 2025 (checked November 9, 2026), which is Corpus Bridge's own claim and a draft, not a deal.
No seller-confirmed price for Zendesk tickets exists in public records. Other programs and their payouts are compared in AI data partnership payouts and program terms compared.
Corpus Bridge is an introducer that never takes the data, so it is not a buyer; its listing here records which systems it names and what its draft says.
Licensing Zendesk Ticket History: Benefits, Risks, Downsides and Alternatives
Licensing Zendesk ticket history can bring revenue from conversations a company already stores, and it also hands customers' and agents' words to a third party for good, so not licensing remains a valid result.
Benefits
- Existing records can already be exported in machine-readable JSON.
- Some programs carry preparation costs, as Turing states for de-identification.
- Read-only routes keep the raw data in place.
- The customer owns Service Data under the Zendesk Customer Agreement.
Risks
- Customer personal data and special categories sit in free text.
- Agents are named in every reply.
- Zendesk's own improvement use is already granted in the Customer Agreement.
- There is no recall: micro1's grant is irrevocable and perpetual, and Labelbox Prism states that models already trained on the data "cannot be unlearned" (checked November 9, 2026).
Downsides
- CSV loses the dialogue, JSON loses the comments of large tickets, and XML stops at 200,000 tickets.
- The enablement request and the cleanup are admin effort.
- Exclusivity periods block other buyers, as in Turing's first 6 months.
Alternatives
- License a subset, such as closed tickets, one brand or older years.
- License tickets together with CRM records as one package; see selling CRM records.
- Keep the data and disable Zendesk's generative AI services where wanted.
- Do not license at all.
Zendesk Among the Support and CRM Systems and the Seller Steps
Zendesk is one of the support and CRM systems whose plans and terms decide what a company can license, next to Salesforce, HubSpot, Intercom, Freshdesk and ServiceNow. The parent page compares export rights and mechanics by source system.
Siblings in the same family are Salesforce data export, HubSpot data export, Intercom conversation export, Freshdesk ticket export and ServiceNow data export. A seller working through Zendesk data follows these steps:
- Build a data inventory of tickets, users and attachments.
- Check customer consent and confidentiality clauses.
- Handle employee notice and consent for agents named in replies.
- Write the data manifest, including the export format.
- Plan delivering licensed data to an AI buyer.
- Weigh should you sell or license your data at all.
Zendesk Data After a Subscription Ends
A company that cancels Zendesk can export Service Data for 30 days after the subscription term ends, and deletion under Zendesk's Service Data Deletion Policy begins 90 days after cancellation. The policy took effect on July 3, 2026 for existing customers and June 3, 2026 for new ones.
- Export window: 30 days after the term (Customer Agreement section 3.4).
- Deletion start: 90 days after cancellation or termination.
- Deletion period: ticket data 40 days and live chat content 120 days after deletion begins; ticketing backups are kept 130 days, and Zendesk offers no expedited deletion.
Deadlines for a closing company are in exporting company data before shutting down. Where the company is gone, see selling data from a defunct company. This is information, not legal advice.
Buyer Programs Cited on This Page
The program terms above come from each program's own pages, checked November 9, 2026, and Turing's on November 16, 2026. Programs, alphabetical:
The wider lists are company data partnership programs and who buys AI training data.
Frequently Asked Questions
How do I export all tickets from Zendesk?
The account owner asks Zendesk Customer Support to enable exports, then runs a JSON export, which keeps comments except on tickets over 1 MB. The export is off by default and the request gives the subdomain.
Does a Zendesk CSV export include ticket comments?
No; the CSV export leaves out ticket comments, ticket descriptions and deleted tickets. Use JSON or XML where the dialogue matters.
Does Zendesk use ticket data to train AI?
The Zendesk Customer Agreement instructs Zendesk to use Service Data to improve its products, and the AI Services Addendum bars LLM Providers from using it beyond the AI Services; neither document read says whether Zendesk trains its own models.
Platform training across vendors is covered under user data and platform terms.
Can a company sell its Zendesk tickets to AI companies?
A company can license Zendesk tickets it owns once customer data, agent names and customer terms are dealt with, and five programs name Zendesk.
The limits are set out under what company data cannot be licensed.