Staging draft · 23 September 2026

Privacy

This draft describes the current testing service. The project owner must finalize the operator identity, retention schedule, contact details and applicable legal requirements before a public production launch.

Information kept by the service

Accounts contain a username, email, password hash and optional display or Riot identity details. Teams, memberships, frozen player names, matches, competition entries, results, statistics and review history are saved in PostgreSQL. Passwords are hashed; server sessions store a hash of the session token.

Sessions and browser storage

An essential HttpOnly cookie keeps you signed in. The default session lasts seven days. Logging out revokes the current session. The service does not store passwords or long-lived access tokens in localStorage. Form drafts and the separate design prototype may use browser memory.

Who can see data

Access depends on the current account and the team, match or competition permissions. Organizers and authorized operators can record data. Competition registration can expose limited event information to signed-in users. Historical roster snapshots and reviewed changes remain available to authorized readers.

Hosting, content and diagnostics

Hosting providers process the service and its database. Operational logs record route templates, response status, request IDs, timing and bounded error references. Application logs exclude passwords, session cookies and submitted review reasons. Hosting infrastructure may process network metadata such as IP addresses. Loading remote artwork or the content catalog contacts valorant-api.com and may disclose browser network information to that provider.

Retention and requests

Historical competition and audit records are retained during controlled testing. A maintenance command removes sessions expired for more than seven days; this is not a promise of an automatic daily deletion schedule. Backup retention depends on the configured hosting plan. Account deletion, export and retention requests are currently handled by the project owner, not an automated page.

Use the testing contact channel for questions. Do not enter unnecessary personal information or sensitive material in names, notes or review reasons.