Provider-Specific Terms - JiBrok Apps

Last updated: March 21, 2026

These Provider-Specific Terms supplement the Atlassian Standard End User Agreement (“Standard Agreement”) for JiBrok apps listed below, provided by JiBrok (“Provider”). In the event of any conflict between these Provider-Specific Terms and the Standard Agreement, these Provider-Specific Terms shall prevail.

1. Covered Products

These Provider-Specific Terms apply to the following JiBrok apps on the Atlassian Marketplace:

Cloud

Data Center / Server

For JiBrok Studio for Jira Cloud, see the separate Provider-Specific Terms - JiBrok Studio.

2. Governing Law and Jurisdiction

Section 19.2 of the Standard Agreement is replaced with the following:

This Agreement shall be governed by and construed in accordance with the laws of the Republic of Cyprus, without regard to its conflict of laws provisions. The parties consent to the exclusive jurisdiction and venue of the courts of Nicosia, Republic of Cyprus.

3. Data Protection

The following documents are incorporated by reference into this Agreement:

Data Processing Agreement (DPA) - JiBrok Cloud Apps: jibrok.com/dpa-jibrok-cloud-apps/ (applies to Time in Status, Timer field, Stopwatch field, JBCF, Display Linked Issues, Fields panel for JSM)
Data Processing Agreement (DPA) - Message Field Cloud: jibrok.com/dpa-message-field-cloud/
Privacy Policy: jibrok.com/privacy-policy/
Cookie Policy: jibrok.com/cookie-policy/

The applicable DPA governs the processing of personal data by the Provider on behalf of the Customer in connection with the Product.

4. Platform Dependency

Cloud Products. JiBrok Cloud apps run on Atlassian Forge, a serverless platform managed by Atlassian. The Provider does not operate its own servers, databases, or network infrastructure for Cloud Products.

The Provider is not responsible for outages, performance degradation, or limitations of the Atlassian Forge platform to the extent such issues are directly caused by the Atlassian platform and could not be avoided through commercially reasonable mitigation by the Provider. However, prolonged material degradation that persists beyond the Force Majeure period entitles the Customer to the remedies otherwise available under the Agreement, including termination and pro-rata refund.

Platform availability is subject to Atlassian’s own service commitments. Current operational status is available at jibrok.statuspage.io.

Where changes to the Atlassian Forge platform, Atlassian REST APIs, or related Atlassian services require the Provider to modify, replace, or remove Product features, such modifications shall not constitute a breach of the warranty in Section 6.1 of the Standard Agreement or a decrease in overall functionality for the purposes of that section, provided that the Provider uses commercially reasonable efforts to (a) maintain equivalent functionality through alternative implementation where technically feasible, or (b) notify affected Customers through the Atlassian Marketplace listing or the Provider’s website within thirty (30) days of becoming aware that a feature will be materially affected. This paragraph does not limit the Customer’s right to terminate and receive a pro-rata refund under the preceding paragraph if prolonged material degradation occurs.

Performance characteristics described in Product documentation - including but not limited to processing capacity, response times, throughput, and supported data volumes - reflect typical behavior under normal Atlassian platform conditions and do not constitute independent performance guarantees beyond Section 6.1 of the Standard Agreement. Actual performance may vary due to factors outside the Provider’s control, including Atlassian Forge platform rate limits, quotas, concurrent usage, and Customer Jira instance size and configuration.

Data Center / Server Products. Data Center and Server products are installed and run on the Customer’s own infrastructure. The Provider is not responsible for the performance, availability, or security of the Customer’s hosting environment, including server hardware, operating systems, database systems, network configuration, or security measures.

5. Customer Data and Configuration

The Customer is solely responsible for the data it processes using the Products, including but not limited to JQL queries, custom field configurations, SLA definitions, timer configurations, message content, calculated field formulas, and display settings.

The Products process and display data based on Customer configurations. The Provider is not responsible for incorrect results, miscalculations, or unintended behavior arising from Customer misconfiguration or incorrect input, except where the Product accepts unsupported input without reasonable validation, provides misleading configuration options, or behaves inconsistently with the Documentation.

