15. ACCOUNTS, SOCIAL SIGN-IN, PAYMENTS, ACCESS RECORDS, AND STRIPE
Accounts may use an email address, display name, player-name preference where applicable, password-derived authentication records, session information, room-seat links, Visitor title-use records, access-status records, and member-progress records so account features and access limits can work across eligible sessions and devices.
LEDDIE GAMES may offer Google sign-in through a Floot-managed OAuth login service. When a user chooses Google sign-in, the service may receive the user’s Google account identifier, email address, profile name, and profile image for authentication and account creation. LEDDIE GAMES keeps its own account identity, membership, player-name settings, room ownership, billing entitlements, and Member Career separate from the Google account. A new user may create a LEDDIE GAMES account with Google. An existing signed-in member may explicitly link a Google account from My Account so Google becomes an additional sign-in method for that same LEDDIE GAMES user record. Merely matching an email address does not silently merge two accounts.
Linking or unlinking a supported sign-in method does not itself purchase, cancel, transfer, duplicate, reset, or move Visitor title-use records, a Room Rental, Game Pass, All-Access subscription, Member Career record, or other account entitlement. Where unlinking could leave the member without another usable sign-in method, the platform may block unlinking to reduce lockout risk.
When paid access is offered, payment processing may be provided by Stripe. Stripe may collect payment-card, billing, fraud-prevention, and transaction information under its own privacy practices. LEDDIE GAMES is designed to retain platform-side billing identifiers and status information such as a Stripe customer identifier, subscription identifier, payment or subscription status, Room Rental credits, prepaid or room-specific player-seat entitlements, selected Game Pass title, and entitlement dates. The platform is not designed to store full payment-card numbers or card security codes.
Billing and account information may be used to create Checkout sessions, confirm payment, maintain room and player-seat entitlements, enforce Visitor one-play-per-title limits, prevent duplicate fulfillment or access abuse, maintain permitted career tracking, provide subscription-management links, reconcile refunds or disputes, and meet accounting, fraud-prevention, or legal obligations. If a member resets visible career progress, the platform may retain a limited completed-game or anti-replay ledger so old completed rooms cannot be credited again.