Kenvara
End user terms
The terms on which ITSM Ltd licenses Kenvara, the known error database for Jira Service Management.
Please read these terms carefully. By installing, accessing or using Kenvara, you agree to be bound by them. If you are agreeing on behalf of an organisation, you confirm that you have authority to bind that organisation, and “you” means that organisation.
Section 9 matters most. Kenvara shows your known errors to your customers. What is published, and to whom, is your decision; Kenvara enforces it. Read section 9 before you install.
1. Parties and structure
1.1 These End User Terms (“Terms”) form a binding agreement between ITSM Ltd, a company registered in England and Wales under company number 17339600 whose registered office is at 167-169 Great Portland Street, 5th Floor, London, W1W 5PF (“we”, “us”, “our”), and you, the customer identified in the applicable Atlassian Marketplace order (“you”, “your”).
1.2 The App is licensed to you by us, not by Atlassian. Atlassian is not a party to these Terms and has no obligation or liability to you in respect of the App.
1.3 The following documents are incorporated into these Terms by reference:
| Document | Location |
|---|---|
| These End User Terms | https://kenvara.itsm-ltd.com/legal/end-user-terms/ |
| Privacy Policy | https://kenvara.itsm-ltd.com/legal/privacy-policy/ |
| Data Processing Agreement | https://kenvara.itsm-ltd.com/legal/data-processing-agreement/ |
| Cloud Security Statement | https://kenvara.itsm-ltd.com/legal/cloud-security-statement/ |
| Support and Maintenance Description | https://kenvara.itsm-ltd.com/legal/support-and-maintenance/ |
1.4 Where there is a conflict, the order of precedence is: (a) any signed order form or amendment between us; (b) the Data Processing Agreement; (c) these Terms; (d) the incorporated documents listed in clause 1.3.
1.5 These Terms are in addition to, and do not replace, your agreement with Atlassian for the underlying Atlassian product. Nothing in these Terms modifies the Atlassian Cloud Terms of Service or the Atlassian Marketplace Terms of Use.
2. Definitions
“App” means Kenvara, including its Forge modules, documentation and any updates we make
available.
“Atlassian” means Atlassian Pty Ltd, Atlassian Corporation and their affiliates.
“Forge” means the Atlassian Forge application platform on which the App runs.
“Known Error” means a record the App keeps of a problem’s cause and workaround.
“Known Issue” means the part of a Known Error written for customers, as the portal shows it.
“Portal Customer” means a person who uses your Jira Service Management portal.
“Customer Organisation” means an organisation of customers in Jira Service Management.
“Audience” means who a Known Issue is published to: all customers, or named Customer Organisations.
“Export File” means a file in the kenvara-export/v1 format.
“Your Data” means data originating from your Atlassian site that the App reads or stores, including
what it keeps in Forge SQL and Forge’s key-value store, together with the configuration and content you
enter into the App.
“Subscription Term” means the period for which you hold a valid licence to the App, as recorded by
Atlassian.
3. Licence grant and licensing model
3.1 Subject to your payment of applicable fees and compliance with these Terms, we grant you a non-exclusive, non-transferable, non-sublicensable, revocable licence during the Subscription Term to install and use the App on the Atlassian site(s) covered by your licence, for your internal business purposes and for showing Known Issues to your own Portal Customers.
3.2 How the App is licensed. Kenvara is sold through the Atlassian Marketplace and billed by Atlassian on your site’s user count, in Atlassian’s user tiers; portal customers are never counted. It has one edition, and every feature is available while your licence is active. What a person can do in Kenvara follows their role in Jira and Jira Service Management (clause 3.5), not what you pay.
3.3 Atlassian’s 30-day evaluation gives you every feature, and counts as an active licence. It is provided without charge and without warranty, and may be withdrawn at any time. Support during an evaluation is provided on a reasonable-endeavours basis only, without response-time targets, as set out in the Support and Maintenance Description.
3.4 What happens if your licence is not active. If an evaluation ends without a subscription, or a subscription lapses, Kenvara becomes read-only, with export, for as long as Atlassian keeps it running: customers see nothing from Kenvara on the portal, agents can read known errors and take them off the portal, and a Jira administrator can still export them. Atlassian later removes a lapsed app and its data from the site, so Kenvara recommends regular exports. A suspended or deactivated licence may stop the app altogether. That is Atlassian’s behaviour, not the app’s. Security and privacy controls never depend on the licence: anything that only switches something off or narrows what customers see stays available.
3.5 Who can do what. Who can do what in Kenvara follows Jira and Jira Service Management. An agent needs an agent licence and the service project’s agent permission. Publishing needs the role your project administrator chooses. A project administrator sets Kenvara up on their service project, and a Jira administrator manages the site settings, export and import. You are responsible for who holds those roles, and for who is in each Customer Organisation (clause 9.3).
3.6 We reserve all rights not expressly granted. The App is licensed, not sold. We and our licensors retain all intellectual property rights in the App.
4. Restrictions
You must not, and must not permit any person to:
- (a) copy, modify, translate or create derivative works of the App;
- (b) reverse engineer, decompile or disassemble the App, or attempt to derive its source code, except to the extent this restriction is prohibited by applicable law;
- (c) rent, lease, lend, resell, sublicense, distribute or provide the App as a service bureau or on a time-share basis to any third party, other than by showing Known Issues to your own Portal Customers;
- (d) use the App to publish unlawful, infringing or misleading content to your customers, or attempt to see Known Issues published to a Customer Organisation you do not belong to;
- (e) circumvent, disable or interfere with any security, licensing, metering or access-control feature of the App or of the Atlassian platform;
- (f) use the App to store or transmit unlawful, infringing or malicious material, or in breach of any applicable law or of the Atlassian Acceptable Use Policy;
- (g) use the App in a manner that imposes an unreasonable or disproportionate load on the Forge platform, or that is designed to defeat platform quotas or rate limits;
- (h) benchmark or publish performance results relating to the App without our prior written consent; or
- (i) use the App to develop a competing product.
5. Platform limits, quotas and availability
5.1 Forge quotas and limits. The App runs on the Atlassian Forge platform and is subject to platform quotas and limits set by Atlassian, including limits on function invocation time, memory, payload size, storage volume and storage operation rates. These limits are set and varied by Atlassian, not by us.
5.2 Atlassian Platform rate limits. The App’s interactions with Jira are subject to Atlassian’s REST API rate limits and, where applicable, per-app rate limits.
5.3 Effect on your use. Where a Forge quota or an Atlassian rate limit is reached, the App may operate more slowly, defer or retry operations, return an error, or temporarily decline to perform a requested operation. Large data volumes and high concurrency make this more likely. You acknowledge that these behaviours arise from the Atlassian platform and that we cannot vary Atlassian’s quotas or limits. We design the App to degrade gracefully and to show meaningful messages where a limit is reached, and we will use reasonable endeavours to work within published limits, but we do not warrant uninterrupted operation and we are not liable for the consequences of Atlassian platform limits.
Kenvara also rations its own calls to stay within Atlassian’s limits: each Portal Customer has an hourly share of the lookups your site can make. When that share, Forge SQL’s quota or Atlassian’s licence service runs out or fails, Kenvara shows fewer Known Issues, or none, until it recovers. It never shows more. If Atlassian cannot confirm Kenvara’s licence for more than 24 hours, customers see nothing from Kenvara until it can.
5.4 Platform dependency. Availability of the App depends entirely on the availability of the Atlassian Cloud and the Forge platform. We do not offer an availability service level for the App and give no uptime commitment. Atlassian’s own service commitments, where applicable to you, are made by Atlassian under your agreement with Atlassian.
5.5 Platform change. Atlassian may change, deprecate or withdraw Forge platform capabilities, APIs, modules or storage services at its discretion. Where such a change materially affects the App, we will notify you as set out in section 9.9 of the Support and Maintenance Description.
6. Fees, payment and refunds
6.1 We set Kenvara’s price. You buy Kenvara from Atlassian, which is the merchant of record: Atlassian shows the price, invoices you, collects the fees, applies its own policies on evaluations, tax and refunds, and pays us. We do not process your payments or hold your payment details.
6.2 Refunds are Atlassian’s to give, under its refund policy, and requests should be directed to Atlassian, not to us.
6.3 Nothing in these Terms conflicts with, or purports to override, Atlassian’s licensing mechanisms, including evaluation licences, grace periods, licence tiers, renewal handling and enforcement of licence status. Where these Terms and an Atlassian licensing policy differ, the Atlassian policy prevails.
7. Your data and data protection
7.1 As between you and us, you own Your Data and are responsible for its accuracy, its legality, and for having the necessary rights and lawful bases to process it.
7.2 Kenvara runs entirely on Atlassian Forge and stores Your Data in Forge SQL and Forge’s key-value store, inside your installation and under your data residency settings. It declares no external access, and sends nothing to us or any third party. It writes to Jira only as section 5.2 of the Privacy Policy describes. Data leaves your site only through Jira’s own notifications, or in an Export File your administrator takes. We have no access to Your Data; we can read Kenvara’s log lines, which hold no account id or record text.
7.3 Where we process personal data on your behalf, we do so as processor and you as controller, on the terms of the Data Processing Agreement at https://kenvara.itsm-ltd.com/legal/data-processing-agreement/, which forms part of these Terms. Our handling of personal data is further described in the Privacy Policy.
7.4 You are responsible for administering user access to your Atlassian site and to the App, for the membership of your Customer Organisations, and for configuring permissions appropriately.
7.5 The history of changes cannot be edited. Kenvara keeps a history of every change, which no one can edit or delete, so that you can show what each Customer Organisation was shown and when. It records Atlassian account ids, which Kenvara replaces with “erased” once Atlassian reports the account closed. Known Errors cannot be deleted; they are withdrawn or retired. Clause 9 of the Data Processing Agreement sets out what this means for erasure requests.
7.6 Export, and what happens on uninstalling. A Jira administrator can export Your Data at any time, in every licence state, as an Export File holding every Known Error of the service projects you choose, with its versions, links and Audience and, unless you untick it, the audit history of the exported service projects. The file holds account ids: keep it as you would other personal data. Importing needs an active licence, and an import that is not a restore on the same site, with every service project still there, arrives unpublished.
Uninstalling Kenvara offers a choice. If you keep access, Atlassian keeps Kenvara running until the subscription or evaluation ends, plus 60 days. If you remove it immediately, it goes at once and any time left is given up. Either way, Atlassian then deletes its known errors under its own retention rules, up to about 30 days after it goes: its storage documentation gives 28 days, and its data-lifecycle page refers to the retention period in Atlassian’s SOC 2 report. So export first. Kenvara tries to turn itself off for every service project when it is uninstalled, but Atlassian does not guarantee when or whether that step runs, so do not rely on it.
If you reinstall and ask within 21 days of uninstalling, Atlassian can relink your earlier data with your consent. After that, your Export File is the only copy.
8. Support and maintenance
8.1 We provide support in accordance with the Support and Maintenance Description at https://kenvara.itsm-ltd.com/legal/support-and-maintenance/. In summary, support is provided by email only, between 09:00 and 17:00 UK time on UK business days, except that a suspected exposure of a Known Issue to the wrong customers is handled as a security incident, whatever the time.
8.2 Support is available only in respect of the App, only to customers holding a current licence, and only for supported versions. Response-time targets apply to paid licences only; see clause 3.3 for evaluation licences.
8.3 Support covers how Kenvara works. It does not cover how to run problem management, what to publish or to whom, or your obligations to your own customers.
8.4 We may release updates to the App. Minor updates deploy automatically across the Forge platform. A version that adds a permission, including Forge’s AI feature, needs your site administrator’s approval before it is installed. Before any AI feature, including a Rovo agent, is added, these documents will describe it, and its release notes will say so. Release cadence, supported versions, notice of breaking changes and end-of-life notice are set out in section 9 of the Support and Maintenance Description, which we will comply with.
9. Showing known issues to your customers
This section allocates the risk that is central to this product. Please read it.
9.1 You decide what customers see. A Known Error reaches the portal only when one of your agents publishes it, and only to the Audience they choose. You are responsible for what you publish, and to whom.
9.2 Kenvara enforces it on the server. On every portal call, Kenvara decides from three things: the viewer, as Atlassian identifies them; the Customer Organisations Jira Service Management says they belong to; and the Audience of the Known Issue. It never uses a request’s Organizations field, its participants or request-sharing settings. Anything it cannot work out hides the Known Issue.
9.3 Membership is yours to keep right. Kenvara treats each Customer Organisation’s member list as the truth. An email domain on an organisation, or open sign-up combined with email-domain grouping, can add people no one chose. Do not use either on an organisation you publish to, and review its members after any change.
9.4 How fast a removal takes effect. When someone is removed from an organisation, they stop seeing its known issues within 2 minutes at Kenvara’s default setting. Jira may take longer to report a removal. A page already open keeps what it showed until it is reloaded. When a removal must take effect at once, unpublish the known issue or change its audience first.
9.5 Customers who sign in with an Atlassian account. In this version, these customers see Known Issues published to specific organisations only while Kenvara’s daily check of your site’s organisations covers three or more organisations and is current. They do not see them if they belong to more than half of the site’s organisations (and at least three of them), or to an organisation created since the last check; they then see Known Issues published to all customers. Kenvara also switches this off by itself if a safety check sees an answer it cannot trust, and an administrator can switch it off at once.
9.6 Hidden is not broken. When Kenvara cannot confirm that a viewer is entitled to see a Known Issue, or when its licence, its share of the rate limit or its storage quota does not allow an answer, it shows nothing rather than risk showing too much. A Known Issue withheld for that reason is Kenvara working as designed, not a defect.
9.7 Replies reach everyone on the request. Applying a workaround as a reply posts the customer text as a public comment, which everyone who can see the request receives. Kenvara offers it only for a Known Error published to all customers.
9.8 Counts are indicative. The counts on a record’s Portal results tab count presses, not people. They are not evidence that any request was avoided.
9.9 Where Kenvara does not appear. Kenvara does not appear on Customer Service Management support sites, to anonymous portal visitors, in the knowledge base, or on another service project’s portal.
9.10 If a customer may have seen another organisation’s Known Issue, treat it as a security incident:
- unpublish the Known Issue or change its Audience;
- if it concerns customers who sign in with an Atlassian account, use Turn off now;
- tell us at once, at support@itsm-ltd.com, with “security” in the subject.
Section 8 of the Cloud Security Statement, and clause 10 of the Data Processing Agreement, say what we then do.
10. Warranties
10.1 We warrant that we have the right to grant the licence in clause 3, and that we will provide support with reasonable skill and care.
10.2 We warrant that the App will perform materially in accordance with its published documentation. Your exclusive remedy for breach of this warranty is that we will, at our option, correct the defect or terminate the licence and support a pro-rata refund request to Atlassian for the unused portion of your Subscription Term.
10.3 Except as expressly stated in these Terms, the App is provided “as is” and we exclude all other warranties, conditions and representations, whether express or implied by statute, common law or otherwise, including implied warranties of satisfactory quality, fitness for a particular purpose and non-infringement, to the fullest extent permitted by law. We do not warrant that the App will be uninterrupted or error-free, or that it will meet your particular requirements.
10.4 Without limiting clause 10.3, we give no warranty that a Known Issue will prevent any request, or that a Known Issue will be shown when Kenvara cannot confirm that a viewer is entitled to see it: Kenvara hides it by design (clause 9.6).
10.5 Safety-critical use. The App is a record-keeping and publishing tool. It is not designed or licensed for use in the operation or control of systems where failure could lead to death, personal injury or severe environmental damage, and must not be used for that purpose. Nor is it a channel for an urgent notice that must reach a particular customer, because it hides a Known Issue whenever it is unsure.
11. Indemnity
11.1 We will defend you against any third-party claim that the App, used in accordance with these Terms, infringes that party’s intellectual property rights, and will pay damages finally awarded or agreed in settlement, provided you notify us promptly, give us sole conduct of the defence and provide reasonable assistance.
11.2 This indemnity does not apply to claims arising from: Your Data or content; modification of the App by anyone other than us; combination of the App with anything not supplied by us where the claim would not have arisen otherwise; use after we have notified you to stop; use of an evaluation licence; or your publication of a Known Issue or other content you write.
11.3 If a claim arises or is likely, we may at our option procure the right for you to continue using the App, modify or replace it so it is non-infringing, or terminate the licence and support a pro-rata refund request. This clause states our entire liability for intellectual property infringement.
12. Limitation of liability
12.1 Nothing in these Terms limits or excludes either party’s liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, or for any liability that cannot lawfully be limited or excluded.
12.2 Subject to clause 12.1, neither party is liable for loss of profit, loss of revenue, loss of anticipated savings, loss of business or business opportunity, loss of goodwill, loss or corruption of data, or any indirect or consequential loss, however arising.
12.3 Subject to clauses 12.1 and 12.2, we are not liable for loss arising from content you publish, the Audiences you choose, or the roles and Customer Organisation memberships you configure in Jira Service Management.
12.4 Subject to clauses 12.1 and 12.2, our total aggregate liability arising out of or in connection with these Terms, whether in contract, tort (including negligence), breach of statutory duty or otherwise, is limited to the total fees you paid for the App in the 12 months immediately preceding the event giving rise to the claim. Where you use the App under an evaluation licence, our total aggregate liability is limited to £100.
12.5 We are not liable for any failure, delay, degradation, data loss or unavailability caused by the Atlassian Cloud, the Forge platform, Atlassian platform quotas or rate limits, Atlassian’s licence service, the customer organisation data Jira Service Management reports, or any act or omission of Atlassian.
12.6 You acknowledge that these limitations are reasonable given the fees charged, the nature of the App, and the allocation of risk between us.
13. Term, changes and termination
13.1 These Terms take effect when you first install or use the App and continue for the duration of your Subscription Term.
13.2 Changes to these Terms. We may amend these Terms. We will publish the amended version and update the effective date. Where a change materially reduces your rights or increases your obligations, we will give at least 30 days’ notice before it takes effect, and the change will not apply retrospectively or materially reduce our obligations during your then-current Subscription Term. Continued use after the notice period constitutes acceptance.
13.3 Termination by you. You may terminate at any time by uninstalling the App. Fees already paid to Atlassian are refundable only under Atlassian’s refund policy. Take any export you need first; see clause 7.6.
13.4 Termination by us. We may suspend or terminate the licence immediately on written notice if you materially breach these Terms and, where the breach is capable of remedy, fail to remedy it within 14 days of notice; or immediately if you become insolvent or cease trading.
13.5 End of life. We may retire Kenvara on Atlassian’s terms for retiring a Marketplace app. We will give at least 90 days’ notice to the technical contact on your licence, and support you for the subscription you have already bought. When Atlassian then archives Kenvara, it stops working for every site and Atlassian deletes its data, so export first (clause 7.6).
13.6 Effect of termination. On termination you must cease use and uninstall the App. Clauses 4, 7.6, 9, 10.3, 10.4, 11, 12, 14 and 15 survive.
14. General
14.1 Assignment. You may not assign these Terms without our written consent. We may assign them to an affiliate or in connection with a merger, reorganisation or sale of substantially all our assets.
14.2 Publicity. We will not use your name or logo as a reference without your prior written consent.
14.3 Notices. Notices to us must be sent to support@itsm-ltd.com. Notices to you will be sent to the technical or billing contact recorded on your Atlassian licence.
14.4 Force majeure. Neither party is liable for failure to perform caused by events beyond its reasonable control.
14.5 Entire agreement. These Terms and the incorporated documents constitute the entire agreement between us in respect of the App and supersede all prior discussions. Nothing in this clause limits liability for fraudulent misrepresentation.
14.6 Third-party rights. No person other than the parties has any right under the Contracts (Rights of Third Parties) Act 1999 to enforce these Terms, save that Atlassian may enforce clause 1.2.
14.7 Severance. If any provision is held invalid or unenforceable, it is severed and the remainder continues in force.
14.8 Waiver. No failure or delay in exercising a right constitutes a waiver of it.
14.9 Export and sanctions. You must comply with all applicable export control and sanctions laws, and confirm you are not located in, or acting on behalf of a person in, a sanctioned territory.
15. Governing law and jurisdiction
15.1 These Terms and any dispute or claim arising out of or in connection with them, including non-contractual disputes, are governed by the laws of England and Wales.
15.2 The courts of England and Wales have exclusive jurisdiction, save that either party may seek injunctive relief in any court of competent jurisdiction.
Published in accordance with the Atlassian Marketplace Partner Agreement. Read alongside the privacy policy, cloud security statement and support and maintenance description for Kenvara.