Skip to main content

How Browser Console Uses Your Credentials to Log In

Updated over 2 months ago

For many problems, Browser Console needs to log into secure sites - like your utility provider, insurance portal, or financial accounts - to complete tasks (for example: downloading recent bills, submitting forms, or checking status).
Loophole makes this process safe, seamless, and fully under your control.


Where to Add or Manage Credentials

You can securely store any credentials at:
https://loophole.com/my-account/settings/#tools

Here, you can add or edit:

  • Service Name (ex: Duke Energy, Payment Portal)

  • Website URL

  • Username or Email

  • Password

  • Account ID or Number

  • Security Questions & Answers

  • 2FA Codes or Backup Codes

  • Google Authenticator / TOTP Codes

  • Notes for special instructions

All data is fully encrypted and only used with your explicit approval.
You can see the 'Last Accessed' date clearly displayed on each record.


How Browser Console Uses Your Credentials

  1. Scheduled Login Action:
    When Research Console suggests a task that requires logging into a site (e.g., Duke Energy), you review and approve the action.

  2. Credentials Check:
    Before running, Browser Console checks if you already have the necessary login details stored for that service.

  3. If Credentials Are Stored:

    • Browser Console logs in automatically, following your approved instructions.

    • 2FA codes (including Google Authenticator, backup codes, and SMS) can be used automatically if you’ve added them to your credentials.

  4. If Credentials Are Missing:

    • You’ll receive a secure notification prompting you to add the required credentials at your account tool settings page.

    • Once added, Browser Console can continue and complete the action without manual intervention.


What If I Don’t Want to Store My Credentials?

You’re always in control!

  • Storing credentials is optional.

  • If you prefer not to save them, you’ll simply need to be present during your Browser Console session to enter usernames, passwords, or 2FA codes when prompted.

  • The session will pause and wait for your input - no information is ever shared without your approval.


Advanced 2FA Support: Google Authenticator & Phone Console

  • Google Authenticator/TOTP:
    Add your authenticator key in your Loophole credentials, and Browser Console can automatically generate and use your time-based one-time passwords (TOTPs) whenever required - no need to be present!

  • Phone Console (if opted-in):
    Advanced users can assign their dedicated Loophole “Phone Console” number as their account’s recovery phone, allowing Browser Console to receive SMS-based codes and log in on your behalf. (See Phone Console for more info)


Security & Privacy

  • Your credentials are always encrypted and only accessed when a scheduled, approved Browser Console action requires them.

  • No credentials are ever shared with third parties or used outside the tasks you’ve authorized.

  • You can add, edit, or remove any credential at any time from your account tool settings page.


Summary

Storing your credentials in Loophole makes Browser Console fully hands-off for logins and automations - even with 2FA. If you’d rather not store them, you stay in the loop and simply enter details when needed.

You’re always in control.
Browser Console will never proceed with a login unless you’ve authorized the action and either stored your credentials or entered them live.

Did this answer your question?