Stephanie_Fong | 2020-07-11 02:46:00 UTC | #1
When I submit new GDPR delete request for any numbers with area code "808", they return 400 error immediately: { "message": "Request subject is invalid: Invalid entry in phoneNumbers (+1808xxxxxxx)", "code": "bad.request", "status": 400, "messageParams": {}, "contextId": "ff13c1f6-2286-4ca8-8e5b-315337724eba", "details": [], "errors": [] } Requests for all other area codes work fine.
Another issue -- there's a significant delay in when GDPR delete requests are performed. For example, if a customer calls in at 12pm with number "+11234567890". And I submit a GDPR delete request for the number "+11234567890" at 12:05pm. If this same number calls back any time from 12:05pm until about 5pm, the interaction data for all those calls will have the phone number deleted.
Is there a consistent delay time period we can expect with GDPR delete requests?? We pull Interaction data from Genesys nightly, if there's an uncertain delay, there could be a non-negligible amount of call data in which phone numbers would be missing from.
anon11147534 | 2020-07-14 13:27:44 UTC | #2
Regarding the error for "808" area codes, please open a case with Genesys Cloud Care as that doesn't appear to be normal behavior.
Regarding the delay issue, from this article on Genesys Cloud GDPR Compliance:
The typical response time for PureCloud to retrieve all personal data in response to an access or portability request is 1-2 days. Regarding a removal or “forget me” request under the GDPR, PureCloud will need no longer than 14 days to remove personal data or make it anonymous upon request.
system | 2020-08-14 13:27:49 UTC | #3
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 8260