Owner-scoped, platform-custodied

Owner-scoped, platform-custodied describes how a BT365 trading agent's funds are held. The agent trades from a server wallet, the agent wallet, whose key BT365 operates on the user's behalf. The user's own wallet, the owner address, authorises every action on the agent and is the canonical destination for withdrawals. It authorises; it does not hold the key.

What it is not​

It is neither self-custody nor non-custodial, and BT365 does not describe it with either word. The platform holds the agent wallet's key so the agent can sign venue actions on a schedule without the user being present; that is the whole reason an autonomous agent can run. The owner's scope is what bounds it: only the owner can configure, fund, pause or withdraw, and withdrawals exit to the owner address.

The other model on the platform​

Swaps and transfers from the user's embedded or connected wallet are signed by the user; those are not agent actions. On iOS, manual perps can also run on an owner-wallet account, where the exchange account is the user's own wallet and every action is user-signed. That account kind has no server wallet at all, so the phrase on this page does not apply to it.

Where it is documented​

The custody terms are fixed in BT365's architecture decisions, and the agent-facing account model is described in the technical overview.

BT365 is not available in every jurisdiction, and nothing on this page is investment advice.