Privacy Policy

Account data: name, work email, company, billing details. Request metadata: timestamp, key, method, response code, latency, region and approximate request size. We do not store request bodies or response payloads for RPC traffic, so we do not hold the addresses you query or the transactions you submit.

Stream and webhook configurations are stored because the service cannot run without them. They include the filters and sink details you provide.

Request metadata is retained for 30 days by default, and 7 days on a residency plan. Aggregated counters, which carry no per-request detail, are retained for 13 months for billing and capacity planning. Account and billing records are retained as long as tax law requires.

On an EU-only or US-only plan, request metadata, logs and support tooling stay in the chosen jurisdiction. The default global routing policy makes no jurisdictional guarantee, and we say so on the networks page rather than in a footnote here.

We use subprocessors for hosting, email, error reporting and payments. The current list is available under NDA and in the DPA, and we give 30 days notice before adding one that processes customer personal data.

We do not sell data. We do not build a profile of your traffic to market to you.

Ask us to access, correct, export or delete your account data at [email protected]. We respond within 30 days. Deleting an account removes account data and stream configuration; aggregated billing counters survive where tax law requires it, with no per-request detail.

The marketing site sets no advertising cookies. It uses Google Analytics to measure visits, which sets first-party analytics cookies (_ga and _ga_*). You can block them in your browser or with Google's opt-out add-on without affecting the site. The dashboard sets a session cookie, which is required for sign-in and cannot be turned off while you are signed in.