Info | ||
---|---|---|
| ||
This part of the documentation relates to Cloud Native Synchronizer. If you use Jira Server and Azure DevOps Server / TFS go to Data Policy for On premises Synchronizer |
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 how we secure our clients' data. If you think something is missing or you have any security related questions please let us know at Spartez Software Support Portal or support@spartez-software.com.
SUB-PROCESSOR - providers with this label are our data sub-processors as defined by European General Data Protection Regulation (GDPR)
Service Providers
Table of Contents | |
---|---|
|
...
|
Google Cloud Platform
SUB-PROCESSOR
Cloud SQL
Cloud SQL stores configuration data for synchronization profiles:
...
Retention period is 30 days.
BigQuery
For a better understanding of our clients, we collect various statistics. These statistics tell us how we should develop our product to make our clients happy.
What is collected
The following table is intended to give you a complete understanding of the policy that we use to collect analytics data.
...
Data type | Comments |
---|---|
Operational metrics | Operational metrics are not anonymized and are correlated with the customer's tenant key in Jira. This is required for operational purposes, so that we can identify and attribute a portion of cloud hosting and processing costs to a specific customer. These metrics do not contain any personally identifiable information, nor any user generated content. For example:
|
User interface and usage | We track the usage of certain features in Jira plugin page, as well as in Synchronizer user interface. For example:
These events do not contain any personally identifiable information, nor any user generated content. |
...
Cloud storage stores backups of data held in Datastore and Cloud SQL.
Amazon Web Services
SUB-PROCESSOR
Simple Storage Service (S3)
...