Skip to content
Argus

Privacy policy

Last updated 13 November 2026

This policy describes exactly what Argus stores and why. We collect the minimum needed to run the service.

What we store

  • Account: your email address and a password hash (Argon2id). We never store your password.
  • Sessions: a SHA-256 hash of your session token and its expiry. The token itself only lives in an httpOnly cookie in your browser.
  • Analyses: the assets you analyze, the market snapshot, every analyst's vote and reasoning, and raw model responses (kept for audit and debugging).
  • Credits: your balance and a ledger of every charge, refund and grant.
  • Sealing: if you seal with your own wallet, the transaction hash and your wallet address.

What becomes public

Unsealed analyses are private to you. Sealing a decision publishes it: its decision page (votes, reasoning, snapshot, hashes) becomes publicly viewable and its hashes are written to a public blockchain, which cannot be deleted. Public pages never show your email or account id. If you sealed with your own wallet, your wallet address is visible on-chain and on the decision page.

Cookies & local storage

  • argus_session — strictly necessary, keeps you signed in (7 days, renewed while active).
  • Theme preference — stored in your browser's local storage.

We do not use advertising or cross-site tracking cookies.

Service providers

  • Hosting and database providers process the data above on our behalf.
  • AI model providers (e.g. Groq, OpenRouter, Google, OpenAI) receive market data and analyst instructions only — never your email or account details.
  • Market data providers (CoinGecko, CryptoCompare, alternative.me) receive the asset symbol being analyzed.
  • Rate limiting may process your IP address transiently (for up to 15 minutes) to prevent abuse.
  • Charts are embedded from TradingView, which receives standard request data when the widget loads.

Retention & your choices

You can change your password or sign out of all devices from your account page. To export or delete your account data, open a request via the project's GitHub repository. On-chain records and the public pages of sealed decisions are retained, because deleting them would break the public audit trail they exist to provide; they contain no account identifiers.