privacy and your data
What stays in this browser, what reaches our servers, and what becomes public when you share a result. No account is needed to run a test.
Last updated: 26 October 2026
Your main controlsCompleted tests contribute to the leaderboard by default. Turn on “Keep my results off the leaderboard” in Settings to stop future reports. Opening sharing or creating a public report uploads a record that anyone with its link can read.
Measurements and browser storage
The browser calculates your live latency, jitter, loss and score from requests to LagScope’s test nodes. It stores preferences, incident history, the last result, language and theme choices, and a first-visit date used to group returning visits.
Local before-and-after comparison. You can keep one comparison in this browser, including the change you selected or named, the saved measurement summaries, the test target, measurement settings and test times. It is valid for 24 hours after you save the first test. Expired data is ignored and removed the next time the app reads it. You can discard the comparison in the app. Its saved contents stay local. We record coarse feature-use stages, such as saving or completing a comparison, without those contents. The usual leaderboard reporting and public sharing still follow the rules below.
“Reset history” clears saved incidents and the last result. It does not clear your preferences or erase reports already sent to our servers. To remove all local settings and history, clear LagScope’s site data in your browser.
The public ISP leaderboard
A completed test sends an ISP name, country, connection metrics and a random ID created for that page visit. These reports and their visit IDs are stored on our servers so repeated reports from the same visit count as one session. Leaderboard reports do not include an IP address or city.
The public board groups results by ISP and country. Your leaderboard opt-out is saved in this browser’s settings. It stops future leaderboard reports from this browser; it does not delete earlier contributions or turn off the ISP lookup described below.
Public proof links and cards
Opening the main test’s sharing panel, or choosing to create a public report in Lite, uploads a result to make a proof link. The record can contain your ISP or organization, country, test target, measurement period, metrics, incident timestamps and a result-card image. Treat the link as public: anyone who has it can read the record.
New public records and cards omit city information. Older shared card images may still contain a city. Check what you share, especially if you use a custom test target.
Proof links expire after 30 days. That access limit is not a guarantee that every stored copy is deleted on that date. Expired server records are removed when new records are saved. An image or copy someone saves can outlive the link.
IP addresses, ISP lookup and request logs
Our servers receive your IP address when you connect. To identify your ISP and approximate location, LagScope sends that IP address to ip-api.com, an external service. Lookup results are cached in server memory for one hour.
The application logs request addresses, response status, response size and timing. We have not verified how long host or proxy logs are retained, so we do not give a deletion deadline for those logs here.
Product counters
We count test starts, completed test results, sharing actions and coarse comparison stages. Existing counters use a random ID for the current tab. New journey counters use a separate random run ID held only in the current page’s memory, with context such as release, coarse device category, language and referrer group. Reloading the page creates a new run ID.
The analytics service uses these IDs in memory to match stages and saves only aggregate counters to analytics files. The counts describe observed use, not unique people or individual retention. Server restarts, changes of day and temporary matching limits can leave stages unmatched.
Daily aggregate counters older than 90 days are cleared when the service starts. All-time sharing totals are kept separately. These counter IDs are separate from the page-visit IDs stored with leaderboard reports.
Discord, assistants and other services
If you add a Discord webhook, alerts and incident details are sent to that Discord channel. Remove the webhook in Settings to stop future alerts. The webhook address is saved with your browser settings.
If you share a result with an assistant, chat app or another service, that service can receive and keep the content under its own policies. Public leaderboard and proof data can also be read through LagScope’s assistant integration.
Questions about a record
For questions about this notice or a record you shared, contact us through Discord or @lagscopeapp. Do not post private connection details in a public channel.