Privacy notice

1. The short version

• Vectr runs no advertising or third-party analytics on vectr.bot, sets no analytics cookie, and switches the wallet connector's analytics off. It keeps its own anonymous event counts, described below.
• If you only connect your own wallet, Vectr stores nothing about you beyond what its indexer already reads from the chain.
• If you sign in with X, Vectr stores your X account id, handle and profile picture, the wallet it creates for you, and that wallet's encrypted private key.
• Everything you do on-chain is public forever: addresses, balances, trades, launches and fee claims are on Robinhood Chain and its explorer, and Vectr indexes and displays them.

2. What Vectr stores, and why

Sign-in with X

X's OAuth flow gives Vectr your X user id, handle and profile image. Vectr stores them to identify your account and to attribute creator fees for tokens launched for an X handle. Vectr does not receive your X password and cannot post as you. A short-lived OAuth session record is kept while the login completes.

Vectr wallet

Signing in with X creates an EVM wallet. Its private key is generated server-side and stored encrypted with AES-256-GCM, with a per-user data key where key-management wrapping is enabled; the address, the last login time and the account status are stored alongside. The security page reports the live state of these controls.

Session cookie

After signing in, a session cookie keeps you signed in. It is HTTP-only, secure and same-site strict in production, and it is the only cookie Vectr sets.

Product event counts

To see which parts of the product people use, vectr.bot counts a short fixed list of actions on Vectr's own server: starting or completing a launch, connecting a wallet, opening the Terminal, creating an API key, starting a trade, claiming creator fees, copying code or a contract address, following links from the docs to the product, to the source code, to the API or to npm, and one "landing" per browser-tab session. vectr.bot, swap.vectr.bot and terminal.vectr.bot also count each page view and one landing per tab session. Each one adds one to a counter for that day, that action, the site, the page path and the kind of place the visit came from: search engine, AI assistant, another site, or direct. Your browser works out that kind from the referring site when you arrive and keeps it in session storage until the tab closes; the referring address itself is never sent. Any wallet address in the path is replaced by a placeholder. No IP address, wallet, account, cookie, device or browser identifier is stored with it, and the request is sent without credentials, so a count can never be tied back to you.

Live visitor count

While a Vectr page is open and visible, your browser tells Vectr's server every 25 seconds which site and page it is on, so Vectr can see how many people are on each site right now. The message carries a random value your tab makes for itself and keeps in session storage until the tab closes, so two open tabs count as two. The server holds it in memory only, forgets it 60 seconds after the last message and never writes it to disk or a database. These counts and the live total are published at api.vectr.bot/events/traffic.

API keys

When you create an API key, Vectr stores the key, its name, the wallet it belongs to, its scope (read-only or read-write), any IP and recipient allowlists you set, and when it was last used. Revoking a key deactivates it immediately.

Agent jobs and memory

Prompts you send to the Vectr agent (Terminal, API, CLI, MCP) are stored with the model's response, the transaction it built, the model used and token counts, so you can review a job and so rate limits and credits can be enforced. Prompts are sent to a third-party language-model provider (currently Anthropic) to be answered. Agent memory you save is stored until you delete it.

Orders, subscriptions and credits

Limit, stop, DCA and TWAP orders, subscription records and LLM credit transactions are stored so they can be executed and accounted for.

Files

Files you upload to your account are stored on Vectr's server under a per-account quota until you delete them. Token logos and metadata you attach to a launch are pinned to IPFS through Pinata and are public by design.

Security logs

Security-relevant events (sign-ins, key creation, export requests, blocked transactions, anomaly flags) are logged with the IP address and user agent of the request, so that abuse can be investigated. Rate limiting also reads the requesting IP address.

Web server logs

The web server that serves vectr.bot keeps an access log for 30 days: the time, the page requested, the response code, the user agent and the referring page, with the IP address cut to its first two parts (for example 203.0.x.x) before it is written. Cookies and authorization headers are never logged. Vectr reads it to see how search engines crawl the site and to find broken links.

3. What Vectr does not do

• No sale of personal data, no advertising profiles, no third-party analytics scripts, no cross-site tracking. The only analytics are the anonymous daily counts and the in-memory live count described above.
• No email is collected; there is no newsletter.
• No decryption of your Vectr wallet key except to sign a transaction you or your read-write API key requested.

4. Third parties that see data

• X (Twitter): the sign-in provider; its own privacy policy applies to the OAuth step.
• Robinhood Chain RPC and block explorer: every transaction is broadcast to the network and is public.
• Anthropic: receives agent prompts and the context needed to answer them.
• Pinata / IPFS: token logos and metadata, which are public.
• Reown (WalletConnect): if you connect a wallet through it; its analytics are disabled in Vectr's configuration.
• Robinhood: Vectr reads Stock Token prices and the token registry from Robinhood's public API; nothing about you is sent to it.

5. Retention and deletion

Account, key and agent data are kept while your account exists. Security logs are kept for as long as needed to investigate abuse. To delete your account data, contact Vectr through the channels on the about page from the X account or wallet in question. On-chain data cannot be deleted by anyone.

6. Your rights and contact

Depending on where you live you may have rights to access, correct, export or delete the data above. Requests and questions go through the about page contact channels. Related documents: the terms of use and the risk disclosure.