Skip to main content

Privacy Policy for Integration Helper for Jira

Effective date: October 31, 2026

This page describes how Integration Helper for Jira (the Atlassian Forge app) handles data. It does not cover this documentation website itself, which does not use cookies or analytics.

What the app accesses​

Integration Helper for Jira reads Jira and Jira Service Management data through Atlassian's own requestJira() bridge, as the currently signed-in user. It only ever reads data that user already has permission to see in Jira — installing or opening the app does not grant any new access. See Security Overview for the exact list of Forge scopes it requests, and Access model for who can open each surface of the app.

Data storage​

The app does not store, persist or retain any Jira or Jira Service Management data. It has no database, no Forge Storage, and no backend of any kind — every screen is rendered directly from data fetched live from Atlassian's APIs for the current page view.

The one file the app can produce — the Project LLM Context Markdown export — is generated and downloaded entirely in the user's browser when they explicitly click "Generate context pack." The app itself does not keep a copy, upload it, or send it anywhere; once downloaded, the file is the user's own, under their own responsibility like any other file they export from Jira.

Data sharing​

No Jira or Jira Service Management data is sent to any service other than Atlassian's own APIs. The app has no analytics, tracking, or third-party integrations of any kind.

Cookies​

The app runs inside Jira's own interface and does not set any cookies of its own.

Changes to this policy​

This page may be updated as the app's capabilities change. Material changes will be reflected here with an updated effective date.

Contact​

Questions about this policy can be directed to the developer via kosarev.pro.