Skip to content
Menu
HelpPrivacy, permissions and data

Privacy, permissions and data

No servers. Changes nothing in Jira. Blockline reads your work items and their links as you, writes nothing back, and runs on Atlassian Forge with no servers of its own.

Permissions

Blockline asks for two:

  • 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 its settings, each person’s last scope, its cache and each person’s risk history in Forge storage.

It has no write permission. It cannot change a work item, a link or a setting in Jira.

Whose permissions

Every Jira read is made as the person looking at the page, so Jira applies that person’s permissions. A work item someone cannot open is never read for them and never shown to them, and Jira leaves links to it out, exactly as in Jira’s own views. That is why someone may not see a blocker a colleague can: ask the work item’s owner for access, or ask someone who can see both work items.

A change to who can see a space shows in Blockline within 10 minutes, or at once with Recalculate: until then a person’s own saved view can still list a work item they could open when it was built, though Jira will not open it for them.

So risk differs per viewer: two people can see a different level, reason and data health for the same epic, and each person’s “changed since your last visit” markers are kept for them alone, never shown to anyone else. The panel’s “At risk since …, when …” is worked out from the work items’ change log in Jira, which is read and not stored.

What it stores

Everything is in Forge storage, hosted by Atlassian:

  • the site’s settings, one entry per site;
  • each person’s last scope on Apps › Blockline (the one they last showed, so the page opens on it), deleted by Forge storage 90 days after it last changed;
  • each person’s computed views: levels, reasons, keys, summaries, dates and the owners’ account ids (no names; a board looks the names up each time it is shown) of the work items in a view, one entry per person and view, replaced on every rebuild, served for at most 10 minutes (to the same person for the rest of the hour while their build allowance is used up) and deleted by Forge storage about an hour after it is written (Forge clears expired entries in the background, within 48 hours). One person’s entries are never served to anyone else;
  • the site’s field list, work types and link types, shared by everyone on the site and deleted by Forge storage about an hour after they are written. They name no person;
  • each person’s risk history behind the boards: for each open deliverable a board showed them, the days its risk level changed for them, with the level and the names of the rules behind it, at most the last 20 changes, so the board can mark what changed since their last visit. The panel does not use it;
  • each person’s last visit to each board: the level, rule names and date of every deliverable it showed them, so the board can mark what changed since, a moved date included;
  • each person’s build allowance: how much of the hour’s Jira requests their fresh views have used, a count and the time the hour started, so one person cannot use up what every site shares. It holds no work item data and is deleted by Forge storage when the hour ends.
  • for each person who dismissed the “where Blockline shows up” card (on the Apps page and the settings page), their account id and when, so it stays dismissed, until the app is uninstalled;
  • once Blockline is on the Marketplace, for each person, their account id, how many times they opened Blockline, counted up to ten, and when they dismissed the banner: from the tenth open, Review Blockline ⭐, a link to its reviews, shows on the settings page, and in a banner at the top of the space page and the Apps page until dismissed. Kept until the app is uninstalled.

Risk history holds work item keys, levels and rule names; last visits hold those and each deliverable’s own date. Neither holds a summary or a name. They are written only when that person opens Blockline, never in the background, are never shown to anyone else, and are deleted by Forge storage 180 days after their last write.

The change log of a work item is read from Jira, as the person looking, to say since when a risk has held. Blockline uses only the day a due date, a link or an assignee changed, and keeps none of it: the answer is a day and a work item key, held with the cached view for about an hour.

The spaces chosen for a dashboard gadget are saved by Jira as that gadget’s configuration, like any other gadget’s, not by Blockline.

When the app is uninstalled, 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.

What leaves your site

Nothing. Blockline makes no request to any service outside Atlassian, loads nothing from a CDN, and has no analytics service or tracking. Its logs carry no work item content, keys or account ids.

Atlassian counts how often each part of Blockline is used on your site and shows us the counts. A count carries no work item data and names no person.

The full policy is on the privacy page.