Atlassian Product-Specific Terms
Effective starting: April 1, 2024 (unless otherwise indicated below)
The following Product-Specific Terms apply to the Products specified in the table below, and, where Customer orders such Products, supplement the Atlassian Customer Agreement or another agreement entered between Customer and Atlassian (the “Agreement”). Capitalized terms used and not defined in the Product-Specific Terms have the meanings given to them in the Agreement.
The Atlassian contracting entity for each of the Products is specified in the table below and is “Atlassian” for purposes of the relevant terms, the Agreement and any associated Orders.
| Product(s) | Atlassian Contracting Entity | Product-Specific Terms |
| All Products not named elsewhere in this table, including Confluence, Jira* and Rovo | Atlassian Pty Ltd | |
| Jira Align | AgileCraft LLC | |
| Loom | Loom, Inc. | |
| Opsgenie | OpsGenie, Inc. | |
| Statuspage | Dogwood Labs, Inc., d/b/a StatusPage.io | |
| Trello | Trello, Inc. | |
| * Halp functionality is now part of Jira Service Management and may not be purchased separately. Any Customer with a standalone Halp subscription should refer to the Archives (below) for the governing Product-Specific Terms. | ||
Archived versions of the product-specific terms are available here, for Customers that purchased under the Atlassian Cloud Terms of Service or Software License Agreement, and here, for Customers that purchased under an Atlassian Subscription Agreement (or predecessor agreement).
Atlassian Pty Ltd Products
Atlassian Intelligence and Rovo
Effective starting: The earlier of (i) October 6, 2024 and (ii) date of enablement on an existing cloud plan or purchase
1. AI Offerings.
1.1. Atlassian Intelligence and Rovo. Atlassian makes Atlassian Intelligence and Rovo available to customers as described in these Product-Specific Terms (together, the “AI Offerings”).
1.2. Loom AI. Loom AI is not covered by these Product-Specific Terms. It is covered separately, here.
2. Input and Output.
2.1. Atlassian Obligations. Each of the AI Offerings provides Output in response to Input. Input and Output are Customer Data under the Agreement. Atlassian may not use Input or Output to train or improve the AI Offerings across customers. Atlassian will not permit its subcontractors to use Input or Output to train or improve their models.
2.2. Additional Customer Obligations, Restrictions and Disclaimers.
(a) Output Use and Assessment. Customer is responsible for its use of Output, including determining whether Output is appropriate for that use.
(b) Restrictions. Customer must not (and must not permit anyone else to): (i) provide Input that either violates third-party rights or Law or is intended, or would reasonably be expected, to generate Output that does so; (ii) provide Input that includes Personal Data of children under 13 or any age of digital consent under Law; (iii) use Output in a manner that Customer knows, or reasonably should know, violates third-party rights or Law or (iv) represent that Output is human generated or approved or endorsed by Atlassian or its subcontractors.
(c) Disclaimers. Output is generated by artificial intelligence, including by using technology provided by third-party subcontractors. Atlassian makes no warranty as to the accuracy, completeness or reliability of Output or that it does not violate third-party rights or Law. Due to the nature of the AI Offerings, (i) Output may not be unique or exclusive to Customer and its Users, (ii) the same or similar Input may yield differing Output, and (iii) Output does not represent Atlassian’s or its subcontractors’ views.
3. Rovo. This Section 3 applies only to Rovo.
3.1. Connection to Other Products.
(a) Interoperation. Rovo includes features designed to connect and interoperate with other Atlassian Products and Third-Party Products. Atlassian does not make any warranties about future Rovo connection and interoperation with any specific Third-Party Products.
(b) Data Sharing with Third-Party Products. When Customer connects Rovo to a Third-Party Product, Customer may instruct Rovo to send Customer Data and other data to that Third-Party Product. The provider of the Third-Party Product will process that data according to its terms and, when Customer instructs, will send data back to Rovo. Data sent to Rovo may continue to be subject to the third party’s terms and is subject to the Agreement.
3.2. Agents.
(a) In General. Agents are features of Rovo that Users may direct to take certain actions on behalf of Customer (“Agents”). These actions are not Output. Agents may be provided by third parties as Third-Party Products, Customer or Atlassian.
(b) Additional Customer Obligations and Restrictions. Customer is responsible for its use of Agents, including determining whether any actions Agents may take are appropriate for that use. Customer must not use Agents in a manner that either violates third-party rights or Law or is intended, or would reasonably be expected, to do so.
3.3. Scope of Use. As described in the Documentation, Customer’s Scope of Use may vary by Rovo feature.
3.4. Output Indemnification. This Section 3.4 applies only when Customer has an active, paid-up subscription to Rovo at the time of the first event out of which the Output Claim arose.
(a) Indemnification. Atlassian will defend Customer from and against any third-party claim to the extent alleging that Output of Rovo, when used by Customer as authorized by the Agreement, directly infringes any copyright of a third party (an “Output Claim”) and indemnify and hold harmless Customer against any damages, fines or costs finally awarded by a court of competent jurisdiction (including reasonable attorneys’ fees) or agreed in settlement by Atlassian resulting from an Output Claim.
(b) Procedures. Atlassian’s obligations in Section 3.4(a) (Indemnification) are subject to Customer providing Atlassian: (i) sufficient notice of the Output Claim so as to not prejudice Atlassian’s defense of the Output Claim, (ii) the exclusive right to control and direct the investigation, defense and settlement of the Output Claim, and (iii) all reasonably requested cooperation (including preserving and sharing the relevant Input and Output), at Atlassian’s expense for reasonable out-of-pocket expenses. Customer may participate in the defense of an Output Claim with its own counsel at its own expense.
(c) Settlement. Customer may not settle an Output Claim without Atlassian’s prior written consent. Atlassian may not settle an Output Claim without Customer’s prior written consent if settlement would require Customer to admit fault or take or refrain from taking any action (other than relating to use of the Output or Rovo).
(d) Exceptions. Atlassian’s obligations in this Section 3.4 do not apply:
(i) where Customer does not have an active, paid-up subscription to Rovo at the time of the first event out of which the Output Claim arose or
(ii) to the extent an Output Claim arises from: (A) Customer’s breach of the Agreement (which includes the Acceptable Use Policy) or unauthorized use of Output or Rovo; (B) Customer’s modification of Output; (C) use of Output in combination with items not provided by Atlassian (including Third-Party Products); (D) Output that, or its use in a manner that, Customer knew, or reasonably should have known, was likely to violate the third-party rights or Laws that are the subject of the Output Claim; (E) any use of Output after Atlassian has instructed Customer to cease use or after Customer has received notice of alleged infringement; or (F) Third-Party Products or their output, Input or other non-Output Customer Data or Customer Materials.
(e) Limitation of Liability and Exclusive Remedy. To the maximum extent permitted by Law, Atlassian’s entire liability arising out of or related to all Output Claims will not exceed in aggregate the amounts paid to Atlassian for Rovo during the twelve (12) months preceding the first event out of which an Output Claim arose. This Section 3.4 sets out Customer’s exclusive remedy and Atlassian’s entire liability regarding Output.
4. Definitions.
“Atlassian Intelligence” means the artificial intelligence features made available by Atlassian as part of certain Cloud Products and plans, including those features labeled or identified by Atlassian as Atlassian Intelligence. Atlassian Intelligence is a set of features and is not a standalone Cloud Product.
“Input” means any input (for instance, textual, audiovisual or other content) Customer or a User provides or makes available to an AI Offering.
“Output” means any output (for instance, textual, audiovisual or other content) generated and returned to Customer or a User by an AI Offering based on Input.
“Rovo” means the artificial intelligence features made available by Atlassian as a standalone Cloud Product(s) that is labeled or identified by Atlassian as Atlassian Rovo or Rovo.
Other Products
1. Secondary Users. As described in the Documentation, certain of the Products may be used as part of Customer’s external support or similar resources related to its or its Affiliates’ own offerings. End users for such resources are Users under the Agreement. Customer must not permit such Users to use the Products for purposes unrelated to supporting its own offerings or grant such Users administrator, configuration or similar use of the Products.
2. Additional Software Terms. For clarity, importing a back-up from an authorized production instance of one of the Products that is a Software Product into an authorized staging environment of such Software Product does not itself violate the requirement in the “Number of Instances” Section of the Agreement. Atlassian may also make available “developer” licenses for certain of such Software Products to allow Customer to deploy non-production instances, such as for staging or QA purposes.
3. Additional Bitbucket Cloud Terms. The following additional terms apply to Bitbucket Cloud.
3.1. Repositories. Customer Data uploaded to Bitbucket Cloud is stored in “repositories.” Customer must designate whether the repositories are public (meaning that anyone coming to the Bitbucket website can view them) or private (meaning that access to those repositories will be limited to those who have permission to access the repositories). For each public repository that Customer maintains, Customer must indicate the license under which Customer is making the contents of the repository available to others, as well as the license under which Customer will accept contributions to the repository.
3.2. Storage Rules. The Documentation specifies pre-defined storage limits for Customer Data. For clarity, Atlassian may enforce those limits in accordance with the Agreement and the Acceptable Use Policy. Similarly, Atlassian may remove Customer Data from Bitbucket Cloud under the Agreement and Acceptable Use Policy where that content is consuming an unreasonable amount of storage in a way that is unrelated to Bitbucket Cloud’s purpose as a source code repository (for instance, music, abhorrent content, videos or pornography). Since Atlassian does not maintain access to Customer’s repositories, any removal of Customer Data by Atlassian means removal of the entire repository in which the offending data resides, not just the offending portions.
3.3. Accessing Repositories. If Customer is accessing code in a third party’s repository, Customer should carefully read all the licenses applicable to that repository before using or contributing any code. Atlassian is not the licensor of any third-party code made available through Bitbucket and is not responsible for the use or contents of such code.
3.4. Granting Permissions. When Customer grants permissions to its repositories, Atlassian will not be able to prevent the applicable users from taking the actions allowed under those permissions, even if Customer does not approve of those actions. Some of these actions may be irreversible. For example, if Customer grants someone permission that allows them to move data in Customer’s repository to another account, Atlassian will not be able to recover the data without permission from the owner or administrator of the other account, as Atlassian is not in a position to arbitrate disputes among users. In that case, Customer’s only recourse may be requesting a takedown under the guidelines for Reporting Copyright and Trademark Violations or pursuing legal action against the other user directly. For clarity, submitting a takedown request does not grant Customer access to the moved data or mean Atlassian can transfer that data back to Customer’s repository.
Jira Align
1. Interoperation with Third-Party Products. As an enterprise agility tool, Jira Align contains functionality or features designed to interoperate with, or that are contingent on access to or use of, other products, some of which may be provided by third parties. For clarity, Atlassian does not control and is not responsible for Customer’s use of any such Third-Party Products.
2. Return Policy. If Customer exercises its rights under the “Return Policy” Section of the Agreement with respect to its initial Order of Jira Align, Atlassian will refund Customer any pre-paid, unused fees for Advisory Services for Jira Align purchased as part of such initial Order (and any corresponding Subscription Terms or consumption periods for such Advisory Services will be terminated).
3. Service Level Agreement for Jira Align Cloud.
3.1. Service Level Commitment. Atlassian must make Jira Align Cloud accessible to one or more Users at least 99.5% of the time during a calendar month (the “Service Level Commitment”).
3.2. Service Credit Eligibility. To be eligible to receive a service credit for Atlassian’s failure to meet the Service Level Commitment, Customer must submit a ticket at https://support.atlassian.com with all fields fully and accurately completed within thirty (30) days after the end of the calendar month in which the alleged failure occurred and provide any other reasonably requested information or documentation. Atlassian’s monitoring and logging infrastructure is the sole source of truth for determining whether Atlassian has met the Service Level Commitment.
3.3. Service Credit Issuance. If Atlassian confirms a failure to meet the Service Level Commitment, Atlassian will apply the service credit (calculated as described in the table below) against a future payment due from Customer for Jira Align, provided that Customer’s account is fully paid-up, without any overdue payments or disputes. No refunds or cash value will be given for unused service credits. Service credits may not be transferred or applied to any other Atlassian account or Product. The aggregate maximum service credit applied to an invoice will not exceed 100% of the amount invoiced for Jira Align in that invoice billing period (which, since service credits are applied to future payments, is not the month in which Jira Align was unavailable).
| Monthly Uptime Percentage* | Service Credit (% of the monthly fees) | |
| Less than 99.5% but greater than or equal to 98.0% | 5% | |
| Less than 98.0% but greater than or equal to 95.0% | 10% | |
| Less than 95.0% | 15% | |
| * The monthly uptime percentage is determined by subtracting from 100% the percentage of minutes that Jira Align did not meet the Service Level Commitment out of the total minutes in the relevant calendar month. All calendar months are measured in the UTC time zone. | ||
3.4. Service Credits and Reseller Purchases. If Customer purchased Jira Align through a Reseller, (a) Customer or the Reseller may submit a ticket as specified above; and (b) any service credits will be based on the fees invoiced by Atlassian to the Reseller for Customer’s use of Jira Align under the Reseller’s applicable order(s) with Atlassian. Atlassian will issue any associated service credits to the Reseller (not directly to Customer), and the Reseller will be solely responsible for issuing the appropriate amounts to Customer.
3.5. Exclusions. Customer is not entitled to a service credit if Customer is in breach of the Agreement or has not provisioned Jira Align. The Service Level Commitment does not include unavailability to the extent due to (a) Customer’s use of Jira Align in a manner not authorized under the Agreement; (b) force majeure events or other factors outside of Atlassian’s reasonable control, including internet access or related problems; (c) Customer equipment, software, network connections or other infrastructure; (d) Customer Data or Customer Materials (or similar concepts defined in the Agreement); (e) Third-Party Products; or (f) routine scheduled maintenance or reasonable emergency maintenance as stated in the Atlassian Maintenance Policy. The Service Level Commitment does not apply to (i) sandbox instances or Free or Beta Products (or similar concepts in the Agreement) or (ii) features excluded from the Service Level Commitment in the applicable Documentation.
3.6. Exclusive Remedy. Service credits are Customer’s exclusive remedy and Atlassian’s entire liability for Atlassian’s failure to meet the Service Level Commitment.
4. Support for Jira Align Software. If Customer uses Jira Align as a Software Product, Customer must remain on the most recent release or the immediately prior release of Jira Align. Prior releases are not supported.
Loom
1. Support, Specific Policies, and Documentation. For purposes of Loom:
1.1. Support Policy. “Support Policy” means the Loom support offerings documentation available here.
1.2. Return Policy. The “Return Policy” Section of the Agreement does not apply to Loom.
1.3. Documentation. “Documentation” means the content located here.
1.4. “Services.” On any URL referenced in these Product-Specific Terms that is a child page of www.loom.com or www.loom.com/support, the term “Services” is replaced by the term “Loom.”
2. Loom AI. Customer’s use of any features or functionality made available as part of Loom or labeled as Loom AI that utilize data models trained by machine learning (“Loom AI”) is subject to the following additional terms.
2.1. Definitions.
“Input” means any input provided by Customer or Users to be processed by Loom AI.
“Loom AI Suite” means the suite of Loom AI offerings as outlined on Loom’s website, in the Documentation, or in the applicable Order for the Loom AI Suite.
“Output” means any output generated and returned to Customer or its Users by Loom AI based on the Input.
2.2. Customer Responsibilities.
(a) Input and Output. Input and Output are Customer Data. Customer must ensure that its Input, Output, and use of Loom AI does not (i) violate any Law; (ii) violate the Agreement or an applicable Order; or (iii) infringe, violate, or misappropriate any Atlassian or third-party rights. Customer acknowledges that due to the nature of machine learning and the technology powering Loom AI, Output may not be unique, and Loom AI may generate the same or similar output for third parties.
(b) Restrictions. Customer must not use Loom AI: (i) to mislead any person that Output was solely human generated; or (ii) in violation of OpenAI’s Usage Policy, or any other third party terms, guidelines, policies or the like to which Loom links in connection with generation of Output.
2.3. Disclaimer. Atlassian does not make any warranty as to Loom AI, Output, the results that may be obtained from the use of Loom AI or the accuracy of any information obtained through Loom AI, including with respect to the factual accuracy of any Output or suitability for Customer’s use case. Use of any material and/or data obtained through the use of any Loom AI feature is at Customer’s sole risk. Customer should not rely on factual assertions in Output without independently fact checking their accuracy. No information or advice, whether oral or written, obtained by Customer from Atlassian or through Loom AI creates any such warranty.
Opsgenie
1. Intended Use. Opsgenie is not intended for providing alerts on disaster scenarios or any other situations directly related to health or safety, including but not limited to acts of terrorism, natural disasters, or emergency responses, and Customer must not use Opsgenie for any such purposes.
2. Service Level Agreement for Opsgenie.
2.1. Service Level Commitment. Atlassian must make Opsgenie available at least 99.9% of the time during a calendar month (the “Service Level Commitment”).
2.2. Service Credit Eligibility. To be eligible to receive a service credit for Atlassian’s failure to meet the Service Level Commitment, Customer must open a case in the Opsgenie support center by the end of the second billing cycle after the cycle in which the incident occurred and provide the date and time of each alleged failure to meet the Service Level Commitment and any other reasonably requested information or documentation. Atlassian’s monitoring and logging infrastructure, which consists of both internal and third party services, is the sole source of truth for determining whether Atlassian has met the Service Level Commitment.
2.3. Service Credit Issuance. If Atlassian confirms a failure to meet the Service Level Commitment, Atlassian will apply the service credit (calculated as described in the table below) against a future payment due from Customer for Opsgenie, provided that Customer’s account is fully paid up, without any overdue payments or disputes. No refunds or cash value will be given for unused service credits. A service credit will be issued only if the credit amount for the applicable calendar month is greater than one U.S. dollar ($1 USD). Service credits may not be transferred or applied to any other Atlassian account or Product. The aggregate maximum service credit applied to an invoice will not exceed 100% of the amount invoiced for Opsgenie in that invoice billing period (which, since service credits are applied to future payments, is not the month in which Opsgenie was Unavailable (as defined below)).
| Monthly Uptime Percentage* | Service Credit (% of the monthly fees) | |
| Less than 99.9% but greater than or equal to 99.0% | 5% | |
| Less than 99% but greater than or equal to 97.0% | 10% | |
| Less than 97.0% | 20% | |
| * The monthly uptime percentage is determined by subtracting from 100% the percentage of Unavailable minutes out of the total minutes in the relevant calendar month. All calendar months are measured in the UTC time zone. “Unavailable” means that Opsgenie was not able to process incoming alerts and send notifications within five (5) minutes of receiving the alerts, according to the policies and notification rules defined by Customer within the Opsgenie service. | ||
2.4. Service Credits and Reseller Purchases. If Customer purchased Opsgenie through a Reseller, (a) Customer or the Reseller may open a case as specified above; and (b) any service credits will be based on the fees invoiced by Atlassian to the Reseller for Customer’s use of Opsgenie under the Reseller’s applicable order(s) with Atlassian. Atlassian will issue any associated service credits to the Reseller (not directly to Customer), and the Reseller will be solely responsible for issuing the appropriate amounts to Customer.
2.5. Exclusions. Customer is not entitled to service credits if Customer is in breach of the Agreement or has not provisioned Opsgenie. The Service Level Commitment does not include unavailability to the extent due to: (a) Customer’s use of Opsgenie in a manner not authorized under the Agreement; (b) force majeure events or other factors outside of Atlassian’s reasonable control, including internet access or related problems; (c) Customer equipment, software, network connections or other infrastructure; (d) Customer Data or Customer Materials (or similar concepts defined in the Agreement); (e) Third-Party Products; or (f) routine scheduled maintenance. The Service Level Commitment does not apply to (i) sandbox instances or Free or Beta Products (or similar concepts in the Agreement) or (ii) features excluded from the Service Level Commitment in the applicable Documentation.
2.6. Exclusive Remedy. Service credits are Customer’s exclusive remedy and Atlassian’s entire liability for Atlassian’s failure to meet the Service Level Commitment.
Statuspage
1. Status Pages and Scope of Use.
1.1. Status Pages. Statuspage enables Customer to create pages hosted by Atlassian that display both current and historical status and uptime information of Customer’s products and services, while also allowing Users to subscribe to status notifications (“Status Pages”). There are different types of Status Pages and different subscription plans for each of these page types. This includes Status Pages that are available to the public, meaning they are not confidential or private to Customer.
1.2. Scope of Use. Customer’s Scope of Use (and the related fees) may vary depending on Status Page type and plan. See more information here.
2. Status Page Configuration. As described in the Documentation, Customer may configure its Status Pages by including look and feel elements (like company brand or logo) and any links or permissions required to collect information from individuals (internal or external to Customer) who view a Status Page (“Statuspage End Users”) or for these individuals to acknowledge that they are subscribing to status notifications (collectively, “Customer Configurations”). Customer Configurations are “Customer Data” under the Agreement.
3. Collection of Statuspage End User Information. As discussed above, Statuspage allows Customer to collect information from Statuspage End Users in order to send these end users status notifications. This may include email addresses and phone numbers. Statuspage End Users are Customer’s Users under the Agreement, and any information collected about Customer’s Statuspage End Users is “Customer Data” under the Agreement.
Trello
1. Settings, Profile Information and Free Plans.
1.1. Settings and Profile Information. Trello permits users to collaborate via workspaces, boards and cards and includes certain membership and privacy settings that may differ according to Customer’s Trello plan. These settings may include designating who can access or view Customer’s Trello workspaces, boards and cards. Customer is responsible for configuring these settings. For instance, where a workspace is “public,” it is available to the public, meaning it (and any Customer Data it contains) is not confidential or private to Customer. In addition, profile information within Trello (for instance, a User’s username, full name, avatar and bio) is available to the public.
1.2. Free Plans. For clarity, the Subscription Term for free Trello plans continues until the applicable plan (and any associated workspace) is terminated.
2. Account Activity. Atlassian may make boards “private” where Atlassian would otherwise have rights to limit access to or remove Customer Data or suspend access to Trello under the Agreement. Atlassian may create limits on use and storage at any time with or without notice for free Trello plans. If Customer’s plan is terminated, Atlassian may withdraw and reallocate the public web address of the corresponding workspace(s). Atlassian may also log off users who are inactive for an extended period of time.
3. Power-Ups and Featured Power-Ups.
3.1. Power-Ups. Atlassian may make available or provide links to optional tools and other features or services that Customer may enable for use with Trello, called “Power-Ups” (“Power-Ups”). Power-Ups may be provided by third parties (“Third-Party Power-Ups”) or by Atlassian (“Trello Power-Ups”). Third-Party Power-Ups are Third-Party Products, and Trello Power-Ups are Free or Beta Products. There may be limits on the number of Power-Ups Customer may use based on Customer’s applicable Trello plan. For certain Power-Ups, Customer must obtain a subscription to the third-party product or service integrated with Trello or pay a fee to enable the Third-Party Power-Up. Atlassian or the third-party provider of a Power-Up may update, modify or remove the Power-Up at any time. Atlassian does not make any promises or guarantees about future price, availability or functionality of Power-Ups.
3.2. Featured Power-Ups. From time to time, Atlassian may feature certain Power-Ups more prominently than others on its website (for instance, by designating Power-Ups as “Featured,” “Essential” or “Taco’s Picks”). This may be based on popularity in the Trello community or positive user reviews. In so featuring a Power-Up, Atlassian does not endorse, or make any warranty or guarantee regarding, the Power-Up.
Related content
Stay informed
Subscribe to receive notifications from us about updates to our legal terms (including our legal policies) and our list of sub-processors.