5 ms·
The result is a new set of data that contains no personal information, but retains the format and statistics of the original. The only way that each field in th
by pcunite 9y ago
The result is a new set of data that contains no personal information, but retains the format and statistics of the original. The only way that each field in the new data set can be returned to its old state is by applying the key used to generate the hash
these keys are held by the accounts teams. The development teams working on the pseudonymous data never see them
Right ... but I would feel better if I supply this hash/key back to them. I understand I can request erasure, but I would like the option to request "hashed" (or a user friendlier term) when I want to keep my data on their server, but I control it.
- mikekchar 9y agoThat's a very interesting idea. How would you implement it? I guess that it's one of those things that won't fly without industry acceptance, but a proof of concept would be very useful, I think...
- jypepin 9y agoYou supply this key? So you are implying that you store the key and the company doesn't have access to it, hence doesn't have access to your data? Then is there any reason for the company to store your data? What if you loose the key? You can't restore your account? I'd be interested to know the % of users loosing their password and needing to use "forgot password" feature. How would that work with a key you own?
- patrickmn 9y agoYou might be interested in Tahoe-LAFS: http://tahoe-lafs.readthedocs.io/en/tahoe-lafs-1.12.1/architecture.html#capabilities http://tahoe-lafs.readthedocs.io/en/tahoe-lafs-1.12.1/archit...