4 ms·
Not a dumb question at all. Yeah, in the process of finding you within a data brokers system and sending a removal request, they need to send that broker your p
by mattstir 3y ago
Not a dumb question at all. Yeah, in the process of finding you within a data brokers system and sending a removal request, they need to send that broker your personal data... it's a bit awkward. Optery, another PII removal service has a whole section about this in their privacy policy (section 7 of https://www.optery.com/privacy-policy/ https://www.optery.com/privacy-policy/):
> Optery, Inc. must send your PII to the data brokers and information aggregators included in the Removal Lists... We cannot control, guarantee or warranty how these third-parties will treat your PII or what they will do with it.
- feedsmgmt 3y agoAnd you need to enter all of the information that you're trying to protect into one central location that is probably heavily targeted. These types of services never made sense to me.
- beyondd 3y agoOptery also has a Help Desk article on this catch-22 where in order to opt out of data broker sites, you must first tell them who you are, otherwise, how else would they know who to opt out: https://help.optery.com/en/article/what-information-does-optery-share-with-data-brokers-when-opting-me-out-1dxtj/ https://help.optery.com/en/article/what-information-does-opt...
- hedora 3y agoThey could use a bloom filter with some sort of a cryptographic hash. On a hit, the data broker could challenge them to compute a salted hash of the "matched" data. If the salted hash matched, the data broker would remove the data. I think the same algorithms that are used for password storage would work for this without modification (except the data broker would pick different salts during each session, and you'd send the hash over the network).
- Jommi 3y agoits called a ZKP
- politician 3y agoNo company wants to implement this. I've been involved in efforts to use this approach with hospitals -- a perfect PII-preserving situation -- that went nowhere. We got it working with a startup once where we published the bloom filter to reduce the traffic load for the counterparty. Do you know what they did? They reverse engineered the filter by blasting it with every key and cached the result.