https://vexthium.com/api/mcp

Legal · Vexthium

Privacy Policy

Vexthium answers your requests without needing to know who you are. Here is the short list of what it keeps, why, and for how long.

In force from
20 November 2026
Sign-up
None needed
Network address
Kept as a keyed hash
Data sales
None

1. In brief

  • Vexthium works with no account, name, email address or wallet on file.
  • Private keys and seed phrases never reach us. A prepared transaction is kept encrypted for 24 hours so its approval link can stay short, then deleted.
  • Your network address is reduced to a keyed one-way hash for rate limiting, and the address itself goes unrecorded.
  • The call log records which tool ran and how it went. Arguments and results stay out of it.
  • Creating an agent key stores your wallet address, a hash of the key and any profile text you write.
  • We sell no personal data and run no advertising or cross-site tracking.
  • Data on Robinhood Chain is public by design, and whatever you place there is governed by the chain.

The numbered sections that follow are the complete policy, and they take precedence over this brief wherever the two differ.

2. The controller

Vexthium ("Vexthium", "we", "us") runs the Vexthium MCP server and this website, together the "Service", and is the controller of the personal data this policy describes.

3. What this policy covers

The policy applies to the Service: the MCP endpoint, the HTTP API and the pages of this site, the console, the approval page and the agent keys page among them.

Services that others run fall under their own policies, even where the Service links to them or reads from them. These include your AI client, your wallet, the Robinhood Chain network and its node operators, block explorers, and protocols such as Uniswap, Lighter and Privacy Pools.

4. Data we keep

4.1 Every tool call

A tool call adds a single row to the call log with these fields:

FieldExampleUsed for
Tool nameget_blockUsage figures and fault finding
Heavy markertrue or falseCounting against the heavy call limit
Chain ID4663Usage figures per chain
Outcomeok or errorTracking reliability
Error coderate_limitedFault finding
Duration182 msTracking speed
TimeTimestampRate limiting and usage figures
CallerAgent key ID, or the client fingerprintRate limiting and usage per key

The arguments you send and the results you receive are left out of the log. A looked-up address, a simulated amount or a compiled contract is handled in memory to answer the call, and our database never receives it.

4.2 Client fingerprint

Calls without a key are counted per caller. To do that we take the network address a request came from, mix it with a secret that exists only on our servers, and compute a keyed one-way hash, of which we store the first 32 characters. The network address is never written to the database, and recovering it from the hash would take both the server secret and a correct guess of the address.

We handle this fingerprint as personal data, since joined with other information it might point to a person.

4.3 Creating an agent key

DataReason we keep it
Your wallet addressSo you can see your keys and revoke them
The one-time sign-in message and its expiryTo check your signature a single time; removed once used
A SHA-256 hash of the key and its first 12 charactersTo recognise the key on later calls; the key itself is never kept
Key name, scopes and allowed chainsTo apply the settings you picked
Agent description and capabilities, when you add themTo show in your key list, and in public when you choose that
When the key was created, last used and revokedTo show you each key's history

We check your wallet signature and then discard it. The sign-in token issued afterwards lasts 30 minutes and lives in your browser; we keep no copy.

4.4 Agent profiles made public

Marking an agent profile public places its name, description and capabilities in the agent directory and the API. The wallet address and the key itself stay unpublished. You can switch a profile back to private whenever you like; copies other people saved before then are in their hands.

4.5 Hosting logs

The companies that host and deliver the Service handle connection data, such as IP addresses, request paths, user agent strings and timestamps, to route traffic, stop abuse and diagnose faults. They act for us and keep it for limited periods on their own schedules. We keep these logs apart from the call log and use neither to identify callers.

5. Data that stays with you

  • Seed phrases and private keys. No part of the Service has a way to take them.
  • Your prepared transactions, beyond 24 hours. Vexthium builds and simulates each one, so it handles the contents. An encrypted copy is kept for 24 hours to keep the approval link short, and its key is the part of the link after #. The approval page sends the transaction back to us for a fresh simulation before you sign. Copies are deleted when they expire.
  • Names, email addresses, phone numbers and identity documents. The Service has no registration.
  • Conversations you have with your AI client. We receive only the tool calls the client decides to send.
  • Secrets for Privacy Pools deposits. For Privacy Pools the Service reads public pool data alone.
  • Advertising identifiers and cross-site tracking data.

A transaction sent through send_signed_transaction travels through our servers to the network and is passed on with no copy kept. From broadcast onward it is public, as the next section explains.

6. The public ledger

Robinhood Chain is a public ledger: addresses, balances, transactions and contract code are open for anyone to read and stay on the chain as a lasting record. The Service reads that data to answer requests. The chain itself holds it, and no single party, us included, edits it.

7. Purposes

  • Running the Service: answering tool calls and operating agent keys.
  • Applying per-minute call limits evenly to every caller.
  • Showing key owners, and their agents, the usage of their own keys.
  • Publishing combined figures, such as total calls, error rate and response times, that point to no individual caller.
  • Spotting, looking into and stopping abuse, and keeping the Service dependable and secure.
  • Meeting legal duties and establishing or defending legal claims.

