Blockline privacy policy
Last updated 10 November 2026
Blockline (“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
Blockline reads work items and the links between them in your Jira site, works out which work items 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 a work item they could not open themselves.
Data the app processes
- Work item data read from your Jira site: work item keys, summaries, work types, hierarchy levels, parent links, status categories and the time of the last status category change, work item links and link types, due dates, Target end dates, sprint values, fix versions and their release dates, and the assignee’s account id. This data is processed to judge dependency risk. The assignee’s display name is read when a board is shown, to label its Owner filter and export, and is never stored.
- Change log of the work item a panel is shown on and of the one or two work items behind its headline reason, read from Jira to say since when that risk has held (“At risk since …, when PAYC-3’s due date moved past this epic’s date”). Blockline uses only the day each due date, link or assignee changed. It is read, never stored: the answer is one day and a work item key, kept with the cached view for about an hour like the rest of it, and it is the same for everyone who can open those work items.
- Spaces and saved filters you can open, to offer them as a scope, with each filter’s owner’s display name, shown only to tell apart two filters with one name and never stored.
- Your Atlassian account id, used only to keep each person’s cached views, last scope and risk history separate from everyone else’s, and to keep a line or card you dismiss dismissed for you.
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:
- Computed views: the risk levels, reasons, keys, summaries, dates and the assignees’ account ids (no names) of the work items 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, served for at most ten minutes, and deleted by Forge storage about an hour after it is written. In that hour it is shown again only to the same person, and only while their build allowance (below) is used up, marked as the last build rather than a new one. A person’s entries are never served to anyone else.
- Last scopes: the scope a person last showed on the Apps page (space keys, a filter id or their own JQL), so the page opens on it next time: one entry per person, replaced each time they press Show risk, kept 90 days from the last change. A scope opened from a link is not kept.
- Settings chosen by your Jira administrators (link types and their direction, the order of date sources, thresholds, deliverable levels, an optional default scope of space keys, and whether Excel downloads end with a line naming Blockline), one entry per site.
- Site metadata: your site’s list of fields (ids, names and types), its work types and its work item link types, one entry each for the whole site, so the app does not ask Jira for them on every view. It names no person. Each entry is deleted by Forge storage about an hour after it is written.
- Risk history behind the boards: for each open deliverable (an epic, by default) a board showed a person, the days its risk level changed for that person, with the level and the names of the rules behind it (for example “a day, At risk, late blocker”), which is what lets the board mark what changed since their last visit. It holds the deliverable’s work item key but no summary, date or name. At most the last 20 changes are kept per person and deliverable. It is written only when that person opens a board, never in the background, and it is never shown to anyone else, because risk is judged with each person’s own permissions. The work item panel does not use it.
- Last visit: for each board a person opens (a space’s Blockline tab, the Apps page, a dashboard gadget), the risk level, rule names and own date of each deliverable the board showed them last time, so the board can mark what changed since, a moved date included. It holds work item keys and dates but no summary or name, one entry per person and board (on the Apps page, one per scope the person picks there).
- Build allowance: how much of the hour’s Jira requests each person’s fresh views have used, as a count and the time the hour started, so one person cannot use up what every site shares. It holds no work item data, one entry per person.
- The review request: once the app is listed on the Atlassian Marketplace, a small “Review Blockline ⭐” 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 Blockline shows up” card: a card on Blockline’s Apps page and settings page lists where Blockline 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.
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. The app’s logs carry no work item content, work item keys or account ids.
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
- Computed views are served for at most ten minutes after they are built (less if an administrator changes the settings), or for the rest of the hour to the same person while their build allowance is used up, and Forge storage deletes each one about an hour after it is written. Forge removes expired entries in the background, so an entry can stay in storage for up to 48 hours after it expires; it is never served after that hour.
- Site metadata is deleted by Forge storage about an hour after it is written (again, at most 48 hours later).
- A build allowance is deleted by Forge storage when its hour ends.
- Risk history and last-visit entries are deleted by Forge storage 180 days after they were last written, so a deliverable or board nobody opens for six months is forgotten.
- Last scopes are deleted by Forge storage 90 days after they last changed (at most 48 hours later).
- 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, work item links, their change log, fields, link types, spaces, saved filters and the viewer’s own permissions.storage:app: to keep the cache, last scopes, settings, each person’s risk history and the review request’s and the card’s records in Forge storage.
The app has no write permission: it cannot change a work item, a link 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.