Privacy

What competitive website data is collected, shown publicly, and kept private.

Public PolicyUpdated 2026-06-14
  • Website sign-in uses email one-time codes for public release.
  • Public competitive data is separated from private account/session data.
  • Analytics and moderation reports use aggregate or audit-safe data, not raw provider identifiers.

Data We Use

  • Email one-time-code session data for website sign-in and logout.
  • Verified TK2 player profile links created through game-generated claim codes or trusted game/backend identity events.
  • Competitive submissions, proof URLs, review status, tournament check-ins, match results, and profile customization fields.
  • Server logs, request IDs, rate-limit buckets, audit events, and aggregate analytics needed to operate the site safely.

Public Data

  • Display name, avatar text, public country when enabled, platform/class preference, badges, showcase records, and public profile text.
  • Verified times, records, rankings, season/monthly ladder data, tournament participation state, bracket results, and public proof links.
  • Moderator-only notes, private proof, emails, internal account IDs, session IDs, raw provider IDs, auth tokens, and rate-limit keys are not part of public DTOs.

Retention And Control

  • Audit logs are retained for competitive integrity and abuse investigation.
  • Submission evidence is retained while it is needed to verify a competitive result or moderation decision.
  • Players can request correction, export, deletion, or profile visibility changes through the support route.
  • If a deletion request conflicts with competitive integrity, the public row can be anonymized while the audit record remains protected.

Third Parties

  • Email delivery, hosting, database, logging, monitoring, and backup providers may process operational data required to run the site.
  • Optional platform identity providers may be added later for account linking or ownership checks.
  • External proof URLs are controlled by the service where the player uploaded the proof.