Logjam for Jira · Last updated 23 September 2026
Logjam for Jira is published by Unleash Consult ApS, Denmark. This policy describes what the app does with data. It is short because the app does very little.
In short: Logjam reads work items from the Jira project you are looking at and renders a summary on screen. It stores nothing, sends nothing anywhere, and has no access to anything outside Atlassian.
Logjam is an Atlassian Forge app. It runs entirely on Atlassian's own infrastructure, inside your Atlassian site. Unleash Consult operates no servers, databases or other infrastructure in connection with this app.
The app requests one permission: read:jira-work — read-only access to Jira work items. From the project page you open it reads: work item key, summary, status, assignee name and account id, due date, last-updated timestamp, and issue links.
It has no write access. It cannot create, edit, transition, comment on or delete anything.
Every request is made as the signed-in user, not as the app, so Jira enforces that user's own permissions. Logjam cannot show you anything you could not already see in Jira yourself.
Nothing. The app has no database, no key-value store and no file storage. Data is read when you open the page, used to render what you see, and discarded when the request ends.
Nothing. The app makes no outbound network calls. There is no analytics, no tracking, no advertising, and no AI or machine-learning service involved. The app's manifest declares no external egress, which means Atlassian's platform would block such a call even if one were attempted.
That describes the app, which is the part that touches your Jira data. The Marketplace listing page is a separate thing: it is a web page hosted by Atlassian, and we may use ordinary page analytics there to see how many people visit it. That measures visits to a public web page. It has no access to your Jira site, your work items or your users, and it is not connected to the app in any way.
If a project is large enough that a query has to be cut short, the app writes a diagnostic line to Atlassian's Forge logs recording which query was truncated and how many items were read. Those logs stay within Atlassian's platform and follow Atlassian's retention.
The app displays the names of people assigned to work items, because naming who to ask is the point of it. That information is read from Jira and shown on screen. It is not stored, copied or transmitted.
No customer data ever reaches Unleash Consult, so we do not process, store or transfer it. Data handling for your Jira site is governed by your agreement with Atlassian.
Material changes will be published on this page with a new date.