Page Comparison

All

Creating a ticket in our service portal

All data which you provide to us during the service case (your name, email address, descriptions, attachments etc.).

In order to process your service case we need some details (e.g. your contact data, the Confluence version you are using, the data of the page causing the problem etc.). Remark: the data is only visible to you and us.

We keep the details for 12 months after the ticket has been closed. This enables us to re-open the ticket in case the problem shows up again.

Atlassian

All

Contacting us via email

All data which you provide to us via email (your name, email address, descriptions, attachments etc.).

In order to process your service case we need some details (e.g. your contact data, the Confluence version you are using, the data of the page causing the problem etc.). Remark: The data is only visible to you and us.

We keep the details for 12 months after the problem has been solved. This enables us to get back to you quickly in case the problem shows up again.

GMail

All

Creating a ticket directly in the Bitbucket repository

All data which you provide to us during the service case (your name, email address, descriptions, attachments etc.).

In order to process your service case we need some details (e.g. your contact data, the Confluence version you are using, the data of the page causing the problem etc.). Additionally other users need to know which bugs have been existing in which version of the software. Remark: this data is visible to all users!

We do not delete created bug reports or feature requests. They are kept for an unlimited time due to the reasons mentioned.

Atlassian

All cloudapps

Installation of cloud apps

The data needed to communicate with your Atlassian Cloud account. This includes e.g. AddOnKey, ProductType, ClientKey, BaseUrl, ServiceEntitlementNumber, SharedSecret, OauthClientId.

We need this data to connect our apps with Confluence cloud. Our apps are not functioning without those data.

In case you terminate the service your data will be deleted latest after 12 months.

Heroku, AWS, Logentries

All cloud apps

Usage of cloud apps

The request URL used by Atlassian to trigger our apps is stored in our logs. The request URL contains information like IP address, BaseUrl, user name, page ID etc.

We need those logging data to analyze problems and react on them properly in a timely manner.

Logging data are kept of 7 calendar days and are automatically deleted after that.

Logentries, AWS

Simple Cite Server (prior to version 1.15.0)

Using the BibTeX function of Simple Cite

The commercial versions of Simple Cite uses our cloud service to render BibTeX cites. Our logs collect information like IP address, BibTeX entry to render, the requested format etc.

We need those logging data to analyze problems and react on them properly in a timely manner.

Logging data are kept of 7 calendar days and are automatically deleted after that.

Logentries

SVG Out Server

Using our cloud based PhantomJS service for SVG to PNG conversion in SVG Out.

As indicated here you may use our PhantomJS based service as an alternative to the embedded Batik transcoder. In case you do so our logs will contain information like your IP address.

We need those logging data to analyze problems and react on them properly in a timely manner.

Logging data are kept of 7 calendar days and are automatically deleted after that.

Logentries

Smart Questions and Answers Cloud and Tree View Cloud

Access to email addresses

N/A

Remark: We are NOT storing email addresses. We only access them in case a notification should be send to the user via email.

N/A

N/A

N/A

Smart Questions and Answers Cloud

Access data to Slack

Access data to Slack (if used)

As a consequence of complying with Slack’s app approval criteria we need to store a copy of the access data to Slack. This is needed as Smart Questions and Answers must send a welcome message once a user opens the app’s tab.

Unlimited

AWS