> ipaddress.you_
Trust

Privacy Policy

Last updated July 3, 2026

ipaddress.you shows you your IP address without keeping it. Your address is processed only to render your page, geolocation runs against a local database, the public site sets no cookies, and we keep no per-visitor records, so there is no personal data here to sell, leak, or subpoena.

The short version

  • Your IP address is never written to a database, log file, or analytics event by our application.
  • Geolocation happens on our own server against local GeoLite2 databases. No third-party API sees your address.
  • The public site is cookie-free. No consent banner, because there is nothing to consent to.
  • We keep only anonymous aggregate counters (tallies without IP addresses or identifiers).
  • There are no ads, no affiliate trackers, and no data sales.

How your IP address is handled

When you open a page, your browser sends your public IP address as part of the connection. That is how the internet works, and it is the very thing this site displays back to you. Our application reads the address from the request, uses it in memory to render your page or JSON response (address, hostname, geolocation), and then discards it. It is not persisted anywhere: not in a database, not in an application log, not in an analytics event, and not in a queue for later processing.

Geolocation is local

The city, country, ISP, and ASN shown next to your IP come from local copies of the GeoLite2 databases (created by MaxMind, available from maxmind.com) that we host on our own server and update regularly. Lookups run entirely on that server. Unlike IP checkers built on geolocation APIs, your address is never transmitted to a third-party service to be located.

What the tools process

  • IP lookup and /ip pages: addresses you enter are resolved against the local databases and via reverse DNS, then discarded. We do not keep a history of looked-up addresses.
  • Blacklist check: checking whether an IP is listed requires DNS queries to the public blocklist operators (Spamhaus, SpamCop, and others). Those queries necessarily contain the checked address (that is how DNSBLs work), but not your own address, and we store neither.
  • WebRTC leak test: runs entirely in your browser. To discover candidate addresses it contacts a public STUN server (operated by Google) directly from your browser, as any WebRTC application does. The result is displayed to you and never reported back to us.
  • Subnet calculator: pure client-side math. Nothing leaves your browser.

Anonymous aggregate counters

To publish first-party statistics (for example, the share of visitors that connect over IPv6, or the most common ISPs among our visitors), we increment anonymous counters. These are plain tallies: a number per category per day. They contain no IP addresses, no fingerprints, no session identifiers, and no timestamps precise enough to trace back to an individual request. Your IP is used in memory to decide which counter to bump (for example "IPv6 visitor") and is then discarded as described above.

Cookies & analytics

The public site sets no cookies and uses no local-storage tracking. In production we load a single lightweight analytics script to count page views in aggregate (which pages are visited, how often). We use it without cookies and do not use it to build visitor profiles. There is no advertising, no remarketing, and no cross-site tracking on this site. The private admin area (staff login) is the only part of the site that uses a session cookie.

Hosting & transport

Like every website, the servers and networks that deliver this site technically handle your IP address in transit. That is unavoidable and applies to the whole internet. What we control is what happens at the application layer, and there your address is never persisted. All traffic is encrypted via HTTPS (HSTS is enforced), and the site is reachable over both IPv4 and IPv6.

Your rights & contact

Because we keep no per-visitor data, there is usually nothing to access, correct, or delete, but you can always ask. For any privacy question or request, email daniel AT ipaddress DOT you (swap AT and DOT for the usual symbols; the address is spelled out to keep spam harvesters away). See the about page for who is behind the site. If this policy ever changes, the date at the top of this page will be updated and the change explained here.

Frequently Asked Questions

Do you log or store my IP address?
No. Your IP is read from the request, used to render your page or API response, and discarded. The application never writes it to a database, log file, or analytics event.
Is my IP sent to a third-party geolocation service?
No. Location, ISP, and ASN come from GeoLite2 databases stored on our own server, so the lookup happens locally. No external API ever receives your address.
Do you use cookies?
The public site sets no cookies at all, so no consent banner is needed: there is nothing to consent to. Only the private admin area uses a session cookie for login.
Do you sell or share any data?
No. There is nothing to sell: the site keeps no per-visitor data. We have no advertisers, no data partners, and no affiliate trackers.
What data do the anonymous counters contain?
Only aggregate tallies, for example how many visitors connected over IPv6 on a given day. They contain no IP addresses, no identifiers, and nothing that could single out one visitor.