|
|
|
|
|
by kenbaylor
3015 days ago
|
|
The reason why this is such a great letter is because it questions the competence of the recipient DPO. The data subject has a right to some of the information, but by no means all of it. If the DPO complies with all of it, they will breach the GDPR (e.g. Request 9b). Of course a data subject also has no right to know what security controls (request 8) you have in place, other than they are 'commercially reasonable'. A regulator can require this information, but not a consumer (data subject). This could be the basis of a great interview test for selecting your DPO. |
|
Request 9b is a bit tricky since the regulator have to be informed but not per se the data subject. Only if there is a risk for the data subject they have to be informed.
The letter is carefully worded itself. The parts the data subject does not have a direct right to know are friendly request (eg 4 vs 8b).
You can answer 8b just with one word: Yes. (Well or No)
The takeaway here:
If you give this letter to you technical personal you will get a detailed overview of the infrastructure they use.
If you give the same letter to your lawyer you would get a very polite letter with the bare minimum of information.
Example for 8b would be this: "We have technology in place which allows us with reasonable certainty to know whether or not you personal data has been disclosed"