Under the Freshworks Terms, effective April 1, 2026, the customer retains all right, title and interest in its Customer Data, and one program, Turing Project Lazarus, lists Freshdesk among the support desks it takes (Freshworks documents read and Turing checked November 17, 2026).
Freshdesk is one source system in AI training data licensing, and its export routes and agreements decide what a company can hand over. Freshworks' own use of Customer Data is tied to providing, maintaining and improving its technology, and whether Freshworks trains any model on tickets is not stated in the documents read.
DataPacts Editorial Team: how we source, date and check every figure. Freshworks documents and Freshdesk help articles were read on November 17, 2026; the Turing terms were checked the same day.
What a Freshdesk Account Holds and What a License Can Cover
A Freshdesk account holds tickets with their conversations and private notes, the contacts and companies behind them, and solution articles, and a license can cover any of these that the company controls.
The ticket is the unit buyers name, and its value to a buyer lies in the dialogue between requester and agent.
Buyer demand and the worth of support records are covered on the page about selling customer support tickets and chats for AI training; this page stays on Freshdesk's mechanics and terms. Freshservice is a separate Freshworks product and is not covered here.
Who Controls Freshdesk Ticket Data in a License
Three layers shape what a company can license from Freshdesk: the Freshworks Terms that say who owns Customer Data, the Data Processing Addendum and Privacy Notice that set Freshworks' role as processor and its own analytics use, and the silence of the Terms and the Addendum on AI training.
The Freshworks Terms: Ownership, Use and Export Window
The Freshworks Terms, effective April 1, 2026, state that the customer retains all right, title, and interest in its Customer Data.
Freshworks Inc., a Delaware corporation, and its Affiliates receive a non-exclusive, worldwide, royalty-free right to process that data "solely to the extent necessary to provide, maintain, and improve the Freshworks Technology". The customer warrants that it holds sufficient rights.
Ownership is the starting point of the rights audit of the data to be licensed. The use restriction on commercially exploiting the Freshworks Technology names the Technology, not Customer Data, and the restriction on processing data for third parties does not address licensing.
Usage Data is a separate category, defined as data gathered in or derived from the use of the Services, which Freshworks may use to develop, improve, support and operate its products. Freshworks' improvement use sits beside a buyer's no-prior-grant warranty; whether the two collide is a question for the buyer and counsel.
The DPA and the Privacy Notice: Processor Role and Analytics
Under the Freshworks Data Processing Addendum, effective March 10, 2026, Freshworks acts as processor and the customer as controller of the personal data in the helpdesk (section 5). The customer may export all Customer Data before its account ends.
The Freshworks Privacy Notice, effective March 1, 2026, defines Hosted Data as data Freshworks processes on behalf of customers and says Freshworks is generally not its controller. It lists chat identifiers and chat content among Service Analytics data and adds that "some Hosted Data may be used as part of our analytics".
Freshworks AI: What the Documents Do Not State
The Freshworks Terms and Addendum do not mention artificial intelligence, machine learning or model training, while the Privacy Notice says Freshworks may "train our algorithms" and "develop new products and services using machine learning technologies" as part of its legitimate interests.
Whether Freshworks trains any model on the Customer Data in tickets, and whether an opt-out exists, is not stated in the three documents read on November 17, 2026.
How Freshdesk Tickets Leave the Account
Freshdesk tickets leave an account by three routes: the ticket export in CSV or Excel, the XML account export, and the API. The archive view adds a fourth run. The table compares the routes by who runs them and what the record shows, as of November 17, 2026.
| Route | Who runs it | What the record shows | Source |
|---|---|---|---|
| Ticket export (CSV or Excel) | Admin or Supervisor role, from the ticket list | chosen ticket fields; Description via multiline fields; not the entire conversation, not archived tickets | support.freshdesk.com, article modified 2026-02-16 |
| Account export (XML) | account administrator, Admin > Account > Account Details | whole account data including tickets and solution articles, mailed as XML | support.freshdesk.com, article modified 2024-05-22 |
| Archive view export | admin or agent with access | archived tickets; one run at a time | support.freshdesk.com, article modified 2026-07-15 |
| API | the company or an app | 300 pages (30,000 tickets) per listing, last 30 days by default, 100 per page; rate limits by plan, values not recorded | developers.freshdesk.com, read 2026-11-17 |
Ticket Export Versus Account Export
Freshdesk states that the ticket export "will NOT give you the entire conversation from the ticket or historical data (archived tickets)" and that an account export is needed for that.
The ticket export needs the Admin or Supervisor role, produces CSV or Excel, and shows the Description only when multiline text fields are ticked; a custom role can hide the Export button.
The account export starts under Admin, Account, Account Details, Export data, and Freshdesk mails the XML file to the account administrator.
The ticket export counts merged tickets separately while reports count them once, and a date range on the list view limits the export range, so the list is set to Any time. The manifest records:
- the format of each export;
- the date range and filter used;
- how merged tickets are counted;
- whether archived tickets are included.
Archived Tickets After 120 Days
Freshdesk automatically archives a closed ticket after 120 consecutive days without a reply, private note or property change. Archived tickets are read-only, a customer reply to one creates a new ticket, and deleting an archived ticket is permanent.
They are exported from the Archive view, and only one archived export can run at a time. For a dataset, any history older than four months of inactivity sits in the Archive view and needs its own export run, so a ticket export alone misses every archived ticket.
The API and Its Limits
The Freshdesk API lists at most 300 pages, or 30,000 tickets, per query, and returns only tickets created in the past 30 days unless an updated_since date is given.
A page holds 100 objects at most (30 by default), each include on the ticket list costs 2 extra API credits, and rate limits depend on the plan; the limit values are not recorded here. Programs that read in place are covered under buyer connectors vs native exports.
What a Freshdesk Export Holds: Conversations, Attachments and Customer Data
A complete Freshdesk export carries personal data in fixed fields and in free text, so removal starts with requester and agent fields and ends with conversations and attachments. The method is set out under PII removal and de-identification.
- Requester name, email and phone number.
- Agent names and signatures.
- Conversation text and private notes.
- Custom fields with order or account IDs.
- Attachments and screenshots.
Freshdesk offers a secure attachments setting, which requires a login to open attachments sent from Freshdesk, and it scans incoming attachments for malware. Whether the XML account export includes attachments is not stated in the articles read.
Records collected to serve customers and reused for AI training need a compatibility assessment under Article 6(4) of Regulation (EU) 2016/679, applicable from May 25, 2018, unless the reuse rests on consent or law; see purpose compatibility under Article 6(4). Special-category data in free text needs an Article 9(2) exception.
What Programs Name When They Ask for Freshdesk Data
One program on record names Freshdesk: Turing lists it with Zendesk and Intercom in the helpdesk category of Project Lazarus, checked November 17, 2026. The table gives the program's own statements, as of November 17, 2026.
| Program | Role | Freshdesk named as | Terms that matter for Freshdesk data | Source |
|---|---|---|---|---|
| Turing Project Lazarus | program (licenses the record on, revenue share) | helpdesk examples "Zendesk, Freshdesk, Intercom"; support desk tool counted in tickets | 6-month exclusive license to Turing; Turing may license the same record to more than one lab; Turing covers de-identification, cleanup and packaging costs | lazarus.turing.com |
No other program on record names Freshdesk, and no paid amount for Freshdesk tickets is stated anywhere on record. Programs are compared in AI data partnership payouts and program terms compared.
Licensing Freshdesk Ticket History: Benefits, Risks, Downsides and Alternatives
Licensing Freshdesk ticket history is a choice with benefits and risks, and not licensing is an equally valid result.
Benefits
- An archive otherwise left to expire after the export window can be put to use.
- The customer owns Customer Data under the Freshworks Terms.
- Turing states that it bears de-identification costs.
Risks
- Customer personal data sits in conversations and attachments.
- The customer warrants to Freshworks that it holds sufficient rights.
- Exclusivity, such as Turing's first 6 months, blocks other buyers.
Downsides
- Preparation effort is real, and the ticket export drops conversations.
- Archived tickets need separate export runs.
Alternatives
- Do not license; keep the archive.
- License a subset, such as one brand or closed tickets.
- License other record types, such as CRM records, instead.
Freshdesk Among the Support and Service-Desk Systems and the Seller Steps
Freshdesk is one of the support systems whose plans and terms decide what a company can license, next to Zendesk, Intercom, ServiceNow, Salesforce and HubSpot. The parent page compares export rights and mechanics by source system.
Siblings in the support family are the Zendesk ticket export, the Intercom conversation export and the ServiceNow data export; IT service-desk tickets for AI training sit with issue trackers. A seller working through Freshdesk data follows these steps:
- Build a data inventory of tickets, contacts 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 route.
- Plan delivering licensed data to an AI buyer.
- Weigh should you sell or license your data at all.
Freshdesk Data After Account Closure
Freshworks makes Customer Data available for export for fourteen days after an account closes and may retain it for up to three months before deleting it.
Deleted data cannot be recovered, and a free trial's data must be exported before the trial ends or it is permanently deleted. Deadlines for a closing company are set out in exporting company data before shutting down.
- Export window: fourteen days from closure of the account.
- Retention: up to three months, then deletion.
Where the company is gone, see selling data from a defunct company. This page is information, not legal advice.
Buyer Programs Cited on This Page
This page cites one program, Turing Project Lazarus.
The wider lists are company data partnership programs and who buys AI training data.
Frequently Asked Questions
How do I export all Freshdesk tickets with conversations?
The account administrator runs the XML account export under Admin, Account, Account Details, because the ticket export omits the entire conversation. The file is mailed to the administrator.
Does a Freshdesk ticket export include archived tickets?
No; archived tickets have their own export from the Archive view. Only one archived export runs at a time.
Does Freshworks use customer data to train AI?
The Freshworks Terms and Addendum do not mention AI training, the Privacy Notice mentions training algorithms in Service Analytics, and whether tickets are used is not stated.
Platform training across vendors is covered under user data and platform terms.
Can a company sell its Freshdesk tickets to AI companies?
The Freshworks Terms leave ownership of Customer Data with the customer, so a company can license tickets it owns once its rights audit and PII removal are done.
The limits are set out under what company data cannot be licensed.