Security & privacy
What we log — and what we never will
An RPC provider sees every call your app or agent makes. That is a lot of trust to hand over. NodeFlare is built to need as little of your data as possible — here is exactly what that means, in plain terms.
We never log
- ✕Request bodies — the JSON-RPC calls you make, the parameters, the addresses you look up
- ✕Response bodies — the balances, logs, traces or any blockchain data you read
- ✕Wallet addresses or transaction hashes from your queries
- ✕Any correlation between your IP address and the data you request
We keep (minimally)
- ✓Per-chain, per-month request counts keyed to your API key — for billing only
- ✓IP address — processed transiently for per-IP rate limiting and DDoS protection, never written to a log of ours
- ✓Account email (via Clerk) and payment-method type + last-4 for card payers (via Stripe)
Own infrastructure, and where its limits are
NodeFlare owns and operates its nodes on bare metal in Frankfurt, London, Falkenstein, Amsterdam, Singapore, New York, Ashburn and Los Angeles. We are not an aggregator reselling Alchemy, Infura or a pool of anonymous backends, and we do not buy the capacity we sell.
Being straight about the shape of that: the major chains run on nodes in several regions at once, so a machine or a region can be lost without interrupting anything. The younger chains — Robinhood Chain, Ink, Zircuit, Sonic and others — run on a single dedicated node each. On most of those a third-party endpoint sits behind ours to keep the chain answering while our node is down; on Zircuit there is deliberately nothing behind it, because failing over there would trade an honest error for a misleading answer. Which chain is in which position is written down in the Uptime & SLA section rather than averaged into a single number.
Access, custody and incidents
We never hold your private keys, seed phrases or funds — NodeFlare reads and relays blockchain data and broadcasts the transactions you sign yourself. Node hosts are reachable only over key-based SSH from an allow-listed set of addresses, with password authentication disabled. API keys are stored so that our dashboard and worker can resolve them; they are never exposed to browsers, because keyed endpoints are deliberately not CORS-enabled.
Every chain is probed automatically against an independent external reference each minute, so a node that stalls while still answering is detected rather than trusted. Health, per-chain block lag and recent incidents are public on our status page. For procurement or vendor-review purposes, a written security overview, the named failover providers and our sub-processor list are available on request at [email protected].
Pay without identifying yourself
The public endpoint needs no key and no account. Paid plans and CU top-ups accept crypto — no card and no KYC. Autonomous agents can pay per call in USDC over x402 with no account at all. Card payers go through Stripe; NodeFlare never stores full card numbers.
FAQ
Do you log the RPC calls I make?
No. We never store request or response bodies. We count how many requests you made per chain per month (for billing), but not what you called, which addresses you touched, or what came back.
Is my IP linked to what I query?
No. IP addresses are processed transiently for per-IP rate limiting and DDoS protection, and are never correlated with your API key, wallet addresses, or request data. We do not write them to a log of our own. Cloudflare processes them as our edge provider under its own retention policy.
Can I use NodeFlare without an account or a card?
Yes. The public endpoint needs no key and no account. Paid plans and top-ups can be paid in USDC, USDT, native ETH or SOL — no card and no KYC. Agents can pay per call in USDC over x402 with no account at all.
Who else sees my traffic?
Normally no one: your requests are served by NodeFlare's own bare-metal nodes and stop there. We are not an aggregator that routes your calls through Alchemy, Infura or a pool of anonymous backends. There is one documented exception. On chains served from a single region, if our node is unavailable the request may be failed over to a third-party RPC endpoint so the service keeps answering — which means that provider sees that request. Which chains those are is listed in the Uptime & SLA section of our Terms; the providers are named on request; and Enterprise customers can require failover to be disabled for their key.
Can I be sure my requests only ever touch your machines?
Yes, on request. Failover to third-party endpoints exists to keep single-region chains answering during an outage, but it can be switched off per API key under an Enterprise agreement. With failover disabled, a request either reaches a NodeFlare node or returns an error — it is never handed to anyone else. Tier 1 chains (Ethereum, Base, BNB Chain, Arbitrum, Robinhood Chain, BOB) are served only by our own nodes in multiple regions, with no third-party failover in the path.
How is my API key protected?
Keyed endpoints are not CORS-enabled for browsers, so your key is never meant to sit in front-end code — route keyed requests through your backend. You can rotate your key any time from the dashboard, which immediately invalidates the old one.
How do I report a vulnerability?
Email [email protected] with details and steps to reproduce. We respond to security reports first, and we won't pursue good-faith research that respects user data and avoids service disruption.
See also the full Privacy Policy (GDPR) and Terms. Security questions or disclosures: [email protected].