Your keys
DeltaPulse never holds your funds. To read your accounts and trade on them it holds keys — and treats them as the most sensitive thing it stores.
What we can never do
- Withdraw. A key with withdrawal rights is refused for trading. On-chain venues get a separate trading key registered by your wallet’s signature; we never see your wallet’s private key or seed phrase.
- Use a key from anywhere else. Trading keys must be restricted to our server addresses, so a stolen key is useless outside our servers.
- Show it back. Once saved, a secret is never displayed again — not to you, not to us in the interface.
Admission checks
When you add a key that will trade, we check it before accepting it:
| Check | Why |
|---|---|
| Futures trading allowed | Otherwise it cannot open a leg. |
| Withdrawals off | A trading key must not be able to move money off the venue. |
| IP allowlist | Restricted to our server addresses. Where a venue does not let us read the list, a wrong address shows up as a refused order. |
If any check fails the key is kept read-only and the card says what to change. The checks fail closed: if we cannot tell, the key cannot trade.
Storage
- Every connection’s secret is encrypted on its own, under a master key held in a dedicated key-management service, never in the database.
- Trading keys use a different master key from read-only keys, so a compromise of one does not expose the other.
- Every change to a connection — added, checked, rotated, removed — is written to an append-only audit log.
Revoking access
Remove the connection in Profile → Connections and delete the key on the venue. For wallet-registered keys, revoke the key on the venue or connect again: the new key replaces the old one.
Use a subaccount holding only the funds you want to trade. It is the simplest limit on what any key can touch.