We take data security very seriously, so we use only trusted service providers with the highest security standards. On this page, you will find details on what data we store, where we store it, and how we secure it. If you think something is missing or you have any security-related questions, please let us know at Appfire Support Portal or support@appfire.com.
Service Providers
| Status | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
| Status | ||||
|---|---|---|---|---|
|
...
The region is chosen automatically for each user based on their location (the nearest server will handle the request). Except for logs (see below), we do not store any other data in those GCP regions directly.
Logging
Besides the application itself, GCP stores server logs that contain the following information:
...
These logs are purged after 30 days.
| Anchor | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
...
The database is backed up daily and weekly, and up to eight previous backups are stored.
Stored Data
Shared secrets for communication with Jira
Key that identifies Jira instance
App license information
Template name and content
Template creator's account ID
Templates scopes including project ids and user account ID
Template creation and update time
Template action configuration
Template usage statistics
Scheduled comments
We store the minimal amount of data needed to provide our service.
We don't store issue summaries, descriptions, comments, or other sensitive information. We don't store full usernames or emails, but we use user account IDs and project IDs provided by Jira instead.
| Anchor | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
Stored data
Jira tenant key
Jira issue ID
User IP address
User language
User browser information (browser, version, locale, operating system, user agent)
| Anchor | ||||
|---|---|---|---|---|
|
To better understand the interactions of our customers with the app, we collect anonymous statistics on the app usage. These statistics help us define the future direction of app development.
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 app. Instead, it is intended to list all rules and exceptions from those rules so that you are able to assess whether something may be collected or not.
What is not collected
We do not collect any personal data. In particular, we do not collect any information about Jira users, issues, values of comments, or any identifiable information about the Jira instance itself.
...