Versions Compared

Old Version 14

changes.mady.by.user spg bot

Saved on

compared with

New Version 15

changes.mady.by.user spg bot

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info
titleCloud 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.

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
minLevel2

Google Cloud Platform

SUB-PROCESSOR 

Cloud SQL

Cloud SQL stores configuration data for synchronization profiles:

...

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. 

Info
titlePersonally identifiable information and user generated content in logs

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.
Please note that external systems, including Jira and Azure can unintentionally return data, containing PII or UGC, as a part of an error message. 
In such cases, Synchronizer will log this data "as is", without making any attempt to discover or remove sensitive data.
These logs will be retained for 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 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 stores backups of data held in Datastore and Cloud SQL.

Amazon Web Services

SUB-PROCESSOR 

Simple Storage Service (S3)

...