Earlier quoted context omitted.
I don't think this is very useful in most cases. Suppose a service requires data transmission to operate, either intrinsically, or it just chooses to require it. It displays a checkbox, unchecked by default, and unless the user checks it, the service isn't going to work; checking the checkbox is functionally equivalent to the "I Agree" TOS button. I expect users will check the checkbox without reading any explanation…
> Suppose a service requires data transmission to operate, either intrinsically, or it just chooses to require it No services really requires data transmission. It's just the owners have decided to run it that way. > I expect users will check the checkbox without reading any explanations, just as today they click "I Agree" without reading anything. Within EU Data Protection law, you have to get "freely given, informe…
Some services do. For instance, Waze builds live traffic maps because all its users upload their locations / speed / etc.
> It's just the owners have decided to run it that way.
Which is their right, as long as the users give informed consent. What I would like to know is how, in practice, such consent can be sought or given.
> And a checkbox which links to 30 pages of legalese does not necessarily count as informed consent.
I'm not saying it does, necessarily. I'm asking what does count as informed consent? Can you give an example of consent done right?