Skip to main content

Data we collect

S
Written by Support

Nekolytics collects data on a need-to-know basis. This document includes all of the data that we collect and what we use it for.

We keep data collection minimal to reduce the risk for our users. We do not sell your user data to 3rd parties.

  1. Account information (email addresses, names, display names, public handles, internal user IDs, and authentication-provider IDs)

    1. This is data you provide to us to create your Nekolytics account. Your chosen authentication provider (ex. Discord) may also forward some of this information to us

  2. Game identifiers (in-game usernames/gamertags, previous usernames, game regions, platforms, game account IDs, and linked accounts)

    1. This is data that you provide to us when you bind an in-game account to your Nekolytics account

  3. User metadata (IP addresses, device/request identifiers)

    1. We collect user metadata to detect and block abuse to our services. We may also use this metadata with diagnostics to identify and resolve bugs

  4. Game data (match history, timestamps, teams, characters, maps, modes, outcomes, ranks, ratings, gameplay events, and performance statistics).

    1. This is data contained or derived from the replay file

  5. Social relationships (in-game friends and friendship levels, on-platform friends, follows, friend requests, and blocks).

    1. These are used to allow you to better share information within your friend groups

  6. Replay files (files uploaded by users, forwarded by partners, or obtained from game providers, including filenames, file sizes, file hashes, and upload timestamps)

    1. These are the files that you or our partners who host tournaments upload to our service

  7. Sessions and preferences (session cookies, session IDs, authentication tokens, language preferences, privacy settings, and sharing preferences)

    1. This allows you to stay logged into our service and save you preferences (ex. How the UI is displayed)

  8. Browser diagnostics and session recordings (error reports, website performance, and recordings of website interactions)

    1. This is used by our developers and our product managers to fix bugs or determine what our next feature or feature improvement we should add

Did this answer your question?