Data residency

OKR for Jira (App or OKR for Jira) supports data residency options, giving you control over where in-scope end-user data is hosted and processed. This lets you follow Jira’s geographic location for your data, aligning with your organization’s compliance and security requirements.

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.

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

Available data residency options for OKR for Jira

The OKR for Jira in-scope end-user data can be stored in one of the listed regions, available from the Google Cloud Platform’s data centers:

• US: South Carolina (us-east1)

• EU: Frankfurt (europe-west3)

• AU: Sydney (australia-southeast1)

• CA: Montreal (northamerica-northeast1)

Moving data between regions

We don’t support data migration from one realm to another. In case of further questions, please contact our support.

In-scope end-user data

App stores the following types of in-scope end-user data:

• Client’s instance IDs (client keys) and URLs

• OKR data, including key, summary, description, OKR type name, periods with names, team names, and label names

• Jira Issue data, including ID, key, summary, icon URL, status name, and status category

• OKR updates with comments

• Generated API tokens

• Jira user account IDs

• Jira group IDs

• Jira shared secrets

• Custom permission roles, including role name

• Data used for import, including CSV file names

• Email data sent to the user, including title and body

• Saved filter data, including custom name

Out-of-scope product data

The following data may be processed outside of the region OKR for Jira is pinned to:

• Amplitude, including instance URL, Jira user account ID, and more

• Pendo, including instance URL, Jira user account ID, Jira user display name, application key, and more

• Hotjar, including a payload of actions triggered in the application and more

• Intercom, including instance URL, Jira user account ID, and more

• Google Cloud Platform Logs, including instance URL, instance ID, shared secrets, and more