Privacy Policy

Privacy Policy

Last updated: Feb 19, 2026

1. ACKNOWLEDGEMENT

By using the QuotaWatch software (the “Product”), you acknowledge that you have reviewed the terms of our End User Licence Agreement (EULA) and this Privacy Policy (“Privacy Policy”), have the authority to act on behalf of any person or organization for whom you are using the Product, and agree that we may collect and process your Data in accordance with this Privacy Policy.

If you are using our Product on behalf of a company or organization, you acknowledge that you are binding your company or organization to this Privacy Policy.

QuotaWatch is built entirely on the Atlassian Forge platform and operates fully within Atlassian’s infrastructure. LogicLemur Labs does not have access to, store, or process any customer or end-user data outside Atlassian’s environment.

2. DEFINITIONS

Company means LogicLemur Labs. The terms “we”, “us” and “our” when used in this Privacy Policy refer to the Company.

Customer means a direct customer of the Company who installs or subscribes to QuotaWatch from the Atlassian Marketplace. The terms “you”, “your” and “yours” when used in this Privacy Policy refer to the Customer.

Product refers to our Jira app QuotaWatch for Jira, built on the Atlassian Forge platform.

Data means Personal Information and User Data.

Data Controller has the meaning given in Rec. 22, Art. 3(1) of the GDPR. In the case of QuotaWatch, Atlassian acts as the primary Data Controller for all data stored and processed within its infrastructure.

Personal Information means information about an identified individual or an individual who is reasonably identifiable.

User Data means configuration and operational data generated during the normal use of QuotaWatch, including rate-limit snapshots and alert thresholds.

Atlassian Platform refers to the hosting and operational environment provided by Atlassian for its Forge-based applications.

3. DATA COLLECTION

3.1 Overview

QuotaWatch operates entirely within the Atlassian Forge platform. All data generated or processed by the app remains stored in Atlassian’s infrastructure (specifically within Forge Storage and Jira Issue Properties). LogicLemur Labs does not collect, transmit, or store any customer or end-user data on its own servers.

3.2 Types of Data Handled

While using QuotaWatch, the following types of data may be displayed or stored within Atlassian’s systems:

  • Rate-Limit Snapshots: The app periodically polls Jira APIs to retrieve and store rate-limit headers (Quota, Remaining, Reset Time). This data is stored in Forge Storage to provide the 24-hour usage timeline.

  • Configuration Data: Threshold settings and the Monitoring Issue Key (used for Jira Automation bridging) are stored securely using Atlassian’s Forge Storage APIs.

  • Alert Signals: When a threshold is exceeded, the app updates a Jira Issue Property (quotawatch.alert) on the user-specified monitoring issue. This is metadata used solely to trigger Jira Automation rules.

3.3 No External Data Collection

QuotaWatch does not:

  • collect personal data from users directly;

  • track or log user activity beyond the monitoring actions described above;

  • use cookies, analytics scripts, or external tracking technologies;

  • transmit or sync data to any third-party services (Zero Egress).

3.4 Visibility to LogicLemur Labs

Our visibility into QuotaWatch’s usage is limited to anonymized and aggregate information made available through Atlassian’s developer console, such as installation counts. We cannot see the status of your rate limits, your configuration, or the content of your Jira issues.

4. SECURITY MEASURES

4.1 Atlassian Platform Security

QuotaWatch is built and hosted entirely on the Atlassian Forge platform. All infrastructure, data storage, and processing are managed by Atlassian. Forge ensures that customer data remains within Atlassian’s secure environment, subject to ISO/IEC 27001, SOC 2, and GDPR compliance standards.

4.2 Company Access and Control

LogicLemur Labs does not have access to your Jira issue content or any personally identifiable information (PII) stored within the app properties.

4.3 Secure Coding

We adhere to Atlassian’s Forge security guidelines, utilizing strictly scoped permissions. QuotaWatch requires specific scopes solely to perform its intended function of monitoring rate limits and signaling alerts.

5. INCIDENT RESPONSE

5.1 Atlassian’s Responsibility

Since QuotaWatch operates within the Atlassian Forge environment, any data incidents or breaches within the hosting infrastructure are governed by Atlassian’s incident response procedures.

5.2 Company Responsibility

If we become aware of a security flaw in the QuotaWatch code that could affect data integrity, we will promptly investigate, patch the application, and communicate with Atlassian and affected customers via the Marketplace support channels.

6. YOUR OBLIGATIONS

As the Customer, you agree that you will ensure your use of QuotaWatch (including the designation of a Monitoring Issue) complies with your internal data protection policies.

7. ACCESS TO DATA

7.1 Data Access Rights

Since QuotaWatch operates fully within Atlassian, all data (including usage history and alerts) resides in your Jira instance. LogicLemur Labs cannot modify or delete this data for you.

7.2 Requests from Data Subjects

Any data tracked by the app is purely operational (rate limit metrics). If a user requires deletion of app configuration, the Customer (Jira Admin) can perform this by uninstalling the app or clearing the monitoring settings.

8. SUBPROCESSING

Atlassian acts as the primary Data Processor. LogicLemur Labs does not engage any other subprocessors for the operation of QuotaWatch. No data leaves the Atlassian ecosystem.

9. DISCLOSURE OF DATA

LogicLemur Labs does not disclose, share, sell, or transfer any customer or user data to third parties. All information processed by QuotaWatch resides exclusively within Atlassian’s infrastructure.

10. CROSS-BORDER TRANSFER OF DATA

QuotaWatch relies on Atlassian’s global cloud infrastructure. Your data resides in the region configured for your Jira instance. LogicLemur Labs does not perform any independent cross-border transfers.

11. WARRANTIES

LogicLemur Labs warrants that we process data strictly to provide the rate-limit monitoring utility and that we do not collect data on external servers.

12. SURVIVAL

All data protection obligations outlined here survive the termination of your use of QuotaWatch, insofar as they relate to our ongoing compliance with Atlassian’s developer terms.

13. TERMINATION

When you uninstall QuotaWatch, data stored in Forge Storage is deleted by Atlassian within approximately 30 days.

14. AUDIT OF MEASURES

We agree to cooperate with Atlassian regarding any security audits of our app's source code. Customers may rely on Atlassian’s SOC 2 and ISO certifications regarding the security of the data storage.

15. UNSOLICITED INFORMATION

If you send us feedback or feature requests, we may use that information to improve the Product, but this will never involve the inclusion of your private Jira content.

16. JURISDICTION

This Privacy Policy is governed by the laws of Pune, Maharashtra, India. Any dispute specifically regarding this policy shall be subject to the exclusive jurisdiction of the courts located in Pune.

17. MAKING A COMPLAINT

If you have a privacy complaint regarding QuotaWatch, please contact us first. If the issue relates to the underlying security of the data stored in Jira, we may refer you to Atlassian Support.

18. CONTACT

For questions regarding this Privacy Policy, please contact us at connect@logiclemurlabs.atlassian.net.