We use none of this data for advertising, profiling, or automated decisions with legal or similarly significant effects, and we neither sell it nor share it for cross-context behavioural advertising.

8. Lawful grounds

Where a law such as the GDPR calls for a lawful ground, these are the ones we use.

ActivityLawful ground
Answering tool calls; creating and running agent keysPerforming our contract with you, the Terms
Rate limiting, abuse prevention, security, combined figuresOur legitimate interest in a dependable, fair and secure service
Making an agent profile publicYour consent, given by making it public and withdrawn by making it private
Answering lawful requests; keeping recordsMeeting a legal obligation

9. Processors and recipients

A short list of providers helps run the Service, and each gets only what its job needs.

RecipientJobWhat it gets
Database providerHolds the call log, agent keys and stored approval linksThe data in sections 4.1 to 4.4, and encrypted approval links
Hosting and content delivery companiesRun the application and route trafficConnection data as set out in section 4.5
RPC node providersChain reads, simulation and broadcastingThe addresses and transactions in your request, sent from our servers
Block explorer (Blockscout)History, verified source and verificationThe addresses, hashes or source code in your request, sent from our servers
Protocol APIs (Lighter)Markets and accountsThe addresses in your request, sent from our servers

Calls to RPC nodes, the explorer and protocol APIs leave from our servers, so those recipients see our servers' network address in place of yours.

Your wallet, and the RPC connection it makes for itself, talk to your browser directly without passing through us. They see your network address and follow their own policies.

We may also disclose data where the law requires it, to protect the rights, property or safety of users or the public, or to a successor in a merger, acquisition or reorganisation that keeps to this policy.

10. Processing abroad

Our providers may handle data in countries other than yours, some of which protect personal data under different rules. Where the law calls for it, we use recognised transfer safeguards such as standard contractual clauses.

11. How long we keep it

DataRetention
Sign-in messagesFive minutes, or until used if that comes sooner
Sign-in tokens30 minutes, held in your browser
Stored approval links24 hours, encrypted
Call logWhile needed for limits, usage history and figures, then deleted or combined
Agent keys and profilesUntil you ask for deletion. A revoked key stops working immediately, and its record stays so you can still see its history
Hosting logsOn each provider's own schedule

When a key record is deleted, its log rows stay but lose their link to that key.

12. Local storage and cookies

The Service sets no advertising, analytics or login cookies. The wallet connection library saves your connection state, such as the wallet you used last, in your browser's local storage so you stay connected from page to page. That data remains in your browser, never reaches us, and can be cleared from your browser settings whenever you like.

13. Protecting the data

Holding little keeps the data easy to protect: keys are stored as hashes, network addresses as keyed hashes, and prepared transactions as ciphertext for 24 hours. Only the server can reach the database, row-level security is switched on, and every connection is encrypted in transit.

Should a breach ever touch personal data, we notify the people affected and the authorities as the law requires. The Security page sets out the design in more detail.

14. Your rights

Depending on where you live, you can ask to access, correct or delete your personal data, to restrict or object to its processing, to receive it in a portable format and to withdraw consent. You can also complain to your local data protection authority.

Handled by you directly

  • Call the Service without a key, and no wallet address is stored.
  • Review your keys and their usage on the agent keys page.
  • Revoke a key whenever you choose, from that page or with the key itself.
  • Switch a public agent profile back to private.

Requests to us

Since the Service holds so little, most requests are ones you can complete yourself as listed above. For anything about agent keys we ask for a signed message proving you control the wallet, because the wallet address is the only identifier we hold. Open access usage is stored as a keyed hash that we usually have no way to connect to you; show us how it relates to you and we will act on it.

Deletion covers the data Vexthium stores. Records on the Robinhood Chain ledger stay part of the public chain.

Exercising these rights never affects how we treat you, and since we sell no personal data, there is no sale to opt out of.

15. Your AI client

You reach the Service through an AI client run by another company. The client picks which tools to call and with which arguments, and it receives the results. Its provider handles your conversation, the tool calls and the results under its own terms and privacy policy, which may permit keeping or reviewing them.

Wallet addresses, balances and transaction details that come up in a conversation are therefore visible to that provider, so pick a client whose data practices suit you.

16. Age

The Service is meant for people aged 18 and over, and we do not knowingly collect personal data from children. With no accounts, names or contact details, the Service holds nothing that would reveal a user's age.

17. Policy updates

We may revise this policy as the Service develops. The date at the top marks the version in force, and significant revisions are recorded in the changelog. A revision that meaningfully narrows your rights is announced on this site before it applies.

18. Handling it yourself

The Service lets you make your own choices directly: call it without a key, and view, revoke or unpublish anything you created on the agent keys page. Your use of the Service falls under the Terms.