Privacy Policy
This policy covers the apps Eolivion builds for Atlassian Cloud: Issues by Team for Jira Dashboards, Scrum Poker by Eolivion (and its free edition, Scrum Poker Free by Eolivion), Scrum Retro by Eolivion (and its free edition, Scrum Retro Free by Eolivion), Issue and Work Item Templates by Eolivion and Time in Status, Cycle Time and Lead Time by Eolivion. The sections below about "the app" describe Issues by Team; Scrum Poker, Scrum Retro, Issue and Work Item Templates and Time in Status have their own sections, because they store a little more.
The short version
The app reads your Jira data to draw a chart, inside Atlassian's own infrastructure, with your own permissions. Eolivion doesn't receive, store or sell any of it. There are no Eolivion servers involved.
What the app reads
When someone views the gadget, the app asks Jira, on behalf of that person:
- the list of Teams on the site (id and name), for the chart's slices
- issue counts for the filter or project picked in the gadget's settings
- the names of saved filters and projects, only while someone is choosing one in the settings
These requests use the viewer's own Jira permissions. The app can't see anything that person can't already see.
What the app stores
| What | Where | Why |
|---|---|---|
| The gadget's settings (chosen filters or projects, sub-task option, date field for periods) | Jira, as the gadget's configuration | so the gadget shows the same thing next time |
| The last tab and period each person picked | that person's browser (local storage) | so the gadget opens where they left it |
Nothing else is stored. The app doesn't keep copies of issues, team names, counts or user details.
Where the app runs
The app is built on Atlassian Forge and runs entirely on Atlassian's platform. It makes no requests to any server outside Atlassian. Your data stays where your Jira data already is, under Atlassian's hosting, data residency and security commitments.
Scrum Poker by Eolivion
Scrum Poker runs entirely on Atlassian's platform too, makes no requests outside Atlassian, and Eolivion can't see its data. Unlike Issues by Team, it keeps some data so a session works for everyone in it.
| What | Why | Until |
|---|---|---|
| The session: name, deck, settings, and the key, summary and type of each issue in it | so everyone sees the same table | someone deletes the session |
| Each vote and its optional written reason, tied to the voter's Atlassian account ID | to reveal the cards and work out the result | the session is deleted |
| Who runs the session and who created it (account ID) | so only they can reveal, save and delete | the session is deleted |
| Who has the session open right now (account ID and time) | to show who's present | refreshed every few seconds; gone when they leave |
| Which column an issue was put in during relative sizing, and who moved it | for the shared board | the session is deleted |
| In the free edition only: when each person last used the app (account ID and date) | to apply the free edition's limit of 10 people in 30 days | 30 days after their last use |
All of this lives in Atlassian Forge storage, on Atlassian's infrastructure. The app shows names and avatars by asking Jira at the moment they're needed; it doesn't store them.
When someone saves an estimate, the app writes it to the Jira field picked for the session. If that field isn't on the issue's edit screen, the app writes it as itself, but only after checking that the person saving is allowed to edit that issue.
Once a week the app asks Atlassian which of the account IDs it holds belong to closed accounts, and erases their votes, reasons and presence.
Scrum Retro by Eolivion
Scrum Retro runs entirely on Atlassian's platform too, makes no requests outside Atlassian, and Eolivion can't see its data. It keeps what a retrospective needs so everyone in it sees the same board.
| What | Why | Until |
|---|---|---|
| The retro: name, format, columns, settings, the sprint it's about, and its action items (with the Jira issue each one became) | so everyone sees the same board, and the next retro can bring back open action items | someone deletes the retro |
| Each card's text and column, tied to the author's Atlassian account ID | so only the author can edit or delete it. In an anonymous retro, the author is never shown to anyone else | the retro is deleted |
| Each vote, tied to the voter's account ID | to limit votes per person and count them | the retro is deleted |
| Each person's answer to the mood check (1 to 5), tied to their account ID | so they can change it; only the average is shown | the retro is deleted |
| Who runs the retro and who created it (account ID) | so only they can move it forward and delete it | the retro is deleted |
| Who has the retro open right now (account ID and time) | to show who's present | refreshed every few seconds; gone when they leave |
| In the free edition only: when each person last used the app (account ID and date) | to apply the free edition's limit of 10 people in 30 days | 30 days after their last use |
All of this lives in Atlassian Forge storage, on Atlassian's infrastructure. Names and avatars are asked from Jira when they're needed and not stored.
When someone turns an action item into a Jira issue, the app creates it in the project as that person, with their permissions.
Once a week the app asks Atlassian which of the account IDs it holds belong to closed accounts. It erases their votes, mood answers and presence, and removes them as the author of their cards (the card text stays with the team).
Issue and Work Item Templates by Eolivion
Issue and Work Item Templates runs entirely on Atlassian's platform too, makes no requests outside Atlassian, and Eolivion can't see its data. It keeps the templates, the schedules and the result of each time a template is applied.
| What | Why | Until |
|---|---|---|
| Each template: name, the work types and projects it applies to, description, labels, priority, and the items and links it creates | to apply it to work items | a Jira admin deletes the template |
| Who last changed each template, and a default assignee if someone set one (account ID) | to show who changed it and to assign the items it creates | the template is deleted |
| Each schedule: the template, project, work type, summary, when it runs, the person who saved it and the people who take turns (account IDs), and the key of the last work item it created | to create the work items on time, with the right reporter and assignee | a Jira admin deletes the schedule |
| The result of each time a template was applied: the template, the keys of the items created, any errors, and notes about who couldn't be assigned an item (which can include a person's name) | to show progress and problems on the work item | the app is uninstalled |
| The ID of the "Template" field the app creates in Jira, and which option belongs to which template | to know which template someone picked | the app is uninstalled |
All of this lives in Atlassian Forge storage, on Atlassian's infrastructure. The work items, subtasks and links a template creates are regular Jira data and stay in Jira.
When a template is applied, the app creates and edits the work items itself and sets the person who created the work item as the reporter of the new items. Before applying from the work item's menu, it checks that the person can edit that work item and create work items in the project.
Once a week the app asks Atlassian which of the account IDs it holds belong to closed accounts, and removes them from the templates and schedules. A schedule whose reporter closed their account pauses.
Time in Status, Cycle Time and Lead Time by Eolivion
Time in Status runs entirely on Atlassian's platform too, makes no requests outside Atlassian, and Eolivion can't see its data. It reads work items and their status history when someone runs a report, with that person's own Jira permissions, and doesn't keep the results.
| What | Why | Until |
|---|---|---|
| The working calendar: time zone, working hours for each day and holidays | to count working hours only | a Jira admin changes it, or the app is uninstalled |
| Saved reports: name, JQL, start and end statuses, grouping and whether to count working hours | so the report can be run again | someone deletes the report, or the app is uninstalled |
| SLA goals for each project: name, statuses, target time, priorities and work types | to show whether work items meet them | a project admin removes the goal, or the app is uninstalled |
All of this lives in Atlassian Forge storage, on Atlassian's infrastructure. None of it identifies a person. The report results, including work item keys, summaries and assignee names, are calculated in the browser of the person running the report and aren't stored anywhere. The dashboard gadget keeps its last summary (counts and times, no work item details) in that person's browser for up to an hour.
What Eolivion receives
When the app is installed, Atlassian shares licensing and contact details about the customer who installs the app (for example, the site name and a billing or technical contact). Eolivion uses these only to manage the license and to answer support requests.
If you contact support, Eolivion keeps your message and contact details for as long as it takes to resolve the request, and for up to 12 months afterwards for reference. You can ask for them to be deleted at any time.
Sharing
Eolivion doesn't sell or share personal data. The only third party involved is Atlassian, as the host of the app and the Marketplace.
Your rights
You can ask what Eolivion holds about you, ask for a correction or ask for deletion, under the GDPR, the Brazilian LGPD or any similar law that applies to you. Open a request on the support portal. Eolivion will answer within 30 days.
Changes
If this policy changes, the new version will be published here with a new date. Material changes will be announced on the app's Marketplace listing.
Contact
Eolivion · Erik Carvalho Gomes de Oliveira · São Paulo, SP, Brazil
Support portal: eolivion.atlassian.net/servicedesk/customer/portal/1