Data residency is a tool to comply with data regulation and compliance laws but may also increased the performance of the application. yasoon ensures the data in-scope are stored only within the specified region.
Data stored temporarily (less than 7 days) for caching purposes are considered as data-in-transit and are not part of the data residency concept.
Regions
We currently provide data residency for the following regions
Country | AWS Region |
|---|---|
Germany | eu-central-1 in Frankfurt |
USA SOON | us-east-1 in N. Virgina |
Australia SOON | ap-southeast-2 |
Regional data
The following data are stored within the region
Data | Description |
|---|---|
User data | Ids, name & email adress of users |
User access tokens | Access tokens (Microsoft Graph, Atlassian OAuth1.0a and OAuth 2) |
Jira & Confluence related data | The apps store data related to issues/projects/spaces etc. |
Microsoft Graph related data | The app store data related to Microsoft Graph activities (e.g. status of active subscriptions) |
Settings | Settings created by the admins, e.g. templates, presets |
Automation data | Data related to the automation features |
Audit log | Log of auditable activities |
Non-Regional data
The following data are “stored globally” and are replicated into every region.
Data | Description |
|---|---|
Teams user data | We keep a mapping and user profile (incl. email address) of Microsoft Teams users to region to forward requests into the correct region. |
Instance data | We maintain a list of all customer instances including their Jira URL and their region. Used to identify the correct region for a user during login. |
Teams bot data | Microsoft Teams does not have a data residency concept for bots. We need to store bot installation data globally to forward these requests into the correct region. |