Security & Compliance

• End-to-end TLS with certificate validation by default.
• Sensitive operations are written to audit logs (key creation, permission changes, quota updates).
• Organization-level RBAC with least-privilege access.
• Anomalies trigger automatic throttling, blocking, or manual review.

Contributor Rights Boundaries

• Contributors can pause sharing at any time and exit the scheduling pool immediately.
• Supports local policies such as Wi-Fi only, charging only, and daily limits.
• The platform does not require exposure of local business data.

FAQ

Q: Can enterprises keep a fixed exit IP?

Yes. Use sticky sessions with ttl_seconds.

Q: How can I reduce 429/503 responses?

Lower concurrency, use exponential backoff, relax geo constraints, and configure multi-zone failover.

Q: What happens if a contributor goes offline?

The node stops carrying requests immediately and no new earnings are generated.

Q: How should API keys be secured?

Use a secret manager, rotate keys regularly, and never store keys in plaintext on frontend or client apps.