Account Security Best Practices

Keep your account secure.

Help Center avatar
Written by Help Center
Updated over a week ago

To help keep your account secure, we recommend these best practices:

  • Use a strong password that you don’t reuse on other websites.

  • Be cautious of suspicious links and always ensure you’re on teams.wethos.co before entering your login information.

  • Never give your login credentials (email address and password) out to third parties.

  • Ensure your computer software, including your browser is up-to-date with the most recent upgrades and antivirus software.

Password Strength

Create a strong and unique password for your Wethos account.

  • Do create a password at least 8 characters long. The longer, the better.

  • Do use a mix of uppercase and lowercase letters, at least one digit number, and at least one special character.

  • Do keep your password in a safe place. Consider using password management software to store your login information securely.

  • Don’t use personal information in your password such as phone numbers, birthdays, etc.

  • Don’t use common words, phrases, or sequences like “password1234”, “ilovewethos365”, “abcd1234”, etc.

  • Don’t reuse passwords across websites. Your Wethos account password should be unique to Wethos.

If you need to change your password, you can select “Change Password” in your Account settings. You'll be prompted to enter your old password and a new password twice for verification.


Wethos will never ask you to provide your password via email or chat support. We’ll never ask you to download anything or sign-in to a non-Wethos website. Never open an attachment or install software from an email that claims to be from us… because it’s not.

If we suspect your account has been phished or hacked, we may reset your password to prevent hackers from misusing your account. In this case, we’ll email you a teams.wethos.co password reset link.

_______________

Still have questions? We're happy to help!

Contact us at [email protected].

Did this answer your question?