Flex Enjoyer Bot

Privacy Policy

Last updated: 4 November 2026

1. Who is responsible

Flex Enjoyer Bot ("the bot") is a non-commercial hobby project run by a private individual in Germany. Contact for all privacy matters: crazytrixs@gmail.com.

2. Whose data is processed

The bot processes data of members of Discord servers where it is installed. League of Legends data is only processed for members who registered themselves by linking their Riot ID. Members who have not registered are not tracked: they are never looked up on their own, have no profile, rank history or statistics, and no tracking is started for them. The only exception is the pre-game scout described in section 3, which shows the line-up of a registered member's own live game.

3. What is stored and why

DataPurpose
Discord user IDLinking games, titles and settings to a member
Riot PUUID and Riot ID (name#tag)Requests to the Riot Games API, display
Up to two secondary accounts you link yourself (PUUID, Riot ID, current rank)Showing their games and counting your highest rank
Current rank / LP and rank historyLeaderboards, LP calculation, recaps
Match history (champion, KDA, win/loss, LP change, damage, vision, objectives, duration)Result cards, statistics, recaps
Monthly totals and all-time recordsMonthly recap, records
Time of last Discord activityInactivity role
Players in a registered member's live ranked flex game (opponents): PUUID, Riot ID, champion, game ID; their public rank is fetched once per game and cached for 6 hoursPre-game scout card and the "last duel" hint when the same players meet again
Entries in the bot's in-server features (titles, quests, lobbies, board entries, virtual points without monetary value)Providing those features

To detect games, the bot reads a member's Discord status (whether League of Legends is running) and voice channel presence. Only timestamps and counters derived from these are stored, not their content.

4. Who can see the data

Cards and statistics are shown only inside the Discord server where the member registered. The companion bot "Capy", run by the same operator, has read-only access to the same database to post recaps and to answer questions about statistics in the same Discord server. Data is never sold and never shared with third parties. The bot is hosted on a private server in Germany; databases and backups do not leave it.

5. Retention

Stored data is cleaned up automatically once a day.

DataDeleted after
Individual games with full details (match history)150 days (aggregated into monthly totals first)
Compact game record per player (champion, role, KDA, LP change, damage, CS, vision, duration) for rank goals, duo and flex-stack statistics400 days after the game
Rank snapshotsthinned to one value per day after 21 days, deleted after 45 days
Daily rank values (end, high and low of each day)400 days
Finished rank goals400 days
Players seen in live games of registered members (pre-game scout)400 days after the game
Open game detections3 days
Technical tracking rows, daily quests180 days
Finished lobbies, in-house rounds, quiz progress10 days
Finished duo and scrim entries30 days
Other finished board entries60–90 days
Database backups14 days

Kept until you delete your data (section 6): registration, linked secondary accounts (or until you unlink them), monthly totals, all-time records, titles, the end-of-split summaries (your frozen results of a finished ranked split) and the results of community challenges you took part in (shown in the Capy Museum).

6. Unregistering and deletion

7. Your rights

Under the GDPR you have the right to access, rectification, erasure, restriction of processing, data portability and objection. Contact the address above. You also have the right to lodge a complaint with a data protection supervisory authority.

Legal basis: your consent when registering (Art. 6(1)(a) GDPR).

8. This website

This website uses no cookies, no analytics and no external fonts or scripts. The hosting provider (Cloudflare) processes technical access data such as IP addresses to deliver the site and protect it against abuse.

9. Changes

Changes to this policy are published on this page with a new date.