All guides

Security / Built around your control

Your exchange keys never leave your machine

How Aello stores exchange credentials locally, which permissions it actually needs, what the private-server option changes, and the habits worth keeping around API keys.

5 minute read Reviewed 4 September 2026
  • API keys
  • Permissions
  • Local-first
  • Operations
01 / Trading decisions
Yours, not a public trader’s.
02 / Exchange credentials
Encrypted on your machine.
03 / Infrastructure
Your computer. Your server.

Where the credentials live

Aello talks to the exchange directly from the machine running it. Exchange API keys are held in your operating system credential store, encrypted at rest, and are never transmitted to the Aello website, analytics, checkout or support systems. There is no account on our side holding your trading access, so there is no such account to breach.

Use one dedicated credential per exchange account. Separate keys make access easier to restrict, rotate and revoke, and they make it obvious which account was involved if you ever need to look.

Aello asks for less than you might expect

It needs the read and trading permissions for the account role and market you enable. It has no use for withdrawal permission, so that stays off.

  • Keep withdrawals disabled. Aello never moves funds. An API key it uses has no reason to carry withdrawal access.
  • Limit markets. Enable only the Spot or derivatives permissions the account actually uses.
  • Restrict by IP where practical. If the machine has a stable outbound address, apply the exchange’s IP restriction.
  • Rotate exposed keys. Revoke and replace any credential that may have been copied, logged or shared.

What the private-server option changes

Run Aello on your own private server with Ultimate, so copying and Telegram updates can continue when your computer is off.

The server stays in your cloud account, under your control. Manage it from the Aello desktop app.

Protect your cloud account with strong authentication and keep its API token private.

What Aello does hold

Licence validation, checkout, delivery, optional analytics and support are entirely separate from your trading credentials. They handle the limited contact, order, licence, activation and website-usage data set out in the Privacy Policy.

Support will never ask for your API secret, seed phrase, private key, password, or a one-time code.

The habits that make the difference

Local-first custody puts you in control, which also means the machine matters. Secure every exchange account with strong authentication, review API-key activity and permissions periodically, keep the operating system and Aello current, and stop copying if an account looks unfamiliar.

Start on demo, then start small. Verify each account’s symbols, margin mode, leverage, sizing and risk limits on their own before you scale exposure up.

Report a security concern

Use the verified contact details on the Contact page. Describe the affected product and behaviour without sending credentials, customer secrets, or payloads containing real account data.

If an exchange credential may be exposed, revoke it at the exchange first. Please do not wait on a support reply before removing access.

Make an informed decision

See how it works for you.

Start on demo. Check the workflow. Choose a plan when it fits.