From recording to tactical review

How match upload will work

Public sign-in and key creation are not enabled on the current Kubernetes release. These steps apply only to an approved test environment until account onboarding opens.

1. Sign in and open Upload match.
2. Select a protocol v2 JSON observation no larger than 8 MB.
3. Review the arena, bracket, player count, and capture time before submitting.
4. Open the returned match. A single perspective is public with an Unverified / Pending corroboration warning until eligible independent evidence corroborates it.

Do not edit an exported observation to add scores or claims. Performance analysis and evidence confidence are calculated by the server.

Desktop agent compatibility

The current desktop source is being prepared as 0.3.6. It pairs a revocable key through Windows protected storage, sends compact authenticated v3 observations, preserves exact retry bytes, and checks pending/corroborated/contested status. Automatic sync defaults to off. No signed 0.3.6 installer or public update channel has been released.

Profile Refresh performs one bounded API v3 read and ends with data, no uploaded matches, Retry, or an error; it does not request fresh data from Blizzard. The current source also restores spell and talent tooltips, tactical-replay icons, Combat Timeline placement, and replay-following Live Index events.

Read the exact agent API contract.

How the Arena Compass works

The character performance tab maps verified output, tempo, control, observed positioning, and survival evidence. Pending and contested matches remain visible in history but never change the Compass. Unknown telemetry stays unknown instead of becoming a zero score.

The current Compass is an absolute evidence index, not a rank percentile. Same-specialization and same-bracket comparisons will remain unavailable until PvP Logs has a sufficiently large corroborated benchmark population.

What match states mean

• Pending corroboration: accepted and visible on its public match detail and participant histories as unverified evidence. It is excluded from verified ratings, records, performance trends, leaderboards, and the global replay index.
• Corroborated: at least two eligible independent accounts supplied compatible evidence.
• Contested: meaningful evidence disagrees; PvP Logs keeps the conflict visible instead of choosing silently.
• Insufficient data: the recording lacks enough telemetry for a defensible performance score.

Common upload responses

• 400: invalid protocol, roster, timing, identity, or replay structure. Do not retry unchanged bytes.
• 401 or 403: sign in again or replace a revoked/wrong-scope key.
• 409: the retry key or same account was already used for different evidence.
• 413: compact the observation below 8 MB before retrying.
• 429 or 5xx: wait for the requested delay and retry the same evidence with the same idempotency key.

Keep the response request ID when diagnosing a failure. Live dependency health is available from the API status endpoint.

Incorrect match or player data

The signed-in reporting flow attaches a reason to an audit record, but public identity is disabled on the current release. A moderator console and public support address are also launch gates, so PvP Logs must not yet be treated as a public dispute-resolution service.

Account, privacy, and billing

Account controls can export account data, revoke keys, remove tracked characters, and request deletion when trusted identity is enabled. Public sign-in and billing are disabled on the current Kubernetes release. An active subscription or unexpired Checkout session must be resolved before deletion; canceled, expired, or customer-only billing history does not block it.

See the current privacy notice and preview terms. Final legal identity, support contact, refund rules, and public billing remain intentionally unavailable until approved.