Revenue Impact for Jira

Privacy Policy

Last updated: 24 October 2026 · Terms of Service

Revenue Impact for Jira is a Jira Cloud app built on Atlassian Forge by YTI Digital OÜ (Estonia). It links HubSpot companies, deals and tickets to Jira issues and shows the revenue behind each issue. Contact: support@yti.digital.

You (your organisation) decide which HubSpot account the app reads and which records are linked. For the HubSpot data the app reads on your behalf, you are the controller and the app only processes it to show it in your Jira site.

What the app stores

  • The HubSpot key (Service Key or private app token) you paste in the settings, in Atlassian's Forge secret storage for your site.
  • Links: which HubSpot record IDs (numbers) are linked to which Jira issue.
  • Settings: HubSpot portal ID, account domain and currency, the chosen ARR property, and the time and count of the last recompute.
  • Three number fields on linked issues (open deal value, ARR, number of customers), stored by Jira like any other field.

The app stores no personal data: no Atlassian account IDs, no HubSpot contacts, and no names or amounts of companies, deals or tickets.

What the app reads

  • From HubSpot: companies, deals, tickets, their associations, pipelines and deal property definitions, using your key.
  • From Jira: whether the current user may see or edit an issue, the app's own fields, and issue search for issues that carry them.

HubSpot data shown in the issue panel is read live and not kept after it is displayed.

Where data goes

  • Requests go from Atlassian's Forge platform directly to HubSpot's API (api.hubapi.com), the HubSpot account you connected.
  • Nothing is sent to YTI Digital: the app has no servers of its own and we cannot see your key, links or HubSpot data.
  • Data is stored and processed by Atlassian (Forge), as described in Atlassian's own privacy policy.

Who can see the data in Jira

Anyone who can see an issue can see its panel and fields, including company names and deal amounts read with the key. Changing links needs permission to edit the issue; settings are for Jira administrators.

Logs

Forge keeps technical logs for the app (for example how many issues a recompute handled). They contain no key, no names and no amounts.

Retention and deletion

  • Disconnecting HubSpot in the settings deletes the key immediately.
  • Unlinking all records from an issue deletes that issue's link entry and clears its fields.
  • Uninstalling the app removes its data according to Atlassian's Forge data retention rules.

Your rights

Because the app stores no personal data, there is nothing to export or delete on our side. Questions about this policy: support@yti.digital. A data processing agreement is available on request.

Changes

We will update this page before releasing a version that stores or sends data differently.