Script Studio for Jira Cloud - Terms of Service

Script Studio for Jira — Terms of Service

Using this Agreement

Standard Agreement. This Terms of Service ("Standard Agreement") sets forth the terms and conditions under which BranchCreation S.L.U. ("Provider") makes available subscriptions to Script Studio for Jira, a Cloud Service offered through a listing on the Atlassian Marketplace (each, a "Product"). Provider may add or modify terms ("Additional Terms") or add attachments by stating so in its Marketplace listing. Any Additional Terms and Attachments are collectively "Provider-Specific Terms." Capitalized terms are defined in context or in the Definitions section below.

Entering the Agreement. Customer and Provider agree to this Standard Agreement and any Provider-Specific Terms (collectively, the "Agreement") upon Customer's first entry into an Order ("Effective Date").

Orders. As specified on the Atlassian Marketplace, an Order may be between Customer and Atlassian (or another reseller or agent of Provider) or directly with Provider. Each Order creates a separate Agreement between Provider and Customer, but Orders do not become part of the Agreement.

Order of Precedence. In the event of a conflict between the elements making up the Agreement, the order of precedence is: (i) any Amendment, (ii) Provider-Specific Terms, (iii) this Standard Agreement.

Products

Cloud Service. Subject to this Agreement, Customer may use Script Studio for Jira for its own business purposes in accordance with the Permitted Use. The Product is an administrator workbench on Jira Cloud: authorized Jira administrators write TypeScript (or JavaScript), store it on Atlassian Forge for that installation, and may run or publish it as a manual run, a schedule, a Jira event, a scripted field, a workflow rule, a REST endpoint, or a UI modification.

Users. Customer may permit Users to use the Product on its behalf. Publishing a script, a schedule, an event, a field, a workflow rule, a REST endpoint, or a UI modification requires Jira Administer permission. Customer is responsible for who it makes a Jira administrator, for those Users' scripts and for the effects those scripts have on Jira and on third parties. Customer will ensure Users keep login credentials and Product secrets (git tokens, REST bearer tokens, installation variables) confidential and will promptly notify Provider upon learning of any compromise.

License. The Product is licensed through the Atlassian Marketplace. Without an active license, Users may open the editor; the Product will not run or publish script execution (manual run, schedule, event, field, REST, workflow, or UI modification).

Customer Data

Use of Customer Data. Subject to this Agreement, Provider will access and use Customer Data solely to provide and maintain the Cloud Service. Customer Data includes script source and related workspace files, run history and console output, Atlassian account identifiers stored as audit stamps, encrypted git remote tokens, hashed REST endpoint tokens, installation variables, and Jira data a script reads or writes while it runs. Provider will not otherwise disclose Customer Data to third parties except as permitted in this Agreement or described in the Privacy Policy: Script Studio for Jira Cloud - Privacy policy

Security. Provider will use appropriate technical and organizational measures designed to prevent unauthorized access, use, alteration, or disclosure of Customer Data. The Product runs on the Atlassian Forge platform (compute, Forge SQL, and Forge key-value storage). Provider does not operate an application server of its own and does not receive Customer Data on Provider-owned hosts.

The Product is not a “Runs on Atlassian” app. If a User enables Source Control, the Forge backend may send script source, commit messages, and git author name and email to a git host the Customer names (github.com, gitlab.com, or bitbucket.org). That copy is governed by the Customer's agreement with that host.

Usage Data. Provider may collect Usage Data, such as run timestamps, success or failure, clipped console lines stored in Forge SQL, and Forge function logs (operational codes, not tokens), and use it to operate, improve, and support the Product. Provider will not disclose Usage Data externally unless it is de-identified and aggregated across customers. Usage Data is never used for advertising.

Scripts and Customer responsibility (Provider-Specific Terms)

These terms apply because the Product executes code the Customer writes.

Customer-authored code. Scripts, UI modifications, Jira expressions, installation variables, and REST endpoint configuration are Customer Materials. Between the parties, Customer is solely responsible for what those materials do when they run: calls to Jira, writes to Forge SQL tables the script creates, data written to a git remote, and any personal data a script logs.

Identity of a run. A manual Run uses the signed-in administrator's Jira identity. Scheduled, event, field, workflow, and token-authenticated REST runs use the app identity (asApp()) because no user is signed into that invocation. Customer understands that publishing those triggers grants the script the Product's Jira scopes on that site.

UI modifications. A UI modification runs in the browser of the person who opens the Jira screen, with that person's requestJira session. Publishing one is Customer's act of shipping JavaScript to those users.

REST doors. A Forge web trigger is not authenticated by Atlassian. The Product protects it with a bearer token it issues. Customer is responsible for keeping that token secret and rotating it if it leaks. The Product's authenticated app REST API is called with an Atlassian 3LO token that has the Product's custom scopes.

