How we protect your money.

Wealthnow reads your positions and, where your broker supports it, sends the orders you approve through the brokerage you already use. Your funds never leave your broker. You can revoke our access at any time.

Built like we mean it.

Every account runs on the same infrastructure, and every order passes through the same safety gate before it reaches a broker.

  • Never custodial

    Wealthnow is not a broker-dealer. Your funds remain with Robinhood, Schwab, IBKR, Coinbase, or whichever broker you connected. Some connections only let us read your account; others also let us send the orders you approve. You can revoke our access inside Wealthnow or at your broker.

  • One order gate

    Every order passes one safety gate before it reaches your broker. It checks an operator kill switch, needs your approval, refuses a sell that your holdings do not cover, and never sends the same order twice.

  • Encrypted and access-controlled

    AES-256 at rest, TLS 1.2 or higher on every connection to Wealthnow, and broker credentials encrypted before we store them.

How custody actually works.

  • How you connect

    You connect a broker by signing in on the broker's or a connection service's own screen (such as Plaid or SnapTrade), or by creating an API key at your broker and entering it in Wealthnow. We never ask for your broker password. We ask only for trading access where a broker offers it. Some brokers, such as Alpaca, do not offer a trade-only key. We never use any connection to move money.

  • Where your money stays

    Your money stays where it always was. Robinhood holds your Robinhood balance. Coinbase holds your crypto. Interactive Brokers holds your IBKR account. We never use a connection to move funds out of those accounts.

  • Where a trade lands

    When Wealthnow submits a trade, it lands inside your broker exactly as if you had clicked Buy on the broker's own app. Fills, settlements, statements, and tax reporting all happen at the broker. We are the brain. The broker is still the bank.

  • How you revoke access

    You can revoke Wealthnow's permission at any time, from inside Wealthnow or from your broker's own app. When you disconnect inside Wealthnow, we stop using the connection, but API keys you entered, and the sign-in tokens from Robinhood, E*TRADE and Interactive Brokers, stay encrypted in our database, and we do not revoke those tokens at the broker. Revoke the key or connection at your broker to end access completely.

Every trade passes these checks first.

One gate sits in front of every broker, for the orders you place and the trades you approve. An order it refuses is never sent.
  1. 01

    Your approval

    Every order needs your approval before it is sent. The gate refuses any order that does not carry it.

  2. 02

    No short selling

    A sell must be covered by what you already hold. The gate refuses a sell larger than your position.

  3. 03

    Kill switch

    Our operators can stop all order flow, or a single account, trading route, symbol or strategy, within about a second. If the switch cannot be read, the order is refused.

  4. 04

    Each order sent once

    Every order is claimed under its own ID before it is sent, so a retry or a double click cannot place it twice.

  5. 05

    Broker circuit breaker

    If a broker connection keeps failing, the gate pauses orders to it for a minute instead of retrying into the outage.

The infrastructure under the brain.

Infrastructure defined in Terraform, in AWS us-east-1. The website is served through CloudFront, behind AWS WAF rules. Secrets kept in AWS Secrets Manager under a KMS key that rotates yearly; the secret values themselves are not rotated on a schedule. No long-lived AWS keys in CI.

Every account runs on this same stack, and every order passes through the same safety gate.

Cloud
AWS, us-east-1
Infra as code
Terraform, S3-backed remote state, DynamoDB locks
CI / CD
GitHub Actions over OIDC, no long-lived AWS keys
Edge
CloudFront + AWS WAF for wealthnow.io
Secrets
AWS Secrets Manager, encrypted under a KMS key that rotates yearly
Encryption
AES-256 at rest, TLS 1.2 or higher on every connection to Wealthnow, HSTS
Observability
CloudWatch logs, metrics and alarms
Data residency
United States

Responsible disclosure.

Found a vulnerability? Email security@wealthnow.io before you publish. We aim to acknowledge reports within two business days and will keep you updated until it is fixed.

security@wealthnow.io
In scope:
wealthnow.io, app.wealthnow.io, api.wealthnow.io and the Wealthnow app. Test only with accounts you own. If you reach data that is not yours, stop, tell us, and do not keep, use or share it.
Out of scope:
accessing, changing or deleting other people's data; denial-of-service or load testing; social engineering, phishing or physical attacks; third-party services we use (report those to the vendor).
Safe harbor:
if you act in good faith within these limits, we will treat your research as authorized, and we will not take legal action against you or ask law enforcement to act against you for it. With your permission, we will thank you publicly once the issue is fixed.

Your next chapter starts here.

Start with a free account. Explore more as you go.