Provider-Specific Terms

Version: 1.0

Publication/version date: 29 August 2026

Last updated: 29 August 2026

Provider: Will Perry trading as PezTech Software, a sole trader in the United Kingdom

Product: Bulk Approvals for Jira Service Management (“Bulk Approvals for JSM”)

Contact: support@peztechsoftware.co.uk

Website: https://peztechsoftware.co.uk

Legal-notice address: [The Bristol Office, 2nd Floor, 5 High Street, Westbury-on-Trym, Bristol, BS9 3BY, England]

1. Agreement and effective date

1. These Provider-Specific Terms supplement and modify the Bonterms Standard End User Agreement made available through Atlassian Marketplace (the “Standard Agreement”). Capitalised terms not defined here have the meanings in the Standard Agreement.
2. The Customer and Provider enter the Standard Agreement and these Provider-Specific Terms on the Effective Date specified by section 1.2 of the Standard Agreement: the Customer’s first entry into an Order through Atlassian Marketplace.
3. The Listing and installation screen will identify and link the Standard Agreement, these Provider-Specific Terms, the PezTech Software Customer DPA and the Support Policy. No separate website click-through is created by these Terms.
4. Each Order creates the agreement described by the Standard Agreement. Installation or evaluation is an acceptance event only to the extent that Atlassian records it as an Order under the applicable Marketplace mechanism.

2. Order of precedence

If documents conflict, the following order applies:

1. any signed Amendment;
2. the PezTech Software Customer DPA, but only for processing of Customer Personal Data and other data-protection matters;
3. these Provider-Specific Terms for Provider- and Product-specific matters;
4. any other Attachment identified in the Listing; and
5. the Standard Agreement.

This order uses the flexibility in section 1.4 of the Standard Agreement. It does not modify Atlassian Marketplace terms or any mandatory law.

3. Product and customer responsibilities

1. Bulk Approvals for JSM helps signed-in Jira Service Management approvers review and decide multiple pending native approvals. It does not replace Jira/JSM approvals.
2. Jira permissions, native approval authority, workflow consequences and audit history remain authoritative.
3. The Customer is responsible for its Jira/JSM configuration, users, request content, approval rules, lawful processing instructions and permitted use. The Product is not designed specifically for special-category or highly sensitive data. Customer administrators choose the portal-visible context fields, and customer-controlled request summaries or fields may nevertheless contain sensitive information. The Customer should avoid configuring unnecessary sensitive information for display and must ensure that its use is lawful and appropriate.
4. The Product is not general Jira/JSM consultancy, Atlassian account administration or a substitute for the Customer’s own workflow, security or data-protection controls.
5. The Product does not make automated approval decisions, profile users or use AI to determine approval outcomes.

4. Service standard, warranty and platform dependency

1. The Provider will perform its obligations and provide the Product with reasonable care and skill.
2. The Standard Agreement’s Performance Warranty, claim process and remedies apply.
3. The Provider does not promise uninterrupted or error-free operation, guaranteed uptime, compatibility with every Jira/JSM configuration, or that Atlassian APIs and platform behaviour will never change.
4. The Product depends on Atlassian Marketplace, Forge and Jira Service Management. Atlassian platform availability and native platform behaviour are outside the Provider’s direct control.
5. Nothing in these Terms excludes any mandatory statutory term or remedy that cannot lawfully be excluded.

5. Support

1. Support is provided at support@peztechsoftware.co.uk under the identified Support Policy.
2. The Provider targets an initial response within two business days and aims to resolve most issues within five business days where reasonably possible and within its control.
3. Those timeframes are service targets, not guaranteed contractual service levels.
4. The Provider does not commit to 24/7 staffing, telephone support, guaranteed resolution times or Atlassian platform uptime.
5. Complex defects, release-dependent work and Atlassian-dependent issues may take longer.

6. Data protection and security

1. The PezTech Software Customer DPA is an Attachment under section 3.3 of the Standard Agreement and applies to Customer Personal Data processed by the Provider solely to provide the Product.
2. The Privacy Notice describes the Provider’s separate controller processing for Marketplace/customer administration and direct support communications.
3. The Product uses Atlassian Forge and supported Atlassian APIs. It has no PezTech-hosted Jira request/approval backend or database and no external analytics service receiving Jira request/approval data.
4. The Provider will maintain appropriate technical and organisational measures as described in the DPA.
5. Customers must not send credentials, tokens, passwords, Jira request or approval content, sensitive custom-field values or unnecessary personal data through ordinary support email.

7. Fees and Marketplace administration

