Skip to end of metadata
Go to start of metadata

The following Privacy Policy was updated on 6/August/2020 and takes effect on 7/September/2020.

If you want to see the Privacy Policy that applies before this date (prior to 7/September/2020), please click here.


Our clients' privacy is important to us, and we strive to maintain a secure environment.

Except where explicitly stated, user data collection is limited to only the necessities for our applications to function correctly.

User data will never be sold or shared outside of Automation Consultants Ltd.


Automation Consultants may send manual and automatic marketing emails to the 'Technical Contact' and 'Billing Contact' as provided by the Atlassian Marketplace.

In order to provide these marketing communications, we use third-party providers SendGrid, Hubspot and SendInBlue

Examples of the content that may be sent are as follows:

  • Onboarding information to help you get up and running with the software
  • Information on upcoming improvements or features
  • App Updates and other product updates
  • Security Notifications
  • Service Announcements
  • Updates to our EULA, Privacy Policy, or other legal documents

Any communication with us through this manner will have an unsubscribe link that will prevent future communication with the address specified. 

Web Analytics

When accessing websites that contain content relating to Automation Consultants products, there may be analytics tags which allow us to track the effectiveness of our content.

This is facilitated by third-party services such as Google Analytics.

Some examples of this are as follows:

In-App Analytics

We use In-App Analytics in a number of our Apps to help us understand areas for improvement.

We do not use analytics in any of our On-Premise Apps (Server and Data Center versions).

For further clarity, please see the table below:

AppIn-App Analytics
Approvals for Confluence Cloud(tick)
Approvals for Confluence Server/Data Center(error)
Approvals for Trello(tick)
Compliance for Confluence Cloud(tick)
Compliance for Confluence Server/Data Center(error)
Hierarchy for Trello(tick)
Issue Charts for Jira(tick)
Matrix for Trello(tick)
Optimizer for Jira Cloud(tick)
Optimizer for Jira Server/Data Center(error)
Pulse for Jira Cloud(tick)
View Tracker for Trello(tick)

An example of the analytics data that is captured by our Cloud Apps is as follows:

  • Action
    • Action Type - what action was performed - e.g. a card is dropped on the Matrix
  • User
    • Location - this is derived from the IP address where the hit originated. The IP address itself is not available in GA as it is considered PII.
    • Language - derived from the language settings of the browser
  • Browser
    • Browser name - the browser the user is using
    • Viewport or Viewing pane - the size of the browser window
    • Screen resolution - the resolution of the user's screen


  • Our analytics products (Pulse for Jira and View Tracker for Trello) store the data required for us to provide the service requested
    • Action Types and Object Identifiers are used to provide these services.
    • PII such as object names, card names etc. are not stored, only their identifiers.

In-App Emails

A number of our Apps provide email communication for events that occur inside of the App, or the containing Application.

An example of this is when a user's approval is requested in Approvals for Confluence - depending on the options selected, the individual will be notified that there is a pending approval.

This section only applies to Cloud Apps, as On-Premise applications operate independently from our infrastructure.

AppIn-App Emails
Approvals for Confluence Cloud(tick)
Workflows for Confluence Cloud(tick)

These Apps do not store email addresses and the relevant addresses are accessed as required, following the permission model laid out by Atlassian.

  • No labels