Page Comparison

Agile Poker for Jira – Planning & Estimation (“App”or “App” or “Agile Poker”) offers data residency options. Data residency gives you control over where your in-scope Endend-User Data user data processed by the App is hosted. In other words, it allows you to choose a defined geographic location for the Endend-User Datauser data.

The data residency option available for the App serves to, in particular:

...

You can choose to store Agile Poker in-scope Endend-User Data user data in one of the listed regions, available from the Google Cloud Platform’s data centers:

...

• If your Jira instance is pinned to a region:

  • When you install Agile Poker, your app data will be stored and processed in the same region, provided Agile Poker supports it (please, see Available Data residency options for Agile Poker, above),

  • If your Jira instance's chosen region isn't supported by Agile Poker, your data will be stored in the U.S. (us-central1, Iowa, United States).

• If your Jira instance isn't pinned to a region:

  • The location will depend on your Jira instance location. Typically, Atlassian will create your Jira instance in a region close to your location. If Agile Poker also supports that region, it will be used (please, see Available Data residency options for Agile Poker, above). 

• For users whose Jira instances had been created before a data residency feature for Agile Poker was introduced, the instance location will remain unspecified. In this case, Agile Poker data will be stored in the U.S. (us-central1, Iowa, United States).

...

• Project IDs

• Issue IDs

• Agile Poker session names

• Comments sent during Asynchronous sessions

• Email invitations IDs and Slack messages IDs created while configuring a session

• A key that identifies Jira instance

• Jira client key

• Board ID to associate session data

• Account IDs of users using the app

• IDs of issues

• Estimation comments

...