Data residency refers to the geographic location where your Agile Poker data is stored and processed. This is important for several reasons, including:
Security: Understanding where your data resides helps assess security risks and controls.
Performance: Data stored closer to your users can improve app responsiveness (latency).
Legal compliance: Certain regulations, like the European General Data Protection Regulation (GDPR), require strict controls over how personal data is handled. While GDPR doesn't mandate specific data locations, some regions may be unsuitable due to local data surveillance laws, making the choice of storage location important for compliance.
Available data residency options
Agile Poker for Jira Cloud is served from the following data centers in the Google Cloud Platform:
europe-west1 (Belgium)
us-central1 (Iowa, United States)
asia-southeast1 (Singapore)
You can choose to store Agile Poker data in one of these regions or leave the decision to Atlassian (the so-called Global region, which is usually the USA).
Moving data between regions
Agile Poker data storage and processing automatically follows Jira’s region settings, which are managed by Atlassian or your organization. Here’s how it works:
If your Jira instance is pinned to a region:
When you install Agile Poker for Jira Cloud, your app data will be stored and processed in the same region, provided Agile Poker supports it.
If your Jira instance's chosen region isn't supported by Agile Poker, or if Atlassian hasn't set up the instance in that region, your data will be stored in the Global region.
If your Jira instance isn't pinned to a region: Atlassian will default your Jira instance and Agile Poker data to the Global region unless you pin Jira to a supported location.
Agile Poker data does not automatically move if you change your Jira instance’s region. For example, if your Jira instance is pinned to Belgium and you later move it to Singapore, Agile Poker data will remain in Belgium.
Once your Jira has moved to a new location, you can request to move Agile Poker’s eligible app data to the same product location. For more information, refer to Atlassian's data residency move guide.
We fully support error handling and rollback during migration to ensure no data is lost. If you require any assistance, do not hesitate to contact our Support team.
In-scope product data
When you select a data residency region for Agile Poker, the following types of data are stored and processed only in that region:
Project IDs
Issue IDs
Agile Poker session names
Comments sent during Asynchronous sessions
Email invitations and Slack messages created while configuring a session