Data Policy
This page is about Canned Responses Pro Templates for Jira Server/Data Center. Using Cloud? Click here.
We take data security very seriously. In Canned Responses Pro for Jira, all data are stored in the clients' Jira database, and we don't store any data on Appfire infrastructure. If you think something on this page is missing or you have any security-related questions, please let us know at the Appfire Support Portal or support@appfire.com.
Google Analytics
To understand our clients' needs better, we collect anonymous statistics on add-on usage. If for any reason you don't want to share usage statistics, you may disable them in the addon settings.
P.S. We do not recommend disabling Google Analytics as it helps us make better decisions, resulting in a product that is better adjusted to users' needs.
What is collected:
The following table is intended to give you a complete understanding of the policy that we use to collect analytics data.
This table is not intended to list all the possible events collected by the add-on. It is, however, intended to list all rules and exceptions from those rules so that you are able to assess whether something can be collected or not.
Data type | Comments |
---|---|
User interface and usage | Displaying and interacting with all components and pages added by Canned Responses, including:
Interacting means clicking on the components or changing their state. |
Flags and statistics | We collect boolean flags and statistic numbers from the entered data. This applies to data gathered via add-on components or pages (including configuration and usage pages). For example:
Flags and statistics do not contain any user-created data. |
Context | We collect a few general context values from Jira.
Context parameters do not contain any user-created data. |
What is not collected:
We do not collect any data other than the minimal and anonymous data listed above. In particular, we do not collect any information about users, issues, the value of the user estimates, or any identifiable information about the Jira instance itself.