6. AI and Machine Learning

The Provider will not use Customer Data to train, fine-tune, or improve artificial intelligence or machine learning models. Usage Data collected under Section 3.4 of the Standard Agreement (aggregated, de-identified product usage metrics) is not Customer Data for these purposes and may be used for product improvement.

7. Backup and Data Recovery

The Customer is solely responsible for maintaining independent backups of its Jira data. The Products are not backup or disaster recovery solutions. App data stored within Atlassian Forge is subject to Atlassian’s standard backup and disaster recovery mechanisms; the Provider does not independently access, back up, or restore Customer data in Forge storage. The Provider shall not be liable for any failure to recover Customer data, whether caused by platform outages, Customer configuration, or any other cause, except to the extent data loss or corruption is directly caused by a defect in the Product’s code.

Upon termination or expiration of this Agreement, the Provider will use commercially reasonable efforts to delete or de-identify Customer data stored within Atlassian Forge within sixty (60) days, in accordance with Section 17.3 of the Standard Agreement. The Customer acknowledges that the Provider’s ability to delete data stored in Atlassian Forge is subject to the capabilities and data lifecycle policies of the Atlassian platform. To the extent that Atlassian retains data in its infrastructure beyond the Provider’s deletion request, such retention is governed by Atlassian’s own data processing and retention policies and shall not constitute a breach by the Provider of Section 17.3 of the Standard Agreement.

8. Liability Clarifications

This section supplements Section 14 of the Standard Agreement.

8.1 General Cap Calculation

For the purposes of Section 14.1 of the Standard Agreement, the “General Cap” means amounts actually paid by the Customer to the Provider for the Product during the twelve (12) month period immediately preceding the first event giving rise to liability. Free trial periods, promotional periods, and any period during which the Customer did not pay fees do not contribute to the General Cap calculation.

8.2 Specific Exclusions from Damages

Without limiting Section 14.2 of the Standard Agreement, neither party shall be liable for:

(a) cost of procurement of substitute goods, technology, or services;
(b) lost goodwill or reputational damage;
(c) damages arising from the Customer’s failure to implement reasonable data backup procedures;
(d) damages arising from the Customer’s continued use of the Product after the Provider has notified the Customer in writing of a critical defect or vulnerability and provided reasonable mitigation guidance;
(e) damages arising from use of the Product in combination with unsupported or undocumented third-party products, platforms, or services;
(f) penalties, fines, or sanctions imposed by regulatory authorities on the Customer.

8.3 Sole Remedy

For any claim related to Product performance or functionality, the Customer’s sole and exclusive remedy is as set forth in Section 6.2 of the Standard Agreement. This exclusive remedy does not apply to repeated or prolonged critical failures that render the Product materially unusable for more than fifteen (15) consecutive business days; in such case, the Customer may terminate the subscription and receive a pro-rata refund for the remainder of the subscription term.

8.4 Overall Liability Cap

Notwithstanding Sections 14.3 and 14.5 of the Standard Agreement, Provider’s total aggregate liability arising out of or related to this Agreement, from all causes of action and under all theories of liability, shall not exceed two times (2x) the General Cap as calculated in Section 8.1 above, except that liability for Enhanced Claims under Section 14.3 of the Standard Agreement (including breach of data protection obligations and security obligations) shall not exceed three times (3x) the General Cap.

For clarity, the 2x cap applies to all other categories of claims, including Provider-Covered Claims (Section 15) and confidentiality obligations.

This limitation does not apply to liability arising from Provider’s fraud or intentional misconduct, or liability that cannot be limited under the laws of the Republic of Cyprus.

8.5 Indemnification Conditions

In addition to the procedures set forth in Section 15.4 of the Standard Agreement, Provider’s obligations under Section 15.1 are subject to the following conditions:

