Lineset
Menu

Logline privacy policy

Last updated 4 October 2026

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

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 and the one custom field the site’s billable rule reads, if it uses one.
  • 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 five things:

  1. 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, who may share reports, which worklogs count as billable, and the hourly rates they enter: a currency, a default rate, rates per space, and rates per person with that person’s account id and name), one entry per site.
  2. 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.
  3. Last opened: when each person last opened each report, one entry per person.
  4. 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 about 11 minutes after it is written (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.
  5. Site metadata: your site’s list of fields (ids, names and types), one entry for the whole site, so the app does not ask Jira for it on every report. It names no person, and is deleted by Forge storage about an hour after it is written.

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, error kinds and counts of requests and issues.

Retention and deletion

  • Report snapshots are served for at most ten minutes after they are built, and Forge storage deletes each one about 11 minutes after it is written. Forge removes expired entries in the background, so a snapshot can stay in storage for up to 48 hours after it expires; it is never served after ten minutes.
  • Site metadata is deleted by Forge storage about an hour after it is written (again, at most 48 hours later).
  • Saved reports are kept until their owner or a Jira administrator deletes them.
  • Settings are kept until an administrator changes them.
  • Last-opened times are kept for each person’s 200 most recently opened reports, until the app is uninstalled.
  • 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.

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.