privacy policy

Last updated: June 26, 2026

NEMESIS is designed to collect the minimum operational data needed to run approval-first wallet agents. This policy explains what data is collected, why it is used, where it may be sent, and what you can control.

1. Data we collect

We collect your public EVM wallet address, SIWE session data, agent configurations, proposal records, transaction hashes that you submit for confirmation, and Telegram Chat ID when you link Telegram. We may also store operational runtime state for agents, such as last checked prices, last proposal time, seen token or pair identifiers, and proposal lifecycle status.

2. Data we do not collect

NEMESIS does not collect or ask for your seed phrase, private keys, wallet recovery phrase, exchange login, payment card data, government ID, or custodial credentials. Do not enter secrets into the app, Telegram bot, or Master Agent chat.

3. How data is used

We use wallet addresses to authenticate sessions, enforce ownership checks, store agent configuration, route proposals, and verify transaction confirmations. Telegram Chat IDs are used only to send proposals and bot responses to the linked chat. Runtime state is used to avoid duplicate proposals and keep agent checks consistent.

4. Master Agent and LLM processing

When you use the Master Agent chat interface, your natural-language prompt, recent conversation messages, and current Base ETH balance may be sent to OpenRouter and the configured model provider to generate a structured strategy plan. NEMESIS does not include your wallet address in the LLM prompt. Do not include private keys, seed phrases, sensitive personal data, or confidential information in prompts.

5. Third-party integrations

NEMESIS uses third-party services to operate, including WalletConnect, Telegram, OpenRouter/model providers, Supabase/Postgres, Railway, Base RPC infrastructure, price feeds, DexScreener, and wallet software selected by the user. Data sent to or generated by these services may be handled under their own terms and privacy policies.

6. Retention

Agent records remain while the agent exists. Old skipped proposals are pruned automatically after 7 days. Approved proposal records and transaction hashes may be retained for auditability and user-facing history. Telegram links can be removed at any time with /unlink, which clears the stored Telegram Chat ID for the linked wallet.

7. Security controls

NEMESIS uses SIWE authentication, signed wallet sessions, ownership checks on sensitive routes, cross-origin rejection on mutating web routes, one-time Telegram link codes, and transaction confirmation checks that compare signer, chain, destination, value, and calldata against the stored proposal payload.

8. Your choices

You can disconnect your wallet in your wallet UI, unlink Telegram with /unlink, pause or resume agents from the dashboard or bot, and decline any proposal by not signing it. You can request deletion of operational records by contacting the project owner through the official NEMESIS support channel.

9. Review status

NEMESIS legal, privacy, and terms content has completed an internal product compliance review for the current release. This is not a statement that external legal counsel has reviewed or approved the product.