Privacy

The Azul RPC endpoint (https://rpc.baseazul.dev) does not log:

• IP addresses
• Request bodies — the JSON-RPC payload itself
• Response bodies
• Wallet addresses
• Headers that could identify you
• Cookies — none are set on the RPC path

We retain no per-request records. There is nothing to subpoena, share, or sell.

• We do not issue API keys, so there is no user account linkage to your activity.
• We do not sell user data.
• We do not correlate Azul usage with any other service.
• We do not transmit identifying headers (X-Forwarded-For, Forwarded, Via, etc.) outside our infrastructure.
• We do not run any third-party analytics, pixels, or trackers on the RPC endpoint.

Anonymous, aggregate operational counters:

• Total requests per minute, bucketed (no per-client breakdown)
• Latency percentiles (no client identifiers)
• Upstream error rate (no client identifiers)

These are bucketed counters with no identifier dimensions attached. They cannot be used to identify a user. They exist to detect outages and capacity-plan.

This site (baseazul.dev) uses Vercel Analytics and Vercel Speed Insights for aggregate page-view and Core Web Vitals metrics. Both:

• Are cookie-free
• Do not persist IP addresses
• Are scoped to baseazul.dev only — they do not run when you point a wallet or library at the RPC endpoint

The Azul entry in ethereum-lists/chains is marked tracking: "none". This page is the backing claim. If anything here becomes inaccurate, the chainlist entry will be updated in the same change.

Material changes to this policy will be reflected in the “Last reviewed” date at the top of this page.