Privacy Policy

This privacy notice discloses the privacy practices for ip2geo.org. This privacy notice applies solely to information collected by this website. It will notify you of the following:

1. What personally identifiable information is collected from you through the website, how it is used and with whom it may be shared.
2. The security procedures in place to protect the misuse of your information.

Information Collection, Use, and Sharing

We are the sole owners of the information collected on this site. We only have access to/collect information that you voluntarily give us via email, direct contact, or use of site features. We will not sell or rent this information to anyone.

IP lookups on the main tool are not logged. With JavaScript on (the normal case), the log text you paste stays in your browser; only the IP addresses pulled out of it are sent to our server, which looks them up and does not store them. With JavaScript off, the page falls back to sending the pasted text itself; the server pulls out the IP addresses, looks them up, and stores neither the text nor the addresses. The "Copy share link" button puts the current view's IP addresses into the link itself, after the #; that part of the link is never sent to our server and nothing about the link is stored, though when the recipient opens it their browser looks the IPs up the same way as a normal lookup. Visitor analytics are collected via a self-hosted instance of Umami, an open-source, privacy-friendly analytics platform that does not use cookies or share data with third parties.

Some features store small amounts of data locally in your browser (for example, your theme preference and, if enabled, your recent lookups). This information stays on your device, is never transmitted to us, and can be cleared at any time through your browser settings.

Community Threat Intelligence

Until v5.0.0, ip2geo ran a community threat feed, the Community Block List, built from anonymized, opted-in contributions: CIDR network ranges and individual IP addresses classified as scanning or VPN/proxy infrastructure. Residential IP addresses were never collected. The feed was retired in v5.0.0: it no longer accepts contributions and is no longer published.

No tokens, email addresses, or other personally identifiable information were included in the aggregate. The aggregate tables that remain contain only network ranges, IP addresses, and counts — with no link back to any individual contribution. Consent was opt-in only. Because contributed data was immediately aggregated with no user identifier retained, individual contributions cannot be separated from the aggregate after the fact; this is consistent with GDPR Recital 26, which excludes truly anonymized data from erasure requirements.

Contact

Questions about this policy or your data can be directed to support@ip2geo.org.

Security

All data is transmitted over HTTPS. You can verify this by looking for a lock icon in the address bar and "https" at the beginning of the page address.