← OrderFill

Security

You are trusting us with access to a trading account. This page states plainly how that access is protected. If anything here is unclear, ask before you connect an account.

Credentials are encrypted at rest

Every trading account's credentials are sealed with their own encryption key, which is itself wrapped by a master key held outside the database. A copy of the database alone is not enough to read them.

Decrypted only in memory, only to connect

Credentials are unsealed at the moment a session starts, used to log the terminal in, and never written to disk in plain text, never logged, and never sent to any third party.

One isolated terminal per account

Each trading account runs in its own terminal process with its own data directory. Accounts cannot see each other's positions, history, or configuration, even when they belong to the same user.

Deletion means deletion

Disconnecting an account destroys its terminal and deletes its stored credentials. Closing your OrderFill account removes the rest.

Private network between our services

Our control plane reaches execution hosts over a private encrypted network. The execution layer is not exposed to the public internet.

Protective orders live at your broker

Stop-loss and take-profit orders sit server-side with your broker, not with us. If our infrastructure were unavailable, your protective orders still stand.

Every action is auditable

Orders and account changes are recorded with their origin, so you can always see what was placed, when, and by which strategy or session.

What we ask of you

Reporting a vulnerability

Email [email protected] with the subject “Security report”. We will confirm receipt and keep you updated until it is resolved. Please give us a reasonable window to fix an issue before disclosing it publicly.