This article provides more detailed information about the data that is stored in our database.
In general, we don’t store actual content from your system(s), but only metadata, settings, etc.


To associate the different entities (like issues & chats) with one another, we store certain kinds of metadata - mostly mappings between two kinds of entities. A few examples include the following - in case you are interested in a full list, please reach out.

Example #1 - User mapping

When you login with Jira & Microsoft Teams in our app, we’ll associate the two accounts with each other. This is necessary, so we can impersonate you correctly, e.g. when posting a reply in a Teams chat from your Jira issue or when creating a Jira issue from Microsoft Teams. An example dataset may look like this:

Jira instance

Jira user

Microsoft instance

Microsoft user




Example #2 - Issue / chat mapping

When you create a new chat from Jira, the chat will show up in the issue. To make this work, we store a link between these two entities, which looks like this:

Jira instance

Jira issue

Jira user

Teams chat id




This is not an exhaustive or complete list, but metadata means, no actual PII or OII content is stored, just identifiers.

User, project & instance settings

When a user or an administrator changes a setting (e.g. appearance of the app), we persist this choice in our database as well. This may look like this:

Jira instance

Setting name

Setting value


{"viewLocation": "issueContent", "quickCreateEnabled": false}

Access tokens or similar

To be able to bi-directionally access Jira & Microsoft Teams, we store access tokens in our database. These tokens are encrypted at rest and additionally, at application level. Our employees have at no time access to either your Jira or Microsoft Teams content, and every access to the secret storage is only allowed for certain core employees and fully logged and monitored. Please also refer to our Security & Privacy docs.