01
Information we collect
When you run a check, HiDHT may store the submitted CID, normalized CID metadata, check status, provider lookup summaries, gateway probe results, response timing, cache metadata, and the time the check was performed.
For abuse prevention and basic operations, HiDHT may store hashed IP address and hashed user-agent values. These hashes are used for rate limiting, debugging, and service protection rather than public display.
02
Monitoring requests
If you request future monitoring, HiDHT stores the submitted email address, an email hash, the requested CID, requested frequency, source page, status, and timestamps.
Monitoring requests are used to validate demand and to contact users about monitoring availability. Email confirmation or notifications are sent only when an email provider is configured.
03
Content safety
HiDHT does not store fetched IPFS content, render gateway responses, proxy content, iframe content, or provide downloads for checked CIDs.
Gateway probes use metadata-oriented requests such as HEAD and small ranged GET fallbacks. The user-facing result shows technical metadata only.
04
Third-party infrastructure
HiDHT is designed to run on Cloudflare infrastructure, including Workers, Pages, D1, and KV. Checks may call delegated routing endpoints and public IPFS gateways to produce availability metadata.
Those external services may receive the CID being checked as part of normal network operation.
05
Contact
For privacy questions, data requests, or account-related concerns, contact contact@hidht.com.