Skip to end of banner
Go to start of banner

Data Policy for Cloud Native Synchronizer

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Cloud Native Synchronizer

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.

Service Providers

Google Cloud Platform

Cloud SQL

Cloud SQL stores configuration data for synchronization profiles:

  • Urls to Jira and Azure DevOps
  • Username and personal access token for synchronizer user, encrypted using Cloud Key Management
  • Value mappings
  • Issue type mappings, workflow / status mappings, etc.

Datastore

Datastore stores operational data, that is generated once a synchronization profile is enabled:

  • Pairs of Jira ids and Azure DevOps ids for
    • Issues / work items
    • Comments
    • Attachments
  • Customer - facing errors that occurred during synchronization

Google Cloud's operations suite

We store application and platform logs to troubleshoot and analyze incidents.

These logs do not contain any personally identifiable information, nor any user generated content. 

Logs might contain:

  • Jira client key
  • Jira issue ids or Azure DevOps work item ids
  • user ids
  • internal application messages

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.

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 typeComments
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:

  • Amount of issues / work items synchronized per day
  • Amount of initial synchronizations run per day

User interface

and usage

We track the usage of certain features in Jira plugin page, as well as in Synchronizer user interface. For example:

  • Clicks on "Learn more" about Hierarchy support
  • Clicks on "Vote up" on Links feature

These events do not contain any personally identifiable information, nor any user generated content. 

Cloud storage

Cloud storage stores backups of data held in Datastore and Cloud SQL.

Amazon Web Services

Simple Storage Service (S3)

S3 stores backups of data stored in Google Cloud storage.

Retention period is 30 days. 


  • No labels