RootlynqTrust Center
Honest by design
Rootlynq separates what it measured from what it inferred, and tells you exactly where your data goes.
No test before you press Start
Opening Rootlynq loads only the app. Measurement and network lookups begin only when you choose to start.
Local reports
No account. Up to 20 reports, kept 30 days, only in your browser. Nothing is uploaded automatically.
Bounded measurement providers
When Test opens, a small Cloudflare metadata request identifies the measurement node. After Start, Rootlynq’s speed engine uses Cloudflare measurement transport for bandwidth, and a registry lookup can identify the network organization visible to Rootlynq. Optional Cloudflare Calls TURN handles the real-time quality path. OpenStreetMap Nominatim is contacted only when you approve device location and Rootlynq needs a city label from a browser-rounded point. First-party Rootlynq aliases handle web/setup and IPv4/IPv6 probes. See every destination.
Your network identity stays page-only
The Test card can show the public IP and registered network name Rootlynq actually observes after Start, but they are never saved in reports or sent to Helios. Optional precise device coordinates stay in page memory; only a two-decimal rounded point may be used server-side to obtain a city label.
Rootlynq capabilities
- Level 1 — Universal web diagnostics Available now
Works without router access, using browser-supported evidence only.
- Level 2 — Native diagnostics Future
iPhone, Android, Windows and macOS apps could use platform-authorized device and Wi-Fi evidence.
- Level 3 — Connected router diagnostics Future
Authorized router and mesh integrations could expose topology, radio, client and backhaul evidence.
- Level 4 — Standards integration Future
TR-369/USP and TR-181 support for compatible managed equipment.
- Level 5 — Provider integration Future
ISP integrations could expose modem, ONT, provisioning and upstream evidence.