Comment Fields for Jira - Privacy Policy
Who we are
BranchCreation S.L.U. (“we”) provides the Atlassian Forge app Comment Fields for Jira Cloud. This policy describes personal data the app processes when it is installed on your Jira site.
What the app does
Comment Fields reads issue comments and writes three read-only custom fields (First comment, Last comment, All comments count). Jira admins can run a site-wide sync. Users can export the current JQL result to an Excel file (issue fields plus a comment table).
Data we process
On the installing customer’s Jira Cloud site only:
- Comment author display name, comment created time, and comment body (plain text extracted from Atlassian Document Format).
- Issue fields used for Excel export: issue type, key, id, summary, reporter display name, priority, status, created, updated.
- Values we write into our custom fields (first/last comment snapshot and comment count).
- Sync progress in Forge Key-Value Storage (counts, timestamps, pagination token). Not used for advertising.
We do not collect account passwords. We do not send this data to BranchCreation servers. Processing runs on the Atlassian Forge platform (Runs on Atlassian).
Legal basis and purpose
We process this data to provide the app to the organisation that installed it: keep the three fields up to date, show them in Jira, and generate the Excel export. The customer (site admin) is the controller of Jira content; we act as a processor on their behalf via Atlassian Cloud.
Sharing
We do not sell personal data. We do not share it with third parties except Atlassian, which hosts Jira Cloud and Forge. Marketplace billing and trials are handled by Atlassian.
Retention
Custom field values and comments remain in the customer’s Jira according to their Jira retention. Sync status stays in Forge storage for that installation until overwritten, the app is uninstalled, or Atlassian deletes installation data (typically after the uninstall retention window). Uninstalling the app removes our fields from Jira after Atlassian’s standard period.
Security
Access uses Forge authentication and the OAuth scopes declared in the app (read:jira-work, write:jira-work, write:app-data:jira, storage:app). Writes to our fields use the app identity. We do not store data outside Atlassian Cloud.
International transfers
Data stays in Atlassian Cloud regions chosen for that site. See Atlassian’s cloud privacy terms.
Your rights
End users should contact their Jira admin. Admins can uninstall the app, remove the fields from screens, or use Jira/Atlassian data-subject tools. You may also contact us (below).
Contact
BranchCreation S.L.U. https://branchcreation.com - Email: support@branchcreation.com