(a) Customer must provide prompt written notice to Provider upon becoming aware of a potential Provider-Covered Claim. Delayed notice reduces Provider’s obligations under this section only to the extent Provider is materially prejudiced by the delay.
(b) Customer must grant Provider sole control of the defense and settlement of any Provider-Covered Claim. Customer shall not settle or compromise any such claim without Provider’s prior written consent.
(c) In addition to the exceptions set forth in Section 15.6 of the Standard Agreement, Provider’s indemnification obligations do not extend to claims arising from Customer’s use of the Product in combination with products, services, or technologies not provided or recommended by Provider or Atlassian.
(d) Provider’s obligations under Section 15.1 shall be reduced to the extent that Customer’s actions or omissions materially contributed to the claim.

9. Data Center / Server Specific Terms

The following terms apply specifically to Data Center and Server products:

(a) The Product is provided for use on the Customer’s self-hosted infrastructure. The Provider makes no representations or warranties regarding the Customer’s infrastructure or its suitability for the Product.
(b) The Provider is not responsible for the Customer’s infrastructure, including server hardware, operating systems, database systems, network configuration, or security measures.
(c) The Customer is responsible for maintaining compatible versions of Atlassian host products (e.g., Jira Software, Jira Service Management) as specified in the Product documentation.
(d) End-of-support dates for Data Center and Server products may be announced via the Atlassian Marketplace listing with at least twelve (12) months’ notice.
(e) The Provider does not process Personal Data on behalf of the Customer in connection with Data Center and Server products. No Data Processing Agreement applies to these products. The Customer is solely responsible for all data processing on its own infrastructure.

10. Force Majeure Extension

In addition to events of Force Majeure described in Section 19.8 of the Standard Agreement, the following shall constitute Force Majeure events:

(a) Atlassian platform outages, degradation, or changes to Forge APIs that materially affect Product functionality;
(b) changes to Atlassian Marketplace policies that require Product modifications;
(c) regulatory actions by government authorities affecting the Provider’s ability to deliver the Product;
(d) supply chain disruptions affecting cloud infrastructure providers used by Atlassian.

For events described in subsections (a) and (b) of this section, the period referenced in Section 19.8 of the Standard Agreement after which either party may terminate shall be fifteen (15) days.

11. Amendments

This section supersedes Section 19.5 of the Standard Agreement with respect to amendments to these Provider-Specific Terms.

The Provider may update these Provider-Specific Terms from time to time. Material changes - including changes to liability limitations, data processing obligations, or governing law - will be communicated through the Atlassian Marketplace listing or via the Provider’s website at least thirty (30) days before taking effect.

Material changes take effect at the start of the Customer’s next renewal term, not during the current subscription period. This restriction does not apply to changes that are (a) required by applicable law or regulation, (b) necessary to address a security vulnerability or incident, or (c) do not materially reduce the Customer’s rights under these terms. Such excepted changes may take effect during the current term upon thirty (30) days’ notice.

If the Customer objects to a material change scheduled for renewal, the Customer may choose not to renew. If the Customer has already been charged for the renewal term, the Customer may terminate within thirty (30) days of the change taking effect and receive a pro-rata refund for the remainder of the renewal term.

12. Security Documentation

The Provider maintains the following security documentation:

Trust Center: jibrok.com/trust-center/
Security & SOC Reports: jibrok.com/security/
Vulnerability Disclosure Policy: jibrok.com/vulnerability-disclosure/

13. Support

Support is provided in accordance with the Provider’s Support Policy at jibrok.com/support-policy/.

Support requests may be submitted through the Provider’s Help Center at jibrok.atlassian.net/servicedesk/customer/portals or by email at support@jibrok.com.

For security-related reports, contact security@jibrok.com.

14. Survival

The following sections of these Provider-Specific Terms survive termination or expiration of this Agreement: Section 2 (Governing Law and Jurisdiction), Section 5 (Customer Data and Configuration), Section 6 (AI and Machine Learning), Section 7 (Backup and Data Recovery), Section 8 (Liability Clarifications), and Section 9 (Data Center / Server Specific Terms).