What we can and cannot do on a client's account
The first question we are asked is rarely about signals. It is simpler: what exactly can your software do with my account, and what can it not do? This note answers that in full.
The account stays the client's
A client opens the exchange account in its own name and keeps the login. Deposits and withdrawals are made by the client, to and from the client. Nothing is ever transferred to us, and we never hold client funds. If Pokesystem disappeared tomorrow, the account and everything in it would still be exactly where it is.
One key, one permission
The client creates an API key and gives it a single permission: trading. Withdrawal and transfer rights stay switched off, and the key is bound to the fixed addresses of the servers we operate, so it is useless anywhere else. We never ask for more than this, and a key that carries more is one we will ask the client to reissue.
With that key the software can do three things: read the account, place orders, and cancel them. It cannot move funds, change the account's settings, or create other keys.
What we check every day
Our systems keep their own record of every position and balance. Once a day that record is compared with what the venue reports, account by account. A difference we cannot explain is treated as an incident: it is investigated before any other work, and the client hears about it from us first.
Between those checks, monitoring runs around the clock. Alerts fire on stale data, lost connectivity, and any position that drifts from its target.
Nothing has to be taken on trust
Every order, fill, fee and funding payment appears in the client's own account history at the venue, the moment it happens. The client can review it at any time with its own login, or give read-only access to its administrator or auditor, without involving us. What we report can always be checked against a source we do not control.
Stopping takes one click
The client can delete the key at any moment, and from that second the software can place no further orders. In practice we agree an orderly wind-down first, because open positions remain in the account either way. But the switch belongs to the client, and it does not need our cooperation to work.
That is the whole arrangement. We build and run the software; the client owns the account, holds the funds, and keeps the off switch.