Logline privacy policy
Last updated 10 November 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, work item, 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, a work item or a comment they could not see themselves, including worklogs restricted to a group or role.
Data the app processes
- Work item data, for the work items with time logged in a report’s period and scope, exactly these Jira fields: summary, work type, status, space, parent, priority, components, labels, original estimate, remaining estimate and time spent, plus the custom choice fields (select lists, radio buttons or checkboxes) a report groups by and the one custom field the site’s billable rule reads, if it uses one.
- Worklogs on those work items: 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, time zones and account status of the people a report shows (the authors of its worklogs, the people it is limited to, the members of the Jira groups it is limited to, and the people its work item fields name), read while the report is open and never stored, and the viewer’s own groups, to check whether a report shared with a group may be opened and, when your administrators keep everyone’s worklogs to chosen groups, whether the viewer may see other people’s worklogs.
- 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, favourites, last report and report snapshots separate from everyone else’s, and to keep a line or card you dismiss dismissed for you, and your time zone from your Jira profile, read each time a report or the work item panel counts days and never stored, so your report counts each worklog on the day it started where you are.
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 nine things:
- Settings chosen by your Jira administrators (the time zone rule and the one time zone for everyone, if they set one, the first day of the week, the working-day length and working days, the hours format, who may share reports, who may see other people’s worklogs, with those Jira groups by id and name, which worklogs count as billable, whether the billable share is coloured and the two percentages where it turns yellow and green (a space may have its own two, or none, by its space key), and the hourly rates they enter: a currency, a default rate, rates per space, rates per client (a value of the client field), rates per person with that person’s account id, never their name, and rates per person in a space (the account id and the space key), each with the day it starts if it has one), the cost rates they enter the same way (what an hour costs: a default, rates per space, per person by account id and per person in a space, each with the day it starts if it has one) and the one Jira group that sees cost and margin, and only its members (its id and name), the budgets they set (a space key, an epic’s key or a value of the client field, in hours or money, for the whole work from a day or for each month) and the client field (its id and name), and whether Excel and PDF downloads end with a line naming Logline, one entry per site. The cost rates and the budgets are kept apart from the other settings.
- Saved reports: each report’s name and description, its owner’s account id, who it is shared with (account ids, or Jira groups by id and name), the people who may edit it (account ids), its scope (space keys, a saved filter’s id and name, or a JQL query), the people it is limited to (account ids, or Jira groups by id and name), its period and its layout, one entry per report. People are kept by account id only, never by name.
- Last opened and favourites: when each person last opened each report, and which reports each person starred as favourites (report ids), one entry of each per person.
- Report snapshots: the worklogs of one report as one person saw them (work item keys and summaries, each author’s account id, dates, hours and the worklog comments, cut to 1,000 characters), keyed by the viewer’s account id, one entry per person and page; the work item panel keeps its read of one work item and its children the same way (the work item keys and summaries, each author’s account id, each child work item’s assignee as an account id, dates and hours, and the worklog comments only while a Jira admin has turned on “Show recent worklogs in the work item panel” in Logline settings, which is off unless they do). People are kept by account id only: their names and time zones are read from Jira while the report is open, never stored. 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, and so does the list of spaces and saved filters a person can see, kept for the report builder’s scope picker. A person’s snapshot is never served to anyone else. When your administrators keep everyone’s worklogs to chosen groups, whether a person may see other people’s worklogs, worked out from their Jira groups, is kept the same way under their account id for an hour (the groups themselves are not stored), and so is whether a person may see cost and margin. Where a report shows budgets for the whole work, what they count is kept under that person’s account id for an hour instead: the worklogs of the budgeted spaces and clients without their comments, and each budgeted epic’s totals (hours, amounts and the work item keys whose estimates were left out). Each is served for at most an hour and deleted by Forge storage about 61 minutes after it is written.
- 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.
- Allowances: how much of the hour’s Jira requests each person’s fresh reports, and the names they show, have used, as a count and the time the hour started, so one person cannot use up what every site shares. They hold no work item data and no name, two entries per person, and are deleted when their hour ends.
- The review request: once the app is listed on the Atlassian Marketplace, a small “Review Logline ⭐” 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.
- The “where Logline shows up” card: a card on Logline’s Apps page and settings page lists where Logline 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.
- Last reports: the report a person last had open on the Apps page, as its address (a saved report’s id, or the report’s scope, people, period and view, which may include their own JQL), so the page opens on it next time: one entry per person, replaced as they change it, kept 90 days from the last change. A report opened from a link is not kept until they change it.
The app stores no passwords, no API tokens and no data about people beyond their account ids where listed above: no names, email addresses, avatars or time zones.
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. 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 work item content, work item keys, comments or account ids: only status codes, error kinds and counts of requests and work items.
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
- 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. What whole-work budgets count is served for at most an hour and deleted about 61 minutes after it is written.
- 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 reports are deleted by Forge storage 90 days after they last changed (at most 48 hours later).
- Last-opened times are kept for each person’s 200 most recently opened reports, until the app is uninstalled.
- Favourites are kept for each person’s starred reports, at most 100, until they unstar them or the app is uninstalled; a star on a report that is deleted, or no longer shared with them, is dropped the next time they open Saved reports.
- Each person’s allowances are deleted by Forge storage when their hour ends.
- 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 work items, 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 and shows: group members, the names and time zones of the people in a report while it is open, the viewer’s own time zone, and the viewer’s own groups for reports shared with a group.storage:app: to keep saved reports, settings, the short-lived report snapshots and the review request’s and the card’s records in Forge storage.
The app has no write permission: it cannot create, change or delete a worklog, a work item 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 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.