Privacy at LammaGo

Creating an account stores your email address, an authentication credential, and an optional public display name. Your email is used for signing in and account recovery; it is never shown to other players. Display names are public in social features (challenges, leaderboards and rivalries). If you never set a display name, LammaGo generates a friendly, positive placeholder from system data — never your email, account id or other personal details.

Game results, Daily/Weekly scores, streaks, experience and unlocked achievements are saved locally in your browser, and — when you are signed in — synced to your account so they appear on other devices. Daily and Weekly leaderboard entries you choose to enable are visible to other players (your display name and score only).

When you create a challenge or a rivalry match, LammaGo stores the challenge snapshot (the five games and their settings), scores, safe display names, and timestamps needed to show the head-to-head record. Rivalries are visible only to the two players involved. Challenge and team invite links use random capability tokens; anyone with the link can open the invite, but only participants can see the full private record.

LammaGo uses its own first-party analytics to understand which features are used and where people get stuck. It is pseudonymous: events are linked to a random anonymous id stored in your browser and a rotating session id, never to your name or email. Analytics are on by default and you can turn them off at any time.

• Event names and coarse properties (for example: page or game, mode, a score band, an outcome, a selected button).
• Sanitised route templates (dynamic identifiers such as challenge or rivalry tokens are removed).
• Coarse device and browser category, and a viewport size bucket.
• Referring domain and campaign parameters when present.
• Performance measurements (Core Web Vitals: LCP, INP, CLS, TTFB, FCP).
• Coarse country and region when the hosting platform supplies them.
• Security-relevant events, such as rate limiting or denied admin access.

When you are signed in, future analytics events are associated with your account internally so the operator can understand retention. Your name and email are never attached to analytics events.

The product analytics system is deliberately built to avoid collecting the following. It is designed not to intentionally collect:

• Account passwords.
• Authentication tokens or session credentials.
• A lasting history of your raw IP address.
• Precise GPS location.
• Keystrokes or typed input.
• Clipboard contents.
• Browser fingerprints.
• DOM snapshots or session replay.
• Puzzle answers, seeds or hidden solutions.
• Arbitrary form contents.

You can turn product analytics off in your Account settings. When it is off, no analytics events are sent from that device. If your browser sends a Global Privacy Control (GPC) or “Do Not Track” signal, analytics are disabled automatically and the setting in your account cannot override it.

As currently documented, product analytics events and security events are retained for about 90 days and presence data for about 2 days; older rows are removed by a maintenance routine. Your account data (profile, stats, challenge and rivalry history) is kept while your account exists.

• Play without an account at all.
• Turn product analytics off (or rely on your browser's GPC signal).
• Download a copy of your account data from the Account page.
• Ask for your account to be deleted.

Account deletion requests are handled through the Account page. Deleting an account removes your profile and account-owned data (stats, achievements, leaderboards, owned challenges) and anonymises the name shown on historical head-to-head records so other players’ match history stays intact.

A support contact will be published here before public launch. This is a placeholder in the current build.