Privacy
Privacy Overview
Xbinodes keeps this simple: some account and request data must be stored to operate the service, protect the infrastructure, and show you usage inside the dashboard.
What is stored
- Account details such as email, password hash, subscriptions, and API keys.
- Request metadata such as chain, method, timestamp, latency, response status, and aggregated usage.
- Operational details such as IP address, user agent, or country when needed for security, abuse prevention, or analytics.
What is not promised
- This is not a zero-log or anonymous relay service.
- If you use Xbinodes, some request metadata will be processed so the platform can enforce limits and keep the service stable.
Why data is used
- Authenticate API keys and subscriptions.
- Enforce rate limits and monthly quotas.
- Monitor service health, prevent abuse, and diagnose incidents.
- Show usage and analytics in your dashboard.
Sharing
Xbinodes is not selling your usage data as a product. Data may still pass through essential infrastructure providers such as hosting, payment, email, or CDN services when needed to run the platform.
Retention
Logs and analytics may be retained for operational and reporting reasons. Exact retention periods can change as the service grows.
Questions
If you need a stricter privacy model for a production workload, ask first at [email protected].