In the situation of Jira Server mode, all data created and used by our plugin are stored in Jira, they are the configuration of our plugin, Working Schedules, Shared Contexts and Personal settings. They are secured directly by the backup services of Jira.
In the configuration of Cluster, all data are synchronized transparently by Jira services
Jira Cloud is the hosting platform designed and used by us to deliver Atlassian applications as a service. Our plugin extends this platform by providing a capability for the project management in this environment. In this environment, each gantt chart uses two kinds of data: Jira Data and
|Nature of Data||Description||Storage|
|Jira Data||The data comes from Jira such as Project, User, Issues, Workflow, Security Scheme, Working log, etc||They are hosted by the Jira Cloud Plafform. They are volatile for our add-on They aren't stored in our Add-on server|
|Add-on Data||The data is nothing with Jira artefacts. In other words, they aren't not used by Jira. They are created and used by our Add-On. The data consists of the configuration of our plugin, Working Schedules, Shared Contexts and Personal settings.||The storage of these data is managed by our Add-on|
Each subscriber's Jira Cloud applications using our plugin are physically located on a server in a dedicated server hosted in Amazon's Elastic Cloud, our data center and hosting provider. This data center provides power, network and backup services. Soyatec owns the servers and is responsible for provisioning, monitoring, and managing the servers, and for providing support to Jira Cloud subscribers.
Access to the data centers is limited to authorized personnel only. Our data center is located in Tokyo, and it can be relocated anywhere. It is possible to extend the capability as needed.
Our global support teams, maintain an account on all hosted systems and applications for the purposes of maintenance and support. This support team accesses hosted applications and data only for purposes of application health monitoring and performing system or application maintenance, and upon customer request via our support system. Within Soyatec, only authorized Soyatec employees have access to application data. Authentication is done via individual passphrase-protected public keys, rather than passwords, and the servers only accept incoming SSH connections from our IP addresses.
Our Add-on respects the JIRA Security Scheme. It allows application data to be accessible only with appropriate credentials, such that one customer cannot access another customer's data. Customers are responsible for maintaining the security of their own login information.
The Soyatec operations team monitors the OnDemand platform 24x7 from operation centers in China and France. The monitoring is activated for our Add-on Servers, some important alarms are created to alert any failure of our server.
In our Add-on server, the backups occur on the following frequencies: On-site backups are performed daily and retained for seven days. The backups file will be kept in two different machines to prevent the lost of data on the failure of hardware.
NOTE: This Security Statement applies to Soyatec's Jira Cloud services. For questions regarding Soyatec's legacy hosted services, please contact us.
Effective as of Avril 12, 2014.