Skip to content

Legal

Privacy policy

This page explains what Algo Nexa stores about you, why, who can see it and the choices you have. It describes how the software works today.

Last updated: 6 November 2026

What we store

  • Your account: full name, email address, gender, and your password as a salted scrypt hash (never the password itself), plus when the account was created and when you last signed in.
  • Email codes: when you sign up, reset your password, or sign in from a browser your account hasn't used in the last 30 days, we email you a 6-digit code. It is kept for at most 10 minutes, and only in a scrambled (hashed) form. These emails are sent through Google's Gmail service.
  • If you sign in with Google: your Google account's ID, name and Google-verified email address — nothing else from your Google account, and never your Google password.
  • Your trading data: the strategies you create, your paper and live orders, journal notes and tags, watchlists and settings, and calendar reminders.
  • Exchange API keys, only if you add them: encrypted on the server with AES-256-GCM and shown afterwards only by their last four characters.
  • Community chat: messages and pictures you post there, which other signed-in users can see.
  • Support chat: if you write to us from the website chat, the messages you send and the optional name and email you give, so we can answer. A secret chat code is kept in your browser's local storage so you can continue the conversation; the server keeps only a scrambled copy of it and of your IP address. Only the administrator can read these chats, and chats nobody has written in for 90 days are deleted. Please don't send passwords or API keys in chat.
  • Technical records: the web server records requests (including IP addresses) for security, and sign-in attempts are counted to stop password guessing.

How it is used

Your data is used to run the service for you: to sign you in, keep your strategies, orders and settings, and show them on your devices. It is not sold, and it is not used for advertising.

Cookies, storage and analytics

  • Signing in sets one session cookie. It is HttpOnly, so scripts on the page cannot read it. Signing in with Google also uses a short-lived cookie (up to 15 minutes) that ties the trip to Google to your browser. After you enter an emailed code, a second HttpOnly cookie marks that browser as trusted for your account for 30 days, so it isn't asked for a code again until then; we keep only a scrambled (hashed) copy of it.
  • Your browser's local storage keeps preferences such as the theme and chart layout.
  • Google Analytics runs only on the public pages (this site's information pages, sign-in and registration) to count visits. It is switched off once you sign in, so nothing inside the trading terminal is reported. You can block it with your browser's privacy settings or an extension.

Who can see your data

Other users cannot see your strategies, orders, journal or balances. The administrator sees the account details listed in the user list (name, email, gender, status, approvals, sign-in times and counts of strategies and open positions), never your password or your full API keys. As the operator of the server, the administrator also has technical access to the database.

Real orders you place in Live mode are sent to the broker or exchange you use, which handles them under its own privacy policy.

Your choices

  • Remove saved API keys at any time from My API keys.
  • Ask us to correct your details, reset your password or delete your account: customercare@algonexa.tech.
  • Use the site without analytics by blocking Google Analytics in your browser.

Security

The site is served over HTTPS only, every request to the trading backend needs a signed-in session, and repeated failed sign-ins lock the account temporarily. No system is perfectly secure; see the FAQ for how passwords and keys are protected.

Changes to this policy

If the way your data is handled changes, this page will be updated and its date changed above.