Skip to main content
This page is the canonical player-facing Terms of Service document linked from the lollol.fun app.

1. Acceptance of these terms

By signing in to lollol.fun, accessing the app, or continuing to use player-facing features, you agree to these Terms of Service and the related documents published in this docs site, including the Privacy Policy. If you do not agree, do not use the service.

2. Eligibility and account access

  • Sign-in is currently available only through a Google account.
  • You are responsible for using an account you are authorized to control.
  • You must comply with any eligibility, usage, or access restrictions that apply to your jurisdiction, platform status, or account standing.
If your account is limited, reviewed, or temporarily restricted, see Account Restriction & Protection.

3. Account responsibility

You are responsible for:
  • Maintaining control of the Google account you use to sign in.
  • Keeping your own device, browser session, and wallet access secure.
  • Reviewing your activity, balances, and transaction history through player-facing product surfaces such as My Activity and Wallet.
  • Contacting support promptly if you believe your account activity is incorrect or unauthorized.
lollol.fun may rely on the authenticated account session as the source of truth for player actions taken through the app.

4. Acceptable use

You must not:
  • Attempt to bypass product restrictions, safety checks, or fair-use controls.
  • Abuse promotions, rewards, missions, refill rules, or other player incentives.
  • Use the service in a way that interferes with platform integrity, security, or other players.
  • Misrepresent identity, ownership, or authorization when using the service or contacting support.
lollol.fun may apply protective actions when activity appears abusive, suspicious, or inconsistent with fair use.

5. Balances, points, and player-visible rules

lollol.fun uses player-visible balance surfaces that may distinguish between Locked and Unlocked value.
  • Player-facing semantics are described in the docs and in-app balance surfaces.
  • Reward eligibility, claim state, daily windows, and related operational rules may be subject to published policy and UTC-based timing rules.
  • Feature-specific rules for games, prediction markets, lotto participation, refill flows, rewards, and wallet actions are described in the relevant guides and policy pages.
Where a feature exposes a specific player rule in the docs, that published rule is the canonical explanation for the player experience.

6. Wallet and withdrawal boundaries

Wallet and withdrawal behavior may be subject to:
  • Status progression and review steps
  • Operational or risk-based checks
  • Fee-aware amounts and processing constraints
  • Runtime-configurable limits or cooldowns
Player-facing withdrawal explanations are documented separately so that stable guarantees and changeable operational controls are not confused. For current guidance, see the docs policy hub and the wallet-related help surfaces in the app.

7. Fairness and result review

Where supported, lollol.fun provides player-facing fairness and result review surfaces.
  • Reveal data may only become available after a game or result reaches a terminal state.
  • Feature-specific verification expectations are explained in the relevant game guides and fairness-related docs.
The existence of a fairness review surface does not remove your responsibility to review the product rules before taking action.

8. Account restriction, suspension, or protection actions

lollol.fun may limit, review, or temporarily restrict access to protect players, maintain fair use, or respond to security concerns. Examples can include:
  • Limited access to some features
  • Temporary review-related restrictions
  • Additional support verification before certain actions are resumed
See Account Restriction & Protection for the player-facing support process.

9. Service changes

lollol.fun may update, replace, suspend, or remove player-facing features, flows, limits, or policy pages over time. When player-facing rules change, the authoritative version is the latest published version on this docs site and the current behavior exposed in the live app.

10. Contact

For support, reports, or appeals, use Contact / Report / Appeal. When contacting support, include enough detail for the team to identify the issue, such as your player ID, what happened, when it happened, and screenshots if available.