Longwatch has no user accounts and does not use advertising trackers. It processes the data needed to execute API calls, maintain watches, deliver alerts, prevent abuse, and operate the service.
A standing watch stores its source configuration, generated access key, polling state, timestamps, and recent alert history. Alert history is capped at 500 events per watch. A webhook watch also stores its destination URL and sends alert payloads to that destination. Deleting a watch through the API deletes its watch and alert records.
Operational metrics may include the request time, method, path, status, MCP client name, a salted hash of the caller IP address, and the public payer wallet address for x402 calls. Raw caller IP addresses and wallet private keys are not stored. Payments are visible on the applicable public blockchain and are processed through the x402 payment infrastructure.
To perform a watch, Longwatch requests the configured public source, such as a web page, RSS feed, CoinGecko price endpoint, or SEC EDGAR endpoint. If a caller configures a webhook, alert data is sent to that caller-selected endpoint.
For privacy questions or deletion help, email contact@coinop.dev. Do not include access keys or wallet secrets in email.
Last updated: August 24, 2026.