Thread · 2 tweets · 8 Oct 2020

So (trying to understand how this works, sorry if slow): when a site obtains consent, it would do so in its own (possibly bad) UI, but it would be required to store that consent with the browser, I assume with 1) a description of what is being consented to, 2) a unique ID, and…

…3) a source domain? And then the user could consult the list of what they’ve consented to, and withdraw consent by hitting a button that would call a .well-know in that domain with the unique ID?