Accounts and test results
PingWatch currently has no account or sign-in feature. After
a test, the browser stores up to five recent test summaries
in local storage under the key
pingwatch.recent-tests. A summary includes the
test date and duration, mode, region name, successful and
failed probe counts, average latency, stability percentage,
lag spike count, and quality score.
Individual measurements are held in the browser's memory while a test is running and can be exported by the user as a CSV file. The application does not upload the measured latencies or save the individual sequence in local storage. Local storage remains in the browser until overwritten by newer summaries or cleared by the user; the code does not set a time-based expiry. Other browser data-clearing behavior is controlled by the browser.
Network requests and IP address processing
Requests to the app's API are rate-limited using the client IP address exposed to Express. The server keeps an in-memory counter keyed by that address for a 60-second window and periodically removes expired counters. This is operational processing; the application code does not write those rate-limit addresses to a database or its own application log.
For WebSocket connections, the server keeps an in-memory
count keyed by the remote address while connections are
open, to limit concurrent connections. When
TRUST_PROXY=true, the configured proxy
handling can use the forwarded client address. The
WebSocket endpoint receives small ping messages and sends
an echo response; message IDs are used to match replies.
The app does not configure general request access logging. It does write server error messages to the process console. The hosting provider, reverse proxy, CDN, or network service may independently process or retain IP addresses, request metadata, and error logs. Their actual retention, location, and use are not specified by this codebase.
WebSocket regions
The available region list is deployment-configured. The browser connects directly to the selected region endpoint. If a region is hosted by a different organization or provider, that endpoint will receive the connection and network information, including the connecting IP address. The applicable privacy practices depend on the organization hosting that endpoint.
Third-party resources
The pages load DM Sans and Space Grotesk fonts from Google
Fonts (fonts.googleapis.com). The PingWatch
test page also loads the Chart.js library from jsDelivr
(cdn.jsdelivr.net). A visitor's browser
requests these assets from those providers. Those providers
may receive technical request information such as an IP
address. The homepage also requests the Google AdSense
publisher script from
pagead2.googlesyndication.com. No ad units
are configured, and the script is not included on this
policy page. Google may receive technical request
information when the script is requested. Consult Google's
current privacy and consent information for details about
its practices.
Choices available to you
You can clear PingWatch's saved summaries by clearing this site's local storage through your browser settings. You can also block or restrict third-party assets in your browser; the interface may have reduced styling or chart functionality if required resources are unavailable.
Privacy questions
For privacy-related questions, contact pingwatch.contact@gmail.com.
Future policy updates
This policy should be updated if PingWatch adds accounts, analytics, ad units or ad serving, new storage, new data uses, or additional region operators, and when relevant provider practices change. Material changes should be reflected here with a revised effective date.
This policy describes the current implementation. It is not legal advice or a statement of regulatory compliance.