Use every signal with its boundary attached.

Polytrack stores trades its monitor receives and processes. Network interruptions, API behavior, pagination, deployment state, validation, late events, and source corrections can create gaps. Historical panels and rankings therefore describe Polytrack coverage, not a complete ledger of Polymarket.

An empty result can mean no matching monitored record, no available upstream row, a temporary failure, or a filter that excluded data. It should not be interpreted automatically as no activity.

A wallet may be controlled by an individual, team, service, contract, proxy, or changing group of operators. Public profile fields and private watchlist labels can help organize research but do not authenticate legal identity, geography, affiliation, or beneficial ownership.

Similarity in timing, direction, or market choice does not by itself prove coordination. Polytrack can surface a pattern for review; it cannot establish the relationship behind that pattern.

LOW, MEDIUM, and HIGH are classifier outputs based on configured activity signals. They are not calibrated probabilities of wrongdoing, private knowledge, market accuracy, or investment return. A HIGH event can have an ordinary explanation, and a meaningful event can fall outside the conditions Polytrack monitors.

Category sensitivity and alert reasons add context but remain classifications. They should be checked against the market, source record, wallet history, liquidity, and later activity.

Position value and PnL fields can change with price, fills, transfers, settlement, redemption, source methodology, and the time of a request. A leaderboard average can be dominated by a small number of trades. A volume rank does not account for capital, age, hedges, risk, or activity outside the monitored dataset.

A displayed orderbook or price is an observation, with no assurance that the same liquidity remains available. Polytrack does not execute an order or verify fillability.

A trade must become available upstream, be received, processed, stored, evaluated, and selected before an alert attempt can occur. Network state, deployments, rate limits, Telegram, and the user's bot and chat configuration add further dependencies. Polytrack does not promise a fixed end-to-end alert delay or uninterrupted delivery.

A dashboard refresh can retrieve newer context than an earlier alert. That does not mean the earlier message was a synchronized snapshot of every source.

Polytrack does not place trades, hold funds, manage portfolios, promise outcomes, or determine whether activity is lawful. Users remain responsible for verifying source data, understanding market rules, assessing risk, and obtaining qualified advice where needed.

Prediction markets can be volatile, illiquid, jurisdiction-sensitive, and subject to resolution or platform rules. A useful signal can still lead to a loss or an incorrect conclusion.