Privacy Policy
This page explains what personal data LMUHub collects, why it is collected, how it is used, and what control users have over that information.
Who This Applies To
This privacy policy applies to LMUHub and the services available through lmuhub.com, including accounts, the forum, schedule pages, setup pages, and related community features.
LMUHub is an independent community project and is not affiliated with Motorsport Games or Studio 397.
Information We Collect
LMUHub may collect account details such as email address, username, password hash, Discord account identifier when Discord login is used, profile preferences, forum posts, setup submissions, moderation reports, and support or contact messages sent to the project.
LMUHub also collects technical and usage information needed to operate the service, such as browser or device details, request logs, authentication events, a minimal first-party anonymous analytics cookie used for baseline traffic measurement, limited first-party request metadata used for aggregate measurement and abuse prevention, and analytics measurement data through Google Consent Mode and optional analytics tooling.
For baseline measurement, request metadata may include a normalized IP prefix. This is used to support aggregate measurement and basic abuse prevention, and is not used for advertising.
How We Use Information
Information is used to create and secure accounts, let users log in, operate the forum and setup features, moderate abuse, respond to support requests, diagnose reliability issues, and improve the product.
Email addresses may also be used to send necessary account and service communications, including sign-up or onboarding emails, password reset emails, login or security-related notices, and other operational messages directly related to use of the service.
Baseline first-party traffic data is used to understand aggregate page demand and reliability trends. Google Analytics runs with consent controls: with “Essential Only” it remains cookieless and limited to aggregate signals, and LMUHub may forward baseline page-view signals server-side in cookieless form for aggregate reporting; with “Accept Analytics” it can use analytics cookies for richer measurement. Additional optional tooling (such as Vercel analytics) only loads after analytics is accepted.
Legal Bases
LMUHub processes personal data where it is necessary to provide the service requested by the user, where it is necessary for legitimate interests such as site security, moderation, reliability, and abuse prevention, and where consent is required for optional analytics or similar tracking technologies.
Sharing And Processors
LMUHub uses third-party infrastructure and service providers to operate the site, including hosting, database, authentication, and analytics providers. Those providers may process personal data on LMUHub’s behalf only to the extent needed to run the service.
Personal data is not sold.
Retention
Account data, forum content, and related service records are kept for as long as reasonably necessary to operate the service, maintain records of community activity, comply with legal obligations, or resolve disputes. Data may be deleted or anonymised when it is no longer needed.
User Rights
Depending on applicable law, users may have rights to access, correct, update, erase, restrict, or object to certain processing of their personal data. Users may also change analytics preferences or opt out of baseline measurement at any time through the analytics settings linked in the footer.
Requests relating to personal data or account information can be directed to the creator via Discord at @masster3.
Security
LMUHub stores passwords as strong password hashes rather than plaintext, keeps long-lived session refresh tokens in secure cookie-based server-side session flows, applies rate limiting to authentication routes, and uses transport security in production. No internet service can guarantee absolute security.
Changes To This Policy
This privacy policy may be updated from time to time as LMUHub changes or legal requirements evolve. Continued use of the site after an update means the revised version applies from the date shown on this page.