* Prompts. (Show a notification on a device)
* Phone Txt or voice
* Backup codes
* Authenticator App (ie TOTP)
* Security Key: Yubikey and the like. (You can use some Android phones as a Bluetooth security key)
I'd say google has more options than anyone else right now.
A few months back I finally enabled 2FA on one of my accounts, I wanted to use totp and that option was completely unavailable until I enabled SMS 2FA.
You can argue that they shouldn't have made that mistake, and I'd agree, but stupidity is always more likely than malice.
It's interesting how the supposedly smartest companies of the world are so regularly so stupid in such consistent ways.
They're never stupid in a "oh no we deleted all your personal information from our system and now can't track you anymore" way, weirdly.
More generally, remember that you could be one of those megacorp employees one day, and you might build a 2fa system which logged to a particular place.
Later (remember the company is growing for 50% for many years) some new person sees the phone numbers and doesn't realise their provenance (very likely culturally at a place like FB, where things are default open) someone else finds the phone numbers and uses them to send marketing messages.
Like, that's what happened (most likely) but it amazes me that people will always want understanding for their own mistakes, but regularly disclaim that others shouldn't have done it, or made a mistake maliciously.
To be clear, I have no special insight here, but I think that assuming everything is malice and pre-planned is a less fruitful headspace to inhabit than realising that everyone is human, all companies make mistakes and that's a good prior.
To be even clearer, FB should have made this bug impossible (and I'm sure they have now), but given the amount of mistakes I've made I hesitate to cast the first (or indeed one of the last I suppose) stone.
And what happens if it's revealed? How large are fines, how long the prison time?
Or just keep a hash of the number as GP described.
My guess is, if they aren't nagging you about verification by phone number, you've likely provided them with your number at least once in the past.
On a related note, there's been a push for supporting the Payment Services Directive (PSD2), which requires strong customer authentication (SCA) in most cases, which implies 2FA.
Try it with a VPN or anything from a datacenter IP or any other public place and it's a no go.
They already have Google Authenticator. (Although authenticator plus is better imo) and they use your email address for that.
Using access to specific phonenumber as second factor is not too good security wise, but there’s no perfect options. I’d say managing 2FA properly is hard even for IT pros, let alone regular people. Like how many store the backup codes offsite, regularly test backup Ubikeys etc.
Beware if they claim they don't store your phone number. It's highly likely they store a hash of it for tracking purposes, and proceed to use child-like logic to claim they didn't break any law in doing so.
Furthermore, data brokers use the same hashing algorithm [1] to connect disparate/separate entities, such as your bank, insurance company, fast food chain, etc, basically, any entity you've shared your phone number/email with, in order to gather data on you behind the scenes. How did that happen, you ask? "Out of sight, out of mind."
Google could restrict non-2FA accounts. That way, users could still access their private collection of playlists, but maybe they're no longer able to make comments.
Google and others should offer a standard palette of 2FA options, where the risk factors are left to the users. Let them choose between verified email, some or other TOTP, but try to avoid scavenging private phone numbers, you know, the highest value, globally unique identifier, ooooh.
[1] https://twitter.com/WolfieChristl/status/1288229191759081472