WehniX Launcher

Privacy Policy

Effective November 15, 2026 · Version 2026-11-15-beta

This policy explains how the WehniX Launcher public beta, its account service and this release website handle information.

Launcher account information

Sign-in uses Google or GitHub through Supabase. The provider and Supabase process authentication information, including the account identifier, email address and profile information the provider shares. The launcher profile stores your account identifier, chosen display name, avatar URL, primary sign-in provider, registration time, accepted Terms version and acceptance time, and record creation and update times.

Device registration stores an installation identifier, launcher version, and first-registration and last-seen times linked to your launcher profile. These records support account access and device registration. Requests to authentication and hosting services also expose ordinary connection information such as IP addresses and request metadata to those services.

Information on your Mac

The launcher stores application settings, linked store account information, library metadata, installed engines, bottles, game files, saves, backups and diagnostic logs on your Mac. Launcher and Steam session credentials persist in private application-support files protected by filesystem permissions. These token files are not encrypted storage. Other store helpers also keep local authentication state needed to access the stores.

The launcher account database described above stores profiles and device registrations. Game installation and save synchronization use the relevant store services as described below. Local diagnostics and any files you choose to submit for support can contain identifiers, paths or technical details, so review them before sharing.

Connected game stores and cloud saves

When you connect Steam, Epic Games or GOG, the launcher and its helpers communicate with that provider for sign-in, account details, ownership and library information, downloads and related game services. Credentials and session tokens are used with the relevant provider. Store account information and library caches are retained locally for those features.

Steam Cloud synchronization transfers supported save files and file metadata between your Mac and Steam. It may run before play and after a game session. Runtime switching can also copy saves between local environments and retain local backups. Games you launch may separately send information to their publishers or other services under their own policies.

Website, updates and downloads

This release website is hosted on Cloudflare. The site requests public GitHub release information and provides release and update links. Your browser, the launcher and download tools contact Cloudflare, GitHub and relevant download hosts when requesting pages, update information, engines or release assets. Those providers receive network request information and apply their own policies.

This release website has no account sign-in form, advertising or third-party analytics script. Its public pages do not require a tracking cookie. Provider sign-in pages and external websites may use their own cookies and storage. Profile avatars may be fetched from the provider URL, exposing a normal image request to that provider.

Use, access and retention

Account information is used to authenticate you, maintain your profile, record your Terms acceptance and register launcher installations. Supabase hosts the launcher account service. Account database policies restrict profile and device access to the relevant signed-in account, with privileged service operations for registration and deletion.

Account records remain until you delete your launcher account or the service removes them. Deleting the account through the launcher removes its Supabase authentication user and associated profile and device records. Local games, bottles, saves and backups remain on your Mac. External store accounts and data held by game providers are managed through those providers. Infrastructure logs and backups may be retained under the hosting providers’ operational policies.

Your choices and questions

You can edit your launcher display name, sign out or delete your launcher account using the application’s account controls. You can manage local files and connected store accounts through the launcher and the relevant provider. Requests about access, correction or deletion can be raised through the existing WehniX Discord community. Avoid posting credentials or private account data in public channels.

The older WehniX website and Community service use a separate backend and policy. This policy describes the launcher beta and this release website. If this policy changes, the revised effective date and version will appear here.