Data residency

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. By default, Atlassian hosts all products in the Global location. For these products, Atlassian determines where their in-scope data is located. To optimize product performance, Atlassian doesn’t limit data movement for these products and moves data between regions as needed.

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, your data will be stored in the Global region.

• 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 supports that region, it will be used. However, for users whose Jira instances were created before Atlassian introduced data residency, the instance location will remain unspecified. In this case, Agile Poker data will be stored in the Global region.

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.

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

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.