What fxyz cannot do

A short, deliberate list. These are things fxyz is structurally incapable of doing, not things we've promised to avoid. No engineer at fxyz, no leaked credential, no malicious strategy, no insider can change any of them.

fxyz cannot withdraw your funds

Not from Hyperliquid, Lighter, Backpack, or any other venue we support.

The credentials we hold are trade-only at the venue level, and our own product has no withdraw code path on top of that. The venues themselves refuse. There is no clever sequence of steps, no admin override, and no buried API endpoint that bypasses this. The capability does not exist, in our code or in the credential we hold.

fxyz cannot transfer your funds to a different address

Same reason. Trading credentials are scoped to trading. Transfers require something fxyz never had and never will have: your main wallet on Hyperliquid, or your full account login on Lighter and Backpack. We could not transfer your funds if we wanted to.

fxyz cannot let one user's strategy read or trade on another user's account

Each user's workspace is cryptographically and operationally partitioned. The credential for user A is not present in user B's workspace, and no API, internal or otherwise, lets a workspace ask for everyone's credentials. There is no shared pool. The blast radius of anything that happens inside a workspace ends at that workspace's wall.

fxyz cannot recover your wallet

If you lose access to the wallet you sign in with, fxyz cannot let you back in under a new wallet. We never held a copy of your wallet's keys. This is the same trade-off that gives you sole ownership of the account in the first place: nobody can lock you out, but nobody can let you back in either.

Your exchanges aren't affected. You'd simply reconnect them under whichever wallet you use next.

fxyz cannot change your account settings on a venue

The credentials we hold don't carry the permissions for this. Account settings on HL require your main wallet; on Lighter and Backpack, they require the venue UI you logged into to generate the API key. Both are out of fxyz's reach by design.

fxyz cannot assemble your credential in any single place

Even our own infrastructure cannot. The credential is never held as a single readable value anywhere in our systems. An attacker would have to breach several independent, fortified stores at the same time, separately for every individual user they wanted to read. There is no master list, no shortcut, and no engineer with the ability to dump credentials.

What fxyz can do

For completeness:

• Place, modify, and cancel orders on the venues you've connected.
• Read your positions, orders, fills, and funding from those venues.
• Run code you (or a strategy you forked) wrote, against those venues, under your credentials.

That's the whole surface. Everything else is off the table, not as a promise but as a property of how the system is built.