IPCheckHub
IPCheckHub policy

IPCheckHub Privacy Policy

This notice explains what the current public tools process, why they process it, where it may go, and the limits of the present release.

1. Scope and current service model

This policy covers the public IPCheckHub website and its IP, privacy, DNS, proxy, connectivity, and network diagnostic tools. The current public service has no user accounts, advertising profile, checkout, or paid subscription.

IPCheckHub is the service name, not a separately identified legal entity in this release. A verified operator identity and public privacy-request channel must be added before the service enables accounts, payments, or long-term user profiles.

2. Information processed

  • Network and request data: the IP address used to reach the service, requested path, request time, standard HTTP headers, and bounded request or security identifiers needed to deliver and protect the service.
  • Values you submit: a public IP address, hostname, domain, port, proxy endpoint, selected probe region, or similar diagnostic target when you explicitly run a tool.
  • Optional proxy credentials: a paired username and password only when you choose to test an authorized proxy that requires them. They are submitted over HTTPS for that check, cleared from the form after submission, excluded from browser task storage, and never displayed in the public result.
  • Browser-side signals: selected privacy tools may read documented network or coarse browser characteristics after you start the check. Local-only values stay in the browser unless the tool page says a bounded value is sent for the requested check.
  • Short-lived browser state: theme preference in local storage and opaque task ownership identifiers in session storage so an in-progress result can be resumed in the same tab session.

3. Why information is processed

  • To return the diagnostic result you requested and distinguish the observation point used.
  • To validate public targets, enforce rate and safety limits, prevent abuse, and investigate service failures.
  • To maintain short-lived task state, support cancellation or expiry, and avoid mixing one request with another.
  • To protect the service and comply with applicable legal obligations.

4. Service providers and disclosures

Cloudflare delivers the website and Worker runtime and may process connection metadata for routing, security, and service operation. Some tools use fixed backend services, DNS resolvers, probes, trackers, or licensed data sources; only the target and technical context needed for the selected check should be sent to them.

IPCheckHub does not intentionally sell personal information or use public tool inputs to build advertising profiles. Information may be disclosed when required by law, to protect users or the service, or to service providers acting for the technical purposes described here.

5. Retention

The current product contracts use short, task-specific retention instead of permanent user histories. Bulk IP job results expire after 24 hours; environment, business-connectivity, and network-job results expire after 15 minutes; DNS-leak and Torrent test sessions expire after 10 minutes. Limited expiry tombstones may remain for up to 24 hours to return a safe expired response and prevent replay confusion.

Browser session-storage task identifiers disappear when the relevant browser session is cleared or expires; theme preference remains until you change it or clear site data. Infrastructure and security logs may be retained separately for a limited operational period under current provider and deployment settings; this release does not promise an exact log-retention duration.

6. Cookies and local storage

IPCheckHub does not currently configure advertising or optional analytics cookies on its public pages. The site uses local or session storage for the limited purposes described above. Cloudflare may use strictly necessary cookies when a security or traffic-management feature requires them; see the Cookie Policy for details.

7. Security and international processing

IPCheckHub uses HTTPS, input validation, public-target restrictions, rate limits, short-lived task records, and output filtering. No internet service can guarantee absolute security. Cloudflare and other infrastructure may process data in more than one country according to their service configuration and legal terms.

Do not submit secrets unless a tool explicitly requests them for the check. Never submit account passwords, authentication cookies, private keys, recovery codes, or personal documents.

8. Your choices and rights

You can avoid entering a target, stop using a tool, delete a supported active task, close the tab to end session storage, or clear IPCheckHub site data in your browser. Depending on where you live, applicable law may provide rights to be informed, access, correct, delete, restrict, port, or object to certain processing, and to complain to a regulator.

A verified privacy-request contact is not yet published. Do not send a rights request to an unverified address. This is a known release limitation and must be resolved before long-lived personal profiles or paid accounts are introduced.

9. Changes to this policy

This policy will be updated before material new data uses, optional analytics, advertising, accounts, payments, or longer retention are enabled. The date at the top identifies the current version.

© 2026 IPCheckHub