Your data isn't kept.
It's displayed and discarded.

When your browser loads Libreprobe, a Cloudflare Worker reads the following from inbound request headers:

• Public IP address — from CF-Connecting-IP
• City, region, country, continent — from Cloudflare GeoIP
• ISP name and ASN — from BGP routing data
• TLS and HTTP protocol versions
• Cloudflare edge PoP code and Ray ID

These are read, formatted, and returned as JSON. Libreprobe itself does not store, log, or retain this data after the response is sent.

• No persistent storage of any kind
• No analytics, tracking, or profiling
• No advertising
• No third-party data sharing for commercial purposes

The Stability tool saves your selected provider preference in localStorage. This stays in your browser — it is never transmitted to Libreprobe's servers.

The Stability page sends HTTP requests to measure responsiveness. Two cases:

• Worker ping (/api/ping) — Libreprobe's own Cloudflare Worker. Processed as described above.
• Third-party endpoints — Cloudflare, jsDelivr, and unpkg are available as probe targets. Requests to these go directly to the provider's infrastructure and are governed by their privacy policy, not Libreprobe's.

Round-trip times, sample counts, and error rates are measured in your browser and never sent to Libreprobe.

Libreprobe is stateless. Cloudflare is not.

Cloudflare Pages and Workers operate within Cloudflare's infrastructure, which retains standard access logs in accordance with its own operational and security policies. These are outside Libreprobe's control and governed by Cloudflare's Privacy Policy.

Cloudflare may set a short-lived security cookie (__cf_bm) to distinguish legitimate traffic from automated abuse. It expires automatically and is not used for tracking.