PulseNet / Legal
This is the one MSRX app that keeps a record, so here is exactly what it keeps.
Last updated 14 September 2026
There is no account and no tracking; page views are counted anonymously. Speed-test results are saved — the measurements plus your ISP's name and a city-level location — and that history is publicly readable. Your IP address is not stored.
Most MSRX apps store nothing at all. This one does, which is why this notice is specific rather than reassuring.
For the purposes of India's Digital Personal Data Protection Act 2023 the data fiduciary — and the data controller under UK and EU GDPR — is Mrinal Singh Raja, an individual publishing under the name "MSRX".
When you run a speed test, the result is saved so the dashboard can show a history and the AI copilot can comment on trends. What is saved is the measurement — download, upload, latency, jitter, packet loss and the derived score — together with your ISP's name, a city-level location and a connection type.
Your IP address is shown to you on the speed-test page, because it is useful to see. It is not stored. Until 10 September 2026 it was, and the stored addresses have since been erased.
Saved results are not tied to an account, a cookie or a device identifier, so there is nothing linking one result to another or to you. They are deleted automatically after 90 days.
The history is public. Anyone can read the recent results, including the ISP and city labels. Do not run a test you would not want listed there.
Uptime monitors. If you add a monitor, its name, URL and check interval are saved, along with the results of each check. There are no accounts here, so monitors are not yours in any private sense: everyone using the site sees the same list, and anyone can add to it or delete from it. Do not put a private hostname, an internal URL or anything confidential into one.
DNS lookups are no longer stored. Until 10 September 2026 every lookup wrote the domain you typed, where it resolved and which organisation owns it to a table that nothing ever read back. A permanent record of what people looked up, serving no purpose, is data collected for its own sake. The write was removed and the stored rows erased.
Until that date, every speed test also wrote the caller's raw IP address to the same table, and the endpoint that serves the history returned it to anyone who requested it. That was wrong: an IP address is personal data, it was collected with no notice and no retention limit, and it was disclosed to third parties.
The endpoint no longer accepts, stores or returns an IP address, and the 96 addresses already held were erased. It is recorded here rather than quietly fixed, because a privacy notice that hides its own history is not worth reading.
When you ask the copilot something, your question and the recent measurements are sent to Groq, our model provider, to generate the answer. Nothing else goes with it, and the exchange is not stored.
Our host, Vercel, records ordinary request logs: time, path, status code and IP address. These exist to keep the service running and to stop abuse. They are Vercel's standard retention, are not joined to the speed-test history, and are not used to profile you.
We count visits with Vercel Web Analytics, which is part of the service that hosts this site. It sets no cookies and stores nothing on your device. For each page view it records the page address, the site that linked you here, an approximate location (country, region and city) worked out from the request, and your browser, operating system and type of device. Anything after a ? or # in the address is removed before the count is sent, because that part can hold something you typed.
It does not store your IP address. Visitors are told apart only by a hash of the request that Vercel discards after 24 hours, so a page view cannot be tied to you, to your other visits, to a speed-test result, or to what you do on other websites. What we see is totals: how many people opened which page.
On this plan Vercel shows the figures for a month and may keep them longer, and we copy the daily total for each app into a private dashboard. Neither describes any individual. We count visits because knowing whether an app is used is in our legitimate interest, and the count is built so that it cannot identify you. A content blocker, or turning JavaScript off, stops the count and changes nothing else about the site.
This is a network diagnostics tool and is not directed at children. It asks for nothing about anybody, of any age.
You may ask what personal data of yours we hold, have it corrected, or have it erased. Because results carry no identifier, we usually cannot tell which entries are yours — if you want one removed, tell us roughly when you ran it and from which ISP and we will find and delete it.
Requests and complaints go to Mrinal Singh Raja at mrinalsinghraja@gmail.com. That address is also the grievance contact for the purposes of India's Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021. We aim to acknowledge within 24 hours and resolve within 15 days.
If you are in India you may also complain to the Data Protection Board; in the EU or UK, to your national data protection authority.
Material changes move the date at the top of this page.
This page describes how PulseNet actually works, in plain language. It is not legal advice and has not been reviewed by a lawyer. Terms · Disclaimer
MSRX