No audit of Customer scripts. Provider does not review, approve, or monitor the content of Customer's scripts. The Performance Warranty covers the workbench and the runtime as described in the Documentation, not the correctness or lawfulness of a particular script.

Mutual Compliance with Laws

Each party will comply with all Laws that apply to its performance under this Agreement. Customer is responsible for ensuring that its scripts and its use of Jira data comply with Laws that apply to Customer, including data-protection Laws.

Support and SLA

Support. Provider will provide support for the Product as described in the applicable Atlassian Marketplace listing and the Product documentation.

SLA. No formal SLA is provided for this Product.

Warranties

Mutual Warranties. Each party represents and warrants that (a) it has the legal power and authority to enter into this Agreement, and (b) it will use industry-standard measures to avoid introducing Viruses into the Cloud Service.

Performance Warranty. Provider warrants that the Product will perform materially as described in the Documentation and that Provider will not materially decrease the overall functionality of the Cloud Service during the Subscription Term (the "Performance Warranty"). The Performance Warranty does not cover failures caused by Customer scripts, Customer-configured git remotes, or Third-Party Platforms.

Claim Report. Customer must report a breach of warranty in reasonable detail ("Claim") within 30 days after discovering the issue (the "Claim Period").
Remedy. Within 30 days of receiving a verified Claim during the Claim Period (the "Fix Period"), Provider will use reasonable efforts to correct or provide a reasonable workaround (a "Fix"). If Provider fails to provide a Fix during the Fix Period, either party may terminate the Subscription for the nonconforming Product on notice, and Provider will refund any prepaid, unused fees for the terminated portion of the Subscription Term.
Exclusive Remedy. The procedures above are Customer's exclusive remedies and Provider's sole liability for breach of the Performance Warranty.

Disclaimers. Except as expressly set out in this Agreement, each party disclaims all warranties, whether express, implied, statutory, or otherwise, including warranties of merchantability, fitness for a particular purpose, title, and noninfringement. Provider's warranties above do not apply to issues arising from Third-Party Platforms, Customer scripts, or misuse or unauthorized modification of the Product. These disclaimers apply to the full extent permitted by Law.

Usage Rules

Compliance. Customer represents and warrants that it has all rights necessary to use Customer Data with the Cloud Service and to grant Provider the rights specified in this Agreement, without violating any third party's intellectual property, privacy, or other rights. Between the parties, Customer is responsible for the content and accuracy of Customer Data, for who may administer Jira, and for configuring scripts, triggers, and secrets.

High-Risk Activities and Sensitive Data. Customer (a) will not use the Product for High-Risk Activities, (b) will not submit Sensitive Data to the Cloud Service except as Customer itself chooses to put in a script, a variable, or a run log, and (c) acknowledges that the Product is not designed for use prohibited in this section, and Provider has no liability for such use.

Restrictions. Customer will not, and will not permit anyone else to: (a) sell, sublicense, distribute, or rent the Product, grant non-Users access to it, or use it to provide a hosted or managed service to others; (b) reverse engineer, decompile, or seek to access the Product's source code, except where prohibited by Law and only after advance notice to Provider; (c) copy, modify, create derivative works of, or remove proprietary notices from the Product (this does not restrict Customer from writing and owning its own scripts); (d) conduct security or vulnerability testing of the Cloud Service or interfere with its operation, except as permitted by Atlassian's Marketplace security programs; (e) circumvent access restrictions to the Product, including license checks; or (f) use the Product to develop a competing product or service.

Third-Party Platforms

Customer uses the Product together with Jira Cloud and the Atlassian Forge platform. If a User enables Source Control, Customer also exchanges Customer Data with GitHub, GitLab, or Bitbucket, as the User configured. Customer's use of a Third-Party Platform is governed by its own agreement with that provider, not this Agreement, and Provider is not responsible for Third-Party Platforms or how their providers use Customer Data.

Fees

Fees will be as stated in the Order, and payment terms are as set forth in the Order or the terms of the Atlassian Marketplace. Marketplace billing for a paid installation applies to the production environment; development and staging installations used by Provider to test the Product are outside this Order.

Suspension

Provider may suspend Customer's access to the Cloud Service due to a Suspension Event, but where practicable will give prior notice so Customer can resolve the issue. Prior notice is not required in exigent circumstances or where suspension is needed to avoid material harm or a violation of Law. Once resolved, Provider will promptly restore access. "Suspension Event" means: (a) Customer's account is 30+ days overdue; (b) Customer is in breach of the Usage Rules section; or (c) Customer's use of the Cloud Service, including a published script, risks material harm to the Cloud Service, Jira, or others.

Term and Termination

Subscription Terms. Each Subscription Term lasts an initial 12-month period unless the Order states otherwise.

Term of Agreement. This Agreement starts on the Effective Date and continues until the end of all Subscription Terms, unless sooner terminated. If no Subscription is in effect, either party may terminate this Agreement for any or no reason on notice to the other.

