Rootlynq

Trust Center

Honest by design

Rootlynq separates what it measured from what it inferred, and tells you exactly where your data goes.

No speed test before Start

Opening Test loads the app, checks the Cloudflare measurement node, and asks the browser for device location when that setting is on. Download, upload, and response measurements begin only when you press Start.

Local reports

Tests and saved reports work without an account. Up to 20 reports are kept for 30 days in this browser. Nothing is uploaded automatically. Helios requires a free Rootlynq sign-in.

Bounded measurement providers

When Test opens, a small Cloudflare metadata request identifies its serving edge. With location details on, your browser also asks permission to show your device city; after approval, a rounded location is sent through Rootlynq to Geoapify when configured, or through Rootlynq’s Fly probe to OpenStreetMap Nominatim. After Start, Rootlynq’s engine uses Cloudflare for bandwidth and may use a separately qualified Rootlynq node for an independent path. Helios may review sanitized server measurements in shadow mode. Optional Cloudflare Calls TURN handles the real-time quality path. Resolve voice calls send microphone audio to OpenAI GPT Live only after you press Talk to Helios and grant microphone access. First-party Rootlynq aliases handle web/setup and IPv4/IPv6 probes. See every destination.

Your public IP stays page-only

The Test card can show the public IP and registered network name Rootlynq observes after Start. Full/partial IP, ASN, and location are never saved in reports or sent to Helios. A coarse provider/network name and browser-reported connection type may be kept only in the active browser-session case so Helios can research relevant provider behavior. 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 Windows preview

    The optional Windows companion can share bounded, read-only PC and gateway evidence after account sign-in and pairing. Other platforms remain future work.

  • 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.