Paradraw
38 published7 named, not published0 expected, not published184 relationships3588 clauses
Every legal document Asana publishes, and the ones its own terms name that nobody published. Free to read.Other companies
HighStructure

Asana Subscriber Terms — subscriber terms 120324 reads as part of the agreement, and nothing in the set refers to it

Asana Subscriber Terms — subscriber terms 120324 is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

Wrong? Ask for access to correct it.

HighStructure

Asana Subscriber Terms — subscriber terms052824 reads as part of the agreement, and nothing in the set refers to it

Asana Subscriber Terms — subscriber terms052824 is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

Wrong? Ask for access to correct it.

HighStructure

Asana Licensed Software Terms • Asana reads as part of the agreement, and nothing in the set refers to it

Asana Licensed Software Terms • Asana is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

Wrong? Ask for access to correct it.

HighStructure

Partner Program Terms • Asana is drafted as if it could incorporate Asana Developer Sandbox Terms of Use

Partner Program Terms • Asana is a perimeter and Asana Developer Sandbox Terms of Use is part of the agreement. cl. 2.4 reads: "Partner acknowledges that any Partner use of the Asana Service in connection with the Agreement is subject to the terms of the Subscriber Terms, User Terms of Service, and any applicable Additional Product Specific Terms and agrees to abide by all terms therei…"

  • PPTA cl. 2.4

    “2.4 Access to Asana Services. Partner acknowledges that any Partner use of the Asana Service in connection with the Agreement is subject to the terms of the Subscriber Terms, User Terms of Service, and any applicable Add…”

  • UT — first clause

    “Legal”

Wrong? Ask for access to correct it.

HighStructure

Partner Program Terms • Asana is drafted as if it could incorporate Data Security Standards

Partner Program Terms • Asana is a perimeter and Data Security Standards is a notice document. ¶80 reads: "Partner also agrees to review, acknowledge and comply with applicable provisions in Asana's Partner Data Security Standards available at https://asana.com/terms/solutions-partner-data-security, as updated by Asana from time to time at its sole discretion, whic…"

  • PPTA ¶80

    “All capitalized terms in this Section 7: Data Security and Privacy that are not defined in the Agreement shall have the meaning as set forth in the Asana Data Processing Addendum available at https://asana.com/terms/solu…”

  • DSS — first clause

    “Security”

Wrong? Ask for access to correct it.

HighStructure

Asana's commitment to privacy • Asana is drafted as if it could incorporate Data Processing Addendum

Asana's commitment to privacy • Asana is a public notice and Data Processing Addendum is part of the agreement. ¶30 reads: "We also work to ensure our agreements with our customers are up to date-our Data Processing Addendum incorporates the latest data privacy frameworks between the US and EU, United Kingdom, and Switzerland as well as the EU and UK Standard Contractual Clauses, w…"

  • ACPA ¶30

    “We also work to ensure our agreements with our customers are up to date-our Data Processing Addendum incorporates the latest data privacy frameworks between the US and EU, United Kingdom, and Switzerland as well as the E…”

  • DPA — first clause

    “Privacy”

Wrong? Ask for access to correct it.

HighStructure

Asana Certification Program Terms • Asana is drafted as if it could incorporate Privacy Policy

Asana Certification Program Terms • Asana is a perimeter and Privacy Policy is a notice document. ¶3 reads: "Your participation in the Certification Program is subject to these Asana Certification Program Terms ("Certification Terms") along with Asana's User Terms of Service, Subscriber Terms, and Privacy Policy, which constitute a legal agreement between the individ…"

  • ACPT ¶3

    “Welcome to the Asana Certification Program ("Certification Program"). Your participation in the Certification Program is subject to these Asana Certification Program Terms ("Certification Terms") along with Asana's User …”

  • PP — first clause

    “Your privacy is important to us. This Privacy Policy explains our practices regarding the collection, use and disclosure of information that we receive through our Services. This Privacy Policy does not apply to any thir…”

Wrong? Ask for access to correct it.

HighStructure

Asana Certification Program Terms • Asana is drafted as if it could outrank Asana Event Terms and Conditions

Asana Certification Program Terms • Asana is a perimeter and Asana Event Terms and Conditions is part of the agreement. ¶3 reads: "If there is a conflict between the Certification Terms and the User Terms of Service or Subscriber Terms, the Certification Terms will control with respect to all matters related to Your participation in the Certification Program."

  • ACPT ¶3

    “Welcome to the Asana Certification Program ("Certification Program"). Your participation in the Certification Program is subject to these Asana Certification Program Terms ("Certification Terms") along with Asana's User …”

  • TOS — first clause

    “Asana Event Terms and Conditions”

Wrong? Ask for access to correct it.

HighStructure

Asana Certification Program Terms • Asana is drafted as if it could outrank Asana Developer Sandbox Terms of Use

