Privacy: no visitor-to-target lookup history is retained by IPJury.

IPJury is designed not to retain a visitor-to-target lookup history.

What is processed

For “check my connection,” the serving edge provides the current request IP and limited edge context. For arbitrary lookups, configured remote adapters receive the target IP as disclosed in Sources. First-party reads of locally held MMDB editions do not send that target to the database publisher. Private and reserved IPs are handled locally.

What is not retained

IPJury does not intentionally store which visitor searched which target IP. Target-IP evidence cache keys are HMAC-derived rather than raw IP paths. Normal application logs should not include raw target IPs. Session history in the UI stays in your browser session.

Caching

Sanitized public evidence may be cached to reduce source cost and latency. Results show cache state and checked time. A stale result is labeled as stale and used only when fresh sources fail. A cached answer is only replayed for as long as the source that produced it licenses; a family past its own window is withheld and the axes it covered abstain, rather than being served from an expired copy.

The evidence ledger

IPJury keeps a record of what published sources claimed and when those claims changed — which addresses the Tor Project listed as exits and when each entered or left that list, which network announces a block and when that changed, what the registries designate a block for. Your lookups never write to it. It is filled by scheduled imports of bulk published lists, not by this lookup or the correction form, so it contains no visitor address, no user agent, no requested URL, and no association between a visitor and a target. A source's own licence decides whether its values may be kept at all: where retention is not permitted, only a one-way digest is stored, which is enough to tell whether an answer changed but does not preserve the answer.

The ledger runs as a first-party service on the same infrastructure as the IPBot evidence API. Answering your lookup sends the address you asked about to it, as a separate first-party source request. No visitor identity is deliberately attached to that request or retained with the source claims.

Third parties

Reverse DNS is disclosed in Sources. IPBot evidence is used only when a field-level host audit profile is active; optional sources remain withheld until separately configured and disclosed. Each source has its own data practices and limitations. When the Bright Data context row is enabled, the checked IPv4 address is also sent to Bright Data's geolocation test endpoint (geo.brdtest.com), which publishes no terms; IPv6 addresses are never sent, and the row can be switched off without a deployment.

Native ASN summary and interpretation

The optional native summary is requested automatically from IPJury after the current network ASN is known. Its public-data permission is checked independently of API access. When enabled after review, the backend requests only the ASN, seven-day window and HTML-request scope from Cloudflare; it does not forward your IP, the checked IP, cookies or report-page referrer. This aggregate has its own short-lived ASN cache. Missing permission or data leaves the official chart fallback available. The experimental IPJury Score is computed from the displayed evidence record, not from visitor behaviour or an account profile. A later chart response does not change an already exported score.

Optional Cloudflare chart

The ASN human/bot chart loads only when you choose Show chart. It is an official Cloudflare Radar embed, with its own usage metrics and data practices. Cloudflare receives your browser's connecting IP and the ASN requested for the chart. IPJury does not send the checked IP or report-page referrer in the embed request. Closing the chart or starting another lookup removes the frame. The percentages are not read into IPJury's evidence record, history, API, or exports.

The deployed Cloudflare platform also injects a Web Analytics beacon independently of the optional chart. This site should not be treated as having zero third-party analytics. See Cloudflare Radar's embed and usage-metrics disclosure.

Corrections

If the D1 correction queue is configured, evidence-backed submissions are stored for review. Otherwise the interface prepares an email and nothing is submitted to IPJury automatically.

Contact

Email hello@ipjury.com for privacy requests.