Skip to main content

1. Purpose

This page explains the player-facing balance model used by lollol.fun. The product may show different balance surfaces for different features, but the core player-facing distinction is between Locked and Unlocked Points.

2. Locked vs Unlocked

Locked Points

Locked Points are player-visible value that is subject to usage restrictions defined by the product. Depending on the feature, locked Points may:
  • Appear in balance and activity surfaces
  • Count toward some player-visible calculations
  • Be issued through refill, reward, mission, or leaderboard flows
  • Remain subject to different usage or withdrawal rules than unlocked value

Unlocked Points

Unlocked Points are player-visible value that is generally treated as the more freely usable balance surface in the app. Where the product distinguishes between locked and unlocked balances, unlocked value is the balance players should treat as the more readily usable side of the pair.

3. Where players can review balances

Players can review balance-related information through player-facing surfaces such as:
  • My Activity
  • Wallet
  • In-app balance widgets
  • Feature-specific result and history views where balance changes are reflected
If a balance view appears delayed, refresh the relevant player-facing page and then contact support if the issue persists.

4. Reward and refill interactions

Some product features may credit value as locked Points rather than unlocked value. Examples documented in the current player docs include:
  • AIRDROP mission rewards
  • Leaderboard rewards
  • Points Refill
If a feature guide states that a reward is paid as locked Points, that guide and this policy should be read together.

5. Season and policy timing

Where the product uses daily windows, reset boundaries, or policy periods, the canonical time basis is UTC unless a more specific player-facing rule is published for that feature. Examples in the current docs include:
  • AIRDROP daily reset at 00:00 UTC
  • Policy windows that are published for a defined UTC period
Players should treat the published UTC-based rule as authoritative rather than relying on local device time.

6. Operational interpretation

This policy explains player-visible semantics only. It does not promise:
  • A specific internal ledger design
  • Permanent treatment of every runtime-configurable operational value
  • That every feature uses identical balance behavior
When a feature has its own documented rule, that feature-specific rule applies alongside this shared balance policy.