Asana Certification Program Terms • Asana is a perimeter and Asana Developer Sandbox Terms of Use is part of the agreement. ¶3 reads: "If there is a conflict between the Certification Terms and the User Terms of Service or Subscriber Terms, the Certification Terms will control with respect to all matters related to Your participation in the Certification Program."

  • ACPT ¶3

    “Welcome to the Asana Certification Program ("Certification Program"). Your participation in the Certification Program is subject to these Asana Certification Program Terms ("Certification Terms") along with Asana's User …”

  • UT — first clause

    “Legal”

Wrong? Ask for access to correct it.

HighStructure

StackAI Data Processing Addendum • Asana reads as part of the agreement, and nothing in the set refers to it

StackAI Data Processing Addendum • Asana is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

Wrong? Ask for access to correct it.

HighStructure

Asana Partner Data Processing Addendum reads as part of the agreement, and nothing in the set refers to it

Asana Partner Data Processing Addendum is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

Wrong? Ask for access to correct it.

HighStructure

API Terms — developer terms reads as part of the agreement, and nothing in the set refers to it

API Terms — developer terms is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

Wrong? Ask for access to correct it.

HighStructure

API Terms — api terms reads as part of the agreement, and nothing in the set refers to it

API Terms — api terms is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

Wrong? Ask for access to correct it.

HighStructure

Asana Product-Specific Terms • Asana reads as part of the agreement, and nothing in the set refers to it

Asana Product-Specific Terms • Asana is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

Wrong? Ask for access to correct it.

HighStructure

Asana Subscriber Terms — subscriber terms reads as part of the agreement, and nothing in the set refers to it

Asana Subscriber Terms — subscriber terms is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

Wrong? Ask for access to correct it.

HighStructure

Asana Subscriber Terms — subscriber terms 052026 reads as part of the agreement, and nothing in the set refers to it

Asana Subscriber Terms — subscriber terms 052026 is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

Wrong? Ask for access to correct it.

HighPrecedence

Subscriber Agreement reads as a commitment, but nothing incorporates it into the agreement

Asana Privacy Statement — privacy statement 101123 ¶11 mentions Subscriber Agreement. No clause anywhere in the published set states that Subscriber Agreement forms part of the agreement.

  • APSP ¶11

    “In situations where our users are subject to our Subscriber Agreement, Enterprise Master Services Agreement, or other Master Services Agreement to use Asana's services, Asana is the processor/service provider (a provider…”

  • SA — first clause

    “Subscriber Agreement”

Wrong? Ask for access to correct it.

HighStructure

Asana Subscriber Terms — subscriber terms040123 reads as part of the agreement, and nothing in the set refers to it

Asana Subscriber Terms — subscriber terms040123 is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

Wrong? Ask for access to correct it.

HighStructure

Asana Business Associate Addendum reads as part of the agreement, and nothing in the set refers to it

Asana Business Associate Addendum is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

Wrong? Ask for access to correct it.

HighStructure

Vendor Security Standards Addendum • Asana reads as part of the agreement, and nothing in the set refers to it

Vendor Security Standards Addendum • Asana is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

Wrong? Ask for access to correct it.

HighStructure

Public Entity Addendum to Asana Subscriber Terms reads as part of the agreement, and nothing in the set refers to it

Public Entity Addendum to Asana Subscriber Terms is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

Wrong? Ask for access to correct it.

HighStructure

Asana EU Data Act Addendum • Asana reads as part of the agreement, and nothing in the set refers to it

Asana EU Data Act Addendum • Asana is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

Wrong? Ask for access to correct it.

HighStructure

Command by Asana MCP Terms • Asana reads as part of the agreement, and nothing in the set refers to it

Command by Asana MCP Terms • Asana is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

Wrong? Ask for access to correct it.

MediumDrafting

“Non-Production Versions” is used 45 times across 8 documents and no published document defines it

The published set uses the capitalised term “Non-Production Versions” 45 times, in 8 documents that create obligations: Asana Subscriber Terms — subscriber terms, Asana Subscriber Terms — subscriber terms 052026, Asana Subscriber Terms — subscriber terms 120324, Asana Subscriber Terms — subscriber terms052824, Asana Licensed Software Terms • Asana, Subscriber Agreement, Asana Subscriber Terms — subscriber terms040123 and Asana EU Data Act Addendum • Asana. Searching all 38 published documents for a definition of it — in each of the forms this set uses elsewhere: (the “Non-Production Versions”), (“Non-Production Versions”), and “Non-Production Versions” means — returns nothing.

Searched 38 documents, 3,588 clauses. No match.

Wrong? Ask for access to correct it.

MediumGap

PP names a Law Enforcement Guidelines we could not find published

