Contents        

Agile Poker Cloud

This part of the documentation relates to Agile Poker - estimation tool for Jira Cloud. If you use Jira Server go to the Agile Poker - estimation tool for Jira Server documentation.

We take data security very seriously so we use only trusted service providers with the highest security standards. On this page, you will find details on how we secure our clients' data. If you think something is missing or you have any security related questions please let us know at Spartez Support Portal or support@spartez.com.

Services providers

SUB-PROCESSOR - providers with this label are our data sub-processors as defined by European General Data Protection Regulation (GDPR)

Heroku 

SUB-PROCESSOR Agile Poker Cloud runs on Heroku environment. Besides the application itself, Heroku stores application access logs that contain user IP, user key, instance URL and user JWT token. These logs are purged after 7 days. 

Heroku Postgres 

Heroku Postgres stores data provided during the installation handshake. Stored keys authenticate us to clients' instances.

The database is secured using a security mechanism provided by Heroku. See https://www.heroku.com/policy/security#postgres for details.

Stored Data

  • A key that identifies Jira instance.
  • Shared secrets for communication with Jira.

Firebase 

SUB-PROCESSOR Firebase is a real-time shared database. We use it to synchronize session data in real time between users.

Stored data

  • JIRA client key
  • Board id to associate session data.
  • Ids of users (participants of any session, users that modified a session properties the last time e.g. change scrum master)
  • Ids of issues (active issue, voted issues, issues selected in the filter, reference issues)
  • Estimation votes of users per issue.
  • Session state (e.g. open/closed flag, timer state).
  • Display name, email addresses and notification message (while sending email notifications we tentatively store these discarding them right after dispatching) 

Security

Firebase database is secured using Firebase security rules. Each user in your Jira instance has access to all data listed in section Stored data for all your poker sessions. Anonymous users and users from different Jira instances do not have access to your data. We also store 30 daily backups of this database.


We store the minimal amount of data needed to provide our service.

We don't store issue summaries, descriptions, comments nor other sensitive information. We don't store users full names nor e-mails but we use user keys provided by Jira which can contain them.

Bugsnag

SUB-PROCESSOR Bugsnag is a tool for reporting of in-browser errors. It allows us to fix errors before people report them to us.

Stored data

  • JIRA client key
  • board id
  • User IP address
  • User language
  • User browser information (browser, version, locale, operating system, user agent)

Amazon Web Services

SUB-PROCESSOR We use AWS to send email notifications to participants (i.e. about asynchronous session start)

Stored data

  • User display name
  • User email address
  • board id
  • board name

Papertrail

SUB-PROCESSOR We use Heroku addon Papertrail to store application logs. Logs are in the system for 2 days. Log archives are stored from the last 7 days. Papertrail allows us to analyze application's behavior after an incident occurs. 

Stored Data

  • Access log - web addresses accessed by user browser when communicating with Agile Poker add-on. It includes following data:
    • request date
    • IP address
    • issue id
    • timezone
    • location
    • user key and user id
    • URL that the application was run on (includes Jira URL, JQL query, project key, and issue key)
    • user authorization token
    • browser name and version
  • Application logs - internal application messages that don't contain any personal data.


We analyse application logs only to monitor application health and to do post-incident analysis

If you would like us to skip processing logs from your instance, please let us know at support@spartez.com.

Google Analytics

For a better understanding of our clients, we collect anonymous statistics of the plugin usage. These statistics tell us how we should develop our plugin to make our clients happy. 

What is collected

The following table is intended to give you a complete understanding of the policy that we use to collect analytics data.

This table is not intended to list all the possible events collected by the add-on. It is however intended to list all rules and exceptions from those rules so that you are able to asses whether something can be collected or not. 

Data type

Comments

User interface and usage

Displaying and interacting with all components and pages added by Agile Poker including:

  • Agile Poker session dialog
  • changelog dialog
  • relative session page
  • issue selector dialog
  • settings pages

Interacting means clicking on the components or changing their state.

Flags and statistics

We collect boolean flags and statistic numbers from entered data. This applies to data gather via add-on components or pages (including configuration and usage pages). For example:

  • Async session started
  • The timer started/stopped
  • index of selected estimate value (actual value is excluded)
  • If and when user interrupted introduction tour

Flags and statistics do not contain any user-created data.

Context

We collect a few general context values from Jira.

  • license type (evaluation/paid)

Context parameters do not contain any user-created data.

What is not collected

In Google Analytics we do not collect any data but the minimal and anonymous data based on the rules described above. In particular, we do not collect any information about users, issues, values of comments, or any identifiable information about the Jira instance itself.

Disabling Google Analytics

We encourage you to keep Google Analytics enabled. Using anonymous usage statistics we improve Agile Poker for Jira to fit our clients' needs better. If you want to disable Google Analytics despite this fact you can follow instructions on page Configuring Agile Poker for Jira Cloud.


  • No labels