The app runs entirely on Atlassian's infrastructure. No issue content, no personal data and no estimate is ever transmitted to us or to any third party. We operate no servers and hold no copy of your data.
What the app stores
To do its job, the app records the following in Atlassian's Forge hosted storage, inside your own Atlassian cloud instance:
- Estimation votes: for each issue being estimated, the Atlassian account ID of each voter, the card they chose and when.
- Round status: who revealed the votes, the agreed estimate, and whether Jira accepted it.
- Live sessions: the session name; the list of issues with their key, summary, type and current estimate as read from Jira; the moderators' account IDs; and the agreed result for each issue.
- Presence and access checks: the account IDs of people who opened a live session, when they were last active, and, for each issue, whether Jira allows them to see it.
- Project settings entered by a project administrator: card scale, where estimates are saved, and whether watchers are emailed.
- Caches: which field each project's board estimates in, and which issue types cannot hold that field.
The only thing the app writes to Jira itself is the agreed estimate, to the field chosen for the project.
What the app does not do
- It does not read or store issue descriptions, comments or attachments.
- It does not collect names, email addresses or IP addresses. Names and avatars shown next to votes are rendered by Jira in your browser from the account ID.
- It does not use cookies, analytics, tracking or advertising.
- It does not send data to any third party. There are no sub-processors.
- It makes no network calls outside Atlassian. The app qualifies for Atlassian's Runs on Atlassian programme, which Atlassian verifies automatically and monitors on an ongoing basis.
Why each permission is requested
Every permission below is one the code actually calls. Each entry names the use, not the permission in general.
| Permission | Why it is needed |
|---|---|
storage:app |
Stores estimation votes, round status, live sessions, project settings and small caches, all in Forge hosted storage inside your own instance. |
read:jira-work |
Reads an issue's key, summary, type and current estimate, and searches issues with JQL to build a live session from the backlog, a sprint or a query. After saving, reads the field back to confirm Jira holds the value. |
write:jira-work |
Writes the agreed estimate to the one field the project estimates in, or to Original estimate for hours. It writes nothing else. |
read:jira-user |
Checks that the person saving an estimate can edit the issue, and that each session participant can browse each issue before it is shown to them. |
read:board-scope:jira-software |
Lists the project's boards to find where the team estimates. |
read:board-scope.admin:jira-software |
Reads a board's estimation configuration, which says which field the board estimates in. Jira requires this permission for that request. |
read:project:jira |
Required by Jira alongside the board permissions to list a project's boards. |
read:sprint:jira-software |
Lists active and future sprints, so a live session can be opened from a sprint. |
Where the data lives
In Atlassian's Forge hosted storage, within the Atlassian cloud environment of your own instance and subject to Atlassian's data residency arrangements for that instance. We have no access to it except where you explicitly share it with us in a support request.
Retention and deletion
Votes stay with the issue until its round is restarted: Vote again and Estimate again delete the previous votes. Everything else is tied to the app installation. When the app is uninstalled, Atlassian soft deletes the data and retains it for 28 days before permanent deletion, under Atlassian's platform data lifecycle. Within 21 days of uninstallation a reinstallation can be relinked to the previous data, but only at the customer's request and with the customer's consent. After the retention window the data cannot be recovered.
Legal basis and your rights
Where the GDPR applies, the customer's Atlassian instance administrator is the data controller for the account identifiers described above. Those records are created and kept inside the customer's own Atlassian instance. We do not receive them, hold a copy of them or have any access to them, and we therefore act as neither a data controller nor a data processor in respect of them. Requests for access, correction, export or erasure are satisfied directly in your own instance, or by uninstalling the app. Contact us at soporte@vantelia.es for anything you cannot resolve there.
Support data
If you contact support, we receive whatever you choose to include in that message. Keep sensitive content out of support requests.
Changes
Material changes will be reflected here and the "Last updated" date revised. Continued use after a change constitutes acceptance.