Cloud Security Statement

1. Overview

Estimation Poker for Jira is built on the Atlassian Forge platform. This statement describes how we use Forge and which controls we apply to help protect customer data.

2. Hosting & Architecture

• All application logic executes within Atlassian Forge's isolated runtime.
• Data used by the App is stored using Forge storage services and Jira properties within Atlassian's infrastructure. Live updates are delivered through Forge Realtime.
• The App makes no connections to external servers: no data leaves Atlassian.
• No production Jira content is stored on servers operated directly by MyStatement, Inc. unless explicitly agreed for support or troubleshooting.

3. Data Protection

• Data at rest is encrypted using Atlassian-managed encryption.
• Data in transit is protected using TLS (HTTPS) enforced by Atlassian.
• The App stores as little as possible: votes (Atlassian account identifier and card), which are deleted when a round ends; the history of saved estimates with their votes, kept for the period a Jira administrator chooses; session lists, which expire a day after their last change; presence records, which expire after 10 minutes; and settings. Work item content is read for display and is not stored.
• The App stores no passwords, PINs or other secrets.
• Access to configuration and logs is restricted to authorized personnel of MyStatement, Inc. under least-privilege principles.

4. Permissions

The App requests only the Jira permissions it needs:

• Read work items, boards, board configurations and sprints, to list the work items to estimate and to find the board's estimation field.
• Write work items, to save the agreed estimate to the estimation field. Saving is done as the user who clicks Save, so Jira's own permissions apply.
• Read user display names, to show who has voted and who is in a session.
• Read and write app, project and user properties, to save the settings.
• Forge storage, to keep votes, sessions, presence and the estimation history.

5. Application Security Practices

• Use of secure coding practices and regular internal reviews.
• Separation of environments for development, staging and production.
• Votes are hidden until the reveal on the server side: the App's backend does not send the values of other people's votes to any browser before the round is revealed, and votes are not stored where other apps or users could read them.
• The identity of a user and the work item or project they are working in are taken from the request context signed by Forge, and the App checks the user's Jira permissions before it accepts a vote or shows a history entry. Site settings can only be changed by Jira administrators.

6. Incident Response

In the event we become aware of a security incident affecting data processed by the App, we will investigate promptly and, where required, notify affected customers in cooperation with Atlassian's incident management processes.

7. Vulnerability Reporting

We encourage responsible disclosure of potential vulnerabilities.