Privacy policy
Group & Project Watchers for Jira · Last updated October 22, 2026.
NITROSOFT TECHNOLOGY INC, 2100 S Ocean Dr, Fort Lauderdale, FL 33316, USA, develops this Jira Cloud app. See the support page for app privacy and support information.
What the app does
The app processes project administrator rules and personal project-watching subscriptions to add individual accounts as watchers of matching new Jira issues. An administrator can optionally enable a Jira notification explaining that a watcher rule added the recipient. Notification is off by default. This policy covers these features.
Data we process
| Record or processing | Data and purpose |
|---|---|
| Saved watcher rules | Rule, project, component, issue-type, group and Atlassian account IDs; enabled and notification options. These determine which new issues receive which watchers. |
| Personal subscriptions | Project and account IDs, enabled choice and optional component ID. These apply the user's project-watching preference. |
| Rule capacity | Project ID, retained-record count and version counter. These enforce the project rule limit during concurrent saves. |
| Notification tracking | Issue, project, run and pending-rule IDs; added and eligible account IDs; a SHA-256 hash of the matched rules' ID/boolean configuration; processing status, attempt count and retry-not-before timestamp. These combine recipients, detect changed rules, throttle delivery and prevent duplicate notices. These records can be linked to the accounts and issues involved. |
| Queued work | Issue IDs and, where needed, issue key, project/component/type references, rule/run IDs, the initiating administrator's account ID for backfill commands, pagination positions and retry timing. Forge processes these to continue bounded work without copying issue content. |
| Privacy reporting and account controls | Atlassian account IDs and stored-data age information reported to Atlassian for account erasure or refresh instructions; reporting times and cycles; scan checkpoints that can contain partial or full subscription account IDs to resume discovery and are reset during account erasure; hashed account-ID suppression markers that prevent removed data from being recreated. |
| Backfill records | Run, project and rule IDs; initiating administrator account ID; recipient and pending-account IDs; progress, status and retry information. Current and historical runs can retain these identifiers to continue and report administrator-requested backfill. |
| Live Jira lookups | Issue project/component/type metadata, group membership, watcher account IDs, current user status and permissions. Display names and group/component/type labels are used transiently for selection and display. |
Atlassian account IDs and preferences are user-linked data, not anonymous records. The app does not save issue summaries, descriptions, comments, email addresses, display names or raw Jira response bodies in its application records or queue payloads. Jira API responses can contain additional profile fields; only needed identifiers or display labels are selected for processing. Customer Jira passwords and API tokens are not requested by the app; Forge supplies installation and user authorization.
Notifications and recipients
When a rule explicitly enables notification, the app asks Jira to notify only eligible accounts newly added by that rule-processing run. It sends fixed text: "A project watcher rule added you as a watcher of this issue." The subject is "You were added as an issue watcher". It does not insert issue content, names or email addresses into that body. Jira resolves account IDs and controls delivery and permissions. Jira manages delivery through its notification settings. Personal project subscriptions do not send this optional rule notification.
App hosting, access and location
Watcher-rule processing, saved records and queues use Atlassian Forge and Jira APIs. The app has no advertising or external analytics integration. We do not sell app data or use it for advertising. Atlassian operates the app platform and processes the relevant Jira requests and notifications.
Forge storage is scoped to the installation. Atlassian documents encryption on disk and storage residency with the host Atlassian app. Actual customer pinning and migrations depend on Atlassian settings. Processing, diagnostics and logs follow Atlassian's platform locations and settings. See Forge data residency. Nitrosoft®'s security controls and reporting contact are described in the security statement.
Retention and controls
Saved rules, subscription records and quota counters have no application-defined automatic expiry. Archiving a rule disables it and retains its IDs and options. Stopping personal project watching retains a disabled account/project record. Neither action removes accounts from issues they already watch.
Notification records do not expire automatically. After a completion is saved, recipient account-ID and pending-rule lists are cleared. Issue, project and run IDs, a configuration hash, status, attempt count and retry timestamps remain to prevent repeat notices. Unfinished work can retain account IDs until processing completes or a privacy instruction removes them. Separate short-term throttle records contain only a boolean and time slot and use a one-day Forge expiry.
Scheduled privacy processing runs hourly, independently of the app license. It discovers stored account IDs in rules, subscriptions, notification tracking and current or historical backfill records, including disabled preferences. Account reports follow Atlassian's reporting cycle, initially seven days per account and then the cycle returned by Atlassian. Reporting sends account identifiers and stored-data age information to Atlassian to obtain account-closure or data-refresh instructions.
When Atlassian directs erasure or refresh, the app removes the account's direct rule selections and saved subscriptions, clears affected notification recipient lists while retaining a suppressed delivery marker, and removes backfill runs owned by that account. Other affected backfill runs are stopped and scrubbed of the account's references. Rules retain unrelated recipients and are disabled if no recipients remain. These actions do not remove existing Jira watchers or erase records held by Jira itself. Work already queued on Atlassian's platform and platform diagnostics follow their own processing and retention controls; the stored-record cleanup does not recall them.
Hashed account-ID suppression markers are retained without automatic expiry to prevent queued work or later group expansion from recreating the removed data. These are pseudonymous identifiers, not anonymous records. A privacy refresh does not automatically restore subscriptions or resume processing for the account; use the support form to assess restoration. Platform or API interruptions can delay processing; checks and cleanup are retried. A Jira request already in progress cannot be recalled by this cleanup.
Uninstallation does not cause immediate physical deletion. Atlassian documents 28-day hosted-storage retention after uninstall. Prior data is not automatically restored on reinstall; recovery requires customer consent and a request within 21 days. See Forge storage and its data lifecycle. Backups, queued work and logs follow their respective platform retention controls.
Privacy requests and operational records
For access, correction or erasure of user-linked app data, use the support form and choose General. Identify the app and relevant Atlassian site/account only as needed for verification. Handling may require coordination with the site administrator or Atlassian. Erasure requests are reviewed through support. The scheduled Atlassian account-reporting and cleanup workflow is separate. It does not automatically erase support tickets, website records or records held by Atlassian. Turning off a preference retains its saved record; it does not erase it.
Application-authored notification logs use fixed status labels. Forge/Jira diagnostics may include platform invocation or request metadata; they are governed by platform access and retention controls. The app does not export its logs to an external service. Support requests are stored separately from the app's Forge records and contain your contact details and the information you submit. Do not send passwords, tokens or customer issue content. Support records do not expire automatically. Use the support form to request access, correction or erasure.
This public website
The website uses Microsoft Azure App Service hosting, separately from Atlassian Forge. Microsoft Azure and DNS services process connection/request metadata, such as IP address, requested URL and browser headers, to deliver and protect the pages. This website does not receive records from your Forge installation. Azure and DNS providers manage these operational records under their hosting settings and retention controls.
The website contains no analytics scripts or external fonts. Its support form asks for your name, email, Jira site URL, category and description. Submitting stores these details in the Nitrosoft® Jira support queue, separately from your installation's Forge records. Nitrosoft® uses them to identify, investigate and triage the request; support records have no automatic retention timer. Do not submit passwords, tokens, customer issue content or unnecessary personal data. The server does not visit the supplied site address or access your Jira installation. It has no email-delivery integration; Jira administrators control Atlassian project notifications separately.
The support page uses a Secure, HttpOnly, SameSite=Strict antiforgery cookie to protect submissions, not to track visits. Form identifiers expire after 30 minutes; hashed network-address limits use windows of up to 10 minutes. These controls live only in worker memory to prevent duplicate submissions and limit abuse. Expired entries are removed on later requests, and all entries clear when the worker restarts. Provider connection/request records remain subject to Azure configuration and retention.
Updates
Changes to app features or data handling may require an updated policy. The date above identifies this version. Use the support form if you have a question about a change affecting your use of the app.