hunch.Execution integrations · 16 October 2026
Execution requests send the supplied wallet address and unsigned calldata to the RH RPC for read-only checks. Those requests are processed in memory; Hunch does not intentionally persist customer wallet requests as background observations. Route observations, including observations collected during proposal preparation, store public contract/configuration evidence without customer requests, with a 14-day snapshot lifecycle and a retained latest record. Observation IDs referenced by receipts are publicly retrievable while retained. Infrastructure providers may process access/security logs under their own service controls.
Who this notice covers
This notice applies to the independently operated Hunch project at hunchagents.xyz and its hosted public API. Contact info@hunchagents.xyz with a privacy question or request. Hunch is separate from the issuers, networks and data providers it references.
A locally run client or MCP server sends checks to the service URL its operator configures. If you use another host or an application that integrates Hunch, that operator's handling of your information also matters.
Information you submit
- Contract and instrument checks: public addresses, token quantities and any chosen counter asset.
- Action policy checks: the proposed amount, slippage, profile and optional untrusted text.
- Simulation: the supplied caller, target, calldata, value and optional gas limit. Hunch simulates these calls; it does not broadcast them.
- Information integrity checks: the text you submit. The application runs deterministic checks and does not send this text to an LLM or use it for model training.
We use these inputs to return the requested evidence. Public wallet addresses and transaction details can be linked to a person or strategy; “public” does not mean anonymous. Submit only information you are entitled to share, and never include signing secrets or credentials.
Queries sent to other providers
| Provider | What is shared or requested |
|---|---|
| Robinhood Chain RPC | Contract addresses, requested chain reads, and simulation call objects. The default endpoint is rpc.mainnet.chain.robinhood.com. |
| DexScreener | The queried token address for indexed pool and market information. |
| Official Robinhood instrument APIs | The asset registry and, for recognized stock tokens, a symbol-specific reference-price request. |
| Microsoft Azure | Website and API traffic delivered through the hosting infrastructure, including technical connection, access and diagnostic metadata. |
| Spacemail | Email address, message content and attachments when you choose to email Hunch. |
Network and market requests are made by the Hunch server. Those providers can observe its network address and the query; simulation payloads also contain the caller address you supplied. Token quantities and text are not deliberately forwarded to market-data providers. Some legacy API routes query their original network providers; the supported RH integration routes are documented under /api/rh/.
Providers process data under their own policies and infrastructure arrangements. Data may be processed outside your country. The application does not control their logging or retention, and we do not promise that a provider deletes a query when Hunch completes your request.
Application memory and retention
The execution guard stores public route-dependency snapshots in private Azure Blob storage in Canada Central. These contain contract addresses, runtime fingerprints, issuer/administrator state, public reference quotes, observation timestamps and blocks. They do not contain the supplied wallet, wallet nonce or balance, trade amount, transaction envelope or request-specific quote. Snapshots are published through the observation API and scheduled for deletion after 14 days by a storage lifecycle rule; deletion is asynchronous. The latest index retains up to 60 snapshot summaries. The guard does not maintain a persistent user receipt database.
The application does not persist user-submitted text, wallet transaction envelopes or their individual evaluation reports, and it does not write request bodies to application logs. It has temporary in-memory caches and request counters:
- RH intelligence reports are held in a bounded cache of up to 150 entries and may be reused for 20 seconds. That is a freshness window, not an erasure deadline. Older entries can remain in process memory until replaced, evicted or the process restarts.
- The official instrument registry is reused for up to 30 seconds before a fresh request is required. Cached registry data is public instrument data.
- IP-based counters apply a one-minute request window. Expired counters are removed on later API traffic or when the process restarts.
Transient inputs and results are also present in memory while a request is processed. Hosting and provider logs have separate retention rules; this notice does not claim a fixed deletion period for them. Email correspondence remains in the project mailbox until deleted; an automatic mailbox-retention schedule has not been established.
Saved evidence, watchlists and cookies
The console uses local storage for up to 10 watched contracts and the most recent 30 reports you explicitly save. Reports may include addresses, call details and matched text excerpts. This storage belongs to the browser profile on that device; it is not an encrypted vault or a cloud account.
Use Saved evidence → Clear saved evidence, remove individual watchlist entries, or clear Hunch site data in your browser to delete local information. Exported JSON files and copies you share are separate and must be deleted separately. Removing local data does not erase public blockchain history or provider logs.
Share cards are generated on your device from the selected public asset report. Check links include the token contract, chain, view and fixed campaign labels; they do not include your saved history, wallet connection or transaction details. A recipient chooses whether to request a new check. Sharing to X opens its website with a suggested caption and link, subject to X’s privacy terms.
Watchlist refreshes send the listed contracts to Hunch. Optional polling runs while the page is open; it stops when the page closes. The current site does not set analytics or advertising cookies, load advertising trackers, connect wallets or require an account.
Your choices and requests
You can browse without running a check, decline local saving, disable polling, clear browser data or stop using the service. Hunch does not sell submitted information or use it for advertising.
Depending on the law that applies, you may have rights to access, correct, delete or restrict personal information, object to processing, or complain to a relevant privacy authority. Email info@hunchagents.xyz to make a request. Describe the relevant interaction and provide only the information needed to locate it. We may need proportionate verification before disclosing or changing personal information.
We cannot remove public on-chain records, data controlled by another provider or files held on your device. Limited information may need to be retained where required by law or to resolve a dispute. There is no Hunch user account to delete in the current public service.
Security, external links and changes
HTTPS protects data in transit to the site, but no transmission or storage method is guaranteed secure. Report concerns through the security contact. The site is intended for adult users and does not offer a children's service.
Following a link to X, a market provider or another site takes you to a service with its own privacy practices. Changes to this notice will be published here with an updated date. Material changes to data collection or a future account service should be described before that new feature is used.