Site / Contact

Contact

Use the contact channel for source updates, disclosure concerns, analytics questions, and public registry feedback.

/contact

Source update path

For registry data issues, send a source-backed update when a tool identity, official URL, capability, pricing route, evidence row, freshness field, or publication state is stale, incomplete, or wrong.

A source update is faster to review when it names the exact field and includes the strongest official source available.

Use [email protected]

Best for source updates to public facts, source URLs, pricing routes, and freshness fields.

context

Add review context

Best for disclosure concerns, privacy or analytics questions, and issues that need extra context.

What to include

The most useful message is specific. It should make the issue reproducible without requiring a broad re-audit of the whole site.

The affected page URL.
The exact field, sentence, source row, pricing route, or link that needs review.
The strongest official source URL available.
Whether the issue changes identity, capability, pricing, evidence, freshness, disclosure, or analytics wording.
Any timing context, such as a recent pricing change, product rename, retired plan, or new official documentation.

Contact reasons

facts

Source updates

Send official source updates for tool identity, capabilities, pricing routes, company pages, or evidence rows.

disclosure

Disclosure concerns

Report places where commercial status, external destinations, or registry facts appear unclear.

analytics

Analytics questions

Ask about public measurement wording, including Google Analytics or Clarity references when enabled.

access

Broken routes

Report pages, links, forms, or public files that do not load as expected.

What this channel is not

AI Tool Graph is not a support desk for third-party tools listed in the registry. It cannot resolve vendor account access, billing, procurement, refunds, security reviews, implementation projects, or product-support requests.

Do not send passwords, private account data, confidential contracts, or sensitive personal information unless it is strictly necessary for the issue being reported.

Email

Use [email protected] for site messages, source updates, disclosure concerns, privacy or analytics questions, and registry feedback.

Use a concise subject line that names the affected route or issue.
Include the source URL directly in the message body.
Use official sources rather than search snippets or unsourced summaries when possible.