End user terms — Custom Field Cleanup & Where-Used for Jira

Version 1.0, dated 4 November 2026. These terms apply to every order, trial and renewal placed on or after that date.

1. Who we are and what these terms cover

1.1 These terms are between Neirfeno Limited (company number SC514019, registered office 7 Thorter Way, Dundee DD1 3DF, Scotland) (“we”, “us”) and the organisation that installs or orders our app (“you”). The person who accepts these terms for an organisation confirms that they have authority to bind it.

1.2 They cover our Atlassian Forge app Custom Field Cleanup & Where-Used for Jira (the “App”), including any updates, its documentation and any support we give.

1.3 You accept these terms when you install, start a trial of, order or use the App. If you don’t agree, don’t install or use it.

1.4 You buy the App through the Atlassian Marketplace. Atlassian acts as our commercial agent for payments. Your order, payment, renewals, trials and refunds are governed by the Atlassian Marketplace Terms of Use. Your use of Jira and of Atlassian’s Forge platform is governed by your agreement with Atlassian. Atlassian is not a party to these terms. If these terms conflict with Atlassian’s licensing rules for trials, grace periods or licence status, Atlassian’s rules apply to that point.

1.5 The App is for business use only. We sell it to organisations, not to consumers. If you are nevertheless a consumer under the law of the country where you live, nothing in these terms takes away the rights that law gives you and that cannot be excluded.

2. What you can do with the App

2.1 For as long as you have a valid trial or paid licence from the Atlassian Marketplace, we give you a non-exclusive, non-transferable right to use the App on the Jira Cloud site where it is installed, for your own internal business purposes, for the number of users your licence covers.

2.2 You must not: (a) resell, sublicense or share the App with anyone outside your organisation, or use it to provide a service to others; (b) copy, modify, reverse engineer or decompile it, except where the law allows you to and we can’t prevent it; (c) try to get round its licence checks or Atlassian’s access controls; (d) use it in breach of any law, including export and sanctions law (§13.4).

2.3 We (and our licensors) keep all rights in the App. If you send us feedback, we may use it freely and without paying you, but we won’t name you as its source without your permission.

3. What the App does

3.1 The App reads your Jira configuration (for example custom fields, contexts, screens, schemes, workflows, statuses, projects, saved filters and their JQL, boards, dashboards and gadgets). It shows where each item is used and lists custom fields that look unused, stale or duplicated. It can then move custom fields you choose to Jira’s trash, and restore them from it, with an audit log.

3.2 The App runs entirely on Atlassian’s Forge platform (“Runs on Atlassian”). It stores its data in Atlassian-hosted Forge storage for your site. It has no connection to any server of ours or of anyone else. The only outbound call is Atlassian’s own personal-data reporting service, which Atlassian requires every app that stores account IDs to use.

3.3 The App does not use artificial intelligence or machine learning. Its findings come from fixed rules in its code. It does not send your data to any AI service.

3.4 Findings are evidence, not guarantees. Each “unused” or “safe to delete” result is a confidence score with the evidence behind it. The App does not check automation rules, scripts (for example ScriptRunner), the data or configuration of other apps, or anything Atlassian’s APIs don’t let it read. It also can’t see items your Jira permissions or Atlassian’s limits hide from it (see §4). Each dry run says so.

4. Atlassian platform limits

4.1 The App depends on Jira Cloud, Forge and Atlassian’s APIs, which we don’t control. Atlassian sets limits that can affect how the App works for you, including:

(a) API rate limits. By default, all installations of the App share one hourly quota of Jira API “points” set by Atlassian (65,000 points an hour on the date of these terms). On large sites, or when many customers scan at once, a scan can pause and resume later, take hours, or finish with some items not checked. The App shows any such “coverage gaps”.

(b) Forge quotas and limits, for example function time-outs, queue limits, storage and log limits.

(c) Changes, outages and maintenance of Jira, Forge or Atlassian’s APIs, including changes to how Jira’s trash works.

4.2 We will try to keep the App working within these limits, but we are not responsible for delays, gaps or failures they cause.

