KnightGames Privacy Policy

Last Updated: September 14, 2026

This Privacy Policy describes how KnightGames (https://knightgames.app) collects, uses, stores, shares, retains, and deletes information when you use the KnightGames website and multiplayer gaming services.

1. Introduction

KnightGames is an online gaming platform where people can create accounts, join multiplayer game rooms, play social board, card, dice, and party games, maintain player profiles and avatars, connect with friends, view game history and statistics, and use related features such as notifications, feedback, and bug reporting.

This Privacy Policy explains what information KnightGames collects, how that information is used and stored, when it may be shared, how long it is retained, how you can remove linked sign-in methods or request further deletion help, and what choices you have.

By using KnightGames, you acknowledge the practices described here. If you do not agree, please do not use the service.

2. Information We Collect

KnightGames collects information that is needed to operate accounts, run multiplayer games, provide support, and keep the service secure. The categories below reflect what the application actually processes.

Account Information

When you sign in with Google or Yahoo, KnightGames creates or updates a KnightGames account and may store:

  • Email address
  • First name and last name (when provided by the authentication provider)
  • An internal KnightGames user ID
  • The external authentication provider name (for example, Google or Yahoo)
  • The provider’s account identifier for your Google or Yahoo account
  • The provider email associated with that linked identity
  • A JSON copy of the authentication claims returned during sign-in (used for account linking and support)
  • A KnightGames player avatar profile (generated with DiceBear-style options; not your Google or Yahoo profile photo)
  • Optional theme preference associated with your account
  • Optional notification preferences and browser push-subscription endpoints if you enable push notifications

KnightGames does not offer local username/password registration as a primary sign-in path. Sign-in is performed through supported external authentication providers.

Game and Activity Information

To operate multiplayer and related features, KnightGames stores gameplay and activity data such as:

  • Game rooms you create or join (including room codes, host, status, and settings)
  • Players seated in rooms, display names shown in games, and avatar snapshots used in rooms
  • Live and completed game state needed to run matches (for example turns, scores, hands where applicable, and event history)
  • Completed game sessions, results, rankings, and player statistics
  • Friend relationships and in-app invitations where those features are used
  • In-game chat messages sent within supported games
  • Account notifications related to invites, turns, or other service events

Feedback and Bug Reports

If you submit feedback or an in-game bug report, KnightGames may collect:

  • Your message, rating, or problem description
  • Your account identifiers and display name
  • Game, room, and session context needed to investigate the issue
  • Browser user-agent, page URL, viewport/screen size, language, theme, and similar client environment details
  • Optional diagnostic details such as recent client errors or room snapshot data captured for troubleshooting

Site feedback submitted through KnightGames may also be emailed to the KnightGames support inbox using your account email so the team can respond.

Technical and Operational Information

Like most web applications, KnightGames and its hosting environment may process technical information such as:

  • Timestamps of authentication, gameplay, feedback, and system events
  • Browser user-agent and similar request headers when you submit feedback or bug reports
  • Server and application logs used for reliability, debugging, and security
  • Network request metadata that may include IP addresses as processed by hosting, load balancing, or web server logs

KnightGames does not operate a separate advertising analytics product, and the application code does not integrate third-party advertising trackers.

3. Google Sign-In and Google User Data

Users may choose to sign in to KnightGames using Google (“Sign in with Google” / Google OAuth). This section explains how KnightGames accesses, uses, stores, shares, retains, and deletes Google user data.

Access — What KnightGames receives from Google

KnightGames requests the standard Google Sign-In identity scopes: openid, profile, and email.

From a successful Google sign-in, KnightGames receives and uses identity information such as:

  • Google account identifier (subject / NameIdentifier)
  • Email address
  • Given name (first name)
  • Family name (last name)
  • Related identity claims returned by Google during authentication (serialized for account linking)

KnightGames does not receive your Google password. KnightGames does not request access to Gmail, Google Drive, Google Calendar, Google Contacts, or other Google Workspace content APIs as part of standard Google Sign-In.

Use — Why KnightGames uses Google user data

Google user data is used only to:

  • Authenticate you and establish a signed-in KnightGames session
  • Create a new KnightGames account or locate an existing one
  • Link your Google account identifier to your KnightGames user record
  • Display your name in games, lobbies, friends features, and account UI
  • Associate multiplayer activity, scores, statistics, notifications, feedback, and bug reports with your account
  • Support account security and abuse prevention

KnightGames generates player avatars using KnightGames avatar tools (DiceBear-based profiles). KnightGames does not use Google Sign-In as a pipeline to scrape or sync Google profile photos for gameplay avatars.

KnightGames does not sell Google user data. Google user data is not used for targeted advertising. Google user data is not sold to data brokers. Google user data is not used for creditworthiness or lending decisions. Google user data is not used to train generalized artificial intelligence or machine-learning models.

Storage — What is stored after Google sign-in

  • Your email, first name, and last name on your KnightGames user record
  • Your Google account identifier and provider email on a linked identity record
  • A JSON snapshot of the Google authentication claims received at sign-in
  • A KnightGames session authentication cookie so you remain signed in

Google OAuth access tokens and refresh tokens are used only transiently during the authentication handshake. KnightGames is not configured to persist Google access or refresh tokens in its database. After sign-in completes, ongoing session state is maintained by KnightGames’ own authentication cookie—not by storing Google tokens.

Sharing — How Google user data may be shared

KnightGames does not sell Google user data and does not share it with advertisers or data brokers. Google user data stored by KnightGames may be processed by infrastructure providers that host the website, database, and email delivery used to operate KnightGames, and may be disclosed if required by law or to protect security. Limited account information (such as display name and avatar) is visible to other players in games and lobbies you join.

Retention and deletion of Google user data

Linked Google identity information is retained while your KnightGames account remains active and the Google identity remains linked. You can remove the linked Google sign-in method from your KnightGames Account page. Removing KnightGames access from your Google Account settings does not by itself delete your KnightGames account or game history. See Account and Data Deletion for details.

4. Yahoo Sign-In and Yahoo User Data

Users may choose to sign in to KnightGames using Yahoo OpenID Connect / OAuth authentication. This section explains how KnightGames accesses, uses, stores, shares, retains, and deletes Yahoo user data.

Access — What KnightGames receives from Yahoo

KnightGames authenticates with Yahoo’s OpenID Connect endpoints and retrieves user information from Yahoo’s OpenID userinfo endpoint. KnightGames is configured to map Yahoo identity fields such as:

  • Yahoo account identifier (sub / NameIdentifier)
  • Email address
  • Name / display name
  • Given name and family name (when provided)
  • Picture URL claim, if Yahoo returns one (stored only if present in authentication claims; not used as the KnightGames gameplay avatar source)

KnightGames does not receive your Yahoo password. KnightGames does not request Yahoo Mail API scopes (such as mail read access) in application code, and KnightGames does not access the contents of your Yahoo Mail account. KnightGames also does not request Yahoo Contacts access for gameplay.

Use — Why KnightGames uses Yahoo user data

Yahoo user information is used only to:

  • Authenticate you and establish a signed-in KnightGames session
  • Create or locate your KnightGames account
  • Link your Yahoo account identifier to your KnightGames user record
  • Display your name in games and account features
  • Associate gameplay, statistics, notifications, feedback, and support activity with your account
  • Support account security and abuse prevention

KnightGames does not sell Yahoo user data. Yahoo user information is not used for targeted advertising. Yahoo information is not provided to data brokers. Yahoo user data is not used for credit or lending decisions. Yahoo user data is not used to train generalized AI / machine-learning models.

Storage — What is stored after Yahoo sign-in

  • Your email, first name, and last name on your KnightGames user record
  • Your Yahoo account identifier and provider email on a linked identity record
  • A JSON snapshot of the Yahoo authentication claims received at sign-in
  • A KnightGames session authentication cookie so you remain signed in

Yahoo OAuth access tokens and refresh tokens are used only transiently during authentication. KnightGames is not configured to persist Yahoo access or refresh tokens in its database.

Sharing, retention, and deletion

Yahoo user data is shared only as described in How Information Is Shared. Linked Yahoo identity information remains while the identity is linked to your KnightGames account. You can remove the Yahoo sign-in method from your Account page. Revoking KnightGames from Yahoo’s account settings does not automatically delete your KnightGames account or game history.

5. External Authentication Providers

Google and Yahoo operate independently of KnightGames and maintain their own privacy policies and account controls. When you authenticate, KnightGames receives only the information authorized through that authentication process and requested by the KnightGames application configuration.

After KnightGames stores account information derived from an authentication provider, that stored KnightGames data is governed by this Privacy Policy—not solely by Google’s or Yahoo’s privacy policy. You should also review the provider’s own privacy documentation for how they process authentication requests.

6. How KnightGames Uses Information

KnightGames uses information to:

  • Provide, operate, and improve the KnightGames service
  • Authenticate users and maintain signed-in sessions
  • Create and maintain accounts and player profiles
  • Run multiplayer game rooms and synchronize game state
  • Record scores, results, statistics, and related gameplay history
  • Support friends, invitations, and notifications
  • Remember preferences such as visual theme
  • Respond to feedback and diagnose bug reports
  • Send transactional emails such as invitations or support-related messages when those features are used
  • Protect against fraud, abuse, and security threats
  • Comply with legal obligations

KnightGames does not sell users’ personal information.

7. How Information Is Shared

KnightGames may share information in the following limited ways:

  • Other players. Display names, avatars, scores, room membership, and public gameplay information are visible to other participants in lobbies and games you join. Chat messages are visible to players in that game room.
  • Service providers / infrastructure. Hosting, database, and SMTP email providers process information as needed to run KnightGames (for example delivering invite or feedback emails).
  • Avatar image delivery. KnightGames avatar URLs may be served via the DiceBear avatar service configuration used to render player images in the browser.
  • Authentication providers. When you choose Google or Yahoo sign-in, you interact directly with that provider to authorize KnightGames.
  • Legal and safety. KnightGames may disclose information if required by law, legal process, or to investigate fraud, abuse, or security incidents.
  • User-directed actions. Information may be shared when you initiate an action that necessarily discloses it (for example inviting a friend by email).

Service providers should receive only information reasonably necessary to perform their services for KnightGames. KnightGames does not sell personal information and does not share personal information with advertising networks for targeted ads.

8. Cookies and Authentication

KnightGames uses cookies and similar browser storage for essential service functions, including:

  • Authentication / session cookie — keeps you signed in securely after Google or Yahoo authentication (HttpOnly session cookie used by ASP.NET Core cookie authentication).
  • Theme preference cookie — remembers your selected visual theme.
  • Anti-forgery / security tokens — protect forms and state-changing requests.

Some browser features (for example sound preferences or certain game UI preferences) may also use local browser storage on your device. That local storage stays on your device unless the feature also syncs a preference to your account.

These cookies are not advertising cookies. KnightGames does not use advertising or third-party marketing tracking cookies in the application.

9. Data Storage and Security

KnightGames uses reasonable administrative and technical measures appropriate to an online game service, including:

  • HTTPS for data in transit when you use the production website
  • Authenticated sessions for signed-in features
  • Server-side authorization for game actions and account operations
  • OAuth / OpenID Connect for Google and Yahoo sign-in (KnightGames never receives provider passwords)
  • Database-backed account and game storage with access restricted to the KnightGames application and operators

No method of transmitting or storing information on the Internet can be guaranteed to be completely secure. KnightGames cannot promise absolute security, but works to protect accounts and service data using industry-standard practices.

10. Data Retention

KnightGames retains personal information only for as long as reasonably necessary to provide the service and fulfill the purposes described in this Privacy Policy, unless a longer retention period is required or permitted by law.

In practice:

  • Account and linked identity information is retained while needed to operate your account and keep sign-in working
  • Game history, room records, scores, and statistics may be retained as part of the KnightGames service
  • Feedback and bug reports may be retained to investigate issues and improve the product
  • Technical and server logs may be retained for troubleshooting, security, and operational purposes

KnightGames does not currently advertise a fixed automatic deletion schedule for all personal data categories. If you need help with a broader deletion request, contact us using the details below.

11. Account and Data Deletion

Delete Your Account and Data

Signed-in users can manage linked sign-in methods on the KnightGames Account page:

Go to Account — manage / remove sign-in methods

Direct path: https://knightgames.app/Account (sign-in required).

What the Account page currently does

The Account page lets you remove one linked authentication identity (for example Google or Yahoo) or remove all linked sign-in methods. When all linked identities are removed, KnightGames signs you out.

Removing a linked identity deletes the corresponding provider identity record, including:

  • Provider type (Google, Yahoo, etc.)
  • Provider account identifier
  • Provider email stored on that identity row
  • Stored provider claims JSON for that identity

The current Account deletion controls do not automatically erase your entire KnightGames user record, completed game history, scores, statistics, feedback, bug reports, friends data, or avatar profile. Signing in again later with the same provider email may re-link an identity to the existing user record.

If you want KnightGames to delete or further anonymize additional personal information associated with your account beyond unlinking sign-in methods, email admin@knightgames.app from the email address on your account and describe your request. We will review and handle requests as reasonably possible consistent with ongoing multiplayer records, security, and legal requirements.

Revoking access at Google or Yahoo

Removing KnightGames authorization from Google or Yahoo account settings stops future sign-in with that provider until you authorize again, but it does not necessarily delete your KnightGames account or associated personal information stored by KnightGames. Use the KnightGames Account page and/or contact support if you want KnightGames-side data removed.

12. Children’s Privacy

KnightGames is a social multiplayer gaming service intended for a general audience. KnightGames does not knowingly collect personal information from children for the purpose of creating accounts without appropriate parental involvement where required by law.

If you are a parent or guardian and believe a child has provided personal information to KnightGames in a way that concerns you, contact us at admin@knightgames.app. We will review the request and take appropriate steps, which may include deleting or restricting the relevant information where feasible.

13. Changes to This Privacy Policy

KnightGames may update this Privacy Policy when application features change, data practices change, authentication integrations change, or legal requirements change. When we update the policy, we will revise the Last Updated date at the top of this page.

Continued use of KnightGames after an update means you acknowledge the revised Privacy Policy. Material changes may also be communicated through the website or other reasonable notice methods.

14. Contact Us

For privacy questions, deletion assistance, or other requests about this Privacy Policy, contact: