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 acitivities |
Non-Regional data
The following data are “stored globally” and are replicated into every region.
Data | Description |
|---|---|
Instance data | We maintain a list of all customer instances including their baseUrl and their region. |
Teams Bot data | MIcrosoft Teams does not have a data residency concept for Bots. We need to forward these requests into the correct region. |
Teams User data | Same as above, we keep a mapping of Team User Ids to region to forward requests into the correct region. |