Skip to content
Workline
Menu

Workline privacy policy

Last updated 3 November 2026

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

Workline shows who has time, week by week, in Jira: each person’s hours planned from the remaining estimates of open work items and from the time a manager books, against the hours they can work. It reads Jira as the person using it. It writes to Jira only when a person presses Move on a work item, and then only that work item’s assignee and, if they gave one, its due date, or presses Apply on a plan of work with no dates, and then only those work items’ start and due dates, as that person. It never changes an estimate, any other field or a setting.

Data the app processes

  • Work items, read from Jira as the person looking: key, summary, space, assignee, estimates, start and due dates and sprint, to place each work item’s hours in the weeks. Workline never stores a work item’s summary, description or any of its fields.
  • People: account ids and display names, read from Jira to name the rows, and the members of a Jira group offered as a team. A person’s display name is read when the page is shown and is 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.
  • Jira’s time tracking settings (hours a day, days a week) and Jira’s group list, to give the default working week and to offer groups on the settings page.
  • What a Jira administrator enters in the settings: the working week, people’s own hours and working days, holidays, a person’s time off and who may book.
  • What a person enters to book time or add a placeholder: who it is for, what it is for (their own words, or the key of a space, an epic or a work item, which Jira is asked to find as that person), the days, the amount, and a placeholder’s role name, first day and hours. Nobody should put personal data in a booking’s words or a placeholder’s name.

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

  1. Settings chosen by your Jira administrators, one entry per site: whether the working week is Jira’s or Workline’s own (and its hours a day and working days), each part-time person’s account id with their own hours and days, the holidays (a day and a name), each person’s time off (an account id and the days), and the id and name of each Jira group offered as a team, and whether everyone who can open the app may book time or only chosen groups (the id and name of each).
  2. Bookings, one entry each: who it is for (an account id, or a placeholder’s id), what for (the booker’s own words of at most 100 characters, or the key of a space, an epic or a work item and, for a work item or epic, its space), the first and last day, the amount (a share of their time, or hours a week), who booked it and when, and who changed it last and when (account ids and times). A booking never holds a work item’s summary or a space’s name. A site holds at most 2,000.
  3. Placeholders, one entry each: a role name of at most 100 characters, its first day, its own hours a day and working days if given, and the id of a team if picked. A site holds at most 200.
  4. The scope a person last showed, under their account id: spaces, a saved filter’s id 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.
  5. A cache of a plan, kept for ten minutes, so a page opens at once: the hours per person and week, without names. After ten minutes, when someone presses Recalculate, or when a booking, a placeholder or a move is saved, it is read from Jira again.
  6. The review request: once the app is listed on the Atlassian Marketplace, a small “Review Workline ⭐” 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 plan itself is never stored: it is worked out again from Jira each time. 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 person’s time off or own hours is removed from the settings page. A booking or a placeholder is kept until a person edits or deletes it in the app; deleting a placeholder deletes its bookings.
  • A remembered scope is deleted by Forge storage 90 days after its last change. A cached plan is deleted after ten minutes.
  • 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 (estimates, dates, sprints and assignees), spaces and saved filters, a booking’s space or work item as the viewer finds it, and the viewer’s own permissions.
  • read:jira-user: to read Jira’s time tracking settings, a team’s members, the display names of the people on screen and Jira’s group list.
  • storage:app: to keep the settings, the bookings and placeholders, each person’s remembered scope, the ten-minute cache and the review request in Forge storage.
  • write:jira-work: to set a work item’s assignee and, when given, its due date when a person presses Move, and a work item’s start and due dates when a person presses Apply on a plan of unscheduled work. It is used for those alone, as the person pressing it, so Jira’s permissions decide and Jira’s history names them. The app writes no comment, estimate or other field.

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.