1. Scope
This Privacy Policy applies to the kogni public website at https://kogni.pro, the kogni desktop app, the kogni backend API, beta access flows, team workspaces, support tools, and integrations that connect to kogni.
kogni is currently an invite-only Beta product. Some features may change as the product evolves, but we will keep this policy updated when our data practices materially change.
2. Data We Collect
Depending on how you use kogni, we may collect the following categories of information:
- Account data: username, email address, password hash, role, invite or beta application status, profile photo, account origin, team memberships, and basic account settings.
- Team and organization data: team names, tags, region, game, roster entries, manager/captain/player roles, logos, setup progress, invites, announcements, goals, tasks, schedules, opponents, and workspace settings.
- Match and pracc data: imported scrim or match JSON data, match IDs, maps, agents, players, rounds, combat stats, economy context, opening duels, plants, defuses, retakes, post-plants, throw rounds, notes, VOD links, snapshots, and review metadata.
- Calendar and operations data: schedule events, event titles, notes, dates, start and end times, recurrence details, event type, opponent fields, stream links, and synchronization metadata.
- Media and files: images, clips, gallery uploads, team logos, profile photos, or support attachments you upload or make available to kogni.
- Third-party account data: Discord account identifiers, Discord username, avatar, and related OAuth data when you connect Discord. Google Calendar data is described separately below.
- Support and feedback data: support tickets, ticket messages, staff replies, feedback reports, bug details, screenshots, and related status or priority metadata.
- Website and technical data: IP address, browser or device information, app version, operating system, request logs, diagnostics, crash or error details, and security/audit logs needed to operate and protect kogni.
3. Google Calendar Data
If a captain or manager connects Google Calendar for a team, kogni requests access only
for the calendar sync feature. The current Google OAuth scopes used by kogni are
https://www.googleapis.com/auth/calendar.events and
https://www.googleapis.com/auth/calendar.readonly.
When Google Calendar sync is connected, kogni may access, store, and process:
- the selected Google calendar ID and sync status;
- OAuth access and refresh tokens needed to keep the team calendar connected;
- event IDs, event titles, descriptions, locations, start and end times, updated timestamps, etags, cancellation status, and private sync properties that kogni writes to identify kogni-created events;
- schedule entries created in kogni that are exported to Google Calendar.
We use Google Calendar data only to provide and maintain the visible team schedule sync: importing Google events into kogni, exporting kogni schedule events to Google Calendar, detecting changes, resolving sync status, and letting authorized team roles disconnect or refresh the integration.
We do not sell Google user data. We do not use Google user data for advertising, retargeting, interest-based ads, credit decisions, or data broker activity. We do not use Google Calendar data to train generalized AI or machine learning models. Humans at kogni do not read Google Calendar data unless you ask for support involving specific calendar data, it is necessary for security or abuse investigation, or it is required by law.
You can disconnect Google Calendar from the schedule sync area in kogni. You can also revoke kogni's Google access from your Google Account permissions. Disconnecting removes the stored Google connection tokens from kogni, but schedule events already synced into your kogni workspace or Google Calendar may remain until deleted according to your team settings and Google Calendar controls.
4. Riot and Match Data
kogni is built for VALORANT practice review. The desktop app and parser workflow may read local Riot/VALORANT session context to collect match data and generate reviewable match records. kogni's model is that match data goes to kogni for team review, while Riot authentication tokens are intended to stay local and are not uploaded to kogni servers.
kogni is not endorsed by Riot Games and is not part of Riot Games. You are responsible for using kogni in a way that follows Riot's rules, tournament rules, and your team's competitive obligations.
5. How We Use Data
We use the data we collect to:
- create, authenticate, and protect user accounts;
- provide team workspaces, roles, roster tools, schedules, tasks, goals, invites, announcements, gallery, and support features;
- import, store, search, filter, and display match/pracc data for review and analytics;
- power AI-assisted review, summaries, coaching prompts, and workflow support when those features are enabled or used;
- connect third-party integrations such as Google Calendar and Discord when authorized;
- send operational messages, beta invite information, product updates, and support replies;
- monitor reliability, debug issues, prevent abuse, enforce access controls, and improve product quality;
- comply with legal obligations and protect kogni, users, and teams.
AI features are intended to assist coaches, managers, analysts, and players. AI output may be incomplete or incorrect, so teams should review it before acting on it. Google Calendar data is not used to train generalized AI or machine learning models.
7. Retention and Security
We keep data for as long as needed to provide kogni, maintain team records, support beta operations, resolve disputes, comply with legal obligations, and protect the service. Team match history, schedule records, tasks, goals, notes, and other workspace content may remain while the team workspace is active unless deleted by authorized users or by request.
Google OAuth tokens are stored only as needed for the connected Calendar sync and are excluded from normal database reads. When the integration is disconnected, kogni removes the stored Google connection tokens. Logs and backups may persist for a limited period after deletion as part of normal security and recovery operations.
We use administrative, technical, and organizational safeguards designed to protect data, including encrypted transport, password hashing, role-based access controls, token access restrictions, audit-oriented logging, and limited access for staff or service providers. No online service can guarantee perfect security, but we work to keep the environment appropriate for the sensitivity of team and integration data.
8. Your Choices and Controls
- You can update account and team profile information inside kogni where the app provides controls.
- Authorized team roles can manage workspace data such as schedules, tasks, goals, team members, and imports.
- You can disconnect Google Calendar from kogni and revoke Google access from your Google Account permissions.
- You can disconnect or avoid connecting optional third-party integrations.
- You can request help with access, correction, deletion, or account questions through the kogni Help page.
Some data may need to be retained for security, fraud prevention, legal compliance, backup recovery, or legitimate team recordkeeping. If you are part of a team workspace, your ability to delete shared team data may depend on your role and the team's ownership decisions.
9. Children
kogni is designed for esports teams, coaches, managers, analysts, and players, and is not directed to children under 13. If you believe a child has provided personal data without appropriate permission, contact us so we can review and take appropriate action.
10. Changes
We may update this Privacy Policy as kogni changes. When we make material changes, we will update the date above and may provide additional notice in the app, on the website, or by email where appropriate.
11. Contact
For privacy, support, data access, deletion, or integration questions, contact kogni through the Help page or the support flow available in your kogni account.