Which terms apply
Canopy is sold through the Atlassian Marketplace. Your purchase is governed by the Atlassian Marketplace Terms of Use. Your use of Canopy is governed by an agreement between you and BLOOMLOGIC LTD, made up of:
- The Bonterms Standard End User Agreement (Version 1.0), the standard form Atlassian offers to Marketplace publishers, which we have adopted for Canopy: https://www.atlassian.com/licensing/marketplace/end-user-agreement-v1
- Our Provider-Specific Terms, set out below, which take precedence over the standard form. They make English law apply, make our Data Processing and Sub-processors page part of the agreement, and set the limits on liability.
The rest of this page explains in plain terms what we undertake. Where it differs from the agreement, the agreement wins.
Provider-Specific Terms
These Provider-Specific Terms modify the Bonterms Standard End User Agreement (Version 1.0) for Canopy. "Provider" means BLOOMLOGIC LTD, a company registered in England and Wales, company number 11173973.
- Governing Law and Courts. The "Governing Law" is the law of England and Wales and the "Courts" are the courts of England and Wales.
- Data Protection Addendum. The DPA is Provider's Data Processing and Sub-processors page at https://bloomlogic.co.uk/data-processing, and is an Attachment. Provider may update the DPA on prior notice to Customer. No update may apply retroactively or reduce any protection the DPA gives, including Customer's rights concerning its personal data, and an update does not itself authorise processing outside Customer's documented instructions. Changes of sub-processor follow the DPA's own procedure.
- Support Policy. Support is as described on Provider's Support page at https://bloomlogic.co.uk/support.
- Limits of liability. "General Cap" means the greater of (a) US$1,000 and (b) the fees paid or payable for the Product under this Agreement in the 12 months immediately preceding the first incident giving rise to liability, whether paid to Provider or to the Marketplace. "Uncapped Claims" means liabilities that cannot be limited under applicable law. "Enhanced Claims" means, other than Uncapped Claims: (a) Provider's breach of Section 3.2 (Security); (b) either party's breach of Section 3.3 (DPA); (c) either party's obligations under Section 15 (Indemnification), including the cost of defending a claim; (d) either party's infringement or misappropriation of the other party's intellectual property rights; and (e) either party's breach of Section 16 (Confidentiality), including breaches related to Customer Data. The Enhanced Cap remains three times the General Cap.
- Usage limits. Canopy runs on Atlassian's Forge platform and works through Jira's own interfaces. Atlassian sets quotas and rate limits on both and may change them. These limits can delay or prevent loading or saving, especially on large projects or when many people work at once. Canopy retries when Jira asks it to slow down, but a load or save can still fail and need to be tried again.
- Canopy and Jira. Canopy is a Cloud Service for the purposes of this Agreement. Jira Cloud, as supplied to Customer under Customer's agreement with Atlassian, is a Third-Party Platform. Customer Data includes Jira data processed by Canopy. Canopy does not provide a backup or recovery service for Jira work. This paragraph does not limit Provider's obligations for Canopy's own processing or for its subcontractors.
- Data Export and Deletion. Customer remains responsible for exporting and deleting records held in Customer's Jira site, including records created there through Canopy (issue links, issue properties and archive marks); Section 12.4 does not require Provider to export or delete those records from Jira. Canopy's own stored data (saved Views, Branches, palettes, templates, baselines, preferences and the other app-storage records the DPA describes) is held by Atlassian in Forge app storage. A Jira administrator of Customer's site (a user holding Jira's Administer Jira permission) can download all of it for a project, as one machine-readable file, from Canopy's menu (Download Canopy's data), including after a subscription has lapsed; the file includes every user's private saved items. Customer can delete individual saved items in Canopy while its subscription and Jira permissions allow. To have the data back and then deleted, Customer downloads it first and then uninstalls Canopy: uninstalling instructs deletion of all of it, on the schedule the DPA sets out for an uninstall, in place of the 60 days in Section 12.4; if Customer asks Provider for deletion instead, Provider will explain how to uninstall. Canopy's diagnostic log has its own 30-day retention. Removal by Atlassian after a subscription is not renewed follows the retention and recovery arrangements in Provider's Privacy Policy. This paragraph does not otherwise modify Section 12.4.
- After a subscription ends. After a subscription ends without renewal, Customer may keep using Canopy read-only for as long as Atlassian keeps it installed, subject to this Agreement. This continued read-only use is not a Trial or Beta merely because no further subscription fee is payable.
- Notices. Provider's notice address is support@bloomlogic.co.uk, or by post its registered office, 82a James Carter Road, Mildenhall, Bury St. Edmunds, IP28 7DE, England.
Who you are buying from
Canopy is published by BLOOMLOGIC LTD, company number 11173973, registered in England and Wales, registered office 82a, James Carter Road, Mildenhall, Bury St. Edmunds, England, IP28 7DE.
Your contract for payment is with Atlassian, not with us. Atlassian bills you, handles your subscription, and processes refunds, including any due to you under the agreement.
What we undertake
- To keep the app working with current versions of Jira Cloud, and to fix faults we can reproduce.
- To answer support requests as set out on our Support page.
- To tell you before we take something away. If a feature is withdrawn, we will say so in the release notes on Canopy's Atlassian Marketplace listing before it disappears, except where it must be removed at once for security or because Atlassian or the law requires it; then we will say so when it is removed. Any withdrawal remains subject to the Performance Warranty in the agreement.
- Not to hold your work hostage. The hierarchy Canopy displays is stored in Jira's own issue links and properties. If you stop using Canopy, that structure stays in Jira and can be read by anything else that reads Jira.
What we do not undertake
- Canopy is not a backup. It displays and edits your Jira work; it does not keep a second copy you could restore from. Deleting an issue through Canopy deletes it in Jira, subject to your own Jira permissions.
- We cannot restore deleted work. Recovering a deleted Jira issue is an Atlassian matter, and often not possible at all.
- Canopy's app-stored settings and records become unavailable on uninstall. Saved Views, Branches, preferences and the rest go when the app is removed; a Jira admin can download them first (Canopy's menu, Download Canopy's data). How long Atlassian keeps them, and how they can be recovered, is in the Privacy Policy. Your issues are not affected.
If your subscription lapses
While Atlassian keeps the app running, Canopy switches to read-only once Atlassian reports the subscription inactive. You can still open it, look at your project, apply your saved Views and change how you are looking at things. You cannot change your Jira work through it, or create, change or delete saved Views, Branches, palettes, templates or baselines. Your Jira work is never deleted, and editing returns when the subscription is active again. Atlassian removes the app about two months after a subscription ends without being renewed, and what Canopy stored (saved Views, Branches, palettes, templates and baselines) is then deleted as the Privacy Policy describes; how long the app keeps running in the meantime is Atlassian's decision, not ours.
Availability
Canopy runs on Atlassian's Forge platform and depends on it and on Jira Cloud. An outage affecting those services, or a fault in Canopy itself, can make the app unavailable. We operate no separate infrastructure of our own for it. Atlassian's quotas and rate limits can also slow it on large projects or under heavy use (paragraph 5 of the Provider-Specific Terms).