3 ms·
We've had to think about this for GDPR. They are contact details that you're giving to a business to contact people. Your email provider needs them, your phone
by mattmanser 9y ago
We've had to think about this for GDPR. They are contact details that you're giving to a business to contact people. Your email provider needs them, your phone company needs it, your cloud contact manager does it, etc.
I think it's not worth debating to start arguing that we can't use addresses and phone numbers to contact people. That's their whole point.
It's when they're being gathered without informed consent it's a problem or if they get stored without explicit consent past the reasonable use you needed them for.
If I click a button saying "look for my friends", was there a reasonable expectation that FB or LinkedIn or WhatsApp or whoever would then keep that data forever.
FB will argue that obviously you wanted to keep on checking that list. But what about combining different people's list, processing the data in unexpected ways, actually clearly telling the user the list will be stored indefinitely, etc.
- onion2k 9y agoAnd further to that, what if FB doesn't store the information itself but does store a unique hash of it? They can still do all the data processing and yet claim to have no "personal data" at all. This is a deep, deep rabbit hole.
- notimetorelax 9y agoUnder GDPR simple hashing is not enough. You have to throw away the hashing salt (delink the hash from the profile) in order to be compliant. The whole point is exactly the result, you should not be able to map the profile to the data you have.