3 ms·
Hmmm. I see your point. I don't know if Heroku is the data processor or controller in this case, but I think it's the data processor. Let's suppose the ex-clie
by eesmith 7y ago
Hmmm. I see your point.
I don't know if Heroku is the data processor or controller in this case, but I think it's the data processor. Let's suppose the ex-client is the data controller. The first thing is to tell the ex-client to change the settings, which doesn't seem to have been the case here.
If the ex-client does not change the settings (eg, perhaps from incompetence), and Heroku know about the issue, then are they obligated as a data processor to inform the ex-client that there is an GDPR violation? That's my reading of the last part of 28.3 GDPR.
And if that violation continues? ... I have no clue.
No idea either of if this relationship is covered under GDPR.