5. Moving fields to Jira’s trash, and restoring them

5.1 Only you decide what goes to the trash. The App never moves a field to the trash on its own. Moving a field to the trash needs a user with Jira’s Administer Jira permission to select the field, review a dry run and confirm. The App then asks Jira, as that user, to trash each selected field. It can trash only unlocked, company-managed custom fields. It never permanently deletes anything.

5.2 How Jira’s trash works. Trash is a Jira feature provided by Atlassian, not by us. Atlassian says that a trashed field is tagged for deletion in 60 days, and that while it’s in the trash it is removed from any automations, advanced workflow functions and third-party apps that use it, and doesn’t show on screens or configurations. This happens straight away, even though the field can be restored. A field restored within the 60 days is re-added to the places it was used, with its data. After the 60 days, Jira permanently deletes the field and its data and neither we nor the App can bring it back. Atlassian may change these rules.

5.3 Your responsibilities. Before you move a field to the trash, you are responsible for: (a) reviewing the evidence and the dry run; (b) checking what the App can’t check (§3.4), including automation rules, scripts, other apps, integrations, reports and anything outside Jira that uses the field; (c) taking any backup or export you need; (d) telling the people who use the field; and (e) restoring the field within Jira’s restore period if you need it back.

5.4 What we are responsible for. We are not responsible for the consequences of a field being trashed because you or your users chose to trash it, or for loss after Jira’s restore period ends. We are responsible, within the limits in §10, if a defect in the App trashes a field that your user did not select, or stops a field you selected from being restored within Jira’s restore period when Jira itself would have allowed it.

6. Our promises, and their limits

6.1 We promise that: (a) we will provide the App with reasonable care and skill; (b) the App will work materially as its documentation and Marketplace listing describe; and (c) we have the right to license it to you.

6.2 If the App doesn’t meet §6.1(b), tell us in reasonable detail at contact@neirfeno.com within 30 days of noticing. We will try to fix it, or give you a reasonable workaround, within 30 days. If we can’t, either of us may end your subscription, and we will ask Atlassian to refund you, or will refund you ourselves, the fees you prepaid for the period after it ends.

6.3 §6.2 does not apply to problems caused by Jira, Forge or other Atlassian services, by Atlassian’s limits (§4), by other apps or scripts, or by use of the App against these terms or its documentation.

6.4 EXCEPT FOR THE PROMISES IN §6.1, AND TO THE FULLEST EXTENT THE LAW ALLOWS, THE APP IS PROVIDED “AS IS” AND “AS AVAILABLE”. WE GIVE NO OTHER WARRANTIES, CONDITIONS OR TERMS, WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, SATISFACTORY QUALITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE OR NON-INFRINGEMENT, OR THAT THE APP WILL BE ERROR-FREE, UNINTERRUPTED OR FIND EVERY USE OF A FIELD.

6.5 Trials and free use (including use free of charge under the Marketplace’s free tier for small sites) are for evaluation. §6.1(b) and §6.2 do not apply to them.

7. Your data and privacy

7.1 Your data stays yours. As between us, you own your Jira data and the data the App stores about your configuration (“Your Data”). We use Your Data only to provide the App and support to you, and as Schedule 1 allows.

7.2 Where it is held. The App stores Your Data only in Atlassian’s Forge-hosted storage (Forge SQL) for your site. Atlassian holds it in the same data-residency location as your Jira site. The App logs a limited amount of information to Atlassian’s Forge logs. Our privacy notice at https://neirfeno.com/custom-field-cleanup/privacy.html describes exactly what the App stores and logs, who can see it and how long it is kept.

7.3 Logs. Atlassian lets us, as the App’s developer, see the App’s logs for your site in Atlassian’s developer console, so that we can fix problems. Your site admins can switch this off at any time in Atlassian Administration (Apps > Connected apps > the App > Logs access). If you switch it off, we may need you to turn it back on, or to send us logs, before we can solve a problem.

