Under the Subscriber Terms, last updated September 1, 2026, the customer and its licensors keep all rights in Customer Data, and Asana holds a separate right to use it to provide and improve the service.
Asana projects are one source in AI training data licensing, and the route used decides how complete a licensed archive is. Licensing nothing is a valid result.
Fact-check note: Asana's statements come from its own terms, pricing page and developer documentation, read on November 16, 2026, and program terms are each program's own statements; how we source, date and check every figure is set out in the methodology.
What an Asana Organization Holds and What a License Can Cover
An Asana organization holds a company's planned and finished work: projects and their sections, tasks and subtasks with assignees and due dates, comments, attachments, custom fields, goals, portfolios and, where used, time entries.
Asana's graph export names portfolio, project, task, section, allocation, time tracking entry and goal as resource types (developer documentation, read November 16, 2026).
The Subscriber Terms define Customer Data in s.1.2 as "all information that Customer or its End Users submit to the Services", and s.1.4 counts consultants and contractors as End Users, so outside people write part of the record.
Five programs and intermediaries name Asana among the systems they want. Value and pricing of task histories are covered on the page about issue trackers and project histories for AI training.
Who Controls Asana Data in a License
Four parties shape what a company can license from Asana: the company as the customer that keeps the rights in Customer Data, Asana with its own use right, app developers bound by the API Terms, and the employees, contractors and clients whose names and work fill the tasks.
The contracting party of the Subscriber Terms is Asana, Inc., and their preamble states that a separate written agreement with Asana on the same subject matter displaces the online terms.
The Subscriber Terms: Ownership, Improvement Use and Restrictions
Asana's Subscriber Terms, last updated September 1, 2026, state that the customer and its licensors retain all right, title and interest in Customer Data (s.7.2).
Asana receives a non-exclusive right to use Customer Data solely to provide and support the Services and to improve them, provided the data stays confidential and no one is publicly identified.
The customer can control whether Customer Data is used for product improvement through the Asana Admin Console, and the default of that setting is not on record here. Ownership is one layer of a rights audit of the data you want to license, which also covers client contracts and outside authors.
The resale bar in s.2.4 names the Services, not Customer Data. A buyer's no-prior-grant warranty, as in micro1's Data License Master Terms (s.5.1, checked November 9, 2026), sits beside Asana's improvement right, and whether the two conflict is a question for counsel.
Asana AI: What the Product-Specific Terms Say About Model Training
Asana's Product-Specific Terms, last updated November 9, 2026, state that "Asana does not use or permit third-party AI partners to use Customer Data to train generative artificial intelligence models used to provide Asana AI."
The same terms say Customer Data includes AI Input and AI Output, which the customer owns. The statement covers the models behind Asana AI, the improvement right in s.7.2 is separate and switchable, and neither is a license route.
The API Terms and Apps That Read Asana
Asana's API Terms, effective March 14, 2022, bar anyone building on the APIs from selling, renting or sharing "any User Content or other information or data obtained through our APIs, directly or indirectly, to or with any third party".
A program's connector app is bound by these terms, and third-party services a customer enables run under their own terms (Subscriber Terms s.2.7).
Whether the clause reaches a company's own export script is not addressed in the terms read, so it is a question to raise with Asana and counsel; the comparison of buyer connectors vs native exports covers the mechanics.
How Asana Data Leaves the Organization
Asana data leaves an organization by four routes: a project export from the app, a whole-organization export, the export endpoints of the API, or a connection that a program runs. The table compares them as of November 16, 2026.
| Route | Plans as Asana states them | Format and scope | Limits on record | Source |
|---|---|---|---|---|
| Project export in the app | Personal, Starter, Advanced, Enterprise, Enterprise+ | CSV or PDF of project data and reports | whether comments, attachments and subtasks travel: not on record here | asana.com/pricing, read 2026-11-16 |
| Organization export | Enterprise with the Compliance management add-on; Enterprise+ | "complete JSON backup" of the organization, "including all projects, tasks, comments, and custom fields" | none stated on the pricing page | asana.com/pricing, read 2026-11-16 |
| Organization export API | "only available to Service Accounts of an Enterprise+ organization" | complete organization data, JSON in gzip | file link, "may only be valid for 1 hour"; minutes to a few hours for large organizations | developers.asana.com, read 2026-11-16 |
| Graph export API | Enterprise and Enterprise+ | JSON Lines in gzip from a goal, team, portfolio or project | presigned URL expires in 1 hour; 5 concurrent export jobs per user | developers.asana.com, read 2026-11-16 |
| Resource export API | not stated in the documentation read | bulk tasks, teams and messages for a workspace, JSON Lines in gzip | rate limits of 150 or 1,500 requests per minute | developers.asana.com, read 2026-11-16 |
| Program connection or in-environment preparation | any, by program | read-only connection (Centific); anonymized inside the company's environment (Scale AI); no OAuth access or install (Troveo) | program terms | centific.com, scale.com, troveo.ai, checked 2026-11-09 |
Plans: Project Export Everywhere, Organization Export on Enterprise Tiers
Asana's pricing page lists CSV and PDF export of project data and reports on all five plans, Personal, Starter, Advanced, Enterprise and Enterprise+, and lists organization exports only on Enterprise with the Compliance management add-on and on Enterprise+.
- Project export: listed on all five plans.
- Organization export on the pricing page: Enterprise with the add-on, included on Enterprise+.
- Organization export API: limited by the developer documentation to Service Accounts of an Enterprise+ organization.
Both plan statements are Asana's own, shown side by side, not reconciled.
Formats and What Each Route Carries
The route decides how complete a licensed Asana archive is, because Asana describes only the organization export as including comments.
The pricing page names comments and custom fields for the organization export, and what a single-project CSV or PDF carries is not on record here. The API routes return JSON or JSON Lines in gzip. The data manifest of a licensed archive names the route, the format and the gaps.
API Exports, Rate Limits and Read-Only Connections
Asana's API limits standard traffic to 150 requests per minute on free domains and 1,500 on paid domains, and it allows five concurrent duplication, instantiation and export jobs per user, counting jobs started in the web app (developer documentation, read November 16, 2026). Backup scripts on the API run into the same limits.
Programs avoid the export step on the company's side: Centific states that it connects read-only, Scale AI states that it anonymizes inside the company's environment before extraction, and Troveo states that no OAuth access or install is required, each checked on November 9, 2026.
People and Client Data Inside Asana Tasks
Asana tasks carry personal data in fixed fields and in free text, and agency, consulting and client-service teams also store their clients' plans and documents there, so removal starts with names and client identifiers and ends with comments and attachments. Each of these places needs PII removal and de-identification.
- Assignees, followers and collaborators.
- Guests from client companies.
- Comments and @mentions.
- Attachments and linked files.
- Custom fields with client names, budgets or rates.
- Time entries and user rates.
Tasks for hiring, performance or sick leave can hold health or other special-category data, which under Article 9(1) of Regulation (EU) 2016/679, applying from May 25, 2018, needs an Article 9(2) exception in addition to an Article 6 basis.
Client confidential material is a separate risk: under 18 U.S.C. 1839(5), in force through the Defend Trade Secrets Act since May 11, 2016, misappropriation includes disclosure by someone who acquired a secret under a duty to keep it. A client contract can therefore bar a license even when the company owns the workspace.
Reusing task data collected for project work as training data raises the question of purpose compatibility under Article 6(4) of the same Regulation, unless a consent or a Union or Member State law applies. This is information, not legal advice.
What Programs Name When They Ask for Asana Data
Five programs and intermediaries name Asana among the systems they want, each with its own terms, checked November 9, 2026, with Turing's system list re-checked November 16, 2026. The table is alphabetical, and every value is the program's own statement.
| Program | Role | Asana named as | Terms that matter for Asana data | Source |
|---|---|---|---|---|
| Avelence seller advisory | broker (intermediary, seller-side) | "Jira/Linear/Asana/Notion" | no default system access; extraction and de-identification on a separate copy; shared under mutual NDA | avelence.com |
| Centific Enterprise Data | licensee (data vendor) | "Office files, Drive, SharePoint, Confluence, Notion, Jira, Asana" among 188 supported apps | read-only connection; "You license your data. You never hand it over."; payment after acceptance | centific.com/enterprise-data |
| Scale Data Partnerships | program (human-data platform) | "Jira, Confluence, Asana, Notion, Linear" | anonymizes inside the company's environment; per-package approval; 40+ employees preferred; exclusivity, term and deletion not published | scale.com/data-partnership |
| Troveo business data licensing | marketplace (intermediary; licenses on the seller's behalf) | "Jira, Linear, Asana, Notion, Figma" | seller retains ownership; no OAuth access or install required; packaged anonymized with a manifest | troveo.ai/business-data |
| Turing Project Lazarus | program (sells the record on, revenue share) | work management category: Jira, Linear, Asana (list not quoted) | 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, cleanup and packaging costs | lazarus.turing.com |
No program publishes an Asana-specific price, and no seller-confirmed amount for Asana data is on record. Payout ranges and terms across programs are set out in AI data partnership payouts and program terms compared.
Avelence and Troveo are intermediaries, not buyers: Avelence advises sellers, and Troveo licenses data on the seller's behalf.
Licensing Asana Task History: Benefits, Risks, Downsides and Alternatives
Licensing Asana task history can earn money from a record of how work was planned and done, and it also hands colleagues' and clients' names and plans to a third party for good, so not licensing remains a valid result.
Benefits
- The customer keeps ownership of Customer Data under Subscriber Terms s.7.2.
- One organization export carries comments, on the plans that offer it.
- Read-only routes spare the company a manual export.
- Turing states that it covers de-identification, cleanup and packaging costs.
Risks
- Client secrets in tasks can fall under confidentiality duties.
- Special-category data in HR or health tasks needs a legal basis of its own.
- Asana's improvement right applies unless the customer switches it off, and its interaction with a buyer's terms is a question to raise.
- Data cannot be recalled: Labelbox states that models already trained on data "cannot be unlearned" (checked November 9, 2026), and micro1's grant is irrevocable and perpetual (s.1.2).
Downsides
- Organization export sits on the top tiers only.
- Export links last one hour, and five export jobs run at once per user.
- The license to Turing is exclusive for the first 6 months.
Alternatives
- License a subset, such as closed projects, one team or older years.
- License tasks together with wiki pages as one package, as set out in selling documents, wikis and drive files.
- Keep the data and switch off product-improvement use in the Admin Console.
- Do not license at all.
Asana Among the Work Trackers and the Seller Steps
Asana is one of the work trackers whose plans and terms decide what a company can license, next to Jira, Linear and Monday.com, with Notion and Confluence holding the written side of the same work. The comparison across systems is export rights and mechanics by source system.
The closest siblings are Jira data export rights, Notion workspace export, Confluence data export, Linear issue export and Monday.com board export. The seller steps for an Asana archive run in this order:
- Take a data inventory of projects, teams and guests.
- Check customer consent and confidentiality clauses for client data in tasks.
- Settle employee notice and consent for assignees and commenters.
- Write the data manifest.
- Plan delivering licensed data to an AI buyer.
- Decide whether to proceed, using should you sell or license your data.
Asana Data After a Subscription Ends
After a subscription ends, Asana may deactivate the account at once and makes Customer Data available for export only if the customer sends written notice within 30 days (Subscriber Terms s.5.4).
- 30 days: written notice needed for export.
- After that: Asana may delete Customer Data.
- On a request logged at the help center: destruction within 180 days, backups within 30 days after that.
The steps for exporting company data before shutting down apply here, and a closed company's records are covered in selling data from a defunct company.
Asana's EU Data Act Addendum: Switching, Not Selling
Asana's EU Data Act Addendum, effective September 12, 2025, lets an EU customer's Super Admin file a switching request to move Customer Data to another provider or its own infrastructure, after a two-month notification period and a 30-day transition.
The transition can run up to 7 months where impracticable, Asana may charge reasonable switching charges, and an early termination fee applies for the rest of the term.
Regulation (EU) 2023/2854 applies from September 12, 2025, and its switching chapter gives a route to export when changing provider, not a general right to export for sale; see EU Data Act and AI training data.
Buyer Programs Cited on This Page
The program terms above come from each program's own pages, checked November 9, 2026, and Turing's system list on November 16, 2026.
- Avelence (seller advisory, intermediary)
- Centific data buyer profile
- Scale AI data buyer profile
- Troveo profile and program terms (intermediary)
- Turing Project Lazarus profile
- All programs: company data partnership programs and who buys AI training data
Frequently Asked Questions
How do I export tasks from Asana?
Any Asana plan can export a project's tasks as CSV or PDF, and a whole organization exports as JSON on Enterprise with the Compliance management add-on or on Enterprise+. What a project export carries beyond the tasks, including comments, is not on record here.
Does Asana use customer data to train AI?
Asana's Product-Specific Terms state that neither Asana nor its AI partners use Customer Data to train the generative models behind Asana AI, while the Subscriber Terms let Asana use it to improve the Services unless the customer switches that off. Training by platforms on their users' data is covered in user data and platform terms.
Can I export a whole Asana organization at once?
Yes, on the plans that carry organization exports: the result is one compressed JSON file, and Asana states its file link may be valid for only one hour. The API route is limited to Service Accounts of an Enterprise+ organization.
Can a company sell its Asana project data to AI companies?
A company can license Asana data it holds rights in once colleagues' and clients' data and client contracts are dealt with, and five programs name Asana. The limits are set out in what company data cannot be licensed.