Skip to content
Changeline
Menu

Changeline privacy policy

Last updated 4 November 2026

Changeline (“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

Changeline shows the five DORA delivery measures in Jira: how often a team deploys, how long a change takes from work started to released, how long a failed release takes to fix, how many releases a failure points at, and how many releases ship a fix for one. It counts them from the versions, work items and history Jira already holds, for a team, never for one person. It reads Jira as the person using it. It writes nothing to Jira: not a work item, not a field, not a setting.

Data the app processes

  • Versions and work items, read from Jira as the person looking: a version’s name, space and release date, and a work item’s key, title (its summary), work type, status, priority, created, resolved and status-change dates, fix versions, affected versions and links, to count deployments, lead time, failures and their fixes. Changeline does not read a work item’s description, comments or attachments. A title is written by a team and can name a person, as anything typed in Jira can; Changeline keeps titles only in the cache described below.
  • People: no figure names or is about a person, and Changeline asks for no permission to read users. A work item’s assignee and reporter are not read. The one name it reads is each saved filter’s owner’s display name, shown only to tell apart two filters with one name and never stored.
  • The viewer’s own permissions, read from Jira as that person, to tell whether they are a Jira administrator and which work items they may browse.
  • Spaces, work types, statuses and saved filters, to offer them in the scope picker and the settings. Each saved filter comes with its owner’s display name.
  • What a Jira administrator enters in the settings: what counts as a deployment, when lead time starts, the failure work types and any other spaces failures are read from.

The app processes no data from outside your Atlassian site.

Data the app stores

Everything the app stores lives in Forge storage, which is hosted by Atlassian inside the Atlassian cloud. The app stores seven things:

  1. Settings chosen by your Jira administrators, one entry per site: whether a deployment is a released version or a work item reaching Done, whether lead time starts at the first move out of To Do or at creation, the failure work types, and any other spaces failures are read from.
  2. The scope a person last showed, under their account id: spaces, a saved filter’s id and name, or a JQL search they wrote (which may name a person). It is kept for 90 days from its last change, then Forge storage deletes it.
  3. A cache of an answer, kept for an hour, so a page opens at once: the figures and the rows they were counted from, for one person’s scope and period and for the same number of days just before it, which each figure is set against. Those rows hold the keys and titles of the work items the figures count, with the work types, statuses and dates their tabs show, and the names of their releases and spaces. After an hour, or when someone presses Recalculate, it is read from Jira again.
  4. A cache of one work item, kept for ten minutes, so the work item panel and the Details column open at once: that work item’s key, title, space and dates, the name of the release it shipped in, the keys of the work items that point at that release as failures and, for a failure, what it points at, for one person and one work item. No person’s name. After ten minutes, or when someone presses Recalculate, it is read from Jira again.
  5. Site metadata: your site’s list of work types (ids, names and levels), one entry for the whole site, so the app does not ask Jira for it on every page. It names no person, and is deleted by Forge storage about an hour after it is written.
  6. The “where Changeline shows up” card: a card on Changeline’s Apps page and settings page lists where Changeline 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.
  7. The review request: once the app is listed on the Atlassian Marketplace, a small “Review Changeline ⭐” link to its reviews shows on its settings page, and in a banner on its pages until each person dismisses it, from each person’s fifth open. For each person the app stores their account id, how many times they opened it, counted up to five, and whether they dismissed the banner. Until the listing is public nothing is stored.

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, loads nothing from a CDN, uses no analytics service or tracking, and shares nothing with third parties. It is built to meet Atlassian’s “Runs on Atlassian” requirements, 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 or a button pressed, 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

  • Settings are kept until the app is uninstalled or an administrator changes them.
  • A remembered scope is deleted by Forge storage 90 days after its last change. A cached answer is deleted after an hour and a cached work item after ten minutes.
  • Site metadata is deleted by Forge storage about an hour after it is written.
  • Each person’s count of opens and dismissal of the banner, 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 spaces, versions, work items with their dates, status changes, links, affected versions and priority, work types, statuses, saved filters, and the viewer’s own permissions.
  • storage:app: to keep the settings, each person’s remembered scope, the one-hour and ten-minute caches, the site’s work types, the card’s dismissal and the review request in Forge storage.

The app asks for no permission to read users and none to write to Jira.

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.