From recording to tactical review

How match publishing works

The desktop app records each player's independent point of view and publishes it with a revocable account key. One valid source is enough for a visible match; additional compatible sources improve confidence without creating duplicate matches.

1. Download the Windows app, sign in, and connect it with a revocable desktop key from your account.
2. Enable automatic publishing or submit a saved protocol v2 observation no larger than 8 MB.
3. Review the arena, bracket, player count, and capture time.
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 desktop app stores its revocable key with Windows protected storage, sends compact authenticated match observations, preserves safe retries, and checks pending, corroborated, or contested publication status. Automatic sync remains opt-in.

Profile Refresh performs one bounded profile update. On the website, Refresh from Blizzard retrieves the current public profile, PvP summary, seasonal PvP achievement history, equipment, and specialization data when Blizzard integration is configured.

Connecting Battle.net from the account page asks for WoW profile permission, imports the account's characters into a private verified Alts list, and queues only a small top-level batch for profile loading. PvP Logs never receives the Battle.net password and never guesses account relationships from similar names.

How performance analysis 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.

How match evidence is verified

A desktop client cannot prove every byte is truthful. PvP Logs binds evidence to authenticated accounts, validates physical and structural constraints, preserves disagreement, and combines compatible uploads into one canonical match.

• Pending corroboration: accepted and visible in recent replays, public match detail, and participant histories as unverified evidence. It is excluded from verified ratings, records, performance trends, and leaderboards.
• 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 service status page.

Incorrect match or player data

The signed-in reporting flow attaches a reason to an audit record. Contested evidence remains visible while it is reviewed rather than silently replacing another player's observation.

Account, privacy, and billing

Account controls can export account data, revoke keys, remove tracked characters, and request deletion. Email and supported social sign-in methods create the same PvP Logs account. 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 terms for account and billing details.