Privacy Policy

Scope of this privacy policy

This privacy policy describes the public connection-testing tool and English guides on this website. The tool is designed to run without an account, payment, Wi-Fi password, personal file selection, or precise location permission. Reading a guide does not start a bandwidth measurement. A test begins when you deliberately select the start control. This privacy policy separates those actions. The distinction matters because loading a webpage and transferring test data are separate activities with different recipients and amounts of network traffic.

This privacy policy describes the implemented public experience. It does not imply that every service involved in delivering the website receives no information. Network requests necessarily expose information to the systems that handle them. The sections below distinguish local browser data from requests to the website host and requests to the measurement provider, so you can make an informed choice before testing.

Privacy policy: Information in a measurement request

As described in this privacy policy, the connection test sends requests directly from your browser to Cloudflare measurement endpoints. Cloudflare receives the IP address used to make those requests, together with ordinary request and connection information. A VPN or proxy may change the address and route visible to the endpoint. The measurement provider can process information under its own policies, separately from the local result history described in this privacy policy.

Cloudflare publishes information about its speed-testing service and privacy practices. Review the Cloudflare privacy policy and Cloudflare speed test disclosures for that provider's current explanation. This website does not claim to control Cloudflare's retention, infrastructure, or independent processing. Using its HTTP endpoints does not mean that Cloudflare endorses this website or that the site operates Cloudflare's network.

Privacy policy: Generated download and upload data

For the measurements covered by this privacy policy, the download test requests generated payloads for timing and throughput measurement. The upload test creates random bytes in browser memory and sends those bytes to the measurement endpoint. It does not browse your documents, inspect photographs, read a disk directory, or ask you to choose a file. The purpose of the payload is to create measurable network traffic, not to transfer personal content from your device.

A standard full test allows up to 96 MB of test payload across both directions. Data saver allows up to 12 MB. Protocol overhead and small timing requests are additional. The amount actually transferred can be lower, depending on connection performance and stopping conditions. Your access provider may count this traffic against an allowance or charge for it. Stopping a test cancels active requests, but cannot undo bytes that have already crossed the network.

Privacy policy: Results displayed in the browser

For the results covered by this privacy policy, the tool calculates download and upload throughput, idle HTTP latency, jitter, and loaded HTTP timing when samples are available. It also records a session identifier, completion context, timestamp, selected mode, selected profile, payload count, and elapsed duration for the result object. Missing values remain unavailable. The public tool does not attach a fabricated provider identity, exact location, or packet-loss percentage to those results.

The application does not submit the completed result object to a site-owned results database. That statement is narrower than saying no service can observe the test. The endpoint provider still receives the underlying requests described above. This privacy policy makes the distinction explicit: local calculation and local result storage do not conceal the network activity from the services carrying or receiving it.

Privacy policy: Optional local history

Under this privacy policy, history is disabled until you enable the option to remember completed results on the current device. When enabled, the tool stores up to ten completed result objects in the browser's local storage. The history belongs to that browser profile and website origin. It is not a public leaderboard, an account-synced archive, or a promise of durable backup across devices.

You can clear the entries using the history control. Turning off the history option also removes the saved entries. Browser settings can clear site data independently, and private browsing or storage restrictions may prevent history from working. Someone with access to the same browser profile may be able to view the saved results. Avoid enabling local history on a shared device if that visibility is not appropriate for your situation.

Privacy policy: Preferences, cookies, and browser storage

The storage covered by this privacy policy includes preferences. The public interface can use browser storage for its history preference and the site's presentation or language behavior. The underlying site framework may also handle ordinary session cookies for separately accessed account or administration features. Those features are not required to use the public connection test. A browser's own site-data controls let you inspect or remove stored information, subject to the behavior of that browser.

This privacy policy does not describe local storage as anonymous merely because it stays on the device. A timestamped connection record can still reveal something about use of the browser. Clearing local entries removes those entries from the current origin's storage; it does not erase independently maintained hosting or provider records. Treat each category separately when deciding which data you want to retain or remove.

Privacy policy: Website delivery and operational requests

The operational processing covered by this privacy policy begins when you visit. Visiting any page sends ordinary HTTP requests to the website's hosting infrastructure. Those requests can include the connection IP address, requested path, user-agent information, and other standard headers. Infrastructure operators may process operational information to deliver content, maintain security, diagnose errors, and manage service availability. This is distinct from opting into the local measurement history.

The website currently loads Google Analytics to understand page usage. Google can receive information about page visits and the browser connection, and its scripts can use cookies. This is separate from the optional local result history; the measurement tool does not send its result object as a custom analytics event. See Google's explanation of partner-site information and its published browser controls. Optional advertising, additional analytics, or support widgets may also be enabled by the site's administrator; their deployed configuration must be reflected in this disclosure. A privacy policy should describe deployed behavior; it should not promise details about a future hosting arrangement or a third-party retention period that has not been verified.

Privacy policy: Clipboard actions and external links

The clipboard action covered by this privacy policy is optional. Selecting Copy results asks the browser to place a plain-text measurement summary on your clipboard. The application does not read the existing clipboard to run a test. Clipboard permission or browser restrictions can prevent copying, in which case the displayed values remain available for manual selection. Other applications with appropriate clipboard access may be able to read content after you copy it.

The guides link to primary documentation and other resources. Following an external link takes you to a service with its own practices. This privacy policy does not govern those external services. Before sharing a result publicly, consider whether the timestamp, connection context, or notes you add reveal information you would prefer to keep private. The copied summary does not need a Wi-Fi password, account credential, or precise address to be useful.

Privacy policy: Your choices and practical controls

The choices explained in this privacy policy are available independently. You can read the guides without starting a test, choose Data saver before measuring, stop an active session, leave history disabled, clear saved entries, or remove site data in browser settings. These controls address different kinds of processing and should not be treated as interchangeable. For example, deleting local history does not reverse requests already sent to Cloudflare, and stopping a session does not refund data charged by an access provider.

For a privacy question, email support@ispeedtest.app. Identify the page, feature, approximate time, and category of information involved. Do not send passwords or unnecessary personal files. An inquiry about the measurement provider's independent processing may need to be directed to that provider through its published privacy channels. This privacy policy is intended to help identify the relevant recipient and control, not to suggest that the website can delete information held independently by every network intermediary.

Privacy policy: Changes and interpretation

Questions about this privacy policy can be sent to support@ispeedtest.app. The date at the top of this privacy policy identifies the current content revision. Material changes to the public test, result storage, providers, or optional services should be reflected here when those changes are introduced. A content date does not claim that every external policy or infrastructure arrangement has been audited continuously. Check linked provider documents for their current terms and explanations.

Read this privacy policy together with the measurement methodology and terms of service. The methodology explains what the tool measures and its limits. The terms explain the intended use of the service. Together they provide the context needed to decide whether to run a test, how to interpret the result, and which local or external information controls apply to your particular use.