The gadgets run on Atlassian's Forge platform with no remote components, which is the design the Runs on Atlassian program requires (Forge's own check, forge eligibility, says each version is eligible). They have no servers of ours, no database, no remote calls and no external network access. Jira data is read when someone opens a dashboard, turned into numbers in memory, shown on the screen, and discarded.
The vendor, Eitan Plaks, is responsible for how these apps process your Jira data. Atlassian is not.
When someone opens a gadget, the app reads Jira data on behalf of the customer. For that data the customer is the controller and the vendor is a processor. The vendor's code runs on Atlassian's Forge platform, so Atlassian acts as a sub-processor under Atlassian's Forge data processing addendum. The vendor does not receive, store or read this data, and the apps are built so that it does not appear in the logs the vendor can see.
The vendor is a controller only for the messages people send to support (see Support correspondence below).
A data processing addendum is part of the terms.
Every call is made as the person looking at the dashboard, with that person's Jira permissions.
| Gadget | Reads | Jira permission (scope) and why |
|---|---|---|
| All three | Issues found by JQL: key, summary, type, priority, status, assignee name, dates (created, resolved, when the status category last changed), estimates, time spent, story points, change history; field and status lists; filters | read:jira-work: search issues, read fields, statuses, filters and change history |
| Scope Creep & Churn | Boards, their sprints, a board's filter and estimation field | read:board-scope:jira-software (list boards), read:sprint:jira-software (read sprints), read:board-scope.admin:jira-software (read a board's configuration), read:project:jira (required by Jira's board endpoints) |
The gadgets make no write calls to Jira. All granted scopes are read scopes.
The gadgets show names that Jira returns, such as the assignee of an issue or the person who added an issue to a sprint. They do not copy, keep or send those names anywhere.
This is the only personal data the vendor holds, and the vendor is its controller.
The vendor stores no Jira data in any country. The processing happens on Atlassian's Forge infrastructure. Atlassian's Forge documentation says an app invocation may sometimes run in a different location from the one that hosts your Jira site; Atlassian's data processing addendum covers that case. What the Forge log holds is described under Logs above.
Nobody outside Atlassian, which hosts the apps and provides the Jira API. The vendor shares no Jira data with any other person or company, and the apps declare no external hosts. Support messages are covered in the section above.
Because the vendor holds no Jira data, a request to see, correct or erase that data goes to your Jira administrator, who controls it. For anything the vendor holds, such as a support message, write to the address below. You can also complain to Israel's Privacy Protection Authority or, if you are in the EU, to your national data protection authority.
Eitan Plaks, support@cooloffapp.com