Vesper End User Licence Agreement

Effective date: 23 August 2026
Last updated: 23 August 2026

This End User Licence Agreement consists of the Bonterms Standard End User Agreement, Version 1.0 offered through Atlassian Marketplace and the Vesper Provider-Specific Terms below. Together they form the agreement for Vesper. By ordering, installing, or using Vesper, Customer agrees to these terms.

Provider-Specific Terms

1. Provider and product

"Provider" means Abhay Bharadwaj, an individual developer operating Vesper, based in Bengaluru, Karnataka, India, as identified in the applicable Atlassian Marketplace listing and Order. "Vesper" or the "Product" means the Vesper Forge app for Jira Cloud.

Vesper reads Jira delivery data available to the invoking user and presents role-aware delivery views, including cross-team dependencies, blockers, portfolio exceptions, release and sprint signals, standup evidence, and story drill-through views.

2. Permitted use and customer responsibilities

Subject to an active Marketplace subscription or evaluation, Customer may install and use Vesper for its internal business purposes on the Jira Cloud sites covered by its Order.

Customer is responsible for:

• maintaining the Jira Cloud account, site, users, permissions, boards, projects, workflows, fields, issue links, comments, and other source data on which Vesper depends;
• ensuring that it has the rights and lawful basis required to make that data available to Vesper and to permit its authorised users to view the resulting delivery information;
• limiting Jira-administrator access and configuring monitored boards, field mappings, company terminology, personas, release mappings, and business timezone accurately; and
• reviewing Vesper's output against the underlying Jira records before making material business decisions.

Vesper is a decision-support and delivery-visibility tool. It is not a system of record, a substitute for Jira, or a guarantee of delivery dates or business outcomes. Coordination and ownership signals must not be treated as measures of individual employee performance or used as the sole basis for employment, disciplinary, legal, safety-critical, or other high-impact decisions.

3. Atlassian platform and usage limits

Vesper is a Forge app that operates inside Jira Cloud. Its availability and operation depend on Jira Cloud, Atlassian Marketplace, Forge, the Customer's Atlassian configuration and permissions, and applicable Atlassian APIs, quotas, rate limits, storage limits, maintenance, and service availability.

Those platform limits may delay a refresh, restrict the amount of Jira data that can be read in one invocation, or make a view temporarily unavailable. Vesper may refuse to present a result when required Jira data is incomplete rather than present an incomplete result as complete. Provider does not control the Atlassian platform and does not provide a separate service-level agreement unless one is agreed in writing.

4. Subscription, trials, and access

Fees, billing, subscription term, renewals, evaluations, refunds, and licence quantities are governed by the applicable Atlassian Marketplace Order and Marketplace terms.

Vesper checks the licence state supplied by Atlassian. When Atlassian reports that the subscription or evaluation is inactive, Vesper may block access to delivery views. An inactive licence does not by itself delete Vesper's stored configuration or account-scoped queue state. Access is restored when Atlassian again reports an active entitlement, subject to the data-retention and deletion rules in the Privacy Policy.

5. Data, privacy, and security

Vesper processes Customer Data only to provide, secure, maintain, and support the Product as described in the Vesper Privacy Policy and Security page.

The Marketplace version uses Atlassian-hosted Forge compute, Custom UI, and persistent storage. It does not require a separate Vesper account, Atlassian password, or Jira API token. Jira reads are made as the invoking user and remain subject to that user's Jira permissions. The current Forge manifest declares no external data egress, and Vesper does not send Jira content to an LLM, advertising network, or third-party analytics service.

The Vesper Privacy Policy forms part of these Provider-Specific Terms. The Vesper Data Processing Addendum applies when Vesper processes personal data on Customer's behalf and is incorporated into the Agreement by reference.

6. Support

Support requests may be sent to contact@vesperfocus.com. Provider will use reasonable efforts to respond and investigate, but no guaranteed response or resolution time applies unless stated in a separate written support policy or agreement.

Suspected security vulnerabilities should be reported privately through the same address or the security channel identified in the Marketplace listing, and not through a public issue.

7. Product changes

Provider may update Vesper to improve or secure the Product, maintain compatibility with Jira or Forge, comply with law or Atlassian requirements, or change functionality. Provider will not materially reduce the Product's overall functionality during a paid subscription term except where reasonably necessary for security, legal compliance, platform compatibility, or to avoid material harm.

8. Relationship with Atlassian

Vesper is a third-party Marketplace app. Provider, not Atlassian, licenses and supports Vesper. Atlassian is not responsible for Vesper except to the extent expressly stated in the Customer's agreements with Atlassian. Customer's use of Jira Cloud, Forge, and Atlassian Marketplace remains governed by its agreements with Atlassian.

9. Governing law and courts

These Provider-Specific Terms and any dispute not governed by a mandatory provision of the Standard Agreement are governed by the laws of India. The courts located in Bengaluru, Karnataka, India have exclusive jurisdiction, except where applicable law gives Customer a mandatory right to bring a claim elsewhere.

Mandatory governing-law, supervisory-authority, and court provisions in the Vesper Data Processing Addendum, EU Standard Contractual Clauses, or UK International Data Transfer Addendum continue to apply to the processing and transfers they cover.

10. Order of precedence and contact

If these Provider-Specific Terms conflict with the Standard Agreement, these Provider-Specific Terms control to the extent of the conflict. If an Order or a signed amendment expressly conflicts with either document, the order of precedence stated in the Standard Agreement applies.

Legal notices and questions about these terms may be sent to contact@vesperfocus.com, subject to any additional notice address identified in the Marketplace listing or Order. Provider's current contact location is Bengaluru, Karnataka, India.