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).
...
Agile Poker for Jira – Planning & Estimation (“App” or “Agile Poker”) offers data residency options. Data residency gives you control over where your in-scope end-user data processed by the App is hosted. In other words, it allows you to choose a defined geographic location for the end-user data.
The data residency option available for the App serves to, in particular:
help you ensure compliance with local data protection laws,
enhance security by storing data within specific jurisdictions, and,
provide users with greater control over their personal information, fostering trust and reducing
legal risks.
Available data residency options for Agile Poker
Agile Poker for Jira Cloud is served from the following data centers in the Google Cloud PlatformYou can choose to store Agile Poker in-scope end-user data in one of the listed regions, available from the Google Cloud Platform’s data centers:
europe-west1 (Belgium)
us-central1 (Iowa, United States)
asia-southeast1 (Singapore)
...
Please note: if you do not choose a region individually, the in-scope End-User Data will be stored in the U.S. (us-central1, Iowa, United States) by default.
Moving data between regions
...
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 .(please, see Available Data residency options for Agile Poker, above),
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 regionU.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).
Note: Agile Poker in-scope end-user data do 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(if available; see Available Data residency options for Agile Poker, above).
| Tip |
|---|
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
...
end-user data
App stores the following types of data are stored and processed only in that regionin-scope end-user data:
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
Out-of-scope product data
The following data may be processed outside of the region Agile Poker is pinned to:
Data residency migration information: Data like instance IDs and details of region changes.
External integrations: Information related to Slack messages created by Appfire Poker integration or Appfire Jira Service Desk requests may be stored in external apps.
Analytics data:
Amplitude (back-end and front-end): Includes instance ID, user ID, license information, session-specific details like estimation values, participant roles, and session settings.
Pendo: Includes user ID, board ID, Jira instance URL, game session configurations, and more.
Bugsnag: Includes application stack traces, issue IDs, and user IDs.
LogRocket: Includes license information, user “digital fingerprint,” and internal app paths.
Google Cloud Platform Logs: Includes instance and board IDs, Jira field names, migration IDs, and Slack-related data.