Hey, pigs have flown! They implemented 2FA late 2024! This thread however is another very important piece of the pie - and while not a traditional request for users to make, it's not all that hard to fulfill. Any Linux system will let you integrate a TOTP style token (e.g. something powered by Google Authenticator) with PAM, at no cost to the company. Administering those tokens in bulk is a bit more of a trick, but with ssh access to the system it is simple enough to script something into place for rapid provisioning, I've done it before. Non-linux systems have commercial solutions at a variety of price points and levels of effort required for integration - there's something for everyone. I have no idea what their backend infrastructure is running, but there should be 2FA to every system in 2026, for users (which is done, yay!) but especially for staff. Where I work, we have no choice in the matter, it's 2FA or we close shop, and we're not dealing with the account security of even hundreds of people, we are merely protecting intellectual property and sensitive info. Also, idk how Roll20 integrates with stripe, but from working with other sites who use them, there are plenty who do not retain payment info on their users, opting to just maintain a token of sorts from the transaction. Stripe of course has the info, but then you require two systems to be compromised in order to get at someone's payment data. This approach might bar you from saving your payment info unless stripe offers that as well through their API, which they probably do. Out of scope for this request, but applicable nonetheless as I'd expect things like real name (from payments especially where you don't want to lie), address, cc info, and IP address to be the most sensitive data roll20 holds, and easy to protect this way. I also imagine chat/forum contents and our personally owned IP used in the VTT to be sensitive as well for most users. We obviously have no way of auditing implementation but a good faith reply from Roll20 saying "hey, yes, we heard you, we're doing 2FA across our infrastructure, and nobody can get at any system with user data without it" would be great and imo enough to close this out, assuming they've taken such steps. Be advised that even with 2FA in place, it doesn't stop things like federation between services, or API tokens and such from being used as potential avenues to get at sensitive data, but it does greatly diminish the value of social engineering or an employee just making a mistake.