1. Fees, subscriptions, evaluations and billing are governed by the applicable Order and Atlassian Marketplace terms.
2. The intended model is Paid via Atlassian. Customers should not provide payment-card details or payment credentials directly to the Product or Provider for a normal Marketplace purchase.
3. Pricing shown in a Listing or Order controls; internal pricing plans do not form part of this Agreement.

8. Liability

1. For section 14.5 of the Standard Agreement, “General Cap” means the greater of:

• £100; and
• the fees paid or payable by the Customer for the Product during the 12 months immediately preceding the first event giving rise to the claim.

1. Sections 14.3 and 14.5 of the Standard Agreement are modified so that the definitions of “Enhanced Cap” and “Enhanced Claims” do not apply. A claim that would otherwise have been an Enhanced Claim—including a contractual claim for breach of section 3.2 (Security) or the DPA—is subject to the General Cap and section 14.2, to the extent permitted by law.
2. Subject to paragraphs 4 and 5 below, neither party is liable for indirect, special, incidental or consequential loss, or for loss of use, profits, revenue, business, anticipated savings or business interruption, even if advised that the loss was possible.
3. Nothing in the Agreement excludes or limits liability for:

• death or personal injury caused by negligence;
• fraud or fraudulent misrepresentation; or
• any other liability that applicable law prohibits from being excluded or limited.

1. Nothing in this section excludes or limits a data subject’s statutory rights, either party’s direct obligations or liability under applicable data-protection law, or regulatory powers and penalties to the extent they cannot lawfully be excluded or limited. The General Cap allocates contractual risk between the parties only.
2. The limits and exclusions apply only to the fullest extent permitted by law and remain subject to any applicable statutory reasonableness requirement, including the Unfair Contract Terms Act 1977.

9. Indemnities

1. Section 15 of the Standard Agreement applies, subject to this section.
2. Notwithstanding sections 14.3, 14.5 and 15.1 of the Standard Agreement, the Provider’s obligations and aggregate liability for Provider-Covered Claims under section 15.1—including defence costs, indemnified damages, settlement amounts and reasonable legal fees—are subject to the General Cap and section 14.2. The Provider’s obligations under section 15.1 are not Uncapped Claims.
3. For clarity, the definition of “Uncapped Claims” in section 14.5 is modified by excluding the Provider’s obligations under section 15.1. The Customer’s obligations under section 15.2 remain governed by the Standard Agreement.
4. No additional data-protection indemnity or other Provider indemnity is created by these Terms.
5. These customer-facing Terms do not amend or limit PezTech Software’s separate obligations to Atlassian under the Marketplace Partner Agreement, Developer Terms, Forge Terms or any other Atlassian agreement.

10. Governing law and courts

For section 19.2 of the Standard Agreement:

1. “Governing Law” means the laws of England and Wales.
2. “Courts” means the courts of England and Wales.
3. The courts of England and Wales have exclusive jurisdiction over actions arising out of or relating to the Agreement, subject to any mandatory law that cannot validly be displaced.

11. Termination and data lifecycle

1. The term, termination rights and effects in section 12 of the Standard Agreement apply.
2. The Customer’s right to use the Product ends when the applicable Marketplace entitlement or Subscription ends or the Product is uninstalled, subject to the Standard Agreement.
3. The DPA governs cessation of processing and deletion or return of Customer Personal Data.
4. Request, approval, context, search, selection, processing and result data is transient and is not intentionally retained by the Provider.
5. Forge-hosted configuration data remains subject to Atlassian’s current Forge storage retention and deletion lifecycle. The Provider does not maintain a separate copy and does not promise immediate physical deletion outside Atlassian’s supported lifecycle.
6. The Provider may retain its own controller records where required by law or under the published retention policy, subject to applicable data-protection law.
7. Clauses which by their nature must survive—including liability, confidentiality, intellectual property, data-protection close-out, accrued payment and governing-law provisions—survive as provided by the Standard Agreement and DPA.

12. Standard DPA and customer-specific requests

1. The published PezTech Software Customer DPA is the standard processing agreement for the Product.
2. Bespoke customer DPAs are not offered by default and are outside standard self-service Marketplace support.
3. The Provider may consider a customer-specific DPA for a sufficiently material commercial opportunity, but has no obligation to accept it. Any such proposal is considered separately and is outside standard self-service Marketplace support.

13. Notices, document versions and changes

1. Legal notices to the Provider must be sent to support@peztechsoftware.co.uk and the legal-notice address stated above once completed.
2. The Standard Agreement version and these Terms’ version must be identified in the Listing or applicable Marketplace configuration.
3. Atlassian does not automatically move an app to a new Standard Agreement version. Any later version requires review and explicit opt-in through the app configuration.
4. Changes do not operate retrospectively and are handled in accordance with the Standard Agreement.

_Last reviewed: 29 August 2026._