Security
Facts about how Sprint Radar handles your Jira credentials and data. We make no certification claims.
Read-only use of Jira
Sprint Radar sends read requests to Jira and no others. It never creates, edits or deletes an issue. An Atlassian API token carries the permissions of the account that made it, so we suggest a token from an account with read access only.
Credentials are encrypted
Your Jira API token is encrypted before it is stored, with AES-256-GCM. The key for each record is derived with scrypt and a random salt, and each record has its own random initialization vector. The token is decrypted in memory when it is needed to call Jira: when you check a connection and when a forecast runs. It is never sent back to the browser.
Tenant isolation
Every workspace is a tenant. Queries for tenant data run in a database transaction that sets the current workspace, and PostgreSQL row-level security enforces that setting for the application role. Requests are also checked by one authorization layer before they reach the data. The application role cannot bypass row-level security.
Outbound request guard
You type the Jira address, so we do not trust it. It must use https. A Jira Cloud address must end in .atlassian.net and use port 443. We resolve the host name and refuse private, loopback, link-local and cloud metadata addresses, at connection time as well as when you save. We do not follow redirects. Requests time out after 10 seconds.
What we store
We store:
- Your account details (name, email) and workspace details.
- Jira connection details: site URL, account email and the encrypted API token.
- Project settings, such as the JQL filters you set.
- Forecast results: dates, throughput, cycle and lead time summaries.
- Generated reports. A report can show issue keys and titles, for example in the list of aging work.
- Funnel events with no personal data, and server logs.
We do not store your source code. We do not keep a copy of your Jira issues: issue data is read while a forecast runs.
Deleting data
You can delete a report, a project or a connection in the app. Deleting a report removes its stored document and its content. For deletion of a whole workspace or of your personal data, write to support@sprintradar.com.
Subprocessors
- Clerk: sign-in and organization membership.
- Atlassian: we call the Jira API of your site on your behalf.
- Cloud host: runs the service, the database and report storage. The provider and region will be named here before launch.
- Stripe: card payments, when billing launches.
Report a problem
Found a security problem? Write to support@sprintradar.com.