Privacy, permissions and data
Sumline only reads your Jira work items and adds up their numbers. It cannot edit a work item or change a field, it has no servers of its own, and nothing it reads or stores leaves your Atlassian site. The privacy policy is the formal version of this page.
The two permissions
read:jira-work: to read work items, their fields and the site’s field definitions.storage:app: to keep the app’s own settings, a cache of its figures and the few small records listed under “What it stores” in Forge storage.
Those are the only two. Sumline asks for no write access, calls no service outside Atlassian and declares no outside hosts.
Whose permissions it uses
Sumline reads Jira as the person viewing, never as the app. Jira applies that person’s own permissions, so each person sees only the work items they could open themselves, and a total only adds up the work items that person can see. The cache is kept per person, so one person’s totals are never shown to another.
So two people can see different totals for the same epic. If a team lead cannot open some of the stories under an epic and a PMO can, each sees the sum of the work items they are allowed to see, and both numbers are right for the person looking. When totals differ, compare what each person can open in Jira; Sumline has no total of its own that bypasses permissions.
What it reads
To roll up, Sumline reads these fields of the work items in view: key, summary, work type, status and its category, priority, parent, space, the created date, due date and fix versions, story points, the time tracking values (original estimate, time spent, remaining estimate), sprint, the Team field, any number fields an admin chose to roll up, and the assignee’s account id and display name (the name only to label the Assignee filter on the table being viewed). It also reads the site’s field list, work types and priorities (to sort a table by priority in the site’s own order), the spaces the viewer can see (for the space picker), and the viewer’s Atlassian account id, only to keep each person’s cache apart. When an admin saves the settings, it asks Jira whether that person is a Jira admin.
What it stores
Everything Sumline stores is in Forge Key-Value Storage, hosted by Atlassian in your site’s data residency region. It stores five things:
- A cache of the figures. The computed numbers for a work item, a space or a set of spaces, with the work item keys, summaries and assignees’ account ids needed to show them, kept per person. It holds no names: the Assignee column draws each name from the account id, and the Assignee filter looks the names up each time the table is shown. An entry is served for at most five minutes (less if an admin changes the settings) and Forge storage deletes it about 6 minutes after it is written (Forge clears expired entries in the background, within 48 hours). A large table is split over several entries, each deleted the same way.
- Site metadata. The site’s field list, work types, priorities and each space’s key, name and type (company- or team-managed), shared by everyone on the site, served for at most an hour and deleted by Forge storage about an hour after it is written. It names no person.
- The settings a Jira admin chose. See Settings.
- The review request. Once Sumline is on the Marketplace, a small “Review Sumline ⭐” link to its reviews shows on Sumline’s settings page, and in a banner at the top of its space page and Apps page until you dismiss it, from your tenth open. For each person, Sumline keeps their account id, how many times they opened it, counted up to ten, and when they dismissed the banner. Before 23 October 2026 it asked in a line under the panel and on the settings page that you could dismiss; the date Sumline was first opened on the site and each dismissal (account id and when) stay, and a person who dismissed the line is not shown the banner. All are kept until Sumline is uninstalled.
- The “where Sumline shows up” card. A card on Sumline’s Apps page and settings page lists where Sumline appears in Jira, each place with a link, until you dismiss it. For each person who dismissed it, Sumline keeps their account id and when, until Sumline is uninstalled.
The spaces, saved filter or JQL chosen for a dashboard gadget are saved by Jira as that gadget’s configuration, like any other gadget’s, not by Sumline.
It stores no passwords, no API tokens and nothing about people beyond the account ids above: no names, no email addresses.
Where data goes
Nowhere. Sumline is built on Atlassian Forge and makes no network request to any service outside Atlassian. It uses no analytics service or tracking and shares nothing with third parties. It is eligible for Atlassian’s “Runs on Atlassian” programme, Atlassian’s designation for apps that send no data outside Atlassian.
Atlassian counts how often each part of Sumline is used on your site and shows us the counts. A count carries no work item data and names no person.
Uninstalling
When Sumline is uninstalled from a site, Atlassian keeps its storage for 28 days, then deletes all of it. A reinstall starts empty: the old storage comes back only if you ask us within 21 days of uninstalling, and we ask Atlassian to restore it. We hold no copy of your data, so there is nothing for us to delete or return; your Atlassian admins control it entirely.
Questions
For a security questionnaire or anything this page does not answer, contact our support site or by email at support@lineset.dev.