Difference between revisions of "SAR Wire 20180427 (Q4877)"

From Wikibase Personal data
Jump to navigation Jump to search
 
(2 intermediate revisions by the same user not shown)
Property / significant event
 +
Property / significant event: subject access response / rank
 +
Normal rank
Property / significant event: subject access response / qualifier
 +
Property / significant event: subject access response / qualifier
 +
date: 8 May 2018
Timestamp+2018-05-08T00:00:00Z
Timezone+00:00
CalendarGregorian
Precision1 day
Before0
After0
Property / significant event: subject access response / qualifier
 +
comment: Responded with the answers about the questions posed by the user about the various categories of data.
Property / significant event
 +
Property / significant event: subject access request closure / rank
 +
Normal rank
Property / significant event: subject access request closure / qualifier
 +
Property / significant event: subject access request closure / qualifier
 +
date: 16 May 2018
Timestamp+2018-05-16T00:00:00Z
Timezone+00:00
CalendarGregorian
Precision1 day
Before0
After0
Property / significant event: subject access request closure / qualifier
 +
Property / significant event: subject access request closure / qualifier
 +
comment: Seeing no response from the user, the organisation closed the ticket for the access request.
Property / final SAR status
 +
Property / final SAR status: provide information / rank
 +
Normal rank
Property / final SAR status: provide information / qualifier
 +
Property / final SAR status: provide information / qualifier
 +
comment: Provided information about GDPR effectuation date; referred to check the application for the personal data; informed about the possibility of a download tool; about data storage and data management.

Latest revision as of 12:35, 23 July 2020

No description defined
Language Label Description Also known as
English
SAR Wire 20180427
No description defined

    Statements

    0 references
    0 references
    27 April 2018
    Subject access request was sent via letter as well.
    0 references
    2 May 2018
    Acknowledged the request and sent a One Time Password on the user's contact number to confirm the account details.
    0 references
    2 May 2018
    User replied to the mail with the one time password
    0 references
    8 May 2018
    Responded with the answers about the questions posed by the user about the various categories of data.
    0 references
    16 May 2018
    Seeing no response from the user, the organisation closed the ticket for the access request.
    0 references
    Provided information about GDPR effectuation date; referred to check the application for the personal data; informed about the possibility of a download tool; about data storage and data management.
    0 references