AIWebSignalsobserve the machine web
Support and feedback

Contact AIWebSignals

Use the appropriate channel below, and never place credentials, management keys, or sensitive personal information in a public report.

Effective August 18, 2026

Product support and feedback

For bug reports, feature requests, documentation corrections, or non-confidential policy questions, use the public AIWebSignals issue tracker.

Open the issue tracker

Before opening an issue, remove scanned domains you do not want to discuss publicly, report IDs, configuration IDs, management tokens, email addresses, phone numbers, webhook URLs, credentials, and other personal or confidential information.

Security concerns

Do not disclose an active vulnerability, secret, or exploit detail in a public issue. Review the repository security area for an available private reporting channel. If private reporting is unavailable, open a public issue containing no sensitive detail and request a private contact path.

Review security reporting options

Privacy questions

You may use the issue tracker for a general privacy-policy question that contains no personal information. For a request involving personal or sensitive details, ask for a private contact path without posting those details publicly.

What to include

  • The page or feature involved.
  • What you expected and what occurred.
  • A safe, reproducible sequence that contains no credentials.
  • Your browser or general environment when relevant.

AIWebSignals cannot guarantee a particular response time, but clear and reproducible reports are easier to investigate.

Connected-ingestion support

When requesting help with a connected traffic source, never post an ingestion key, management key, provider API credential, signed request, authorization header, raw access-log file, or unredacted visitor identifier in a public issue. You may safely identify the provider type and describe the configuration step or error without exposing the credential.

Agent Policy support

Never send a management key or policy decision key in a public support message. A connection ID, policy revision, rule ID, provider type, and non-sensitive error description are sufficient for most troubleshooting.

Payment support boundary

For AI Revenue support, do not send wallet private keys, seed phrases, payment signatures, facilitator credentials, or other secrets. Transaction identifiers and connection IDs may be used for troubleshooting when necessary.

Sponsorships

For advertising or research sponsorship opportunities, use the AIWebSignals sponsorship inquiry.