Public Telegram bot
Core team-organization flow
Riot product review
A transparent view of LeagueCaller
LeagueCaller is an unofficial Telegram bot that helps existing friends organize friendly League of Legends sessions. The live product works without Riot API access; all public Riot API features remain disabled until written production approval is received.
Public Riot API features
Pending written production approval
Telegram Stars
No production invoices or paid entitlements
Product purpose
Coordination, not competitive advantage
The product replaces scattered group-chat messages with a single invitation card, role selection, reserve list, reminders and a ready-check. It is designed for pre-game social coordination among friends.
LeagueCaller does not modify the game client, provide live tactical recommendations, scout opponents, calculate an alternative MMR or ELO, enable betting, or resell raw Riot API data.
Live core flow
What users can do today
These are real public-bot screens. The workflow does not require Riot API data.
Game invitation
One message tracks time, responses, confirmed players and reserve.
Role selection
Participants choose preferred positions before the lobby starts.
Ready-check
The group confirms availability immediately before the planned start.
Riot data flow
Fail-closed until approval
The production build gates all public Riot API calls. This is the complete intended approved-stage user flow.
- 01
Open Riot ID
The user sees what data would be requested, why it is used, and that manual Riot ID entry does not prove account ownership.
- 02
Explicitly submit an ID
No Riot profile request is inferred from Telegram identity or from membership in a friend circle.
- 03
Current gate stops the request
Until written production approval, the bot returns an unavailable-state message and makes no public Riot API call.
- 04
Approved-stage public lookup
After production approval only, Account, League and Match requests may run as a transient lookup. The result is public profile data and never claims that the requester owns the Riot account.
- 05
RSO for account-specific features
Persistent linking, Spectator checks and post-match notifications remain disabled unless Riot separately approves RSO and the relevant use. They would require authenticated ownership plus an off-by-default opt-in.
- 06
Unlink or delete
If account linking is approved later, “Unlink Riot account” removes identifiers and caches.
/delete_mestarts full LeagueCaller account-data deletion.
Endpoint matrix
Purpose-limited API use
APIIntended useCurrent state
account-v1Resolve a user-submitted Riot ID for a transient public lookupDisabled pending approvalleague-v4Show a public ranked snapshot without claiming account ownershipDisabled pending approvalmatch-v5Show a short public match summary after an explicit lookupDisabled pending approvalspectator-v5Account-linked live status only after RSO and separate Riot acceptanceDisabled; not part of initial launchStatic champion and item information may come from Riot’s Data Dragon or official patch publications. It is not used to provide live competitive guidance.
Safeguards
Data minimization and user control
No passwords or API keys
The bot never asks for a Riot password, Telegram password, two-factor code or Riot API key.
Short-lived caches
Rank snapshots expire after 24 hours without refresh; match summaries after 30 days; live status within 24 hours.
Documented backups
The Essential-0 scheduled backup policy retains 7 daily and 1 weekly snapshot; Heroku stores PGBackups in the United States.
Monetization remains off
No Stars invoice is created and no paid entitlement is active while approval and legal setup remain incomplete.
Policies and contact
Reviewer resources
This English page is the reviewer summary of current status, intended data flow and safeguards. The controlling legal documents are currently published in Ukrainian with Russian equivalents.