Privacy

Checking a release

You send a plugin slug and a version. That is the whole input. No account, no key, no cookie-based identity and no personal data are required, on the site or through the JSON and MCP endpoints.

Cloudflare processes standard request data such as IP address, user agent and timestamp to deliver and protect the service. For rate limiting, the application uses an IP address transiently and stores only a one-way digest in its database fallback; that digest is deleted within 24 hours. Raw IP addresses and user agents are not stored in the application database.

Usage counts

Calls are counted in aggregate — per calendar day, channel, tool and outcome — so the operator can see whether the service is answering anything. Those counters hold no site address, plugin list or caller identity and are retained as non-personal product statistics. Older operational call rows may contain only a plugin slug and version; they are deleted after 30 days.

Site addresses you paste

If you use the site reader, the address is used to fetch that public page and read the plugins it exposes. It is not stored and not used to build any profile.

Accounts (optional)

An account is not needed for the public release check. If you create one, an email address and a salted password hash are stored. “Continue with Google” stores the verified email and an internal no-password marker; it does not store your Google account id. A session is stored only as a hash and expires after 30 days. Password-reset token hashes expire after one hour and expired or used rows are removed by the daily cleanup.

Account data remains until you ask for deletion. To access or delete an account and its email, contact hello@utilityhouse.xyz from the account address. Transaction records that must be retained are kept separately as described below.

Sponsor messages

The sponsor form stores the name, email address and message you submit so the operator can reply. These requests are automatically deleted after 180 days.

Legacy Scan Pass and testnet payments

New Scan Pass sales are closed. For an existing Scan Pass, the application may retain its hashed access token, plugin scan history, Paddle transaction id, amount and currency to provide recovery, fulfilment and transaction records. The original Paddle webhook payload and card details are not retained. Unpaid pending passes are deleted after 24 hours; completed transaction records are deleted after five years.

The separate invite-only x402 testnet route processes a payment proof with its facilitator only for that request. It does not retain the proof, wallet or payer.

What is swept

The sweep reads only public wordpress.org data: plugin metadata, the release list, and support-forum thread titles, links and timestamps. Thread bodies, authors and release notes are not collected. It never touches your site or your WordPress installation.

Third parties

Cloudflare hosts and protects the service. Resend delivers password-reset email, Google provides optional OAuth sign-in, Paddle processes legacy Scan Pass payments, and an x402 facilitator handles invite-only testnet payment verification. Each receives only the data needed for that function. There are no third-party advertising or analytics trackers on this site, and no data is sold.

Essential cookies and cleanup

Secure, host-only cookies are used for login sessions, OAuth state and CSRF protection. They are not used for advertising or cross-site tracking. A daily database task enforces the retention periods above; Cloudflare’s own Worker logs, when enabled, follow the plan’s platform retention, currently no more than seven days.