| Table of Contents |
|---|
Introduction
This document sets out our policy for responding to requests for deletion of data. This document explains the rights of the data subject in relation to data deletion and the responsibilities of Release Management Apps (by Y2 ENGR.) in responding with such a request.
Default data retention policy
By default we do not automatically delete client data after
...
In order to permanently delete client data from our hosts a request for data deletion should be created.
What data is stored?
On our hosts we keep mainly “Release Management“ boards and configurations. This includes references (IDs) to some Jira entities and fields, like Project IDs, Version IDs, Issue IDs, Standard & Custom Field IDs, User & GroupIDs, Custom JQLs plus all the client data inserted into free text fields throughout the App.
Where is the data located?
All client data is stored in our documents store - a highly available cluster with 3x replica sets - in 3 locations - 2x Germany and 1x Finland.
...
Please also check our Sub-processors table.
How to request data deletion?
Only authorized people can request data deletion on the client behalf. This could be either the person (email) behind the commercial license issued or the person (email) behind the billing transaction executed.
...
Please also check Section 2.13 of the DPA and also “Duration of processing“ rows in the tables of Exhibit A, Part A and Exhibit A, Part B.
What are the timeframes for data deletion?
Upon confirmation of receiving your request (up to 24 hours) it might take up to 30 days to process your request and confirm that data has been deleted permanently plus sending you a copy if requested.
Can I restore the data after deletion if I changed my mind?
No, this is not supported.
...