TuneCraft terms of service
Effective [date of publication]
The short version
- The app is a subscription sold through the Atlassian Marketplace, and Atlassian handles the billing. Without an active subscription or trial, its tools stop working.
- Your data is yours. It stays in your Jira site, and we don't access it. TuneCraft changes your Jira configuration only when a Jira admin confirms. The work items it creates are owner notices, sent by a person at the Manage level as themselves; the work items of the To do page, created as the Jira admin who confirms them; and alerts, which the app creates as itself.
- We work hard to make the app reliable, but we provide it as is and you use it at your own risk. We accept no liability for any damage.
The full terms below are what count.
- About these terms
- Licensing
- What you agree not to do
- Updates and support
- Your data
- Atlassian's platform and usage limits
- Ownership
- No warranty
- No liability
- Governing law
- General
1. About these terms
These terms are an agreement between Plugincraft Software Inc. ("Plugincraft", "we", "us"), a company incorporated under the laws of Québec, Canada, and you, the organization or person using our products ("you"). They cover the TuneCraft: Automation & Site Cleanup app for Jira Cloud (the "app"), our support for it, and the website at plugincraft.ca.
You accept these terms when you install or use the app. If you accept them for an organization, you confirm that you're allowed to bind it.
2. Licensing
The app is sold as a subscription through the Atlassian Marketplace. These terms are its end-user agreement: the Marketplace listing links to them, and you accept them when you install the app, try it or subscribe to it.
Atlassian bills you, renews your subscription and handles refunds under the Atlassian Marketplace Terms of Use. The price and billing cycle are the ones shown on the listing. We don't bill you directly.
You can try the app free of charge for the trial period Atlassian offers. During a trial every tool's reports and checks work in full, with these limits: each clean-up tool may change at most 10 objects in Jira, a label change may touch at most 1,000 work items, and Optimize prepares a fix for one flow only. Undoing a change never counts against the limit.
When your Jira site has no active subscription or trial, the app's tools stop working: its pages say why, and it refuses to scan, report or make a new change. Help, the History page (to list and delete scans), each tool's Changes page with Undo for a change already recorded (Jira admins only), Maintenance, Database size and the support bundle keep working, and so do the settings of who may open the app and of how long without use makes something stale (a field, a filter or a space, for example), and turning a tool's background checks off, so that an admin can still get help, give a change back and clean up. These wait for an active subscription or trial: the cost model and the measured run counts, the alert settings that turn alerts on and test alerts, the rules of Policy checks, targets and guidance for checks, the usage a Jira admin types from Jira's usage page, and turning a tool's background checks on. The tools work again as soon as a subscription is active.
You may use the app only for your organization's own internal business purposes.
You can stop using the app at any time by uninstalling it.
3. What you agree not to do
- Sell, rent, sublicense or share the app with anyone outside your organization.
- Copy, modify, decompile or reverse engineer the app, except where the law allows it despite this restriction.
- Use the app to break the law, to infringe anyone's rights, or in breach of Atlassian's terms.
4. Updates and support
We release fixes and improvements from time to time. Atlassian delivers them to your site. A version that asks for a new permission is a major version, and your site admins must approve it before it is installed on your site. We may change or remove a feature, for example when Atlassian changes its platform, but we won't take away the core purpose of the app.
Support is by email to info@plugincraft.ca. Support hours are Monday to Friday, 9:00 to 17:00 Eastern Time (Montréal), except Québec statutory holidays, in English and French. A request that arrives outside these hours counts from the start of the next business day. We respond to critical problems (the app is unusable, or a security matter) within 24 hours, five business days a week, and to security alerts from Atlassian within 8 business hours, as set out in Incident Response. We answer other requests as quickly as we reasonably can, usually within two business days. Apart from those commitments, we don't promise fixed response or resolution times unless we agree to them in writing.
If we ever decide to stop offering the app, we'll announce it at least 90 days ahead.
5. Your data
Everything you create with the app belongs to you. The app stores it in Atlassian's Forge storage for your Jira site, and it does not send it to us. You are responsible for what you put in it.
When a Jira admin confirms a change, the app makes it in Jira with that admin's Jira rights: for example a new owner or name for a filter, the removal of a custom field, label, space, version, status or workflow, or the deletion of attachments. The app shows what it will do first, keeps a record, and offers an undo where Jira allows one. Some changes cannot be undone, such as what Jira deletes for good, and the app says so before it asks. You are responsible for checking a change before you confirm it, and for keeping the record files you need.
The app also creates Jira work items. An owner notice can be sent by anyone at the Manage level (a Jira admin, or a member of a group a Jira admin allowed to manage TuneCraft), and it is created as that person. The To do page's work items are created as the Jira admin who confirms them. An alert is created by the app, as itself, in the project and work item type a Jira admin picked.
The app's findings are suggestions based on what it can read. A field, flow or filter it lists as unused may still be needed by something it cannot see, such as another app or a rule it was not given. Its figures say whether they are measured or estimated. An estimate, such as the steps a fix would save a month, is not a promise of savings or of what Atlassian will bill.
If a Jira admin turns on the automatic scan, the sender is a script that you run, on your own systems or as a scheduled job in ScriptRunner Cloud, a script app from another publisher that you installed. You are responsible for the sender, where it runs, its schedule, the Atlassian API token it uses and the automatic scan's key, which you keep secret: whoever holds it can push scans to the app. Plugincraft does not run the sender and does not receive the token.
Our privacy policy explains how we handle personal information. If you need a data processing agreement, ours is the Data Processing Agreement, and it forms part of these terms for the personal data the app processes for you.
6. Atlassian's platform and usage limits
The app runs on Jira Cloud and Atlassian Forge, which Atlassian operates. Your use of Atlassian's products is governed by your agreement with Atlassian. We don't control Atlassian's services and aren't responsible for their outages, limits or changes. If a change by Atlassian makes a feature impossible to offer, we may remove it.
Atlassian gives apps no access to your Jira automation rules, to read or to change. TuneCraft therefore works from the export of your rules, or from what a sender you run pushes, and prepares a corrected flow for you to import in Jira. It never changes a rule itself.
Atlassian limits how many requests can be made to Jira in a given period, as described in Atlassian's rate limiting documentation. When a limit is reached, Jira refuses requests until it resets. The app then pauses: pages may say Jira is limiting requests and ask you to try again a little later, a background check waits for its next turn, and a change that stops part way reports what it has not done yet.
The background checks read Jira as the app, and only when a Jira admin turns them on. They run within a budget of Jira points that the app sets for itself, so on a busy site they can take a while to catch up. The app also caps the size of what it handles, such as the size of a scan, how many objects a change may touch at once and how much a check reads in one pass, so that it stays within what Jira and Forge allow.
Atlassian sets its limits and may change them at any time, and we may adjust the app's own caps to match. These limits, and the delays, pauses and partial results they cause, are part of how the app works. They are not a defect and do not entitle you to any compensation.
7. Ownership
Plugincraft owns the app, its code, its documentation, this website and our names and logos. Apart from the use of the app described in section 2, these terms give you no rights in them. If you send us suggestions, we may use them freely, with no obligation to you.
8. No warranty
The app, the website and our support are provided "as is" and "as available". To the fullest extent the law allows, we make no warranty of any kind, express or implied, including any warranty of merchantability, fitness for a particular purpose, or that the app will be uninterrupted or error-free.
9. No liability
You use the app, the website and our support at your own risk. To the fullest extent the law allows, Plugincraft is not liable for any damage of any kind arising from their use or from being unable to use them, whether direct or indirect, incidental, special, consequential or punitive. This includes any loss or corruption of data, any change made to Jira, and any loss of profits, revenue, business or goodwill, even if we were told such damage was possible.
If a court decides that some liability cannot be excluded despite this section, that liability is limited to the amount paid for your subscription to the app in the 12 months before the claim arose.
Nothing in these terms excludes or limits liability for intentional or gross fault, for bodily or moral injury caused to a person, or any right a consumer has under the law that cannot be waived by contract.
10. Governing law
These terms are governed by the laws of Québec and the federal laws of Canada that apply there. Any dispute goes before the courts of Québec, unless the law gives you, as a consumer, the right to bring it in your own district. Before going to court, we both agree to try to settle the matter in good faith by email for at least 30 days.
11. General
- Changes. We may update these terms. We'll change the date at the top, and post a significant change on this page at least 30 days before it takes effect. A change never applies to a dispute that started before it.
- Whole agreement. These terms and our privacy policy are the whole agreement between us about the app.
- Severability. If a court finds part of these terms unenforceable, the rest still applies.
- No waiver. If one of us doesn't enforce a right immediately, that right is not lost.
- Transfer. We may transfer these terms to a buyer of Plugincraft, who must honour them.
- Notices. We'll write to the email address you gave us. You can write to us at info@plugincraft.ca.
- Language. These terms are available in English and French. You may choose either version, and both have the same value.