Algoagent Core — algoagent.in
Last updated: October 11, 2026
1. Reporting a vulnerability
Email bugs@algoagent.in, or support@algoagent.in, with Security in the subject line. Say which app and version you used (Settings, then Account, shows the version), your operating system, what you found, and the steps that show it. Describe any secret rather than sending it: never include a real API key, broker credential, session token or holdings.
- We read every report, reply to confirm we have it, and tell you when a fix ships.
- Please give us reasonable time to ship that fix before you publish details, and tell us when you plan to publish.
- Test against your own installation and your own account. Do not access other people's accounts or data, do not load-test or disrupt algoagent.in or api.algoagent.in, and do not use social engineering. We will not take action against research done in good faith within these limits.
- There is no paid bug bounty.
The same contact is published in machine-readable form at /.well-known/security.txt.
2. Verifying a download
Every download on the Releases page is listed with its SHA-256 checksum. Compare it with the file you downloaded before you open it:
- macOS:
shasum -a 256 AlgoagentCore-2.2.0.dmg. The 2.2.0 app is signed with an Apple Development certificate and is not yet notarized by Apple, so the checksum is the check that matters. - Windows: in PowerShell,
Get-FileHash ".\Algo Agent_0.2.9_x64-setup.exe" -Algorithm SHA256. The Windows beta installer is not code-signed yet. - Linux:
sha256sum "Algo Agent_0.2.9_amd64.AppImage", or the same with the .deb file name.
Linux downloads are also signed with the Algoagent release key, so you can check that a file is the one we built, not only that it arrived intact. The key's fingerprint is:
5F77 06C5 94CC 081B 4DE1 2FC0 7C5F 667B F14B 23B7("Algoagent Releases <support@algoagent.in>")
Fetch the key from Ubuntu's keyserver with gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys 5F7706C594CC081B4DE12FC07C5F667BF14B23B7, or import it from this site with curl -fsSL https://algoagent.in/algoagent-release-key.asc | gpg --import. Save the .asc file listed beside the download, then run gpg --verify "Algo Agent_0.2.9_amd64.AppImage.asc" "Algo Agent_0.2.9_amd64.AppImage". A genuine file prints Good signature from "Algoagent Releases"; check that the fingerprint GnuPG shows matches the one above. The warning that the key is not certified with a trusted signature is normal for a key you have not signed yourself. BAD signature means the file was changed or damaged: delete it and download it again. The release key's private half exists only on our build machine.
The desktop apps update themselves only with an update whose signature matches the public key built into the installed app, and they refuse one that does not.
3. What the app sends over the network
Your holdings, research database, chat history, API keys and broker credentials never go to us. The apps send no usage analytics and no crash reports. What does leave your computer:
- To our account server (api.algoagent.in). When you sign in: the Google authorization code or Apple identity token, which the server checks with Google or Apple and exchanges for a session, or your email address and password, of which the server keeps only a bcrypt hash. Repeated wrong passwords pause sign-in for that account and network address for a while, and a new email account signs in only after its address is confirmed. At launch: that session token, to confirm it is still valid. At sign-out or account deletion: the token again, to end it. The server stores your email address, your sign-in identifier and a hash of the session token, as the Privacy Policy describes. When you sign in on another device, it also keeps the short code, the public half of that sign-in attempt and the address it ends on, for at most ten minutes.
- To the update service (api.algoagent.in). Your app version, platform and package type, with no account token and no system profile. Downloads come from the same service or dl.algoagent.in.
- To Google or Apple. Sign-in happens in your browser, on their pages. We never see your Google or Apple password.
- To the providers you connect, with your own keys. The AI model provider you choose receives your messages and the holdings and research context a request needs. Gemini Live receives microphone audio while voice is on. Your broker (Zerodha Kite) receives sign-in and holdings requests: the app has no order endpoint and never places a trade. Market-data, fundamentals and news sources receive the queries and identifiers they answer. Messaging channels you turn on receive the exports you send them.
Inside your computer, the research core listens only on 127.0.0.1 and accepts only the app, through a token made new at each launch. The Privacy Policy has the full detail for each of these.
4. How the app keeps what it stores
- Keys and sign-in. The app keeps them in your operating system's credential store: the Keychain on macOS and iPhone, Credential Manager on Windows, and the Secret Service (GNOME Keyring or KWallet) on Linux. Your sign-in session and your Zerodha API secret can never be shown in the app's window. Other keys are shown back only after Windows or Linux confirms it is you; the Mac app does not show them back at all.
- Linux without a keyring. On a server, in a container or on a minimal desktop where nothing provides the Secret Service, the app keeps them in an encrypted file in its data folder, readable by your user account only. The file is sealed with AES-256-GCM under a key derived from the computer's machine ID and your user ID. A copy of the file taken to another computer cannot be opened, but a program running as you on the same computer could derive the key and read it. A keyring also locks secrets with your login password, so it protects them better; the app shows this trade-off wherever the file is in use.
- The research core. The bundled Python runtime is sealed at build time; the app checks its SHA-256 at every launch and refuses a runtime that was changed.