Trust
Router One is in the request path of customer applications, so the things below need to be load-bearing: how numbers are measured, what data we hold, how we fall back when an upstream fails, and what the contractual terms are. Each card links to the canonical page for that topic.
Last updated:
Methodology
Index of how latency, pricing, retention, and availability numbers across the site are measured.
Open →Security
What Router One stores, what it never stores, transport, key handling, upstream isolation.
Open →Data retention
Per-request bodies never stored. Metadata windows. Customer-initiated deletion.
Open →Availability & SLA
Uptime measurement, automatic provider fallback, enterprise SLA with credits.
Open →Smart routing
Routing signals, weights, fallback triggers, what shows up in your trace.
Open →Pricing methodology
No hidden markup on the pay-as-you-go token line. Wallet billing is live; subscription plans are coming soon. RMB conversion and channel fees are shown at checkout.
Open →China latency benchmark
p50 and timeout rate across Beijing, Shanghai, Shenzhen. Refreshed monthly.
Open →Privacy policy
Information collection, use, sharing, and your rights.
Open →Terms of service
Service description, account responsibilities, acceptable use, payment, disclaimers.
Open →Still have questions?
Email contact@routerone.ai or reach out via /contact. Enterprise contracts can extend or adjust any of the items above under NDA.