7.4 Data processing terms. Your Data may include personal data (for example Atlassian account IDs, and anything your users have typed into the names or JQL of filters, boards, dashboards and gadgets). To the extent we process personal data for you, Schedule 1 applies. It is our data processing agreement.

7.5 Your responsibilities. You are responsible for having the right to let the App read Your Data, for the content of Your Data, and for telling your users about the App where the law requires.

8. Support and changes to the App

8.1 We give support by email at contact@neirfeno.com, Monday to Friday, 09:00 to 17:00 UK time, excluding Scottish public holidays. We aim to reply within 2 business days. Support covers the App only, not Jira or Atlassian services.

8.2 We may update the App, for example to fix bugs, improve it, or keep up with changes to Atlassian’s platform. We won’t materially reduce its core functions (where-used views, the finder, dry run, trash and restore) during a paid subscription period, unless Atlassian or the law makes us.

8.3 We can stop offering the App. If we do, we will give at least 90 days’ notice by email or in the Marketplace listing where we can. We will keep the App available, and support it, until the end of any paid subscription period, as Atlassian’s Marketplace rules require.

9. Fees, renewals and refunds

9.1 Fees are as shown in the Marketplace listing or your order, and you pay them to Atlassian. Atlassian handles renewals, upgrades, price changes and taxes.

9.2 Refunds are handled by Atlassian under its Marketplace refund policy. On the date of these terms, it lets you cancel an initial order (not a renewal or upgrade) within 30 days and get a refund. For later requests, contact us at contact@neirfeno.com; we will consider them case by case. §6.2, §11.3 and §12.2 give you further refund rights in specific cases.

10. Limits on our liability

10.1 Nothing in these terms limits or excludes liability that cannot lawfully be limited or excluded, including liability for death or personal injury caused by negligence, or for fraud or fraudulent misrepresentation.

10.2 SUBJECT TO §10.1, WE ARE NOT LIABLE, WHETHER IN CONTRACT, DELICT OR TORT (INCLUDING NEGLIGENCE), FOR BREACH OF STATUTORY DUTY OR OTHERWISE, FOR ANY OF THE FOLLOWING, WHETHER DIRECT OR INDIRECT:
(a) LOSS OF PROFITS, REVENUE, SALES OR BUSINESS;
(b) LOSS OF ANTICIPATED SAVINGS;
(c) LOSS OF GOODWILL OR REPUTATION;
(d) WASTED EXPENDITURE OR WASTED MANAGEMENT OR STAFF TIME;
(e) LOSS OR CORRUPTION OF DATA, EXCEPT THE REASONABLE COST OF RESTORING IT FROM A BACKUP OR FROM JIRA’S TRASH; OR
(f) ANY OTHER INDIRECT, SPECIAL OR CONSEQUENTIAL LOSS, OR ANY OTHER PURE ECONOMIC LOSS,
EVEN IF THE LOSS WAS FORESEEABLE OR WE WERE TOLD IT MIGHT HAPPEN.

10.3 SUBJECT TO §10.1, OUR TOTAL LIABILITY TO YOU FOR ALL CLAIMS ARISING OUT OF OR IN CONNECTION WITH THE APP OR THESE TERMS, WHETHER IN CONTRACT, DELICT OR TORT (INCLUDING NEGLIGENCE), FOR BREACH OF STATUTORY DUTY OR OTHERWISE, IS LIMITED TO THE GREATER OF:
(a) THE FEES PAID OR PAYABLE FOR THE APP BY OR FOR YOU IN THE 12 MONTHS BEFORE THE EVENT THAT GAVE RISE TO THE FIRST CLAIM; AND
(b) £5,000 (OR ITS EQUIVALENT IN THE CURRENCY YOU PAID IN).

10.4 Why these limits are reasonable. The App is low cost and sold to many customers. It never deletes anything permanently, and it gives you a dry run and a 60-day restore window before anything is lost. You are best placed to judge your own setup, to take backups and to insure your own business losses. Our fees are set on the basis of these limits.

10.5 Nothing in §10 limits your duty to pay fees to Atlassian.

