Asana
Work management · asana.com · last read 2026-11-16
At a glance
- Is Asana GDPR compliant?
- No tool is GDPR compliant on its own: compliance depends on what you process with it and how. What follows is what Asana itself publishes, each answer linked to its source and the date we read it.
- Does Asana have a data processing agreement (DPA)?
- Yes. Asana publishes a data processing agreement at asana.com. It gives 10 days' notice before a new subprocessor is added. It promises breach notification "without undue delay", with no number of hours. Source and date
- Which version of the Asana DPA is current?
- On 2026-11-09, Asana's DPA at asana.com printed “Last updated: September 1, 2026, Effective Date: 1 September 2026”. Source and date
- Does Asana have a SOC 2 report?
- Asana states SOC 2 Type 2 on its own page, but does not say there how to get a report. We read this on 2026-10-05. Source and date
- Is Asana ISO 27001 certified?
- Asana states ISO/IEC 27001 (2022 edition, as Asana names it) on its own page, but does not say there how to get the certificate. We read this on 2026-10-05. Source and date
- Where is Asana's trust center?
- Asana publishes a page it calls “Trust Center” at trustcenter.asana.com. Some of its documents sit behind a request or sign-in: the page says “Get Access”. The page mentions SOC 2, ISO 27001, a penetration test, subprocessors and security questionnaires. We read it on 2026-11-03. Source and date
- Does Asana use your data to train AI models?
- For business plans (Asana AI): Asana's AI partners do not use customer data to train their models. For business plans (Asana AI): Neither Asana nor its AI partners use customer data to train AI models. Source and date
- Does Asana offer zero data retention?
- For business plans (Asana AI): AI partners are required to delete customer data after each query. Source and date
- How does Asana transfer personal data out of the EU?
- Asana's agreement relies on the EU standard contractual clauses, the EU-U.S. Data Privacy Framework and the UK transfer addendum. Asana is on the official Data Privacy Framework List (status: Active). Source and date
- Does Asana offer EU data residency?
- An EU location exists but requires a paid plan or add-on. Plan it needs: Enterprise. Source and date
- Who are Asana's subprocessors?
- Asana lists 33 third-party subprocessors; 24 of them name at least one processing country outside the EEA. We last read the list on 2026-10-05. Source and date
- How do you report a security vulnerability to Asana?
- Asana publishes a security.txt at asana.com naming https://bugcrowd.com/asana or security@asana.com. Source and date
The same questions for any vendor, and the rule behind each: the vendor due diligence checklist.
Identity
| Legal entity | Asana, Inc. |
|---|---|
| HQ | US |
| Parent company | — |
| Ultimate ownership | US |
| EU contracting entity | — |
| LEI | 254900X7UAJNMLPLZ510 |
| US CLOUD Act reach | Contracting entity incorporated in the US |
| Source | asana.com · 2026-10-08 |
Legal entity from the vendor's own terms. LEI, registered country and parent company from the Global LEI Index (GLEIF); ownership is left empty where GLEIF names no parent. The CLOUD Act row is arithmetic over those countries, not an assessment of risk.
Asana data residency
| Region | EU data location | Minimum plan | Source | Observed |
|---|---|---|---|---|
| EU | Paid upgrade | Enterprise | help.asana.com | 2026-10-12 |
EU: Data residency (including Frankfurt, Germany) is available to be purchased as an add-on in Enterprise organizations and divisions and is included in Enterprise+ tiers. Customers must contact Sales to opt in.
The same question for every vendor: where SaaS vendors store EU data.
Asana's subprocessor list names AWS and Google for hosting or infrastructure. Which SaaS vendors run on which cloud, and the sovereign offerings of each: sovereign clouds.
Subprocessor chain
33 third parties · 17 of the vendor's own group companies · 24 with a country outside the EEA · all read 2026-10-05
| Subprocessor | Country | Purpose |
|---|---|---|
| Amazon Web Services Inc (AWS Bedrock) | US, EU | Artificial intelligence enabled functionality |
| Amazon Web Services, Inc. | US, DE, IE, AU, JP | Cloud service provider |
| Amplitude, Inc. | US | Analytics and Data Visualization |
| Anthropic, PBC | — | — |
| Anthropic, PBC | — | AI chat functionality |
| Anthropic, PBC | US | Artificial intelligence enabled functionality |
| Anthropic, PBC | US | Artificial intelligence functionality for customer support |
| Anthropic, PBC | US | LLM Provider |
| Apple, Inc. | US | Mobile push notifications |
| AWS Bedrock | — | — |
| Cloudflare, Inc. | US | Model Context Protocol (MCP) server |
| Databricks, Inc. | US | Data Warehouse |
| Databricks, Inc. | — | data warehouse |
| Fireworks AI, Inc. | US | Cloud service provider |
| Google, LLC | US | Mobile push notifications |
| Google, LLC (Gemini Enterprise Agent Platform) | US, BE, DE, GB, ES, IT, CH | Artificial intelligence enabled functionality for Google Gemini |
| Google, LLC (Google Cloud) | US, BE, DE, GB, ES, IT, CH | Cloud service provider |
| Hyperdoc Inc. (Recall.ai) | US, DE, JP | Transcription service provider |
| Intercom, Inc | US | Artificial intelligence chatbot for customer support |
| KMC Solutions | PH | — |
| OpenAI OpCo, LLC | US, NO | Artificial intelligence enabled functionality |
| OpenAI OpCo, LLC | US, NO | Artificial intelligence functionality for customer support |
| OpenAI OpCo, LLC | US, NO | LLM Provider |
| OpenAI, LLC | — | — |
| OpenAI, LLC | — | AI chat functionality |
| Segment (Twilio, Inc.) | US | Customer Data Platform |
| Segment (Twilio, inc.) | — | customer data platform |
| Service Cloud (Salesforce, Inc.) | US | Customer and sales support |
| Service Cloud (Salesforce, Inc.) | — | customer and sales support |
| Tableau Software, LLC (Salesforce, Inc.) | US | Analytics and Data Visualization |
| Tray.io | — | — |
| Tray.io | US | Integration infrastructure provider |
| Vimeo, LLC | US | Video messaging |
Asana's own group companies listed as subprocessors (17)
| Company | Country | Purpose |
|---|---|---|
| Asana France SAS | FR | — |
| Asana Germany Gmbh | DE | — |
| Asana Ireland Technology Limited | IE | — |
| Asana Japan KK | JP | — |
| Asana Poland sp. z o.o | PL | — |
| Asana Poland sp. z o.o | — | — |
| Asana Software Australia Pty Ltd | AU | — |
| Asana Software Canada Ltd | CA | — |
| Asana Software Iceland ehf | IS | — |
| Asana Software Ireland Limited | IE | — |
| Asana Software Singapore Pte Ltd | SG | — |
| Asana Software UK Limited | GB | — |
| Asana Switzerland GmbH | CH | — |
| Asana Switzerland GmbH | CH | — |
| Asana, Inc. | US | — |
| Eigen, Inc. dba StackAI | US | — |
| KMC Solutions | PH | — |
The count outside the EEA is arithmetic over the country column, not a judgement about lawfulness. A transfer outside the EEA can be perfectly lawful; whether this one is depends on your use, not on the vendor.
Every subprocessor in the registry, and which vendors name it: subprocessors.
Processing terms
From the vendor's data processing agreement · read 2026-10-09 · asana.com
| Term | What the agreement says |
|---|---|
| Transfer mechanism | EU-U.S. DPF |
| Transfer mechanism | SCC module 2 |
| Transfer mechanism | SCC module 3 |
| Transfer mechanism | Swiss FADP clauses |
| Transfer mechanism | UK Addendum |
| Notice of new subprocessors | 10 business days before authorization, automatic notice to customers subscribed to updates on the Subprocessors page (in an emergency, as soon as reasonably practicable) |
| If you object to one | Customer may object on reasonable data-protection grounds in writing to dpa@asana.com within 30 days of the notice. Asana will try to offer a change to avoid the subprocessor. If it can't within 30 days, either party may terminate the affected Order Form(s) or the Agreement without penalty |
| Obligations passed to subprocessors | contractual obligations no less protective than this DPA |
| Breach notification | without undue delay or within the time period required under Applicable Law |
| Deletion when the service ends | On termination and a written verified request from Customer's authorized representative, Asana deletes Customer Personal Data unless Applicable Law prohibits it; if no request is received, Asana may delete it in line with Applicable Law |
| Requests from data subjects | Refers individuals who send requests directly to Asana back to Customer (where legally permitted); on Customer's request, uses commercially reasonable efforts to help Customer respond when Customer cannot address the request through its own use of the Service |
| Audit | Annual SOC 2 Type 2 report and evidence of ISO certifications made available to Customer under the Agreement |
| Audit | Audit of records (documentation, certifications, reports) by customer or a mutually agreed auditor at customer's sole expense; 14 days' prior written notice; once a year, more often after a Security Incident. On-site inspection only if written requests are not enough: 21 days' notice, scope agreed in advance, customer bears all costs, once a year except after a Security Incident |
| Audit | Third-party reports: annual external assessments producing a SOC 2 Type 2 report and evidence of ISO certifications, made available to Customer under the Agreement |
| Processing on your instructions | processes Customer Personal Data to provide the Service per the Agreement, on Customer's lawful instructions (Section 3.3), as required by Applicable Law, to de-identify/aggregate for analysis and Service improvement, or as otherwise agreed in writing |
| Confidentiality of staff | authorised persons under written confidentiality agreements or a statutory obligation of confidentiality |
| Security measures | appropriate technical and organizational measures to protect Customer Personal Data |
Terms as the agreement states them. Where it is silent on a term, there is no row; that is not a statement that the vendor does not offer it.
Which version applies
On 2026-11-09, the agreement printed: Last updated: September 1, 2026, Effective Date: 1 September 2026
at asana.com
In effect from 2026-09-01 · Last updated 2026-09-01
This version is in our copies from 2026-10-09.
These terms side by side for every vendor: data processing agreements compared. What vendors give you for a transfer impact assessment: transfer impact assessments.
AI and your data
What Asana's own pages state about the data you send its AI products, plan by plan. Compared with other vendors on AI vendors and your data.
| Plans | Term | What the page says | Source | Observed |
|---|---|---|---|---|
| Business Asana AI | Training on your data | Not used Asana's AI partners do not use customer data to train their models | asana.com | 2026-10-28 |
| Business Asana AI | Training on your data | Not used Neither Asana nor its AI partners use customer data to train AI models | help.asana.com | 2026-10-29 |
| Business Asana AI | Zero data retention | With its model providers AI partners are required to delete customer data after each query | asana.com | 2026-10-28 |
| Business Asana AI | Model providers | AWS Bedrock | help.asana.com | 2026-10-29 |
| Business Asana AI | Model providers | Anthropic | asana.com | 2026-10-28 |
| Business Asana AI | Model providers | Fireworks.ai | help.asana.com | 2026-10-29 |
| Business Asana AI | Model providers | help.asana.com | 2026-10-29 | |
| Business Asana AI | Model providers | OpenAI | asana.com | 2026-10-28 |
Assurance
Does Asana have a SOC 2 report?
Asana states SOC 2 Type 2 on its own page, but does not say there how to get a report. We read this on 2026-10-05.
Of the 114 vendors in this registry whose own pages mention SOC 2, 57 say the report is available on request, 1 links to the report itself, and 56 state it without saying how to get it. The type is the one the vendor names.
Is Asana ISO 27001 certified?
Asana states ISO/IEC 27001 (2022 edition, as Asana names it) on its own page, but does not say there how to get the certificate. We read this on 2026-10-05.
On the same list Asana also names ISO/IEC 27017, ISO/IEC 27018 and ISO/IEC 27701. Each standard's page says how it relates to ISO/IEC 27001.
Of the 122 vendors in this registry whose own pages state ISO/IEC 27001, 16 link to the certificate, 43 say it is available on request, and 63 state it without saying how to get it. A certificate names the certification body, the scope and the expiry date: those are the three things to check.
| Scheme | Status | Scope | Source | Observed |
|---|---|---|---|---|
| California Consumer Privacy Act · CCPA | Claimed | — | asana.com | 2026-10-05 |
| CSA STAR Level 1 · CSA | Claimed | Cloud security controls compliance self-assessment | asana.com | 2026-10-05 |
| GDPR | Claimed | Data protection and data subject rights for EU residents | asana.com | 2026-10-05 |
| General Data Protection Regulation · GDPR | Claimed | — | asana.com | 2026-10-05 |
| HIPAA | Claimed | Protection of patient health information in the United States | asana.com | 2026-10-05 |
| ISO/IEC 27001:2022 · ISO27001 | Claimed | Global standard for information security management systems | asana.com | 2026-10-05 |
| ISO/IEC 27017:2015 · ISO27017 | Claimed | Code of practice for information security controls for cloud services | asana.com | 2026-10-05 |
| ISO/IEC 27018:2019 · ISO27018 | Claimed | Code of practice for protecting personally identifiable information (PII) | asana.com | 2026-10-05 |
| ISO/IEC 27701:2019 · ISO27701 | Claimed | Privacy information management standard supporting compliance with global privacy laws | asana.com | 2026-10-05 |
| APPI and other global privacy laws | Claimed | — | asana.com | 2026-10-05 |
| FERPA | Claimed | Privacy rights for educational information and records | asana.com | 2026-10-05 |
| GLBA | Claimed | Privacy Rule and Safeguards Rule for financial institutions | asana.com | 2026-10-05 |
| US State Privacy Laws | Claimed | Compliant with relevant US state privacy laws in California, Colorado, Virginia, and more | asana.com | 2026-10-05 |
| SOC 2 (Type 2) · SOC2T2 | Claimed | Security, availability, confidentiality, and privacy trust services criteria | asana.com | 2026-10-05 |
| SOC 3 · SOC3 | Claimed | Overview of Service Organization Controls | asana.com | 2026-10-05 |
Claimed means the vendor asserts the scheme on its own page and offers nothing further. Available on request means the report or certificate exists but sits behind a request, a login or an NDA. Neither is a certificate we have seen. That is a distinction an auditor makes, so we make it too.
SecNumCloud, C5, ENS and HDS for every vendor, with the pages for ISO standards, SOC 2 and TISAX: certifications compared.
Official registers
| Register | Offering, as the register names it | Status | Level | Valid until | Observed |
|---|---|---|---|---|---|
| Data Privacy Framework List (US) | EU-U.S. Data Privacy Framework · Asana | Active | non-HR data | 2027-08-12 | 2026-10-07 |
| Data Privacy Framework List (US) | Swiss-U.S. Data Privacy Framework · Asana | Active | non-HR data | 2027-08-12 | 2026-10-07 |
| Data Privacy Framework List (US) | UK Extension to the EU-U.S. DPF · Asana | Active | non-HR data | 2027-08-12 | 2026-10-07 |
| FedRAMP Marketplace (US) | Asana · Asana Inc. | FedRAMP In Process | Moderate | — | 2026-10-07 |
| Global LEI Index (GLEIF) | Asana, Inc. · Asana, Inc. | ISSUED | US-DE | 2027-02-01 | 2026-10-08 |
- ACN qualified cloud (Italy): checked 2026-11-16, no entry under Asana; Asana, Inc.
- ISO 27001 on the basis of IT-Grundschutz (BSI, Germany): checked 2026-11-16, no entry under Asana; Asana, Inc.
- CISPE Data Protection Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under Asana; Asana, Inc.
- DORA critical ICT third-party providers (ESAs): checked 2026-11-16, no entry under Asana; Asana, Inc.
- Data Privacy Framework List (US): checked 2026-11-16, 3 entries under Asana; Asana, Inc.
- ENS certificates of conformity (CCN, Spain): checked 2026-11-16, no entry under Asana; Asana, Inc.
- EU Cloud Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under Asana; Asana, Inc.
- FedRAMP Marketplace (US): checked 2026-11-16, 1 entry under Asana; Asana, Inc.
- GPAI Code of Practice signatories (European Commission): checked 2026-11-16, no entry under Asana; Asana, Inc.
- SecNumCloud qualified services (ANSSI, France): checked 2026-11-16, no entry under Asana; Asana, Inc.
What the authority publishes, not what the vendor claims. An entry covers the offering it names and nothing else: a FedRAMP authorisation for a government edition says nothing about the commercial service. No entry is not a finding about security - most vendors never apply - and an entry filed under a name not listed above would not have been found.
What an entry on the Data Privacy Framework List covers, and which vendors hold one: EU-US Data Privacy Framework.
Support window
| Product | Support period | State | SBOM | Source | Observed |
|---|---|---|---|---|---|
| Asana for iOS | — | Not declared | unknown | help.asana.com | 2026-10-19 |
Vulnerability reporting: bugcrowd.com, security@asana.com (security.txt, expires 2026-12-31; read 2026-10-17)
How other vendors publish theirs: security.txt across the registry.
Documents
Where is Asana's trust center?
Asana publishes a page it calls “Trust Center” at trustcenter.asana.com. Some of its documents sit behind a request or sign-in. The page mentions SOC 2, ISO 27001, a penetration test, subprocessors and security questionnaires. We read it on 2026-11-03. Open trustcenter.asana.com
- Name “This Trust Center provides you with resources demonstrating Asana's continuous commitment to protecting customer data. Below you'll find”
- Request step “Get Access”
Source: trustcenter.asana.com, 2026-11-03. Read from the page's text, without a model; every vendor's trust center.
| Document | Disclosure | Transcription | HTTP | Observed |
|---|---|---|---|---|
| ai | Public | full | 200 | 2026-10-29 |
| ai-2 | Public | full | 200 | 2026-10-28 |
| certifications | Public | full | 200 | 2026-10-05 |
| dpa | Public | full | 200 | 2026-10-09 |
| lifecycle | Public | full | 200 | 2026-10-19 |
| residency | Public | full | 200 | 2026-10-12 |
| subprocessors | Public | full | 200 | 2026-10-05 |
History
Nothing has moved since we started watching this vendor on 2026-10-29. Changes appear here only after a human has reviewed them.
Every reviewed change across the registry, newest first: vendor changes.