Termination. Either party may terminate this Agreement (including all Subscriptions) if the other party (a) fails to cure a material breach within 30 days of notice, (b) ceases operation without a successor, or (c) seeks protection under, or has instituted against it and not dismissed within 60 days, bankruptcy or similar insolvency proceedings.

Data Export and Deletion. During a Subscription Term, Customer may export script source through the Product's Source Control feature or by copying files from the editor, as described in the Documentation. Uninstalling the Product from a Jira site deletes Forge SQL and Forge key-value storage for that installation. Within 60 days of a request after termination or expiration, Provider will delete any Customer Data still in its control, subject to standard backup and legal-retention policies.

Native Jira issues, comments, worklogs, workflows, and fields remain in Jira as the Customer's data. Copies already pushed to a Customer git remote remain in that repository; Provider cannot delete them.

Effect of Termination. Customer's right to use the Product ceases upon termination or expiration, subject to the Data Export and Deletion terms above. Sections dealing with Usage Data, Scripts and Customer responsibility, Disclaimers, Usage Rules, Data Export and Deletion, Intellectual Property, Limitations of Liability, Indemnification, Confidentiality, General Terms, and Definitions survive termination.

Intellectual Property

Reserved Rights. Neither party grants the other any rights not expressly set out in this Agreement. Customer retains all rights in Customer Data and Customer Materials, including scripts Customer writes. Provider and its licensors retain all rights in the Product and related technology, including the editor, the runtime, and bundled type declarations.

Feedback. If Customer gives Provider feedback about the Product, Provider may use it without restriction or obligation. Feedback is provided "AS IS," and Provider will not publicly identify Customer as its source without permission.

Limitations of Liability

General Cap. Each party's entire liability arising out of this Agreement will not exceed the General Cap.

Consequential Damages Waiver. Neither party will be liable for indirect, special, incidental, reliance, or consequential damages, or for loss of use, lost profits, or interruption of business, even if advised of their possibility.

Liability Definitions. "General Cap" means amounts paid or payable by Customer to Provider in the 12 months preceding the first incident giving rise to liability. Uncapped Claims include indemnification obligations, infringement or misappropriation of the other party's intellectual property, breach of Confidentiality, and liabilities that cannot be limited by Law.

Provider is not liable for loss arising from Customer's scripts, from a leaked REST or git token, or from a Third-Party Platform the Customer enabled, except to the extent caused by Provider's failure to provide the Product as described in the Documentation.

Confidentiality

Use and Protection. Each party will use Confidential Information only to fulfill its obligations and exercise its rights under this Agreement, will not disclose it to third parties without the discloser's prior approval except as permitted here, and will protect it using at least the same precautions it uses for its own similar information.

Exclusions. These obligations do not apply to information that is or becomes public through no fault of the recipient, was already rightfully known or possessed, was rightfully received from a third party, or was independently developed without reference to the Confidential Information.

General Terms

Governing Law and Courts. Unless otherwise specified in Provider-Specific Terms, this Agreement is governed by the laws of Spain, and the parties submit to the exclusive jurisdiction of the courts of Elche, Alicante, Spain.

Notices. Notices must be in writing to the addresses specified by each party. Provider's notice address is support@branchcreation.com. Provider may also send operational notices through the Product.

Entire Agreement. This Agreement is the parties' entire agreement regarding its subject matter and supersedes prior agreements on the same subject. Neither Atlassian (as Marketplace operator) nor Bonterms (publisher of the underlying Standard Agreement) is a party to this Agreement or has any liability in connection with its use.

Force Majeure. Neither party is liable for delay or failure to perform due to a Force Majeure event. If it materially affects the Product for 15+ consecutive days, either party may terminate the affected Subscription on notice, with a refund of prepaid, unused fees.

Definitions

"Cloud Service" — Script Studio for Jira, Provider's SaaS/cloud app as identified in the Atlassian Marketplace listing.
"Customer" — the party placing the Order.
"Customer Data" — any data, content, or materials Customer or its Users submit to Jira Cloud or the Product and that the Product processes, including script source, workspace files, run history, account identifiers, tokens and variables, and Jira records a script reads or writes.
"Customer Materials" — scripts, expressions, variables, and configuration Customer creates in the Product.
"Documentation" — Provider's standard usage documentation for the Product, including the Privacy Policy.
"Laws" — all laws, regulations, rules, court orders, or other binding government requirements applicable to a party.
"Marketplace" — the Atlassian Marketplace, on which Provider has published its Listing.
"Permitted Use" — use of the Product per the applicable Subscription, any Use Restrictions, and the Documentation.
"Product" — Script Studio for Jira.
"Provider" — BranchCreation S.L.U.
"Subscription" — Customer's right to access the Product as described in the Listing and applicable Order.
"User" — anyone Customer allows to use its accounts for the Product, including Jira administrators who open the workbench.
"Usage Data" — Provider's technical logs and data about Customer's use of the Product, excluding Customer Data.