Privacy policy — Lineset

This policy covers every Jira Cloud app published under the Lineset name, and the websites that describe them. The apps are published by Sugar Systems, SIA (registration number 40203386400), Stirnu street 5-29, Riga, LV-1035, Latvia (“we”, “us”). Each app has its own section below: what it reads in your Jira site, what it stores, and for how long. The sections on the websites, the waitlist and your rights apply to every app.

Sumline

What the app does

Sumline reads issues in your Jira site and adds up their estimates and time fields across the issue 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 an issue they could not open themselves.

Data the app processes

Issue data read from your Jira site: issue keys, summaries, issue types, status categories, parent links, story points, time-tracking values, sprint values and the assignee's display name and account id. This data is processed to compute rollups.
Your Atlassian account id, used only to keep each person's cached rollups separate from everyone else's.

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 two things:

A rollup cache: the computed numbers for an issue, a space or a set of spaces, together with the issue keys and summaries needed to show them, keyed by the viewer's account id. Each entry is treated as expired after five minutes and overwritten on the next view.
Settings chosen by your Jira administrators (which fields to roll up, which hierarchy level makes a row, the done-only switch, the mixed-estimate rule).

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 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.

Retention and deletion

Cache entries are ignored five minutes after they are computed, or as soon as an administrator changes the settings, and overwritten by the next rollup. Storage has no expiry of its own.
All app storage is deleted by Atlassian when the app is uninstalled from your site.
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 issues, their fields and the site's field definitions.
storage:app — to keep the cache and settings in Forge storage.

Blockline

What the app does

Blockline reads issues and the links between them in your Jira site, works out which issues are at risk because of work they wait on, and 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 an issue they could not open themselves.

Data the app processes

Issue data read from your Jira site: issue keys, summaries, issue types, hierarchy levels, parent links, status categories and the time of the last status category change, issue links and link types, due dates, Target end dates, sprint values, fix versions and their release dates, and the assignee’s display name and account id. This data is processed to judge dependency risk.
Spaces and saved filters you can open, to offer them as a scope.
Your Atlassian account id, used only to keep each person’s cached views and saved scope separate from everyone else’s.

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 three things:

Computed views: the risk levels, reasons, keys, summaries, dates and owner names of the issues in a view, keyed by the viewer’s account id, one entry per person and view. Each entry is replaced every time the view is rebuilt and served for at most ten minutes. A person’s entries are never served to anyone else.
Saved scopes: the scope a person saved on the Apps page (space keys, a filter id or their own JQL), one entry per person.
Settings chosen by your Jira administrators (link types and their direction, the order of date sources, thresholds, deliverable levels and an optional default scope of space keys), one entry per site.

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 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. The app’s logs carry no issue content, issue keys or account ids.

Retention and deletion

Computed views are served for at most ten minutes after they are built, or until an administrator changes the settings, and are overwritten by the next build.
Saved scopes are kept until the person saves a different one.
All app storage is deleted by Atlassian when the app is uninstalled from your site.
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 issues, issue links, fields, link types, spaces, saved filters and the viewer’s own permissions.
storage:app: to keep the cache, saved scopes and settings in Forge storage.

The app has no write permission: it cannot change an issue, a link or a setting in Jira.

Logline

What the app does

Logline reads the worklogs in your Jira site, adds them up by person, issue, space or field over a period, and shows the result inside Jira as a report. It reads on behalf of the person looking at the page, using their Jira permissions, so it never shows anyone a worklog, an issue or a comment they could not see themselves, including worklogs restricted to a group or role.

Data the app processes

Issue data, for the issues with time logged in a report’s period and scope, exactly these Jira fields: summary, issue type, status, space, parent, priority, components, labels, original estimate, remaining estimate and time spent, plus the custom choice fields (select or radio) a report groups by.
Worklogs on those issues: each worklog’s author, start time, time spent and comment. This data is processed to group and total the hours.
People and Jira groups from your site’s user directory: the names and time zones of the people a report is limited to, the members of the Jira groups it is limited to, and the viewer’s own groups, to check whether a report shared with a group may be opened.
Spaces and saved filters you can open, to offer them as a scope.
Your Atlassian account id, used to keep each person’s saved reports and report snapshots separate from everyone else’s.

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 four things:

Settings chosen by your Jira administrators (the time zone rule, the first day of the week, the working-day length and working days, the hours format, and who may share reports), one entry per site.
Saved reports: each report’s name, its owner’s account id, who it is shared with (account ids or group ids), its scope (space keys, a filter id or a JQL query), the people it is limited to (account ids or group ids), its period and its layout, one entry per report.
Last opened: when each person last opened each report, one entry per person.
Report snapshots: the worklogs of one report as one person saw them (issue keys and summaries, author names, dates, hours and the worklog comments, cut to 1,000 characters), keyed by the viewer’s account id, one entry per person and page. Each snapshot is served for at most ten minutes and deleted by Forge storage one minute later (a time-to-live on every entry); a big report being read in steps keeps its partial state the same way. A person’s snapshot is never served to anyone else.

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 or tracking, and shares nothing with third parties. Exports are built in your browser from what is on screen; they are not sent anywhere. The app is built to meet Atlassian’s “Runs on Atlassian” requirements, Atlassian’s designation for apps with no data egress. The app’s logs carry no issue content, issue keys, comments or account ids: only status codes and error kinds.

Retention and deletion

Report snapshots expire 11 minutes after they are built: they are served for at most ten minutes, then deleted by Forge storage.
Saved reports are kept until their owner or a Jira administrator deletes them.
Settings are kept until an administrator changes them.
All app storage is deleted by Atlassian when the app is uninstalled from your site.
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 issues, worklogs, fields, spaces, saved filters and the viewer’s own permissions.
read:jira-user: to read the people and Jira groups a report is limited to: group members, names for the people picked, and the viewer’s own groups for reports shared with a group.
storage:app: to keep saved reports, settings and the short-lived report snapshots in Forge storage.

The app has no write permission: it cannot create, change or delete a worklog, an issue or a setting in Jira.

The websites

This website (https://lineset.dev) and each app’s site under it are static pages hosted by Netlify.

Access logs. Netlify keeps its own short-term server logs (IP address, requested page, browser type) to run the service.
Visit counts. We count visits with Umami Cloud, run by Umami Software, Inc. as our processor: the page, the site you came from, your browser, operating system, device type and country, and which buttons and links were clicked. Umami sets no cookies, does not store your IP address and does not follow you to other websites. It runs only on https://lineset.dev, never on an app’s own domain.
Cookies. The sites set no cookies.
No accounts. Apart from the waitlist below, the sites take no input.

The waitlist

An app that is not on the Atlassian Marketplace yet has a “Get notified” form. If you send it:

What we keep: the email address you type, which app it is for, and when you sent it.
Why: to send you one email when that app is on the Atlassian Marketplace. We send nothing else, and we share the address with no one.
Where: in Netlify Forms, part of the hosting these sites run on. Netlify stores it for us as our processor.
How long: until that email is sent; then we delete it. Ask us through our support site at https://sumline.atlassian.net/servicedesk/customer/portal/1 or by email at [email protected] and we delete it sooner.

We keep the address because you asked us to, by sending the form. You can withdraw that at any time by asking us to delete it.

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 at https://sumline.atlassian.net/servicedesk/customer/portal/1 or by email at [email protected]. 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.