3 ms·

My understanding was you had to either not allow connections from that country to access your site or have some version that doesn’t track them. Your probably

My understanding was you had to either not allow connections from that country to access your site or have some version that doesn’t track them. Your probably not at risk for anything, as your using googles service, but I’m not a lawyer. I’d assume if your using google analytics, google would be responsible for following these guidelines? Google will probably release info on this if they haven’t already. But I find it hard to believe unless your rolling your own analytics anyone would come after you.

cassianoleal 5y ago
> I’d assume if your using google analytics, google would be responsible for following these guidelines? IANAL but I doubt that's the case. If GA is being used through your site, you're the data controller and Google are the data processor. [0] At the very least, you're liable as you're the one sending the user's data to GA. This probably holds true even if technically it's the user's own browser making the calls to GA directly, since it was only doing so because your site instructed. Happy to be corrected if that's not the case. [0] https://www.gdpreu.org/the-regulation/key-concepts/data-controllers-and-processors/#What_Is_The_Difference_A_Between_Controller_And_Processor https://www.gdpreu.org/the-regulation/key-concepts/data-cont...
whakim 5y ago
The GP's blog (the "data controller" in GDPR parlance) isn't an EU entity and it's not clearly intending to offer goods or services to EU data subjects. The blog therefore isn't subject to the GDPR.