Effective date:  

Please also check our general Privacy Policy, which applies to all aspects of our processing of personal data.

This End User Privacy Policy describes how Stiltsoft Europe OÜ (“Stiltsoft”, “we”, “our” or “us”) or Handy Macros for Confluence Cloud collect, store, or otherwise process End User Data.

Your privacy is important to us, and we are strongly committed to making our practices regarding your personal data more transparent and fairer. Please read this Privacy Policy carefully and make sure that you fully understand and agree to it.

This Privacy Policy for our Product forms a part of our End User License Agreement and our general Privacy Policy.

Definitions

App means our Handy Macros app for Confluence (Cloud) application.

Service Provider or Subprocessor means a third-party whose services we use in connection with the App.

End User Data means any data, content, or information of an End User that is accessed, collected or otherwise processed by us or the App in connection with use of the Atlassian Marketplace. 

End User, “you”, or “yours" means an Atlassian and our customer who holds a subscription to Atlassian Confluence (Cloud) and to the App.

AWS RDS means Amazon Relational Database Service.

Data Collection

We collect the following categories of data:

Technical data. When you use theApp, we may collect certain technical data about your interaction with the App. We do so either directly, or with the help of Service Providers, including by using “cookies” and other tracking technologies.

Such data includes, in particular:

  • URL address of your Confluence Cloud instance
  • App logs
  • error and issue logs

Operational data. By using the App you manage macros on Confluence pages. Identifiers of macros are saved on the page, while the macros content is stored in the encrypted form in the AWS RDS database.The following information about macros is saved to the App’s database:

In relation to Handy Status and Handy Page Status macros:

  • status set name
  • status set description
  • status name
  • text color (HEX code)
  • status background color (HEX code)
  • position in the status set

In relation to Handy Poll macro:

  • Confluence page id
  • account id of the poll creator
  • id of polls variants

The parameters of Handy Date macro are saved within the page markup. Some parameters of Handy Status and Handy Poll macros are also saved within the page markup.


Data from Analytics Tools. We use certain analytics tools (Google Analytics) to collect data about the use and activities in our Product. Analytics tools collect data such as how often Users are using our macros, how they configure them, and so on.

In addition to action data, we track some additional anonymized data about you and your Confluence Cloud instance, as follows:

  • Client key - unique anonymized identifier of Confluence Cloud instance.
  • Account ID - unique anonymized identifier or a Confluence user.
  • App License Type - license type of our Product.
  • Options count - number of statuses in the set or variants in the poll.
  • Status id
  • Status set id
  • Colors of the status background and title
  • Macro id
  • Confluence page id
  • Poll type - single or multiple choice.

Technical data, operational data, and data from analytics tools do not include any personal data.

Personal Data. When you start a subscription (either trial or paid), Atlassian makes accessible to us names and email addresses of your billing and technical contacts. If you contact us with support inquiries, you will share the contact details of your representative making the inquiry and the specifics of the issue encountered.

For more details on how we handle personal data, please refer to our general Privacy Policy.

End User Data Use

We use End User  Data for the following internal purposes:

Personal data is used to provide you with support services in relation to the Apps and for limited marketing purposes in compliance with applicable laws. For more details on how we use personal data, please refer to our general Privacy Policy.

Technical data is used for identifying and addressing the probable operational and performance issues within the App.

Data from Analytics data is used for identifying the frequently used features and pinpointing areas for improvement and optimization. This helps us gain a better understanding on how the App is evaluated, used, and interacted with. Ultimately, our goal is to enhance overall user experience and continually improve the App.

Operational data is used strictly for service provision within the App.

We do not sell End User Data. All the collected data is used only for internal purposes (operation and development of the product).

End User Data Retention

End User Data collected by us is stored as follows:

Personal Data: Personal data is stored in the Atlassian Marketplace. When we store such data, it is done in encrypted form within AWS RDS.

Technical data, including operational logs, is stored in encrypted form within AWS RDS.

Data from Analytics Tools is stored in Google Analytics. The retention period for such data is determined by Google. Please refer to Google data retention policy for more details.

Operational data related to macros is stored in encrypted form within AWS RDS. The App accesses this data when you use the App.

Please refer to our Data Retention Policy for further information on this matter.

Third-Party Subprocessors and Data They Collect

Subprocessor

Purpose

Data collected

Location

Amazon

Data hosting

-

USA East (Northern Virginia) region (us-east-1)

Google Analytics

Web analytics service

Anonymous information about certain interactions with the App.

By using Google Analytics we track only information that pertains to the App (such as the event of status change) and how often our macros are used, how they are configured, etc.

For example, we collect the following information:

  • App License Type - license type of the App.
  • Options count - the number of statuses in the set or variants in the poll.
  • Status id
  • Status set id
  • Colors of the status background and title
  • Macro id
  • Confluence page id
  • Poll type - single or multiple choice.

Learn more about how the data is collected and processed by Google.

USA

Sentry

An error monitoring tool

Sentry.io collects and stores the following data to help us discover, triage, and prioritize the App’s errors in real-time:

  • Information about the page on which the error occurred (the page URL (including query parameters, description of the user’s actions on the page that preceded the error (places the user clicked, URLs of requests initiated from the page), and stack trace)
  • Information about the user’s environment (IP address, browser type and version, and operating system type and version).

USA

Mailchimp

Transactional and broadcast emails

Business contact information (billing and technical contacts) from the Marketplace account.

Learn more about the Mailchimp Security and Privacy Policy.

USA

Datadog

Application monitoring and security

Datadog allows monitoring, troubleshooting, and optimizing application performance.

USA


Cookies and Tracking Technologies

We and our Service Providers use cookies and other technologies for performance, tracking, and analytics purposes.

The App utilizes “cookies”, including third-party cookies, and anonymous identifiers in order for us to provide the services  and ensure that it performs properly and to analyze our performance activities. Such cookies and similar files or tags may also be temporarily placed on your device.

Please note that we do not change our practices in response to a “Do Not Track” signal in the HTTP header from a browser or mobile application, however, most browsers allow you to control cookies, including whether or not to accept them and how to remove them. You may set most browsers to notify you if you receive a cookie, or to block or remove cookies altogether.

Data Security

Please refer to the App’s “Security” page and to the “Privacy and Security” tab of the App’s page on Atlassian Marketplace for all details on the End User Data security.

Disclosure

The End User Data may be available to our Service Providers as outlined in Section “Third-Party Subprocessors and Data They Collect” above.

We may disclose End User Data  if we have to comply with subpoenas or court orders.

With whom we may share personal data is described in our general Privacy Policy.

Changes

We may update this Policy from time to time. We will notify you about material changes.

End User Data Related Questions

If you have any questions regarding this Policy, please address them to our support.