How your password and broker access are protected
Last updated: 2026-08-23
Your Bridge password
Stored as an argon2id hash — the current best-practice password hashing algorithm. Nobody at Bridge can read your password; we can only verify it. Add two-factor authentication (authenticator app or email codes) in Settings → Account for a second layer — see Two-factor auth & recovery.
Your broker connection
You connect through SnapTrade, a brokerage-connection provider. You log in on your broker's own page — your broker password never touches Bridge's servers. What Bridge stores is a revocable access credential scoped to reading balances/positions and placing the orders you've authorized.
| What | Stored by Bridge? | Protection |
|---|---|---|
| Bridge password | Hash only | argon2id |
| Broker username/password | Never | — (stays with your broker) |
| Broker access credential | Yes | AES-256 encrypted, per-user key |
| 2FA secrets / recovery codes | Yes | Encrypted at rest |
Encryption keys live in a managed secrets service, separate from the database. A stolen database copy alone cannot decrypt broker credentials.
What the connection can never do
- Withdraw or transfer funds (brokers don't expose this to connections).
- Change your broker password or personal details.
- Trade any account you didn't explicitly connect.
What Bridge does on a suspected breach
- Revoke all broker access credentials immediately (orders stop).
- Force password reset + re-authentication for affected users.
- Notify you by email with what happened and what we did.
What you can do
- Use a unique password for Bridge (a password manager helps).
- Enable 2FA — an authenticator app is stronger than email codes.
- Set a daily-loss limit at your broker too. Bridge has its own daily-loss cap, and your broker's hard limit is an independent backstop that no software above it can override.
- Review Settings → Brokerages occasionally and disconnect anything you no longer use.