Skip to content
Menu

Sumline privacy policy

Last updated 10 November 2026

Sumline (“the app”) is a Jira Cloud app built on Atlassian Forge and published by Sugar Systems, SIA (registration number 40203386400), Stirnu street 5-29, Riga, LV-1035, Latvia (“we”, “us”). This policy explains what the app does with data when a Jira site administrator installs it. What the Lineset websites and the app’s waitlist keep is in the Lineset privacy policy, which covers every app.

What the app does

Sumline reads work items in your Jira site and adds up their estimates and time fields across the work item hierarchy, then shows the result inside Jira. It reads on behalf of the person looking at the page, using their Jira permissions, so it never shows anyone a work item they could not open themselves.

Data the app processes

  • Work item data read from your Jira site: work item keys, summaries, work item types, status categories and the day each last changed, created and due dates, releases, parent links, story points, time-tracking values, sprint values, the values of any number fields your administrators chose to roll up, the Team field's id and name, and the assignee's account id and display name. This data is processed to roll up the figures. Display names are used only to label the assignee filter on the page being viewed and are never stored.
  • Your Atlassian account id, used only to keep each person's cached figures and last scope separate from everyone else's and, if you dismiss the request for a review or the card that says where Sumline shows up, to keep it dismissed for you.

The app processes no data from outside your Atlassian site.

Data the app stores

Everything the app stores lives in Forge Key-Value Storage, which is hosted by Atlassian inside the Atlassian cloud, in the data residency region of your site. The app stores six things:

  1. A cache of the figures: the computed numbers for a work item, a space, a set of spaces, a saved filter or a JQL query, together with the work item keys, summaries and assignees' account ids needed to show them (never their names), the saved filter's name or the query's text, keyed by the viewer's account id. Each entry is served for at most five minutes and deleted by Forge storage about 6 minutes after it is written.
  2. Site metadata: your site's list of fields (ids, names and types), its work types, its priorities, and the id, key, name and type (company- or team-managed) of the spaces the app has read, one entry each for the whole site, so the app does not ask Jira for them on every view. It names no person. Each entry is deleted by Forge storage about an hour after it is written.
  3. Settings chosen by your Jira administrators (which fields to roll up, including any number fields of your own, which hierarchy level makes a row, the done-only switch, whether the remaining estimate of done work items counts, the mixed-estimate rule, which delivery warnings show, whether % by work item count counts only work items with nothing under them, any rules to roll up through links (a work type's name, a link type's id and its direction), and whether Excel downloads end with a line naming Sumline).
  4. The review request: once the app is listed on the Atlassian Marketplace, a small “Review Sumline ⭐” link to its reviews shows on its settings page, and in a banner at the top of its space page and Apps page until each person dismisses it, from each person’s tenth open. For each person, the app stores their account id, how many times they opened it, counted up to ten, and the date they dismissed the banner. Before 23 October 2026 it asked in a line each person could dismiss, and stored the date the app was first opened on your site and, for each person who dismissed the line, their account id and the date; a person who dismissed it is not shown the banner.
  5. The “where Sumline shows up” card: a card on Sumline's Apps page and settings page lists where Sumline appears in Jira until each person dismisses it. For each person who dismissed it, the app stores their account id and the date, so the card stays dismissed.
  6. Last scopes: the scope a person last rolled up on the Apps page (space keys, a filter id or their own JQL), so the page opens on it next time: one entry per person, replaced each time they press Roll up, kept 90 days from the last change. A scope opened from a link is not kept.

The app stores no passwords, no API tokens and no data about people beyond what is listed above.

Where data goes

Nowhere. The app makes no network requests to any service outside Atlassian. It has no servers of its own, uses no analytics service or tracking, and shares nothing with third parties. It is eligible for Atlassian's "Runs on Atlassian" program, which is Atlassian's designation for apps with no data egress.

Atlassian counts how often each part of the app is used on your site, such as a page opened, a button pressed or a file downloaded, and shows us those counts in its developer console. A count is a number under a name: it carries no work item data and names no person. Your Atlassian administrators can turn the counts off for the app in Atlassian Administration (Apps, Connected apps, the app's Details).

Retention and deletion

  • Cache entries are served for at most five minutes after they are computed (less if an administrator changes the settings), and Forge storage deletes each one about 6 minutes after it is written. Forge removes expired entries in the background, so an entry can stay in storage for up to 48 hours after it expires; it is never served after five minutes.
  • Site metadata is deleted by Forge storage about an hour after it is written (again, at most 48 hours later).
  • Settings are kept until an administrator changes them.
  • Last scopes are deleted by Forge storage 90 days after they last changed (at most 48 hours later).
  • Each person’s count of opens and dismissal of the banner, the first-opened date and dismissals of the earlier review line, and each dismissal of the card are kept until the app is uninstalled.
  • When the app is uninstalled from your 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 on request; your Atlassian administrators control it entirely.

Permissions the app asks for

  • read:jira-work — to read work items, their fields and the site's field definitions.
  • storage:app — to keep the cache, the site metadata, the settings, the review request's records and the card's in Forge storage.

Your rights and contact

The apps keep no copy of your Jira data outside your Atlassian site, so requests about it are handled by your Atlassian site administrators. For the waitlist, or questions about this policy, an app or the websites, contact our support site or by email at support@lineset.dev. You can also complain to Latvia’s Data State Inspectorate (Datu valsts inspekcija).

Changes

We will update this page when an app’s data handling changes and note the date above. Material changes are also announced in that app’s Marketplace release notes.