Privacy
Short version: we show what your connection already tells a server. We don't keep it, sell it, or build a profile from it.
We show the IP addresses our servers see when your browser connects. We don't run ads, set tracking cookies, or store a history of your IP address. Network providers and intermediate proxies may see connection metadata.
This page describes the intended behaviour of the production service. Details marked To verify are assumptions that must be checked against the deployed infrastructure, proxy configuration and hosting-provider terms before this page is published.
What is processed
When your browser loads this site, the request carries the network address it connects from. Our server reads that public address so it can send the page back, and so the page can show it to you. The address of the connection that loaded the page is written into the page itself.
If that address is IPv4, the page may make one extra request to v6.ip.privacylink.nl; if it is IPv6, one extra request to v4.ip.privacylink.nl. That request exists only to learn the address of the other family as seen from this connection. There is never more than one such request per page load, and nothing else is sent.
Why it is needed
An IP address is how a reply finds its way back to you. Without it the server cannot answer at all. Showing it is also the entire purpose of this tool: it answers "what address does the outside world see for me right now?"
What is not stored
- No history or database of visitors' IP addresses.
- No accounts, profiles, identifiers or fingerprinting.
- No analytics, pixels, third-party scripts or external fonts.
- No page content or request bodies are recorded.
Your browser keeps the address on screen only for as long as the page is open. Nothing you see here is saved on our side.
Cookies and tracking
None. This site sets no cookies and stores nothing in your browser, so no cookie banner is needed. The scripts and styles are served from this domain only; loading the page contacts no third party in your browser.
Servers, proxies and infrastructure
The application itself does not write access logs containing visitor IP addresses To verify. Running any public service still involves infrastructure we do not control: the reverse proxy in front of the application, the network firewall and the hosting provider can process connection metadata such as source address, time and volume to deliver traffic and protect the service To verify retention. This page does not claim that no metadata exists anywhere — only that this application does not build a record of visitors.
Network providers and NAT
Your internet provider, employer, VPN or mobile network can see that you connected here, as they can for any site. If you use a VPN, proxy, CGNAT or a protocol translator such as NAT64, the address shown is the one that reaches our server — it may belong to that gateway rather than to your device.
Contact and source
Questions about this page: privacy@privacylink.nl To verify. The source code is public so you can check these claims yourself To verify. Security reports are welcome through the repository's security policy.
Changes
If the way this service handles data changes, this page changes with it. Geo-location or network metadata would only be added with a clearly labelled source and an update to this text.