Data Residency

Foxly: Requirements Backlog Prioritization, Planning Poker (App or Foxly) 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 lets you choose a defined geographic location for the end-user data.

The data residency option available for the App serves to:

• Help ensure compliance with local data protection laws.

• Enhance security by storing data within specific jurisdictions.

• Provide users with greater control over their personal information, fostering trust and reducing

  legal risks.

Available data residency options for Foxly

You can choose to store Foxly in-scope end-user data in one of the listed regions, available from AWS’s data centers:

• US: us-east-2 (Ohio)

• EU: eu-central-1 (Frankfurt)

• DE: eu-central-1 (Frankfurt)

• AU: ap-southeast-2 (Sydney)

• CA: ca-central-1 (Montreal)

Moving data between regions

Foxly data storage and processing automatically follow 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 Foxly, your app data is stored and processed in the same region, provided Foxly supports it (see Available Data residency options for Foxly, above).

  • If Foxly doesn't support your Jira instance's chosen region, your data is stored in the U.S. (us-east-2, Ohio, United States).

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

  • The location depends on your Jira instance location. Typically, Atlassian creates your Jira instance in a region close to your location. If Foxly also supports that region, it will be used. 

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