A reminder, ahead of news today, that we alerted the European Commission in October that it could not grant the UK a free data flow "adequacy decision" because of failings of @ICOnews.
@ICCLtweet
iccl.ie/monitoring-hum…
@ICCLtweet
iccl.ie/monitoring-hum…
https://twitter.com/johnnyryan/status/1315551079317278720
Problems with the draft:
1. GDPR Article 46(2)a tells the Commission what to consider when granting an adequacy decision. One must be able to take the ICO to court for mistakes. Ask @OpenRightsGroup @jimkillock @RaviNa1k whether this is notional or real.
ec.europa.eu/info/sites/inf…
1. GDPR Article 46(2)a tells the Commission what to consider when granting an adequacy decision. One must be able to take the ICO to court for mistakes. Ask @OpenRightsGroup @jimkillock @RaviNa1k whether this is notional or real.
ec.europa.eu/info/sites/inf…
2. GDPR Article 46(2)b tells the European Commission that there must be an "effective[ly] functioning" a supervisory.
Paras 85-98 of the draft decision give a positive review of @ICOnews' performance.
But in fact the ICO failed to act on RTB, the biggest data breach in history.
Paras 85-98 of the draft decision give a positive review of @ICOnews' performance.
But in fact the ICO failed to act on RTB, the biggest data breach in history.
These problems are additional to the UK acting as a back door for transfer of EU data to US security organisations. Judging by Article 46(2)(a) and (b), that there is a problem with processing of data in the UK itself.
https://twitter.com/maxschrems/status/1362715631653711872?s=20
For context on @ICOnews and its failure to act against vast, systematic GDPR infringement, see thread
https://twitter.com/johnnyryan/status/1218140830512214017?s=20
And there are other issues, too
https://twitter.com/tjmcintyre/status/1362768132532805633?s=20
• • •
Missing some Tweet in this thread? You can try to
force a refresh
