4 ms·
To be fair, isn't this the case with most credit cards as well? Any record of purchases you create is a privacy risk because somewhere there's at least one ent
by soylentcola 7y ago
To be fair, isn't this the case with most credit cards as well? Any record of purchases you create is a privacy risk because somewhere there's at least one entity involved in authorizing and processing transactions.
If anything, wouldn't being able to use an app specific to your bank remove one more middleman (Apple, Google, whoever) from the process?
- Fnoord 7y agoI've never used credit cards; only debit cards and bank cards. I'm not so sure they sell my data, given GDPR. They might've in past though.
- soylentcola 7y agoI guess my point is that there's a lot to "privacy" when used generally. Direct selling data is one thing, but not the only thing of concern. There's also the issue of data breaches and other malfeasance like that. Even if the bank itself doesn't sell data do Visa or Mastercard (or whatever company handles processing?) How about other entities, like retailers? Bank/debit cards can still be used to build a profile, no? I don't mean to criticize your personal usage policies because I've largely come to accept that we can't avoid all risk of data theft or misuse as long as we're using electronic payment. I just think it's more complicated than "but Google, therefore selling data". For my part, I try to limit the number of hands in the pot, so to speak. If my bank and the card processor and the seller get info, do I benefit from adding my device's OS maker to the mix? On Android I can choose to use my bank's app rather than Google's service if I want to avoid yet another potential for leaks or profile building. I look at skipping Apple or Google Pay the way I look at skipping "loyalty cards" which offer some minor discount or convenience in exchange for another hand in the pot.