Send the context needed to resolve the question.

For access, signup, login, subscription, dashboard, or alert issues, identify the relevant page and the email address on the account. Describe the last successful step and any visible error text. Do not send a password or authentication token.

For Telegram issues, state whether the connection test, HIGH severity switch, or watched-wallet switch is affected. Share only a redacted chat identifier or the last four characters already displayed by the product. Revoke a bot token through Telegram if you believe it was exposed.

For a possible data discrepancy, include the market or wallet URL, the field at issue, the observed value, the approximate observation time and timezone, and the upstream source you compared. Remember that current positions, prices, PnL, activity, and ranks can change after the observation.

For a public-copy correction, include the exact page URL and sentence. Polytrack will compare it with current product behavior and primary documentation, then update the visible review date when a material correction is published.

Describe the affected route, preconditions, impact, and a minimal safe reproduction. Do not access another user's data, degrade production, publish a live secret, or send destructive payloads. A report should prove the issue with the least sensitive evidence possible.

Polytrack does not currently publish a bounty or promise a reward. Coordinated disclosure and clear evidence are still appreciated.

For methodology questions, link the exact definition or research note. For press or citation requests, state the deadline, intended use, and whether you need a source explanation, a product screenshot, or a correction check.

Polytrack can explain what its monitored data shows and where its coverage stops. It will not turn a classifier output into an allegation about a wallet controller.

The public site does not promise a fixed support-response time. Complete, reproducible reports can be triaged more reliably than messages without a URL, timestamp, or expected result. If an issue involves an external service such as Polymarket, Telegram, a news publisher, or a payment provider, resolution may also depend on that system.