These End User Terms ("Terms") govern your access to and use of OrgPulse, a Jira Cloud application provided by OrgPulse ("we", "us", "our"). By installing OrgPulse from the Atlassian Marketplace, you accept these Terms on behalf of yourself and the organisation that owns the Jira workspace into which you install the application ("you", "your", "Customer").
If you do not agree to these Terms, do not install or use OrgPulse.
1. The Service
OrgPulse is a team health diagnostics application that analyses engineering workflow data from Jira Cloud to identify dysfunction patterns and surface actionable insights for team leads and engineering managers. The application runs entirely on Atlassian's managed Forge infrastructure.
The specific features available to you depend on the subscription plan associated with your Atlassian Marketplace account.
2. Eligibility and Authority
You may use OrgPulse if you:
- Are at least 18 years of age
- Have the authority to accept these Terms on behalf of your organisation
- Are a Jira Cloud workspace administrator, or have been granted installation permissions by a workspace administrator
OrgPulse is intended for use by organisations managing software engineering teams. It is not intended for personal use.
3. Your Account and Access
3.1 Workspace administrator responsibility
The Jira workspace administrator who installs OrgPulse is responsible for:
- Configuring status mappings and issue type classifications during onboarding
- Managing which team members can access the OrgPulse dashboard (via the Access Manager)
- Ensuring that team members are appropriately informed that workflow metadata is processed for team-level analytics
3.2 Authorised users
You may grant access to OrgPulse to team leads and managers within your organisation. Authorised users must comply with these Terms. You are responsible for all activity that occurs under your workspace's OrgPulse instance.
3.3 Account security
You are responsible for maintaining the security of your Jira workspace credentials. OrgPulse does not manage separate login credentials — access is controlled by the Jira workspace permission model and the OrgPulse access configuration you set during onboarding.
4. Acceptable Use
You may use OrgPulse solely for lawful purposes and in accordance with these Terms. You must not:
- Use OrgPulse to monitor individual team members' personal performance or to make employment decisions about individuals (OrgPulse is designed for team-level analysis only and does not produce individual-level metrics)
- Attempt to circumvent or reverse-engineer any aspect of the service
- Use OrgPulse in a manner that violates any applicable law, including employment or labour law in your jurisdiction
- Interfere with or disrupt the integrity or performance of the service or Atlassian's Forge infrastructure
We reserve the right to suspend or terminate access where we have reason to believe these restrictions are being violated.
5. Subscription and Payment
5.1 Atlassian Marketplace billing
OrgPulse subscriptions are purchased and managed through the Atlassian Marketplace. Billing, invoicing, and payment processing are handled by Atlassian in accordance with Atlassian's Marketplace terms. We do not directly process payment card information.
5.2 Subscription plans
Your subscription plan determines the features available to you. Current plan details and pricing are listed on the OrgPulse Atlassian Marketplace listing.
5.3 Free trial
Where a free trial is offered, it is subject to the duration and feature limits stated at the time of installation. Continued use after the trial period requires a paid subscription.
5.4 Changes to pricing
We reserve the right to change subscription pricing at any time. Price changes will be communicated to you in advance via the Atlassian Marketplace and, where possible, by email to the workspace administrator's registered address. Continued use of OrgPulse following a price change constitutes acceptance of the revised pricing.
6. Data and Privacy
6.1 What OrgPulse accesses
OrgPulse accesses Jira Cloud data using three read-only OAuth 2.0 scopes (read:jira-work, read:jira-user, read:sprint) for the sole purpose of computing team-level workflow metrics. Full details are set out in the OrgPulse Privacy Policy.
6.2 What OrgPulse stores
OrgPulse stores only derived, team-level aggregates — never raw issue content. No issue titles, descriptions, comments, or individual-level data are stored at any point.
6.3 Data retention and deletion
Stored aggregates and diagnostic events are retained for 18 months. Uninstalling OrgPulse triggers immediate deletion of all stored data for your workspace.
6.4 Data Processing Addendum
For Customers who require a formal data processing agreement for GDPR compliance, the OrgPulse Data Processing Addendum ("DPA") is incorporated into these Terms by reference. In the event of a conflict between these Terms and the DPA, the DPA prevails with respect to the processing of personal data.
6.5 Security
OrgPulse operates entirely on Atlassian's managed Forge infrastructure. No external servers are operated by us. Atlassian Forge provides encryption at rest and in transit for all stored data.
7. Intellectual Property
7.1 Our property
OrgPulse, including its software, algorithms, diagnostic models, and documentation, is our proprietary product. Nothing in these Terms transfers ownership of any intellectual property to you.
7.2 Your data
You retain all rights to the underlying Jira data in your workspace. We claim no rights over your Jira data. The team-level aggregates we compute from your data remain yours and are deleted upon uninstallation.
7.3 Feedback
If you provide feedback, suggestions, or ideas about OrgPulse, you grant us a perpetual, royalty-free licence to use that feedback to improve the service. You retain any intellectual property rights in the feedback itself.
8. Availability and Changes to the Service
8.1 Availability
We aim to provide a reliable service but do not guarantee uninterrupted availability. OrgPulse availability depends in part on Atlassian's Forge infrastructure, and we are not liable for downtime caused by Atlassian or other third parties.
8.2 Changes to features
We may update, modify, or discontinue features of OrgPulse at any time. Where a change is material, we will provide reasonable advance notice via the Atlassian Marketplace or by email to the workspace administrator. Your continued use of the service following notification constitutes acceptance of the changes.
8.3 Scheduled maintenance
Maintenance that requires downtime will be performed outside peak working hours where reasonably practicable and communicated in advance.
9. Disclaimer of Warranties
OrgPulse is provided "as is" and "as available", without warranties of any kind, express or implied, including but not limited to warranties of merchantability, fitness for a particular purpose, non-infringement, or uninterrupted access.
We do not warrant that:
- OrgPulse will identify every instance of team dysfunction
- The diagnoses or metrics produced by OrgPulse will be accurate or complete in all circumstances
- The service will be error-free or that defects will be corrected
Nothing in these Terms excludes or limits our liability for fraud, death, or personal injury caused by our negligence, or any other liability that cannot be excluded by law.
10. Limitation of Liability
To the fullest extent permitted by law:
- Our aggregate liability to you for any claim arising under or in connection with these Terms or your use of OrgPulse shall not exceed the fees paid by you for OrgPulse in the 12 months preceding the event giving rise to the claim
- We shall not be liable for any indirect, incidental, consequential, special, or punitive damages, including loss of profit, loss of data, or loss of business opportunity, arising from your use of or inability to use OrgPulse, even if we have been advised of the possibility of such damages
11. Indemnity
You agree to indemnify and hold us harmless from any claims, damages, losses, or costs (including reasonable legal fees) arising out of:
- Your use of OrgPulse in violation of these Terms
- Your violation of any applicable law or third-party rights
- Your use of OrgPulse to make employment or disciplinary decisions about individuals
12. Termination
12.1 Termination by you
You may terminate your use of OrgPulse at any time by uninstalling it from your Jira workspace via the Atlassian Marketplace. Uninstallation triggers immediate deletion of all stored data as described in Section 6.3. Refunds for unused subscription periods (if any) are subject to Atlassian's Marketplace refund policy.
12.2 Termination by us
We may suspend or terminate your access to OrgPulse immediately if:
- You breach these Terms and fail to remedy the breach within 14 days of written notice
- We are required to do so by law or by Atlassian's Marketplace policies
- We decide to discontinue the OrgPulse service (with reasonable advance notice where possible)
12.3 Effect of termination
Upon termination, your right to use OrgPulse ceases immediately. All stored data for your workspace is deleted as described in Section 6.3. Sections 7, 9, 10, 11, and 13 survive termination.
13. Governing Law and Disputes
These Terms are governed by the laws of England and Wales. Any dispute arising from or in connection with these Terms shall be subject to the exclusive jurisdiction of the courts of England and Wales, unless you are a consumer in a jurisdiction that provides mandatory local consumer law protections that override this choice.
14. General
14.1 Entire agreement
These Terms, together with the Privacy Policy and (where applicable) the Data Processing Addendum, constitute the entire agreement between you and us relating to OrgPulse, and supersede all prior agreements and understandings.
14.2 Atlassian Marketplace terms
Your use of OrgPulse is also subject to Atlassian's Marketplace terms. In the event of a conflict between these Terms and Atlassian's Marketplace terms, Atlassian's Marketplace terms prevail with respect to matters within Atlassian's control (billing, data residency, Forge infrastructure).
14.3 Severability
If any provision of these Terms is found to be unenforceable, the remaining provisions continue in full force and effect.
14.4 Waiver
Our failure to enforce any provision of these Terms does not constitute a waiver of our right to enforce it in the future.
14.5 Changes to these Terms
We may update these Terms from time to time. Where changes are material, we will notify you at least 30 days in advance via the Atlassian Marketplace or by email to the workspace administrator. Your continued use of OrgPulse after the effective date of the revised Terms constitutes acceptance. If you do not accept the revised Terms, you may terminate your use of OrgPulse as described in Section 12.1.
Contact
For questions about these Terms:
- General enquiries: support@orgpulse.io
- Legal / compliance: legal@orgpulse.io
- Privacy and data: privacy@orgpulse.io