On my service - <a href="https://next-episode.net" rel="nofollow noreferrer">https://next-episode.net</a> - along with signing in with username and password, there is an option to sign in with Google and Facebook.<p>3 days ago, I get this email from Facebook "Complete business verification for Next Episode" which notifies me that my Facebook app (which handles the Facebook login functionality) now needs to be connected to a verified business account.<p>This is where they announced this back in February: <a href="https://developers.facebook.com/blog/post/2023/02/01/developer-platform-requiring-business-verification-for-advanced-access/" rel="nofollow noreferrer">https://developers.facebook.com/blog/post/2023/02/01/develop...</a><p>Now, going through the steps of filling out my name, address, phone number etc, I checked the "How we use your information" link and in it, it said "In certain cases, we'll update your publicly available Page Transparency information with some of the details you confirm during verification".<p>In the Page Transparency information page: <a href="https://www.facebook.com/help/323314944866264/" rel="nofollow noreferrer">https://www.facebook.com/help/323314944866264/</a> it says the information about the owner may include "The Confirmed Page Owner's verified legal name and registered city, country and/or phone number". Later on, on the same page, they say you can remove (or request to remove) some of the information visible there, but they never specify which information you'll be able to remove.<p>Anyone with an experience with this? I don't want my address and/or phone number publicly visible, so what are my options here?<p>For now, I have removed the option to sign up with Facebook (existing users can still use it to sign in) and I plan to completely remove it (by the time the December 11th deadline comes around) notifying users about the change upfront and giving them the option to switch to Sign in with Google or with username and password.
Could you switch to just using passkeys instead of Google, Apple, or Facebook federated identity? This eliminates the risk of storing passwords, and also doesn't create a dependency on one of the companies mentioned. You'll still need to store username, email, or both, depending on your use case. You can also create a code path that will transition accounts from federated identity to self hosted with passkeys as well.<p><a href="https://passkeys.dev/docs/tools-libraries/libraries/" rel="nofollow noreferrer">https://passkeys.dev/docs/tools-libraries/libraries/</a><p><a href="https://passkeys.directory/" rel="nofollow noreferrer">https://passkeys.directory/</a><p><a href="https://www.corbado.com/blog/user-transition-passkeys-expert-strategies" rel="nofollow noreferrer">https://www.corbado.com/blog/user-transition-passkeys-expert...</a>
Same here.<p>For transparency reasons I will also be listing Mark Zuckerberg's phone, postal and residence address on our contact page (100% of the support requests we get are about facebook problems anyway)
It depends on what level of access you want. My app just uses basic verification - I get to see the user's name, Facebook ID number, and photo. That's it.<p>I don't have to provide any of my personal data as a developer to Facebook. I do have to provide a privacy policy. I haven't received a similar email to you.<p>As that blog post says, Business Verification is required for "Advanced Access".<p>So, if you can, change the level of access that you need. If all you're using Facebook for is an identity provider see if you can drop the number of permissions you're requesting.<p>If that fails. Get a cheap disposable SIM and use that as your phone number for Facebook verification.
Every year september / october FTC compliance push happens - and your product will get randomly flagged and disabled by AI.<p>This year, there’s gonna be even fewer humans to correct the madness. Not having FB login is a mercy, not a mistake.
I don't know what country you are in, but if you are concerned about a phone number and postal address, there are myriad ways to obtain both of those which can effectively obscure your location and identity.<p><pre><code> * Get a Google Voice or other VoIP provider.
* Get a burner cell phone.
* Get a business account with your PSTN provider and run an Asterisk PBX or something.
* Obtain a PO Box at your US Postal Service, UPS Store, or an independent provider of boxes.
* Identify a coworking space where you can receive postal mail, and use its address.
</code></pre>
Since you are a business, (you are a business, or just an "indie developer"?) then you should be able to establish business-class accounts in this manner and satisfy Facebook's requirements. They do not seem overly onerous.
This may be what you're looking for.<p>Something like OAuth2 or OICD "Permission Scopes" -- the permissions that a user can grant your app, just prior to their accepting the log in via that particular social-media authentication provider.<p><a href="https://developers.facebook.com/docs/permissions/reference/" rel="nofollow noreferrer">https://developers.facebook.com/docs/permissions/reference/</a><p>Here are examples:<p><a href="https://www.loginradius.com/blog/engineering/facebook-authentication-using-node-and-passport/" rel="nofollow noreferrer">https://www.loginradius.com/blog/engineering/facebook-authen...</a>
> Anyone with an experience with this? I don't want my address and/or phone number publicly visible, so what are my options here?<p>Depending where you are, you may <i>already</i> be required to share this information, for example any business here in the UK must have their company registration number , registered office address, and contact (email and post) details, on any website.