3 ms·
I mean, there's nothing wrong with statutes and regulations being worded generally as long as they are not vague. Getting too prescriptive in this particular c
by cryptonector 8y ago
I mean, there's nothing wrong with statutes and regulations being worded generally as long as they are not vague. Getting too prescriptive in this particular context would be counterproductive as the technology issues change over time.
What GDPR should say: things like "do not allow third-parties to track your users" or "warn users about third-party tracking". That would be exceedingly clear and actionable.
Now, "do not allow third-parties to track your users" might require some additional regarding implementation via contractual clauses. For example, if site A uses resources from site B and has a contract with B stipulating non-tracking of A's users, is that good enough? What if B is outside the EU? And so on. But aside from such side issues, "do not allow third-parties to track your users" is trivial to implement: a) only embed resources from third-parties that agree not to track your users, b) do not embed resources from any other third-parties.
"Warn users about third-party tracking" is even easier to implement: if you embed resources from third parties, you must warn.
> With GDPR it's not the data it's what done with the data.
Good! You can use contracts to manage this with all the third-parties you deal with.
Now, what about links to [non-embedded] external resources? We must not kill the web.
- michaelbuckbee 8y agoOk, so you're describing (IMO) exactly what's in the text of the GDPR. Here is a "plain english" translation of the GDPR that makes much of this more evident: https://blog.varonis.com/gdpr-requirements-list-in-plain-english/ https://blog.varonis.com/gdpr-requirements-list-in-plain-eng... If you dig into it, I think you'll find it lines up nicely with what you are suggesting.