Helpmonks Logo
Underdog. Fast. Unfiltered.

Helpmonks for Jira: data and privacy

Helpmonks for Jira connects a Helpmonks shared inbox to a Jira Cloud project chosen by your administrator. This page explains the connector's data handling. It supplements the Helpmonks privacy policy, terms of service and data-processing agreement.

What is shared with Jira

When someone creates a linked issue, Helpmonks sends the conversation's subject, messages, sender details and customer context to the selected Jira project. Shared internal notes and attachments are included when enabled. Author-only notes are excluded. Customer email addresses appear in the issue description and labels. Subsequent messages and selected shared notes can be copied while synchronization is enabled.

People with access to the Jira issue can see the information copied there. Copies are retained under your Jira account's access and retention controls. Disconnecting Helpmonks does not delete these Jira issues, comments or attachments.

What Helpmonks stores from Jira

Helpmonks stores the selected site and project, linked issue IDs and keys, issue summaries, status, priority, and assignee account IDs and display names. When comment imports are enabled, it also stores Jira comment bodies, author account IDs and display names, and structured mentions. Those comments appear as read-only shared internal notes for people who can access the Helpmonks mailbox. They are never sent to customers as email. Restricted Jira comments and comments created by this integration are excluded.

The connector does not fetch Jira profile email addresses or avatars. Jira attachment references link back to Jira; the connector does not download those files into Helpmonks. Comment bodies and issue summaries can contain personal information entered by their authors.

Authorization and processing

Your administrator connects through Atlassian OAuth. Helpmonks supplies the OAuth application; customers do not need API tokens or their own developer app. The requested permissions allow reading Jira work, creating and updating Jira work, and keeping the authorized connection active for background synchronization. The connector does not request Jira administration or profile-email permissions.

Helpmonks encrypts the OAuth client secret and access and refresh tokens in its database using authenticated encryption. Communication with Atlassian uses HTTPS. Helpmonks processes Jira data outside Atlassian as part of the Helpmonks service. US and EU Helpmonks installations use separate OAuth registrations. This is not an Atlassian-hosted app or a claim of Atlassian data-residency certification or EU-only processing.

The Jira connector does not send Jira content to an AI provider or add analytics collection. This statement applies to the connector; other Helpmonks features have their own behavior and settings.

Privacy reporting and deletion

Helpmonks reports retained Jira account IDs and their oldest acquisition times to Atlassian's personal-data reporting API. Its background worker checks for reporting work hourly and follows Atlassian's reporting cycle and retry instructions. If Atlassian reports that an account has been closed or its personal data has changed, Helpmonks invalidates affected cached identities and erases affected imported comment copies. Assignee details may be refreshed; erased comment copies are not restored.

Disconnect stops synchronization, removes the stored OAuth tokens, and erases imported Jira comment content and cached assignee identities for that Helpmonks account. Detected permanent authorization revocation starts the same cleanup. Background processing retries incomplete cleanup. Pause sync and disabling the extension preserve retained copies, so required privacy reporting continues.

Issue links, delivery IDs and hashed erasure markers remain to prevent duplicate delivery and erased comments from being imported again. Reconnecting does not restore erased comments; new comments may be imported after synchronization resumes. Original Helpmonks emails and content already copied to Jira remain subject to their respective account controls.

Copies are otherwise append-only: ordinary edits and deletions of an original do not automatically change its copy. Automated account reporting cannot identify every person mentioned in free text. For a request involving customer content, account deletion, retention or backup copies, contact Helpmonks support and identify the account and affected conversation or issue. Do not include passwords or OAuth tokens.

For connection instructions, see Connect Helpmonks to Jira.

Bring everyone into the customer conversation.

Unlimited users. Shared inbox pricing. One place for customer context.

Book demo Start 30-day free trial