What is recorded, where it goes, and how to have it removed.
Effective 2026-09-17. Signal Nodus is a human-owned service with no separate legal entity. The operator answers at hgenix@agentmail.to.
The site and its API run on Cloudflare Workers with a Cloudflare D1 database, so Cloudflare handles every request as the hosting provider under its own terms.
By activity
| When you | We record | Kept |
|---|---|---|
| view a page on signalnodus.ai | your IP address, the first 60 characters of your user agent, the path, and the time; obvious bots are skipped | IP and user agent are erased after 90 days by a daily job; the row survives only as a count |
| email us, including a request for a review | your message, at our mail provider (AgentMail) | until the matter is closed |
| take part in an incident evidence review | nothing under this page. An engagement runs under signed data terms, and the controls on the trust page apply: raw logs stay in a vault, names become tokens before anything else touches them, and every byte that leaves is logged and handed back with the pack | as the signed terms say |
| appear in a source the Watch reads | the Watch reads public filings, notices and advisories, and our own servers. It keeps the public record it found and its source link. It does not look people up | while the signal is open |
| install the gate from the gate page | nothing. It runs on your machine, writes its record to your disk, and sends nothing anywhere | nothing kept |
| call an API tool with a key (MCP or HTTP) | a SHA-256 hash of the key (the key itself is never stored), the tool name, the price charged, the time, and the SEC accession numbers the answer was built from | as the billing record for that key; the last 30 days are readable at /v1/usage |
| call a priced route without a key | your IP address, the first 80 characters of your user agent, the tool, the time, and the amount if a payment settled | IP and user agent are erased after 90 days |
take a free test key at /trial | a truncated SHA-256 hash of your IP address as the key's label, so one connection gets one key; the Turnstile check sends your IP and the challenge token to Cloudflare | for the life of the key |
| buy credit with a card | Stripe collects the card details and the receipt email; we never see the card. We store the hash of the key that was minted, Stripe's event ids, and the pack bought | abandoned checkouts are deleted after 72 hours; completed ones stay as the billing record |
| pay per call over x402 | the settlement is a public transaction on the Base blockchain handled by Coinbase's facilitator; on our side it is logged like any unkeyed call | as above; the blockchain record is permanent and outside our control |
| connect through a client's OAuth flow (Claude.ai, Claude Desktop, Claude Code) | you paste your key on our consent page; it is sealed into an authorization code that expires in five minutes and handed back to your client as the bearer token | nothing kept |
reveal the contact address on /compliance | only the Turnstile check with Cloudflare | nothing kept |
What leaves the service
The arguments you send to an API tool go to the source that holds the data: SEC EDGAR for the core tools, and for the experimental ones EIA, USDA NASS, the US Census Bureau, USAspending, the Senate lobbying disclosure database, the ECB, Polymarket, public EVM RPC endpoints, and DNS and RDAP servers. Those requests carry our identity in the User-Agent, never yours. Payment providers see what they need to take a payment. Cloudflare's error logs can include an IP address and user agent when a request fails, and Cloudflare keeps those briefly under its own policy.
What we do not do
No selling or sharing of data for anyone else's use. No advertising. No profiling. No cookies of our own; Cloudflare's Turnstile and bot protection may set theirs. An MCP client sends us only the arguments of the tool it calls, and we never receive your conversation.
Your requests
Email hgenix@agentmail.to. To find your records, give the key hash (the first characters of sha256(key)) or the IP address and approximate time. We send what we hold and delete it on request, except a billing row needed to settle an open payment dispute. A person replies within one business day.
See also the terms and how engagement data is handled.