11. Third-party claims about our App

11.1 If someone claims that your authorised use of the App infringes their intellectual property rights, tell us promptly, let us control the defence and any settlement, and give us reasonable help (at our cost). We will then defend the claim and pay any damages finally awarded against you, or agreed by us in settlement, because of it.

11.2 §11.1 doesn’t apply to claims caused by Jira, Forge or other Atlassian technology, other apps, changes not made by us, or use against these terms.

11.3 If such a claim is made or we think it likely, we may change the App so that it doesn’t infringe, get you the right to keep using it, or end your subscription and refund the prepaid fees for the rest of the paid period.

11.4 §11 is your only remedy for intellectual property claims, and our liability under it is subject to §10.3.

12. Ending these terms

12.1 Your right to use the App ends when your trial or licence ends, or when you uninstall the App.

12.2 Either of us may end these terms by notice if the other seriously breaches them and doesn’t put the breach right within 30 days of notice. If you end them because of our breach, we will refund (or ask Atlassian to refund) the prepaid fees for the rest of the paid period.

12.3 We may suspend or end your use of the App straight away if you breach §2.2, or if Atlassian or the law requires it.

12.4 What happens to Your Data. When the App is uninstalled, Atlassian deletes the App’s storage for your site under its own retention rules (see our privacy notice). We hold no copy. Fields already in Jira’s trash stay in Jira under Atlassian’s rules and can still be restored there until Jira’s restore period ends.

12.5 Sections 2.3, 5.4, 7, 10, 11.4, 12.4, 13 and Schedule 1 (for as long as we process personal data for you) continue after these terms end.

13. General

13.1 Changes to these terms. We may update these terms, for example to reflect changes to the App, Atlassian’s rules or the law. We will publish the new version, with its date, at this address and give notice in the Marketplace listing. A new version applies from your next renewal or order after it is published, unless the change is needed to comply with law or Atlassian’s rules, in which case it applies from 30 days after publication. Earlier versions are available on request.

13.2 Law. These terms, and any dispute or claim (including non-contractual disputes or claims) arising out of or in connection with them or the App, are governed by the law of Scotland. The United Nations Convention on Contracts for the International Sale of Goods does not apply.

13.3 Courts. THE COURTS OF SCOTLAND HAVE EXCLUSIVE JURISDICTION to settle any such dispute or claim, and each of us submits to them. TO THE EXTENT THE LAW ALLOWS: (A) EACH OF US WAIVES ANY RIGHT TO A JURY TRIAL; AND (B) ANY CLAIM MUST BE BROUGHT BY EACH OF US ONLY ON OUR OWN BEHALF, AND NOT AS A CLAIMANT OR MEMBER IN ANY CLASS, COLLECTIVE OR REPRESENTATIVE ACTION. Before starting proceedings, the party with a complaint will first email the other with details and allow 30 days to try to settle it, except where urgent action is needed to protect intellectual property or confidential information.

13.4 Export and sanctions. Each of us will comply with the export control and sanctions laws that apply to it, including those of the United Kingdom and, where they apply, the United States. You confirm that you are not named on, or owned or controlled by anyone named on, a UK, United Nations, EU or US sanctions or restricted-party list, and that you will not use the App in, or for anyone in, a country or region subject to comprehensive UK or US sanctions.

13.5 US government users. The App is “commercial computer software” and its documentation is “commercial computer software documentation”, as those terms are used in FAR 12.212 and DFARS 227.7202. US government users get only the rights set out in these terms.

13.6 Things outside our control. Neither of us is liable for delay or failure caused by events beyond our reasonable control, including outages or changes of Atlassian services.

13.7 Other terms. These terms (with Schedule 1 and the documents they refer to) are the whole agreement between us about the App. Purchase-order terms do not apply. Each of us confirms that it has not relied on any statement not set out in these terms, but this does not limit liability for fraud. If a court finds part of these terms unenforceable, the rest still applies. A delay in enforcing a term is not a waiver. No one else has any right to enforce these terms, including under the Contract (Third Party Rights) (Scotland) Act 2017. You may not transfer these terms without our consent; we may transfer them to a business that takes over the App, if we tell you.

