Parser sessions start on purpose.
The parser is started manually before a practice block. kogni is not a hidden live-match agent.
Security model
Match data goes to kogni. Riot tokens do not.
kogni is built around a simple boundary: the desktop parser runs locally, Riot session material stays on the user's machine, and imported match data is sent to the team workspace for review.
01
Local desktop
Parser starts manually and reads the active Riot session locally.
02
kogni API
Imported match data is received for workspace review and analytics.
03
Team workspace
Managers, coaches, analysts, and players see data according to role.
Riot auth tokens stay local
They are not stored by the kogni backend.
Trust principles
Clear boundaries for VALORANT teams.
kogni needs enough information to make scrim review useful, but the sensitive local session boundary stays on the player's machine.
Auth material stays out of the backend.
The backend receives imported match payloads for review, not Riot account authentication tokens.
Team data is tied to roles.
Accounts, team memberships, workspace roles, and plan gates shape what each user can access.
Custom deployments can isolate more.
Custom plans can scope hosting, storage, routes, integrations, parser delivery, onboarding, and support.
What moves
The review record is shared. The local session is not.
kogni turns practice data into shared review context: match history, player stats, rounds, economy, minimap moments, VOD references, notes, tasks, schedules, and strategy work.
Data kogni may store
- Account, team, organization, invite, and workspace settings.
- Imported PRACC or scrim match data, round data, players, maps, agents, and review metadata.
- Notes, strategy references, tasks, goals, schedules, announcements, and support tickets.
- Optional integration data needed for connected Calendar, Sheets, Discord, or billing flows.
Data kogni does not need on the backend
- Riot auth tokens from the local parser session.
- Direct control over a player's Riot account.
- Gameplay modification or live competitive assistance.
- Raw local credentials for optional third-party accounts.
Controls
Designed for teams, orgs, and private deployments.
kogni uses encrypted transport for production services and stores integration tokens only when needed for connected workflows.
Managers, coaches, captains, players, and organization owners work inside scoped team and organization permissions.
Website accounts can use supported login methods such as email, Discord, and Google, depending on the active account flow.
Teams can contact kogni for access, privacy, deletion, export, or deployment-specific security questions.
Calendar or Sheets connections use scoped OAuth access only for the workspace features the team connects.
Custom deployments can define private hosting, data retention, support expectations, optional SSO/SAML, and feature gates.
Need a security answer for your team or organization?
Send the exact requirement. We can clarify parser behavior, stored data, integrations, privacy requests, or the right Custom deployment scope.