1. Scope
This Privacy Policy applies to the kogni public website at https://kogni.pro, the kogni desktop app, the kogni backend API, account and workspace setup flows, billing, team workspaces, support tools, and integrations that connect to kogni.
kogni is a live, evolving product with public account and workspace setup. 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, workspace, billing, or legacy access status, profile photo, account origin, team memberships, and basic account settings.
- Team and organization data: team names, tags, region, game, roster entries, manager/coach/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 identifiers, email, avatar, and verification status when you use Google sign-in; Google Calendar and Google Sheets data as described below.
- Google Sheets data: spreadsheet ID, spreadsheet name, sheet tab name, mapping cache, sync status, and OAuth access and refresh tokens needed to export PRACC data when your team connects Sheets.
- Support and feedback data: support tickets, ticket messages, staff replies, feedback reports, bug details, screenshots, attachments, and related status or priority metadata.
- AI data: user prompts and messages, assistant responses, action drafts, limited screen context you submit to the AI feature, extracted attachment text or previews, model metadata, token usage metadata, and analysis caches needed to provide AI-assisted review.
- Website and technical data: IP address, approximate country inferred from the IP, browser or device information, app version, operating system, request metadata, diagnostics, crash or error details, security/audit logs, and abuse-prevention counters 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.app.created.
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, encrypted at rest when stored, needed to keep the team calendar connected;
- event IDs, event titles, descriptions, locations, start and end times, updated timestamps, etags, cancellation status, sync tokens, 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 email verification, workspace onboarding, billing, product update, and support messages;
- confirm available billing options, validate payment signals, and review suspected payment abuse;
- 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 and Google Sheets data are 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 workspace 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 connected Calendar or Sheets sync, encrypted at rest when stored, and excluded from normal database reads. When an integration is disconnected, kogni removes the stored Google connection tokens. AI conversations are retained for a configurable period, currently designed around 180 days of inactivity, and AI analysis caches are retained for a shorter configurable period, currently designed around 30 days. Security audit logs are retained for about 90 days unless a longer period is needed for security, abuse, legal, or backup recovery reasons. 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, encryption for stored OAuth tokens, role-based access controls, token access restrictions, rate limits, audit-oriented metadata 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 delete your own AI conversations from the AI Analyst interface where that feature is available.
- You can request export or deletion help for account, team, support, and integration data through the Help page.
- 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.