Updated
Privacy policy
Play without optional statistics. Your game data and your analytics choice are handled separately.
Who operates Lolzy
Lolzy is operated under the name Lolzy (MikuBets). For privacy questions or requests, contact:
Playing and public rankings
When you use a game, Lolzy uses the HttpOnly rift_player cookie to recognise your browser and keep server-side progress, scores and game history. Your chosen language and temporary ranked-run state also use browser storage. This processing provides the service you request; proportionate security measures rely on the legitimate interest of protecting that service.
A nickname and run time appear in public rankings only when you explicitly publish a run. You can hide your ranking entry using the ranking visibility controls. Hiding an entry does not erase your private game history.
Esports favorites and the “My teams” filter are requested features stored only on this device in lolzy_esports_favorites_v1 and lolzy_esports_my_teams_v1. They do not sync between devices or require optional statistics.
The private management panel uses Sign in with ChatGPT and checks the signed-in account against the owner’s server-side access list. Usage and service statistics are not publicly available.
Optional usage statistics
Optional first-party statistics are off until you explicitly agree. They help us understand visits, which games people start or complete, and returning visits. A separate random HttpOnly cookie, lolzy_metrics, identifies an opted-in browser; it is not linked to your player profile.
Lolzy’s own game-statistics fields are limited to the UTC day, game, casual/ranked mode, language, a broad source category (direct, x, discord, reddit, youtube, tiktok, search or other), and start, completion or outcome information. Separate random technical event/run identifiers prevent duplicate counts and link starts with completions; they are not player-profile IDs. These first-party game statistics do not store answers, nicknames, player-profile IDs, full URLs or queries, raw referrers, IP addresses or user agents.
An optional browser queue and run links support delivery and counting only after you opt in. Withdrawing consent immediately stops new browser events and clears this optional local state. Lolzy requests deletion of the analytics cookie, server identity and linked duplicate-prevention rows; if the server cannot be reached, deletion is retried when connected. Existing daily aggregate counts without visitor identifiers remain.
With your optional-statistics consent, Cloudflare Web Analytics separately measures page visits and loading performance. Its reports include page paths, referring-site information, country, device type, browser and operating system. Its script and reporting requests go directly to Cloudflare and share the network information needed to make those requests. These measurements are separate from your Lolzy player profile.
This provider is new, so Lolzy asks you to renew your optional-statistics choice before enabling either statistics service. You can withdraw that choice in privacy settings. If the Cloudflare script has loaded, the page reloads with it disabled; a final report may be sent during that reload. Disabling collection does not delete measurements already sent to Cloudflare.
Only if you accept optional statistics, Lolzy measures esports interactions using fixed action types and public match, player, team or competition IDs, plus numeric browser load, DOM and early layout-shift measurements. No browsing URLs, answers or names are sent. Deduplication receipts expire within 90 days and are deleted when consent is withdrawn; anonymous daily aggregates remain.
For service reliability, Lolzy stores aggregate totals of fixed service names, response status codes, request duration and stale-response indicators, without a visitor identity. These operational totals are separate from optional usage statistics.
Storage and retention
| Storage | Purpose | Lifetime |
|---|---|---|
rift_playerHttpOnly cookie | Recognise your browser and save game progress, scores and history. | 1 year |
rift-language / lolzy_daily_expanded_v1 / lolzy_esports_favorites_v1 / lolzy_esports_my_teams_v1localStorage | Remember your chosen language. Remember whether daily challenges are expanded or collapsed (open/closed), without an identifier. Esports favorites and the “My teams” filter are requested features stored only on this device in lolzy_esports_favorites_v1 and lolzy_esports_my_teams_v1. They do not sync between devices or require optional statistics. | Until cleared |
| Ranked-run statesessionStorage | Keep the current ranked run and prevent duplicate actions. | Until the tab/session ends |
lolzy_privacy_v1 / lolzy_privacy_deny_session_v1localStorage / sessionStorage | Remember an explicit optional-statistics choice. A necessary session-only denial marker, without an identifier, prevents an old permission from returning after a reload when browser storage cannot save withdrawal. It is cleared on explicit acceptance or when the tab/session ends. | 365 days / Until the tab/session ends |
lolzy_metricsHttpOnly cookie | Recognise a consenting browser for optional statistics, separately from the player profile. | 90 days |
lolzy.analytics.v1localStorage | Deliver opted-in statistics and associate a start with its completion. | Until overwritten, cleared or consent is withdrawn; not restored after 90 days from the last save. |
lolzy.analytics.revoke-pendinglocalStorage | Remember a pending analytics-deletion request after withdrawal, without storing event data. | Until the server acknowledges deletion; retried when connected. |
Cookie lifetimes describe storage in your browser, not automatic deletion of all server records. Game progress, scores and history currently have no automatic server-deletion schedule; you can request deletion by email.
An analytics identity is valid for 90 days from its latest consented use or renewal; individual duplicate-prevention and visitor-day records expire independently after 90 days. Expired records are removed progressively by automated, bounded cleanup when later consent or event requests reach the service. Daily aggregate counts are kept without visitor identifiers.
Cloudflare currently makes Web Analytics reports available for up to six months. Its reporting, aggregation and retention are described in the linked Cloudflare documentation.
Service providers and external links
Hosting is provided through Sites (OpenAI) and Cloudflare. These providers process network and technical information needed to deliver and protect the website. Requests for remotely loaded Google Fonts also send the browser’s network information to Google. These service requests are separate from Lolzy’s optional analytics.
External links, including X and Riot Games credits, lead to services with their own privacy policies when you click them. The providers’ policies explain their processing, locations and applicable transfer arrangements:
The esports match centre obtains LoL Esports data through Lolzy’s server. Team and league logos can load directly in your browser from official logo CDNs (static.lolesports.com, am-a.akamaihd.net and cmsassets.rgpub.io), sharing the network information needed for those requests.
Advertising
Google advertising is currently disabled pending configuration of a certified consent-management platform. Lolzy’s optional-statistics choice does not authorise Google advertising. If advertising is enabled later, its consent will be requested and managed separately through the relevant Google-certified message.
Your choices and rights
Use the privacy-settings button below to refuse or withdraw optional statistics at any time. Refusing them does not prevent you from playing. You can also clear site storage through your browser; this may remove language preferences or access to saved progress, and does not itself request deletion of server-side game data.
Where applicable, you can request access, correction, deletion, restriction, objection or portability by contacting the email above. Reasonable verification may be needed to protect your records. You may complain to your local data-protection authority, including Spain’s AEPD.
Changes to this policy
This policy reflects the features and data use described above on the update date. It will be revised when those practices change; additional optional purposes will require a new choice.