End User License Agreement for Impediment Ledger for Jira
Important terms
Please note in particular section 12 (limited warranty), section 13 (limitation of liability), section 16 (Hungarian law and courts) and section 17 (changes). By accepting this Agreement on the Atlassian Marketplace or by installing the App, the Customer expressly accepts these terms.
1. Parties and acceptance
This End User License Agreement (the “Agreement”) is between PR Flow, a trading name of Árpád Kozma, sole proprietor (egyéni vállalkozó), registered address Szabadság tér 6., 2337 Délegyháza, Hungary, sole proprietor registration number 62570660, tax number (EU VAT) HU92217287, email [email protected] (the “Publisher”), and the entity that installs, obtains a licence for or uses the App (the “Customer”).
The App is offered only to businesses and other organisations, and to individuals acting for purposes of their trade, business or profession. It is not offered to consumers.
By installing, enabling or using the App, the Customer accepts this Agreement. A person who accepts it on behalf of an organisation confirms that they are authorised to bind that organisation. If the Customer does not accept this Agreement, it must not install or use the App.
2. Definitions
- App: the Atlassian Forge app “Impediment Ledger for Jira”, including its updates, and the Documentation.
- Documentation: the user and admin guide and the other material published by the Publisher at prflow.app/impediment-ledger/docs.
- Atlassian: Atlassian Pty Ltd and its affiliates, which operate the Atlassian Marketplace, the Forge platform and the Atlassian cloud products.
- Marketplace Terms: the terms under which Atlassian makes apps available on the Atlassian Marketplace and sells licences for them, as in force from time to time.
- Licence: the subscription for the App that the Customer obtains through the Atlassian Marketplace for a given Atlassian site, user tier and term, including an evaluation licence.
- Customer Data: the data the App stores for the Customer, as described in the privacy notice.
- Users: the individuals the Customer allows to use the Jira site on which the App is installed.
3. Atlassian Marketplace
The App is sold through the Atlassian Marketplace as a “Paid via Atlassian” app. Atlassian, not the Publisher, handles ordering, pricing presented at checkout, billing, invoicing, taxes, payment, renewals, cancellations and refunds, under the Marketplace Terms and Atlassian's policies. The Publisher does not invoice the Customer and does not receive the Customer's payment details.
Atlassian is not a party to this Agreement and is not responsible for the App. The Customer's use of Jira and other Atlassian products remains governed by the Customer's agreement with Atlassian. If this Agreement conflicts with the Marketplace Terms on a matter that the Marketplace Terms reserve to Atlassian (in particular payment and refunds), the Marketplace Terms prevail on that matter.
4. Licence grant
Subject to this Agreement and to a valid Licence, the Publisher grants the Customer a non-exclusive, non-transferable, non-sublicensable licence, revocable only as set out in section 14, for the term of the Licence, to use the App on the Atlassian site for which the Licence was obtained, by up to the number of Users covered by the Licence, for the Customer's internal business purposes.
An evaluation licence is granted for the evaluation period offered on the Atlassian Marketplace and only for evaluating the App.
5. Restrictions
The Customer shall not, and shall not allow any third party to:
- copy, modify, translate or create derivative works of the App, except as permitted by mandatory law;
- decompile, disassemble or reverse engineer the App, except to the extent mandatory law permits this despite this restriction;
- sell, rent, lease, sublicense, distribute or otherwise make the App available to third parties;
- circumvent the Licence check, the App's permission checks or any usage limit;
- use the App in breach of applicable law or of the Customer's agreement with Atlassian;
- use the App to build a competing product, or remove proprietary notices from it.
6. Customer Data
As between the parties, the Customer owns the Customer Data. The App stores Customer Data in the Forge hosted storage of the Customer's Atlassian site, on Atlassian's infrastructure, and sends no data outside Atlassian. The Publisher does not access Customer Data and processes it only as described in section 7 (Data Processing Terms).
The Customer is the controller of any personal data in the Customer Data and is responsible for the content its Users enter, including notes and resolutions, and for having a lawful basis for that processing. The privacy notice describes what the App stores, retention and deletion.
The Customer may export its Customer Data at any time, including after the Licence ends and for as long as the App remains installed (at least thirty (30) days), using the App's export, in a structured, commonly used, machine-readable format (JSON Lines). The Publisher charges nothing for export or switching. Because the Publisher does not access Customer Data, the Customer should export it before the App is uninstalled. After uninstallation, Atlassian keeps the App's data for the period set by its Forge data lifecycle (currently 28 days) and then deletes it.
7. Data Processing Terms (Article 28 GDPR)
- Roles and scope. For personal data in the Customer Data, the Customer is the controller and the Publisher is the processor. The subject matter, nature and purpose of the processing, the types of personal data (Atlassian account IDs, and personal data Users type into notes and resolutions) and the categories of data subjects (the Customer's Users) are as described in the privacy notice. Processing lasts for the term of this Agreement and until the Customer Data is deleted.
- Instructions. The Publisher processes that data only on the Customer's documented instructions, which are this Agreement and the Customer's configuration and use of the App, unless Union or Member State law requires otherwise. The Publisher will inform the Customer if, in its opinion, an instruction infringes data protection law.
- Confidentiality. The Publisher works alone. Anyone the Publisher authorises to process that data will be bound by confidentiality.
- Security. The Publisher implements the measures described in the Documentation and the privacy notice: no network calls outside Atlassian, permission checks for every user-facing result, logs without personal data, and retention. Atlassian provides storage encryption and tenant isolation on Forge.
- Sub-processors. The Customer authorises Atlassian (under the Forge Terms and the Forge Data Processing Addendum) and Atlassian's sub-processors as sub-processors. The Publisher will announce any other sub-processor in the privacy notice at least thirty (30) days before it is used; the Customer may object on reasonable data protection grounds and, if no solution is found, terminate this Agreement. The Publisher remains responsible for its sub-processors as Article 28(4) GDPR provides.
- Transfers. Where Atlassian processes the data outside the European Economic Area, the transfer is covered by the Standard Contractual Clauses and the EU–U.S. Data Privacy Framework as set out in the Forge Data Processing Addendum.
- Assistance. The App's export, correction and retention features, and its handling of closed Atlassian accounts, are the Publisher's assistance with data subject requests. The Publisher will otherwise reasonably assist the Customer with Articles 32 to 36 GDPR, taking into account that it does not access the data.
- Personal data breaches. The Publisher will notify the Customer without undue delay after becoming aware of a personal data breach affecting the Customer Data, with the information available to it.
- Deletion. At the end of the processing the Customer can export the data. After uninstallation the data is deleted under Atlassian's Forge data lifecycle, as described in the privacy notice. The Publisher keeps no copy.
- Audits. The Publisher will make available the information necessary to demonstrate compliance with this section, including answers to reasonable security questionnaires and Atlassian's published certifications for the Forge platform. It will allow audits, including inspections, by the Customer or an auditor it mandates, on reasonable prior notice, at most once a year unless there is a breach or a regulator's request, at the Customer's cost and subject to confidentiality.
8. Platform dependencies, quotas and rate limits
The App runs on Atlassian Forge and relies on Jira Cloud APIs, events and storage provided by Atlassian. The availability, performance and behaviour of the App depend on these services, which the Publisher does not control.
Atlassian applies quotas, rate limits and invocation limits to Forge apps, including limits on Jira API usage shared across installations. When these limits are reached, or to stay within them, the App may delay, slow down or defer background work, for example the processing of flag changes, the loading of history or the daily check, and some operations may fail and need to be retried. Results may then be incomplete or appear later. The Publisher does not warrant any processing time.
Some features depend on Atlassian products or settings that the Customer controls or Atlassian provides, such as Rovo, Jira Automation or app access rules. Answers in Rovo are generated by Atlassian's AI service from the data the App provides and may be incomplete or inaccurate; Rovo is governed by the Customer's agreement with Atlassian. Atlassian may change or discontinue platform features, which may require the Publisher to change, limit or remove features of the App.
9. Inactive licence
When the Licence is not active, the App restricts its functions as described in the Documentation: each issue's blocker panel stays readable and the admin data export and the processing of personal data requests keep working, while edits, enabling new projects and the App's pages, reports and CSV export are paused, and tracking pauses. When the Licence becomes active again, the App fills the gap from Jira's history up to 35 days back; older short blockers may not be recovered.
10. Updates and support
The Publisher may update the App from time to time. Updates are delivered through Atlassian Forge. Updates that require new permissions are subject to approval by a Jira admin, as the Forge platform provides.
Support is provided as described on the support page, with a response-time target of two business days; requests that Atlassian marks as critical are answered within 24 hours. The target is not a service-level commitment.
11. Intellectual property and feedback
The App, including all intellectual property rights in it, is and remains the property of the Publisher and its licensors. No rights are granted other than those expressly stated in this Agreement. If the Customer gives feedback or suggestions about the App, the Publisher may use them without restriction or obligation.
12. Limited warranty
The Publisher warrants that, during the Licence term, the App will perform materially as described in the Documentation. If it does not, the Customer's remedy is that the Publisher will use reasonable efforts to correct the non-conformity and, if it cannot do so within a reasonable time, either party may terminate the Licence, and the Publisher will not object to a refund by Atlassian of the fees for the remaining term.
Except for this warranty, and to the maximum extent permitted by applicable law, the App is provided “as is” and “as available”, without warranties of any kind, whether express, implied or statutory, including warranties of merchantability, fitness for a particular purpose, accuracy and non-infringement. The Publisher does not warrant that the App will be uninterrupted or error-free, or that the durations, reports and other figures it produces are complete or accurate in every case. In particular, the App derives blocked periods from Jira's history and events, which may be incomplete.
13. Limitation of liability
To the maximum extent permitted by applicable law, the Publisher shall not be liable for any indirect, incidental, special, consequential or punitive damages, or for any loss of profits, revenue, data or goodwill, arising out of or in connection with this Agreement or the App.
To the maximum extent permitted by applicable law, the Publisher's total aggregate liability arising out of or in connection with this Agreement or the App shall not exceed the greater of (a) the fees paid for the Customer's Licence in the twelve (12) months before the event giving rise to the liability and (b) one hundred euros (EUR 100).
Nothing in this Agreement excludes or limits liability for intentional or grossly negligent breach, for damage to life, physical integrity or health, or any other liability that cannot be excluded or limited under applicable law (including section 6:152 of the Hungarian Civil Code). Liability under the Data Processing Terms is subject to this section, except where Article 82 GDPR provides otherwise.
Neither party is liable for a failure caused by circumstances beyond its reasonable control, including outages or changes of the Atlassian platform.
14. Term and termination
This Agreement applies from the moment the Customer first installs or uses the App and continues for as long as the Customer has a Licence or uses the App. It ends automatically when the Licence ends without renewal or is cancelled through Atlassian, subject to any grace period under Atlassian's licensing policies.
Either party may terminate this Agreement by written notice if the other party materially breaches it and does not remedy the breach within thirty (30) days of notice. The Publisher may suspend or terminate the licence immediately if the Customer breaches section 5.
The Publisher may discontinue the App by giving at least ninety (90) days' notice on the App's Marketplace listing or by email to the Customer's contact known to the Publisher, subject to the Marketplace Terms. If the Publisher discontinues the App before the end of a prepaid term, it will not object to a pro-rata refund by Atlassian, and the export will remain available until the end of that term.
On termination the Customer shall stop using the App and uninstall it. Sections 6, 7 (until the Customer Data is deleted), 11, 12, 13, 16, 18 and 19, and any rights accrued before termination, survive termination.
15. Compliance
The Customer shall comply with the export control and sanctions laws that apply to its use of the App, and confirms that it is not subject to sanctions that would prohibit the Publisher from licensing the App to it, and that it is not located in, or owned or controlled from, a country or territory subject to comprehensive EU, UN or US sanctions.
16. Governing law and jurisdiction
This Agreement is governed by the laws of Hungary, excluding its conflict-of-law rules and the United Nations Convention on Contracts for the International Sale of Goods. The Hungarian court having jurisdiction for the Publisher's place of residence has exclusive jurisdiction. Mandatory provisions of law that cannot be derogated from by agreement remain unaffected.
17. Changes to this Agreement
The Publisher may amend this Agreement. The amended version applies from the date shown at the top, and to existing Customers from their next Licence renewal or, for changes required by law or by Atlassian, from the date of publication. Continued use of the App after an amendment takes effect constitutes acceptance.
18. General
- This Agreement, including its Data Processing Terms, is the entire agreement between the parties about the App and supersedes any prior understanding about it.
- If a provision is found invalid or unenforceable, the remaining provisions remain in force, and the provision shall be replaced by a valid one that comes closest to its purpose.
- The Customer may not assign this Agreement without the Publisher's prior written consent.
- A failure or delay in exercising a right is not a waiver of it.
- Notices to the Customer may be given by email to the technical or billing contact that Atlassian makes available to the Publisher, or on the App's Marketplace listing; the Customer agrees to receive notices about security, material changes to this Agreement and discontinuation of the App in this way. Notices to the Publisher must be sent to [email protected].
- This Agreement is written in English, and the English version is binding. Translations are provided for convenience only; in case of any discrepancy, the English version prevails.
19. Contact
Questions about this Agreement: [email protected]. Support: [email protected]. Security reports: [email protected].