Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

Scope

Protecting your data and privacy is an important goal for us. This policy explains which data we are collecting, why we are collecting it, how long it will be stored and how can influence it. Please feel free to contact us in case you have any questions.

This policy is intended to precise the Atlassian's privacy policy which you read and accepted when downloading or installing a plug-in.

Who we are - data controller

Whenever we are using "we" or "us" we mean:

Purde Software
Max-Friedlaender-Bogen 17
80339 München
Germany

Why do we collect data at all?

Collecting a certain amount of data is necessary to offer a good service for you. Please refer to the table below to see which data we are collecting in which use case and why. In some cases we are not alone but use service provides. Those service providers have their own privacy policy - we provide links to those policies further below in this document.

The data we are collecting

Affected plug-ins

Use case

Data collected

Reasons for data collection

Retention period

Involved third parties

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 6 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 6 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 know which bugs have been existing in which version of the software. Remark: this data is visible to all users!

Please use the service portal in case you are worried about the mentioned facts.


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

Please use the service portal in case you are worried about the mentioned facts.


Atlassian

All cloud plug-ins

Installation of cloud plugins

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 plug-ins with Confluence cloud. Our plug-ins 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 plug-ins

Usage of cloud plugins

The request URL used by Atlassian to trigger our plug-ins 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

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

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

Do we give your data away?

Apart from the mentioned involved third parties nobody else has access to the data. We do not give your data away.

Involved third parties policies

In the listing below you see the involved third party policies and in brackets the location of their service.

Can I influence the data storage?

You may request us to delete certain data earlier than the planned retention period as shown above. Just raise a ticket our email us. Please consider that we need some data to service you.

Can I see my data stored?

Yes, you can. Just raise a ticket our email us.

Can I raise a complaint?

Yes, you can. Just raise a ticket our email us. In addition you also have the right to lodge a complaint with a supervisory authority.

  • No labels