Help and support

Product help

Choose your surface

Before reporting

Fast checks that solve most problems

1. Read the visible result state. “Not evaluated” means the tool could not make that check; it is not a pass, zero, or proof that no issue exists.
2. Retry once with the same safe input. A target site, upstream source, browser permission, network timeout, rate limit, or temporary service problem may prevent a result.
3. Confirm the input is supported. Public URL tools generally need an ordinary public HTTP(S) URL. Do not submit credentials, private preview links, session URLs, or secrets.
4. Preserve the evidence. Keep the exact error text and any request, report, or public reference ID. For the extension, export and review its sanitized audit bundle if the problem is reproducible.

Automated results are point-in-time observations. A clean result does not guarantee crawling, indexing, rankings, rich results, accessibility conformance, privacy compliance, security, availability, or a business outcome.

Availability

When something appears unavailable

Check the public changelog for a recent product or methodology change, wait a few minutes if a rate or upstream limit is shown, then retry once. If the same failure continues across more than one safe public input, report it with the details below.

View current service status →

Contact

Send a useful support report

Use the contact form and choose the closest topic. For a tool or MCP problem, include:

• the tool, MCP method, or extension module;
• what you expected and what happened instead;
• the exact error text and safe request/reference ID, if one appeared;
• browser and extension version when relevant; and
• whether the problem repeats with another non-sensitive public URL or input.

Expert community

Expert profiles, sign-in, and contributions

Verified industry experts can apply through the expert registration page. Applications are reviewed before an expert can sign in, add scoped notes to article passages, or answer questions opened to the panel.

1. Application pending: wait for the owner review. Registering does not immediately create an approved publishing account.
2. Magic link did not arrive: confirm you used the approved profile email, check spam or filtering, wait a few minutes, then request one new link. Use only the newest link and never forward it.
3. Link expired or was already used: return to expert sign-in and request a new one.
4. A contribution is not visible: untrusted notes and answers remain in review until approved. A submitted contribution is not a promise of publication.

If sign-in still fails, use the contact form, choose Account or access, and include the approved profile email plus the time of the latest request. Do not include the magic-link URL or token.

Newsletter

Subscription confirmation and unsubscribe

1. After subscribing: check the inbox for the address you entered and open the confirmation link. No newsletter is sent until that double opt-in step succeeds.
2. Confirmation did not arrive: check spam or filtering, wait a few minutes, then submit the address once more. Use the newest confirmation message.
3. The link is invalid or expired: subscribe again to create a new confirmation link.
4. To stop delivery: use the unsubscribe link in any newsletter. The address remains on a suppression record so it is not mailed again unless you resubscribe.

For a deletion request or a delivery problem that continues, use the contact form and choose Other. Do not forward a confirmation or unsubscribe URL because it contains a private token.

Privacy and security

Privacy, deletion, and security reports

The main Privacy Policy explains site forms, analytics, public URL tools, retention, and deletion requests. The Traverse browser extension has a separate, stable extension privacy notice because browser stores and extension permissions need a more specific data-flow explanation; that notice currently lives in the owner-only preview area pending a public store listing.

For access, correction, or deletion requests, or to report a suspected vulnerability or privacy problem, use the contact form and choose Privacy or security. Share the minimum evidence needed; do not place vulnerability details or sensitive customer data in a public issue.

Paid products

What's coming, and what works today

One-time Runs

Current state: the planned Runs catalog (products, bands, caps, and unavailable states) is not published. Checkout, order projection, customer access, dispatch, and execution are implemented behind separate default-off launch gates; none is enabled for public purchase or use.

Planned support coverage: before purchase, expect accepted input, capture mode, purchased cap, estimated processing, and a rule that oversized inputs are rejected or moved to another band—never silently truncated. After submission, expect an order/reference ID, Run ID, current state, accepted and skipped input counts, cap state, retry state, report availability, and expiration. Failure states will distinguish a target block, invalid/import failure, internal failure, timeout, and safety/cost-cap stop—"not evaluated" will never read as a clean result. A refund/cancellation rule will publish once the policy is decided, the merchant workflow is implemented, and counsel has reviewed it.

Watchtower

Current state: Watchtower's paid catalog entry is not public; this site's own live monitoring still dogfoods the product at /watchtower/. Customer billing, entitlements, customer execution, retention, and notification delivery are implemented as separately gated paths and are not active for customers.

Planned support coverage: setup (monitored domain, key URLs, schedule, optional international seed/cap, email on/off), observation state (last checked time, baseline date, individual check states, recent failure/recovery events), and alert diagnosis that separates "change was not observed," "event was recorded," and "notification delivery failed." Retention, export/deletion, revocation, and post-cancellation access will publish only once implemented and legally approved.

Paid REST and MCP

Current state: the public free MCP server is live and read-only. License-backed REST and MCP execution paths exist but are disabled, and public REST documentation has not launched.

Planned support coverage: Patrick REST and MCP as two transports over one license, shared keys, and one execution ledger — multiple keys will not multiply capacity. Zero-execution-cost reads of your own purchased outputs will stay separate from metered Fetch, Render, and AI execution. Rate-limit responses will expose the limit type, remaining capacity, reset time, and a request/job ID; paid monthly exhaustion will create no automatic overage.

Billing, license access, and branding

Current state: the subscription configurator and license manager are owner-only previews and are not currently public. Checkout, entitlement projection, cancellation, key and license access, branding, and customer communications are implemented behind default-off gates; refunds, final policy, production configuration, and end-to-end delivery remain launch requirements.

When billing goes live: cancellation will be at least as easy as signup, with its effective date and data consequences explained before purchase; priority execution will never be called "priority support"; and refund decisions will be recorded against the real merchant transaction rather than an invented credit.

Privacy, deletion, and security for paid products

A legal packet covering product/subscription terms, refunds, data processing, security, support operations, advertising, and satellite/plugin terms for the paid layer exists in draft but is not currently public. Before launch, support answers must match the implemented processors, logs, storage, retention, backup deletion, export, and account/license model. Report privacy, deletion, account-ownership, or security concerns through the contact form today — the same route used for the free tools.

Reference

Policies and release history

This help hub covers products and community features that are publicly available today, plus honest expectation-setting for the launch-gated paid layer above. Support routes for paid products will expand when public purchase, access, execution, and delivery are enabled.