←back to thread

Brave taking cryptocurrency donations “for me” without my consent

(twitter.com)
323 points plusCubed | 1 comments | 21 Dec 18 17:48 UTC | HN request time: 1.757s | source
Show context
davidgerard ◴[21 Dec 18 19:23 UTC] No.18735792[source]▶
Brendan Eich answers on Twitter: https://twitter.com/BrendanEich/status/1076187316748615680

basically he plans to keep it working the way it works now, "opt out" and all - he's confident this is a completely legal way to work

replies(5): >>18735934 #>>18735953 #>>18736012 #>>18736066 #>>18744548 #
ShannonAlther ◴[21 Dec 18 19:50 UTC] No.18736012[source]▶
Just realized I didn't know this: how are you supposed to comply with GDPR if your clients are partially anonymous?
replies(1): >>18736344 #
icebraining ◴[21 Dec 18 20:29 UTC] No.18736344[source]▶
I assume you're talking about the user requests regarding their data? Well, if the data is so anonymized that even the person can't prove who they are, then I'd say it falls in the provision that exempts anonymized data.

But in this case, I'm assuming the user must have a private key (for signing BAT transactions), so they could build a feature in the browser to sign messages using it.

replies(1): >>18736382 #
1. _corym ◴[21 Dec 18 20:34 UTC] No.18736382[source]▶
The problem with signing transactions is basically then you can identify the browser history of the user. The BAT-ledger explains the principles of the transaction system

https://github.com/brave-intl/bat-ledger/blob/master/documen...

The current process is the data is anonymized and then sent out for privacy reasons.