No cookies
This site sets no cookies of any kind, and uses no local storage. There is nothing to consent to, which is why you are not being asked.
Privacy
This site sets no cookies and asks you for nothing.
ProdIPData is a set of static files. There are no accounts, no sign-in, no forms that submit anything to us, and no tracking scripts. You can read every page and download every dataset without telling us who you are. This notice sets out the little that does happen, and who else is involved when you load a page.
See also the dataset licence, the publication methodology, or how to reach us.
No accounts
Nothing on this site requires registration. Dataset packages are password-protected, and the password is sent by email on request — that request is the only thing we ever ask you for.
No advertising
Nothing here is monetised. No advertising networks, no data brokers, no third-party marketing tags, and nothing about you is sold or shared for anyone else's marketing.
Visitor measurement
We use Cloudflare Web Analytics to count page views. It is cookieless: it sets nothing on your device, stores no identifier for you, and does not fingerprint your browser. It reports aggregates only — how many people opened a page, roughly where in the world, which referrer sent them, which browser they used.
We cannot single you out in it, follow you between visits, or match you to anything else. If you block it, everything on the site still works exactly the same.
Until 10 September 2026 this site used Google Analytics and, from around April 2026, Microsoft Clarity session recording. Both loaded before you had agreed to anything, and this notice did not exist. Both have been removed.
If you visited before that date your browser may still be holding cookies they set — _ga, _ga_<stream>, _clck. Nothing here sets them any more, and the site now deletes any it finds on your next visit. You are welcome to check: DevTools → Application → Cookies, or the icon at the left of your address bar.
If you email us
contact@prodipdata.com is a forwarding address, not a mailbox. Cloudflare Email Routing passes messages to a personal inbox; Cloudflare stores nothing beyond a short activity log of the forwarding itself.
We use what you send only to reply — most often to send the release password for a dataset package. We do not add you to a mailing list, and there is no mailing list to add you to. Messages stay in that inbox unless you ask us to delete them.
The data correction form does not submit anything to us. It assembles a message and opens it in your own email client, so nothing leaves your machine until you press send, and you can see exactly what it says first.
Who else sees a request
Loading a page here necessarily involves other companies, each under its own privacy terms rather than ours:
- GitHub Pages serves the site. Like any web server it receives your IP address and request details.
- Cloudflare provides DNS, the analytics beacon, and the email forwarding described above.
- jsDelivr serves the Prefix Lookup data shards, so opening that page fetches files from their CDN.
- Hugging Face and GitHub Releases host the downloadable datasets. Following a download link takes you to them.
We receive nothing from any of them beyond the aggregate counts described above.
Your choices
Because we hold nothing tied to you, there is usually nothing for us to look up, correct or erase. The exception is email you have sent us.
- Ask what we hold from your correspondence, and we will tell you.
- Ask us to delete it, and we will delete it.
- Ask how a dataset figure was derived — the methodology is public, and we will answer specifics.
Write to contact@prodipdata.com. One person reads it, so please allow a few days.
Our datasets describe the ownership and approximate location of IP address ranges, not the people using them. They are built from public registry and routing data. If you believe a record about your own network is wrong, please submit a correction.
Changes to this notice
Effective 10 September 2026. If what we collect changes, this page changes in the same commit as the code that changes it — and the change is visible in the site's public repository history, not only here.