13.8 Notices. Send notices to us at contact@neirfeno.com and by post to our registered office. We will send notices to the email address you have used to contact us, or through the Marketplace listing. Email notices take effect when sent, unless the sender gets an error message.

Schedule 1: Data processing terms

This Schedule is our data processing agreement under Article 28 of the UK GDPR and, where it applies, the EU GDPR. It applies to the extent that we process personal data on your behalf through the App.

1. Roles. You (or your own customer, if you act for them) are the controller. We are your processor. Atlassian, which hosts and runs the App on its Forge platform, is our sub-processor.

2. Details of the processing.

Subject matter and duration: providing the App and support to you, for as long as the App is installed and for the retention periods in our privacy notice.
Nature and purpose: reading your Jira configuration, storing it in Forge storage to show where items are used and what changes affect, auditing trash and restore actions, reporting stored account IDs to Atlassian’s personal-data service as Atlassian requires, and troubleshooting through logs.
Personal data: Atlassian account IDs (filter and dashboard owners; admins who trash or restore fields; any account ID that appears in saved-filter JQL); and personal data your users have put into the names or JQL of filters, boards, dashboards, gadgets or custom fields, or that Jira quotes in JQL error messages. The App does not store display names or email addresses as separate data. It doesn’t read issue content.
Data subjects: your Jira users and anyone named in your Jira configuration.
Special category data: none intended. Don’t put it into configuration names or JQL.

3. Our commitments. We will:
(a) process the personal data only on your documented instructions, which are these terms and your use of the App’s settings, including for any transfer outside the UK or EEA, unless the law requires otherwise (in which case we will tell you first unless the law forbids it). We will tell you if we think an instruction breaks data protection law;
(b) make sure anyone we authorise to process the data is under a duty of confidentiality;
(c) take the security measures required by Article 32, described in our privacy notice and security page, including relying on Atlassian’s Forge security, not storing data outside Atlassian, using only Atlassian-managed authentication, limiting log content, and restricting access to our developer console;
(d) not engage another sub-processor except Atlassian (which you authorise) without telling you at least 30 days in advance through the Marketplace listing or by email, so that you can object. If you object on reasonable data protection grounds and we can’t meet your concern, you may end your subscription and get a refund of prepaid fees for the rest of the paid period. We will impose data protection obligations on any sub-processor equivalent to this Schedule, and stay responsible for it;
(e) help you, taking into account the nature of the processing, to respond to requests from people exercising their data protection rights. In practice most requests can be met in Jira or by Atlassian; the App’s stored account IDs are refreshed or anonymised through Atlassian’s personal-data reporting service;
(f) help you with security, breach notification, data protection impact assessments and prior consultation (Articles 32 to 36), taking into account the information available to us;
(g) tell you without undue delay, and in any case within 72 hours, after becoming aware of a personal data breach affecting your data;
(h) at the end of the services, leave deletion to the App’s uninstallation, which makes Atlassian delete the App’s storage under its retention rules. We keep no copy, except where the law requires;
(i) make available the information you reasonably need to show compliance with Article 28, and allow for and contribute to audits, including inspections, by you or an auditor you mandate. Audits will be by reasonable notice, no more than once a year unless a regulator requires it or after a breach, and at your cost. Our first response will be written information, as we hold no Your Data on our own systems.

4. Transfers. We are in the United Kingdom, which the European Commission has found adequate for transfers from the EEA (Implementing Decision (EU) 2025/2574). Atlassian’s processing as our sub-processor is covered by the Forge Data Processing Addendum, which includes the EU standard contractual clauses and the UK provisions. The App’s data storage follows your Jira site’s data residency location.

5. Precedence and liability. If this Schedule conflicts with the rest of these terms on data protection, this Schedule applies. §10 applies to this Schedule, except where data protection law does not allow it to.

Custom Field Cleanup & Where-Used for Jira: End User Terms