Lvlup App — Companion for Tournament & Team Coverage | Lvlup
The app carries the same editorial coverage the desk publishes on the web. It is a companion, not a separate product. Downloads carry the publisher age and jurisdiction rules.
What we know and what is still under verification
Verified items as of 01 August 2026
DESK CONFIRM| Item | Detail | Source |
|---|---|---|
| Domain | lvlupin.com — published 2026 | Domain registry · A |
| Editorial desk | Lvlup newsroom — broadcast-grade esports coverage | Editorial standard · A |
| Editorial independence | Lvlup coverage decisions are made by the editorial board | Editorial charter · A |
| Age gate | Where wagering routes connect (download, bonus, refer), publisher's age & jurisdiction rules apply | Editor's read · C |
| Operational details | Office location, customer-care phone lines, ownership — to be verified through public records before publishing | Editor's read · C |
Editorial scope of a brand SERP cluster page
What's verified
Items the desk can tie to a publisher feed, registry, or independent press. Stamped Tier A.
What's open
Items awaiting verification. Listed under VERIFICATION PENDING. Desk commits to a check-back date.
What's interpretation
Editorial framing of the verified items. Tier C, flagged in line.
Brand SERP cluster — every canonical brand-intent page
Brand SERP cluster FAQ
Where money is involved, age and jurisdiction apply.
This is a Brand SERP cluster page maintained by the Lvlup editorial desk. Wagering and account mechanics are publisher-controlled; Lvlup does not represent any product as appropriate for any specific reader.
The Lvlup companion app — what the editorial desk publishes inside it
The companion app is the desk's reader-supported companion product. It carries the same editorial coverage the desk publishes on the web, plus app-specific features that take advantage of push alerts and per-team filters. This page describes how the desk's coverage surfaces inside the app, not what the app is structurally — the app store page covers the structural description.
Editorial coverage inside the app
The companion app's coverage is the desk's coverage. A reader following a single team inside the app sees the same verified scores, the same editorial reads, the same corrections log as a reader following the same team on the web. The only difference is the alert cadence: the app pushes alerts 24 hours before every match day for teams the reader follows, and pushes breaking news for any team that lands a Tier-A roster move.
The app's reading list is built per-team. A reader who follows Sakura Apex sees a Sakura Apex reading list; the list pulls from the desk's coverage shape across the eight desks. The list is generated nightly; the list updates when the desk publishes a Tier-A correction.
App-specific features
The app carries four app-specific features: a daily fixture timeline, a per-team alert slider, a patch-watch rail, and a corrections shortcut. Each feature maps to a desk beat — fixtures to the matches desk, alerts to the rosters desk, patch-watch to the games desk, corrections to the editorial board.
The daily fixture timeline is the app's signature construct. It carries every fixture across the four regional series for the next 48 hours, with the same verified scores and editorial reads as the matches page. The timeline is interactive on app surfaces — readers can scroll across the timeline, tap into a preview ledger, and save the fixture to their per-team alert list.
What the desk does not publish inside the app
The desk does not publish wagering tips inside the app. The desk's editorial coverage ends at preview, post-match and editorial interpretation. Where a publisher product is referenced inside the app, the reference is editorial framing — the publisher's commercial mechanics remain publisher-owned.
The desk does not collect any data inside the app that is not needed for the app to operate. The app's telemetry is per-anonymous; it does not share data with the editorial desk or with advertisers. The desk does not run retargeting pixels inside the app.
The desk does not push notifications that violate the reader's chosen preferences. The reader's per-team alert slider is the only source of push notifications; the desk does not push unscheduled notifications outside the per-team alert list.
Reader questions the desk gets on the companion app
The companion app is the desk's most-engaged reader surface. Below are the questions the desk receives most often.
Do I need an account to read the desk coverage?
No. Reading the desk coverage on the web does not require an account. The companion app's coverage surfaces are the desk's coverage; reading them inside the app does not require an account, only the alert slider you want.
How do alerts work?
Alerts push via standard mobile push notification. Each alert carries the desk Tier-A stamp; each alert links to the desk's matching editorial surface. A reader can configure their per-team alert slider to limit alerts to the teams they follow.
Can I subscribe to a single tournament?
Yes — the per-team alert slider extends to per-tournament alerts. A reader who follows Sakura Apex and the APAC Major will receive APAC Major alerts even if they do not follow any other team.
Can I export my alert log?
Yes — the companion app exports an alert log on request. The export is delivered via email; the export carries the alert timestamp and the alert's editorial surface.
Is the app free to install?
The app follows the publisher pricing. The publisher controls the app's price and any subscription the reader opts into. The desk does not run the app or its pricing.
The four app-specific features and how the desk maps each to a beat
The companion app carries four app-specific features, each mapped to a desk beat. The mapping is the desk's editorial scaffolding — when the app surfaces a new feature, the desk maps it back to the desk beat so a reader can follow the editorial surface back to the newsroom.
Feature one — daily fixture timeline
The daily fixture timeline is the app's signature construct. It carries every fixture across the four regional series for the next 48 hours. The timeline maps to the matches desk: every fixture is anchored against a verified score and an editorial scenario.
Feature two — per-team alert slider
The per-team alert slider is the app's reader-side construct. The slider lets a reader pick the team or teams they want to receive alerts about. The slider maps to the rosters desk: every roster move on a followed team produces an alert.
Feature three — patch-watch rail
The patch-watch rail surfaces the next major patch and the recent balance updates. The rail maps to the games desk: every patch read on the rail is anchored against the publisher's balance log and the desk's editorial scenario.
Feature four — corrections shortcut
The corrections shortcut surfaces the most recent corrections log entry inside the app. The shortcut maps to the editorial board: every corrections entry is on the corrections log with a timestamp and a re-citation.
Why each feature maps back to a beat
The mapping is editorial. A reader who follows a single team inside the app can see which beat a feature maps to, can locate the editorial surface behind the feature, and can follow the editorial surface back to the source. The mapping is the desk's commitment to editorial transparency — the app's features are not magic; they are surfaces over the desk's beats.