MyIPScan
Home>Privacy
Legal

Privacy Policy

A clear explanation of what MyIPScan processes to show IP and privacy diagnostic results.

Last updated: October 28, 2026

Who is responsible

MyIPScan is owned and operated by Katia Belokon, who is responsible for the processing described on this page. Contact: hello@myipscan.net.

Summary

  • MyIPScan does not require an account for core tools.
  • Your IP address and browser request details are processed in real time so the site can display IP, location, ISP, ASN, VPN leak, DNS, WebRTC, IPv6, and browser-signal results.
  • Tool results are not stored in a MyIPScan user account or MyIPScan database.
  • Some checks use browser APIs, Cloudflare infrastructure, public DNS/STUN services, server-side IP enrichment providers, or public routing and reputation data providers. Those services may process technical request data under their own policies.
  • When you submit an IP address or ASN to lookup tools, that value may be sent to selected lookup providers so the result can be generated.
  • Some pages may contain affiliate links, and ads may be added later. Monetized content is disclosed when present.

Data processed to show results

When you use the IP check or related diagnostics, MyIPScan may process your public IP address, user-agent, approximate country, region, city, ASN, ISP or organization, timezone, and Cloudflare edge metadata. This processing happens to generate the result shown in your browser.

The Cloudflare Pages Function implementation can call IP enrichment services such as ipwho.is, ipapi.co, or ipwhois.app from the server side when Cloudflare metadata is not enough or when you submit an arbitrary IP address for lookup. For a submitted address, the IP Geolocation Lookup asks RIPEstat (the MaxMind GeoLite2 database) first and uses those three services only if RIPEstat gives no usable answer. The Worker implementation can use Cloudflare request metadata instead. In both cases, the result is best-effort and approximate. To name your town and provider, MyIPScan’s server also asks RIPEstat (RIPE NCC) about your network: the /24 (IPv4) or /48 (IPv6) block your address belongs to, and its AS number. Your exact address is not sent.

Tool-specific processing

  • DNS leak test: the check runs only when you press its button. Your browser then looks up one-time test names at bash.ws, whose authoritative DNS server records which resolvers asked for them. bash.ws sees your public IP and the DNS resolvers that ask on your behalf, and reports them back to the page. The VPN Leak Test and the Public Exposure Report use the same lookup. MyIPScan does not store the result.
  • IP geolocation, ASN, and blacklist lookup tools: submitted IPs or ASNs may be sent from MyIPScan server-side functions to selected providers such as IP geolocation APIs, RIPEstat, DNS-over-HTTPS resolvers, SpamCop, blocklist.de, or Feodo Tracker. IP geolocation is approximate, blacklist checks query selected sources only, and results are not guarantees. The Public Exposure Report runs the same blacklist check on your own public IPv4 address automatically when you start it.
  • WebRTC and IPv6 tests: the browser may create WebRTC ICE candidates and may contact a public STUN server currently configured as stun.l.google.com:19302. If the test finds a global IPv6 address that differs from the one your connection already showed, MyIPScan’s server asks RIPEstat which network announces it (ASN and holder); that address is not sent to IP geolocation providers.
  • Browser fingerprint demo: the tool reads browser, screen, canvas, WebGL, audio, font, timezone, and device signals in your browser to explain fingerprinting risk.
  • Password generator: generated passwords are created in your browser and are not sent to MyIPScan lookup APIs.
  • Utilities: tools such as the calculator may store convenience history or state locally in your browser.

Storage and local browser state

MyIPScan does not provide user accounts, so tool results are not saved into a MyIPScan account. Shared site scripts may use browser local storage for convenience features such as privacy-score status, recent IP history, or utility history. You can clear this storage in your browser settings.

Analytics, cookies, and advertising

MyIPScan uses Google Analytics 4 only if you allow it. A small notice asks once; until you answer, and if you choose “No thanks”, Google Analytics does not load and no analytics cookie is set. It never loads when your browser sends Global Privacy Control or Do Not Track. If you allow it, Google Analytics sets its own cookies and receives page views plus three tool events (run_test, test_result and share_result) that carry only the tool’s name and a result category such as clean or review: no IP address, location, resolver or fingerprint from a test is put into them, and Google states that Google Analytics 4 does not log or store IP addresses. Page addresses go to Google without the part after “?”, so a domain, IP address or URL in a shared link is not sent, and Google’s automatic tracking of outside-link clicks, site search, forms, scrolling, video and downloads is switched off. The blog at blog.myipscan.net asks the same question on its own; the “Analytics choice” button at the bottom of each blog page changes the answer there. Cloudflare, which serves the site, keeps its own request logs under the Cloudflare privacy policy, and its Web Analytics script, which Cloudflare adds to every page, counts page views, referrers and load times for every visitor without cookies or any identifier stored in your browser. MyIPScan does not create user accounts or store tool results in a database.

MyIPScan sets no cookies of its own. Some tools keep results only in your browser's local storage, as described above, and you can clear them there. Websites you open from a link on MyIPScan apply their own cookies and policies.

Hosting and third-party services

MyIPScan is hosted through Cloudflare. Cloudflare and other infrastructure providers may process request logs, IP addresses, security events, and performance data under their own policies. Public DNS, STUN, IP enrichment, email, and affiliate destinations may also process data when used.

Affiliate links and future ads

Some pages may include affiliate links. If you buy through those links, MyIPScan may earn a commission at no extra cost to you. Ads may be added later, but they should be disclosed and should not change tool results.

Children

MyIPScan is not directed to children under 13, and the site is not designed to collect children's personal information.

How long data is kept

MyIPScan keeps no database of visitors or tool results. To limit abuse, the API keeps short-lived request counters keyed on a hash of your IP address (for IPv6, of its /64 block) in Cloudflare's cache; they expire after about a minute. Lookups you submit, such as a domain or an IP address, are cached for up to a day so repeated checks do not hit the same public registry again; the cache holds the public answer, not who asked.

Legal basis and your rights

Your IP address is processed to show it back to you and to run the checks you request; the legal basis is the legitimate interest in providing the service you asked for (GDPR Article 6(1)(f)). Because MyIPScan stores no personal data beyond the short-lived counters above, there is usually nothing to access, correct or delete. You can still ask about any processing or object to it at hello@myipscan.net, and you can complain to your local data protection authority.

Changes

Material privacy changes should be reflected on this page by updating the last-updated date and the relevant sections.

Contact

Questions about privacy can be sent to hello@myipscan.net.