ISHOB
Policy

Privacy

ISHOB has no user accounts, sets no cookies and runs no analytics or advertising trackers.

Request data

The site and API run on Cloudflare. Like any web service, requests (including IP address and user agent) are processed by Cloudflare to deliver responses, enforce rate limits and protect the service. ISHOB does not build profiles of visitors. For abuse and fraud monitoring, the operator's private dashboard shows the IP address, network operator and user agent of payment-related requests (HTTP 402 challenges and payments); IP addresses are held in memory for only the most recent 300 such requests and are never written to storage. For capacity planning, every request is also counted in hourly aggregates by client type (for example "search engine" or "AI crawler", derived from the User-Agent), site section, response status class and country; these counters contain no IP address, URL, query or other personal data and are kept for 90 days.

Payments

Paid endpoints use the x402 protocol. Payments are blockchain transactions: the paying wallet address, amount and time are publicly visible on-chain and are processed by a third-party payment facilitator. ISHOB never receives private keys.

Scheduled callbacks

When you schedule an agent alarm (/v1/alarm), ISHOB stores the callback URL, the JSON payload you supply, the delivery time, the per-alarm signing secret and the delivery attempts (time and HTTP status) so it can deliver and report on the callback. This record is deleted 7 days after the alarm is delivered, fails or is cancelled. Unpaid alarms are deleted immediately. Do not put secrets or personal data in alarm payloads.

Contact

Questions: a contact address has not been published yet.