Algoagent Core — algoagent.in
Last updated: October 16, 2026
1. Scope and summary
This notice explains how K S V N ANAND SAGAR, the operator of Algoagent Core, handles information in the native apps, on this website, in the browser demo, and in support correspondence. Contact support@algoagent.in for privacy questions or requests. The website distributes the macOS app and beta builds of the Windows and Linux apps; references to iPhone describe development builds, not an App Store availability announcement.
Local-first does not mean offline or that nothing leaves your device. Native-app holdings and research are stored on your device. Connected features send credentials and relevant context directly to your chosen providers. Our account service stores identity and session information, not a copy of that research database. The browser demo is different: messages pass through our hosted service to Google Gemini and are stored briefly. Do not submit private holdings, documents, passwords, or API keys to the demo.
This policy describes processing; it is not blanket consent to unrelated uses. See Support & FAQ for setup and deletion instructions and Terms of Service for terms of use.
2. Accounts and updates
The desktop app requires an account: Google, Apple, or an email address and password. Current desktop code validates saved sessions with the account server before opening the workspace; a saved token does not guarantee offline access. On iPhone, sign-in is optional. Available sign-in methods depend on the build and provider configuration.
Our Cloudflare-hosted account database stores:
- An internal account ID, sign-in provider and subject ID, email address (including an Apple relay address where used), email-verification status, and account creation time.
- Session IDs, token hashes, and creation, last-use, expiry and revocation timestamps. The app keeps its session credential in the operating system credential store (Keychain on macOS and iPhone, Credential Manager on Windows, Secret Service on Linux, or, on a Linux system without one, an encrypted file that only your user account can read, sealed with a key derived from that computer's machine ID); the account database stores its hash rather than the usable Algoagent session token.
- For Sign in with Apple, the Apple client ID and a revocation credential so we can revoke authorization when the account is deleted. This is separate from the hashed Algoagent session token.
- A one-way fingerprint and expiry of each used provider sign-in proof, to prevent reuse. Raw identity tokens are not kept in this replay-protection table.
- For an email account: a bcrypt hash of the password, never the password itself. Until the address is confirmed the account cannot sign in, and one never confirmed is deleted seven days after sign-up.
- Single-use links mailed to confirm an address or choose a new password, stored only as a hash. Each is deleted when used, when a newer one replaces it, or when it expires (24 hours for confirmation, one hour for a new password).
- Counters that limit sign-in failures, sign-ups and mailed links, keyed by a hash of the email address and by IP address (or IPv6 network prefix). They are deleted after a day without new attempts.
- When you sign in on another device: the short code shown in the app, the public values of that sign-in attempt, and the address the other device's browser ends on. These are deleted once the app collects them, or after ten minutes.
Google and Apple process their sign-in flows. We do not receive your Google or Apple password. For email accounts, Resend delivers the confirmation and password-reset emails and the notice sent when someone tries to sign up with an address that already has an account; it receives the address and the message. Different sign-in identities can create separate accounts; matching email addresses do not automatically link them. We use these records to authenticate sessions, handle account requests, and provide support. Algoagent has no billing system or payment-card collection; your own providers can charge separately.
Desktop builds with update checking enabled request the public update feed after launch, without an Algoagent session token or system profile. Hosting infrastructure receives connection information such as IP address and app user-agent/version. Updates are installed only after you choose to update; availability depends on the installed build.
3. Native-app requests to other services
The native apps do not upload their holdings or research database to our account service and do not include automatic usage-analytics or crash-report uploads to us. Operating-system diagnostics and files you send to support are separate. Connected features use the network:
- Models: messages, selected holdings, research context, and relevant document extracts go to the model endpoint you configure using your credentials. Research and audit calls may use different configured providers. Review the endpoint, provider policy, and account settings before using confidential material; retention and training practices vary.
- Brokers: authentication and holdings or market-data requests go to your broker. The app uses read-only data operations and blocks order paths. This does not reduce the credential's permissions at the broker; protect it and choose restricted permissions where available.
- Research, news, and search: queries, identifiers, document URLs, and required credentials go to the relevant vendors, exchanges, RSS services, or publishers, along with ordinary network metadata such as IP address. Opening a news link contacts its publisher; loading a news thumbnail can also contact the publisher’s image host. On iPhone, typed company searches go to Yahoo Finance for listing suggestions. Coverage depends on platform, build, and provider setup.
- Voice: Gemini Live sends microphone audio to Google for transcription while voice mode is open. If you add your own Gemini key, your credentials are used. Otherwise, when you are signed in, our account service gives the app a short-lived token on our Gemini credentials, which use Google's unpaid API quota: Google can use that audio and its transcript to improve its products, and human reviewers may process them, under the Gemini API terms linked below. Hosted Live is unavailable in the EEA, UK and Switzerland and in regions Google does not serve; it is limited per account and per day. The token goes to the app only; our service does not receive your audio. On phones, Live is off until you turn it on in Voice settings. The local speech fallback uses on-device recognition where supported. Recognized text can become chat or research requests to your model provider. Read the voice panel's transport notice before starting.
- Sharing: exports go where you choose to save or share them. Optional desktop delivery channels send exported dossiers to your configured messaging service or SMTP server. Channels are off by default. The provider and recipients receive the content; a public channel can make it public.
Native-app provider credentials are stored locally and sent to the configured service for authentication, not to our account service. If you paste credentials or portfolio information into demo chat or support email, we receive what you send. Never send secrets to support.
4. Local storage
Device data can include holdings and history, research and revisions, chat history, preferences, supplied documents and figures, cached news, and diagnostics. Fetch receipts record source metadata such as URL, checksum, and timestamp, with retrieved text while cached. Receipts are not a permanent archive: current desktop core code prunes fetched text older than 14 days when the research store opens. Metadata remains; checks may require fetching the source again. Other caches and supplied documents have separate lifecycles.
There is no account-based synchronization or cloud backup of your research. Device backups, shared folders, and exports may create copies under your settings. Local research files do not have the same protection as credential-store entries; secure your device and backups.
Deleting an account does not erase local data. Uninstalling the desktop app alone can leave app data and credential-store entries. Deleting the iPhone app removes its container, but Keychain entries can survive uninstall. Remove saved credentials in the app first and revoke provider credentials if needed. Device-only iOS Keychain items are not synchronized through iCloud Keychain or migrated to another device. We cannot remotely erase your device or shared copies.
5. Website and browser demo
Cloudflare serves the website, downloads, account API, and demo. Requests expose IP address, approximate country, user-agent, requested path, and request time to hosting infrastructure for delivery, operation, and abuse prevention. We do not embed advertising trackers or third-party analytics scripts; hosting services still process request data.
Bot check: starting a demo chat or a website-help chat, and the website sign-in page, use Cloudflare Turnstile, an invisible check that tells people from automated traffic. It loads a script and frame from challenges.cloudflare.com, which receive your IP address and browser and device signals; our service then sends Cloudflare the check's one-time token and your IP address to confirm it. Elsewhere on the site Turnstile is not loaded. See Cloudflare's Turnstile privacy addendum.
The demo saves your theme choice and selected tab in local storage. The homepage saves its film-pause preference, and the website-help button saves the edge and height you dock it at, for the tab in session storage. Remove these preferences through your browser's site-data controls.
Demo chat: no Algoagent sign-in or personal provider key is required. When you send or clear a conversation, the service sets or replaces a random session cookie named demo_sid, lasting up to 30 minutes and limited to the demo API path. Our Cloudflare Worker sends your message, recent conversation, and fictional demo context to Google Gemini using our service credentials. Chat responses are generated by a model; broker connections, prices, dossiers, and research controls elsewhere in the demo are illustrative.
The demo stores up to eight recent messages (including replies), session timestamps, turn counts, and token counts. Deletion of session state is scheduled 30 minutes after the last successful turn. The open tab also keeps its chat list and transcripts in memory until you delete them or reload. Opening a new chat keeps earlier transcripts in that tab; they are not an account-based archive. Separate abuse counters keyed by IP address (or IPv6 network prefix) are scheduled for deletion 48 hours after their last counted request. These are operational limits, not an anonymity guarantee. Sessions expire after 15 minutes idle or 30 minutes total; message and daily limits also apply.
Clear history in the chat menu requests deletion of the active hosted conversation and removes the tab’s chat list and transcripts after success. Deleting the live chat also requests server deletion; deleting an older chat removes its in-memory copy. Failure is reported for retry. It does not erase hosting logs, abuse counters, or information already processed by Google. If you lose the session cookie, automatic expiry still applies to stored state. Clearing browser site data alone does not send a server deletion request.
The demo uses Google Gemini’s unpaid API quota; billing is not enabled. Under the Gemini API terms, Google can use submitted content and responses to improve its products, and human reviewers may process them. Demo chat is unavailable in the EEA, UK, and Switzerland because Google requires paid service for those users. Country eligibility is checked using hosting-provider location metadata; chat is also unavailable in other unsupported regions or when location cannot be established. Do not use the demo for confidential or personal information. Our session-retention window does not set Google's retention period.
Demo voice: opening the voice panel does not start recording. Start listening requests microphone access and uses your browser's speech service, which may send audio to its provider. Recognized text goes to hosted demo chat. Spoken replies use browser speech synthesis; processing depends on the voice selected. Our demo endpoint receives text, not microphone audio. Stop or close the panel to end listening. Voice is unavailable in the homepage preview.
6. Support and purposes
Website help (“Ask Algoagent”): this is a separate AI service for questions about the website and the app it describes. Adults 18+ can start it after reading its notice. Questions, up to three recent verified question-and-source pairs, and public website excerpts go through our Cloudflare service to Google's unpaid Gemini API. Google may use that content for product improvement and human review under the terms linked above. Do not submit personal, confidential, or financial information, or credentials. The same country restrictions described for demo chat apply.
The tab keeps a random support-session token in memory, not a cookie or local storage. Temporary Cloudflare Durable Object storage holds session timestamps, turn counts, up to three recent verified questions and source identifiers. Expiry and deletion are scheduled for 30 minutes after activity or one hour after creation, whichever comes first. Responses quote public website passages; the service cannot inspect your account or your native-app sessions. Clear chat requests deletion of the active support conversation and cancels pending work. Errors are shown for retry. Closing the tab loses its token; automatic expiry still applies.
Separate support abuse counters use an IP address or IPv6 network prefix to derive a counter identifier; this is not an anonymity guarantee. Counter deletion is scheduled 48 hours after activity. Clear chat does not delete those counters, hosting logs, backups, or Google-held data. A provider timeout does not prove that a question was never processed. Support AI availability depends on provider quota and service limits.
When you email support@algoagent.in or bugs@algoagent.in, we and our email service provider receive your address, message, and attachments. We use them to respond, troubleshoot, and handle account or privacy requests. Send app and operating-system versions and a redacted description. Review screenshots and diagnostics; exclude keys, tokens, account numbers, private holdings, and unrelated documents.
We use the information described here to provide requested features, authenticate accounts, deliver files, prevent abuse, and respond to requests. We do not sell personal information or use it for advertising or cross-site tracking. Provider processing described above is separate.
7. Retention and deletion
- Account: kept while it exists. Use Account → Delete account in the app, or email us from the account address if you cannot open it. We may need to verify ownership. Success removes the account and its sessions from the active database and revokes stored Apple authorization where applicable. A failed request is not deletion; retry or contact support.
- Sessions: expire 90 days after creation, not last use. Expired and revoked sessions are removed by bounded hourly cleanup. Sign-out revokes the current session but leaves the account. Account deletion removes all its sessions. Neither action erases local research or third-party accounts.
- Sign-in proof fingerprints: retained separately after sign-out or account deletion to prevent an unexpired proof from creating another session. They become eligible for hourly cleanup when the provider proof expires.
- Demo: conversation and counter deletion are scheduled as described in Section 5; upstream providers have separate retention.
- Website help: session and abuse-counter deletion are scheduled as described in Section 6; Google's retention is independent.
- Support and operational records: our retention policy is one month for support correspondence, hosting logs, and backup copies. Deleted database records may remain in backups until that cycle expires. This does not change the shorter demo windows or independent retention by Google and other providers.
- Local and third-party copies: remove device data, exports, backups, and provider-held content separately. Account deletion does not cancel provider billing or revoke your model or broker keys.
After deletion the desktop workspace requires a new sign-in; iPhone can continue signed out. Signing in again can create a new account.
8. Providers, locations, and security
We use Cloudflare for hosting, storage, and request protection; Google and Apple for sign-in; Resend for account emails; Google Gemini for demo responses; and an email provider for correspondence. Your native-app providers and sharing destinations receive the requests you configure. See Cloudflare's privacy policy, Google's privacy policy, Apple's privacy policy, Resend's privacy policy, and your chosen providers' policies.
Services may process information outside your country. We do not promise India-only storage or processing. Applicable rights and required transfer safeguards depend on service and jurisdiction; contact us for information relevant to you.
Public services use HTTPS, and Algoagent account tokens are hashed in the account database. Credentials, local databases, and provider requests have different protections. No system is perfectly secure. Protect your devices and accounts and revoke exposed credentials.
9. Rights and children
Depending on applicable law, you may have rights to access, correct, delete, or restrict use of personal information, object to processing, withdraw consent where processing relies on it, and complain to a competent data-protection authority. Email support@algoagent.in to make a request or raise a grievance. We may request proportionate verification, never passwords or API keys. These rights are not limited by how little information we hold or by the Terms' governing-law clause.
The apps and demo are intended for adults aged 18 or above (or the age of majority where higher). They are not directed at children. Contact us if you believe a child has provided personal information so we can investigate and address it.
10. Changes and contact
We revise the date above when this notice changes and describe material changes on the website or in the app where practicable. Operator: K S V N ANAND SAGAR. For privacy or account deletion, email support@algoagent.in. For technical bugs, use bugs@algoagent.in.