Yes, the two questions are in fact quite orthogonal. - Should data truly intended to be public be scrapable by HiQ (or anyone)? The answer has to be yes. - Sh

Yes, the two questions are in fact quite orthogonal. - Should data truly intended to be public be scrapable by HiQ (or anyone)? The answer has to be yes. - Should you be able to use "public" data to seek out essentially private information behind the user's back (like what HiQ is doing)? The answer has to be no. On this latter question, there is a notion of continuous consent and discoverability. There should be a feedback trail all the way back to the original provider of data (the user) about who is accessing the data and for what purpose, even if (or especially because) it is public; and this fact should be made known to the accessor. There has to be a semblance of symmetry in how a public exchange of information should take place. Both the provider and the accessor should be in the open if it is truly public. Then the user can take actions to affirmatively provide continuous consent or withdraw.