Asana Privacy Statement — privacy statement 010120 ¶45 refers to a Law Enforcement Guidelines. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.

  • PP ¶45

    “To comply with a valid legal subpoena, request, or other lawful process that meets the requirements of the Customer Agreement and our Law Enforcement Guidelines”

Wrong? Ask for access to correct it.

MediumGap

APSP names a Community Terms we could not find published

Asana Privacy Statement — privacy statement § public forums refers to a Community Terms. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.

  • APSP § public forums

    “Public Forums. Our public forums, such as the Asana community forum, make it possible for you to upload and post comments or feedback publicly with other users. Any information that you submit through such public forums …”

Wrong? Ask for access to correct it.

MediumGap

PP names a Google User Data Policy we could not find published

Privacy Policy ¶78 refers to a Google User Data Policy. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.

  • PP ¶78

    “The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.”

Wrong? Ask for access to correct it.

MediumGap

ATDT names 2 documents we could not find published

API Terms — developer terms cl. 2.3 names Asana Brand Guidelines and Attribution Guidelines. None appears in the sitemap, the legal index or the trust centre. They may exist and be available on request.

  • ATDT cl. 2.3

    “Trademarks. Subject to your compliance with these Terms, we grant you a license to reproduce and display the appropriate Asana names, logos and trademarks designated in the Asana Brand Guidelines (the "Asana Marks") (i) …”

Wrong? Ask for access to correct it.

MediumGap

PEAA names a Agreement terms we could not find published

Public Entity Addendum to Asana Subscriber Terms cl. 50 refers to a Agreement terms. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.

  • PEAA cl. 50

    “L. Further Amendment. Asana may unilaterally revise the Agreement terms if such revisions are not material. A material revision is defined as: (a) terms that change the Public Entity's rights or obligations; (b) terms th…”

Wrong? Ask for access to correct it.

MediumGap

PPTA relies on a statement of work that is not published

Partner Program Terms • Asana cl. 4.4 relies on a statement of work. No statement of work was found anywhere in the published set.

  • PPTA cl. 4.4

    “4.4 Payments to Partner. If applicable, Asana agrees to pay fees to Partner, in accordance with the Partner Program Guide, for (a) a referral, (b) commission from a sales-assist activity, (c) other applicable payments, o…”

Wrong? Ask for access to correct it.

LowStructure

Asana Privacy Statement — privacy statement is published but no other document refers to it

Asana Privacy Statement — privacy statement sits in the published set with no incoming reference from any other document in the corpus.

Wrong? Ask for access to correct it.

LowStructure

Asana Privacy Statement — privacy statement 101123 is published but no other document refers to it

Asana Privacy Statement — privacy statement 101123 sits in the published set with no incoming reference from any other document in the corpus.

Wrong? Ask for access to correct it.

LowStructure

Asana Privacy Statement — privacy statement 121521 is published but no other document refers to it

Asana Privacy Statement — privacy statement 121521 sits in the published set with no incoming reference from any other document in the corpus.

Wrong? Ask for access to correct it.

LowStructure

Partner Program Terms • Asana is published but no other document refers to it

Partner Program Terms • Asana sits in the published set with no incoming reference from any other document in the corpus.

Wrong? Ask for access to correct it.

LowStructure

Asana's commitment to privacy • Asana is published but no other document refers to it

Asana's commitment to privacy • Asana sits in the published set with no incoming reference from any other document in the corpus.

Wrong? Ask for access to correct it.

LowStructure

Asana Certification Program Terms • Asana is published but no other document refers to it

Asana Certification Program Terms • Asana sits in the published set with no incoming reference from any other document in the corpus.

Wrong? Ask for access to correct it.

LowStructure

DMCA Policy is published but no other document refers to it

DMCA Policy sits in the published set with no incoming reference from any other document in the corpus.

Wrong? Ask for access to correct it.

Held back

16 readings, on top of the 37 above

Each puts two clauses side by side that answer the same question differently, and quotes both.

Sign up free — €5 of free drawing credit, enough for your first drawing — and come back here to unlock them.

The drawing, in words

Asana’s legal documents

Asana publishes 38 legal documents. Its own terms name 7 more that we could not find published. Every cross-reference inside them resolves.

Published 38

Named, not published 7

  • Law Enforcement Guidelines
  • Community Terms
  • Google User Data Policy
  • Asana Brand Guidelines
  • Attribution Guidelines
  • Agreement terms
  • Statement of work

Named in Asana’s own terms and not found in its sitemap, legal index or trust centre. It may exist and be available on request.

How they connect 105

  • 31 times a document cite another document
  • 29 times a document incorporate another by reference
  • 17 times a document depend on another existing
  • 16 times a document say which document wins on a conflict
  • 9 times a document rely on a definition from another
  • 2 times a document replace another
  • 1 time a document amend another

Read from asana.com on 8 October 2026. A description of how the documents fit together, not legal advice. Is this your company?