| 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.
PROCESSOR - providers with this label are our data processors as defined by European General Data Protection Regulation (GDPR).
Spartez Software is the data controller, as defined in GDPR.
Spartez Software as the data controller and data processors guarantee that all servers used for data processing are located in the European Union.
Service Providers
| Table of Contents | ||
|---|---|---|
|
Google Cloud Platform
PROCESSOR
Cloud SQL
Cloud SQL stores data provided during the installation handshake. Stored keys authenticate us to clients' Jira instances. We store
- A key that identifies Jira instance.
- Shared secrets for communication with Jira.
Cloud SQL also stores configuration data for synchronization profiles:
...
- Pairs of Jira ids and Azure DevOps ids for
- Issues / work items
- Comments
- Attachments
- Links
- Customer - facing errors that occurred during synchronization
- High-level aggregated data for initial synchronizations, like date started and number of items processed
Google Cloud's operations suite
...
| Info | ||
|---|---|---|
| ||
Synchronizer does not add any UGC to logs during normal operation, however, we reserve the right to log such data when errors occur and to temporarily extend logging with such data when it is necessary to troubleshoot an incident. |
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 contain any personally identifiable information, nor any but may contain user-generated content. This data is used to gain insights into user needs and improve application experience. |
Cloud storage
Cloud storage stores backups of data held in Datastore and Cloud SQL.
Retention period is 7 days.
Amazon Web Services
PROCESSOR
Simple Storage Service (S3)
...
Retention period is 30 days.
Relational Database Service (RDS)
RDS stores data provided during the installation handshake. Stored keys authenticate us to clients' Jira instances.
Stored Data
...