| Quick facts | |
|---|---|
| API terms on AI training | No express AI clause found |
| Does Zendesk train on your data? | Vendor trains limited, non-generative models[1] |
| Recommended export path | Tickets, users and organizations export to JSON, CSV or XML. Zendesk’s help center says the account owner may need to contact support to activate data exports.[2] |
| Connector risk | Unreviewed. |
Section 1
What Zendesk holds that AI buyers value
- Tickets and comment threads
- Users and organizations
- Macros and help-center articles
- Satisfaction ratings
Where the value is: Ticket threads that show a problem being diagnosed, escalated and resolved — exactly the “reasoning captured while the work happened” buyers describe.
Section 2
How to export your Zendesk data
Tickets, users and organizations export to JSON, CSV or XML. Zendesk’s help center says the account owner may need to contact support to activate data exports.[2]
- Have the account owner confirm data exports are activated.
- Export tickets in JSON to keep full comment threads.
- Export users and organizations separately for pseudonymization keys.
Keep a note of who ran each export, when, and with what filters. It is the first page of the documentation file a buyer — and later an acquirer — will ask for.
Section 3
What Zendesk’s API terms say about AI
We did not review Zendesk API terms in this pass.
Absence of an express clause is not permission. Your subscription agreement, acceptable-use policy and order form still govern what you may do with records held in the platform, and other vendors have added AI clauses during 2025–2026. Use an administrator export, and have counsel read the current agreement.
Section 4
Does Zendesk train AI on your data?
Zendesk says its proprietary, non-generative models may be trained on customer data after identifier fields are excluded and PII is sanitized; its generative features use pre-trained third-party models not trained on customer data.[1]
A vendor’s own use of your data does not transfer ownership, but it belongs in your disclosure to a buyer: it bears on uniqueness and on whether the same records have already fed a competing product.
Section 5
Fields to scrub before licensing
- Requester names and emails
- Free-text ticket bodies (often containing addresses, order numbers, health or payment detail)
- Attachments
Removing names is not de-identification; combinations of quasi-identifiers re-identify people.[3] California’s statute sets the bar for a “deidentified” consumer record.[4] Test a sample with the browser-local PII scanner before anyone else sees it.
Section 6
Check the rest of your stack
Most licensable files span several systems. The software AI data rights checker lists the API clause, vendor-training position and export path for every system we have reviewed, and the SaaS AI data ownership index publishes the same findings as a downloadable dataset.
Frequently asked questions
Can I sell my Zendesk data to AI companies?
How do I export all my data from Zendesk?
Does Zendesk use my data to train AI?
References
Sourced from primary industry reports, government data, SEC filings, and peer-reviewed valuation research. Retrieved at time of publication.
- 1.Zendesk, Inc. — Zendesk AI Data Use Information — Edited 7 July 2025; proprietary non-generative models may be trained on sanitized customer data, generative features are not (2025)
- 2.Zendesk, Inc. — Exporting ticket, user, or organization data from your account — JSON, CSV or XML exports of tickets, users and organizations
- 3.U.S. National Institute of Standards and Technology — NISTIR 8053 — De-Identification of Personal Information — Reference treatment of de-identification techniques and re-identification risk (2015)
- 4.State of California — California Consumer Privacy Act, Civil Code § 1798.140 — definitions of "deidentified" and "sale" — Statutory standard a de-identified operational record must meet, and the breadth of "sale"