Ascend at a glance
The rest of this website is in Italian, the language of our community. This page summarizes in English what Ascend does, how it uses the VALORANT API and how it follows Riot's policies.
1. What Ascend is
Ascend is a free, ad-free public Discord community for Italian VALORANT players, built around healthy competition and personal growth. Its bot, Coach, turns the competitive matches of members who opt in via Riot Sign On into personal stats, community leaderboards, a weekly recap and simple post-match coaching tips in Italian.
- The public server opens once the production key is approved; anyone will be able to join. It is not a private, personal-use or friends-only server.
- No paid features, no ads, no donations.
- Only competitive (ranked) matches are tracked. Other queues are ignored and never downloaded.
- EU (Italian) players only, on PC.
2. User flow
The flow is illustrated step by step, with mockups, in the "Come funziona" section of the home page.
- In Discord, the member runs
/collega("link"). Coach replies privately with a single-use link valid for 10 minutes. - The link opens a consent page that explains what we store, why, who can see it and how to delete it. It clearly states that linking makes the player's match stats public in the community and on this website, and that players who have not linked are never shown. The player confirms they are at least 14 (the Italian age of digital consent) and accepts the privacy policy.
- The player logs in on Riot's own RSO page. We never see their credentials.
- Our server exchanges the authorization code, calls
/riot/account/v1/accounts/meonce to read the PUUID and Riot ID, then discards the access token. Nooffline_access, no stored RSO tokens. - A background worker loads the player's competitive matches from the last 30 days, then checks for new matches periodically.
- The player uses
/stats, appears in leaderboards once they reach a minimum number of matches, and is included in the Monday recap. /scollega("unlink") deletes all of the player's data immediately;/privacyshows or exports it.
3. Policy compliance
- Opt-in only. No data is collected or shown for players who have not linked via RSO; we never look up players by Riot ID. Match details include all ten players: data of non-opted-in players is used only in memory (for example, to find who got the first kill in a round) and is never stored or shown. Players hidden by the game are never analyzed.
- Official rank only. No MMR or ELO calculators and no estimates of hidden RR. The rank leaderboard uses the official tier and, for Immortal and Radiant, the official Rank Rating from VAL-RANKED-V1. Below Immortal, players of the same tier are shown as ties.
- Post-match only. Coaching uses completed matches. No overlay, no live assistance, no scouting of opponents. Tips never discourage the use of any agent or map.
- Players are honored, never shamed. Only positive milestones are announced, leaderboards never highlight drops, and coaching tips and weak spots are visible only to the player they belong to.
- No alternate reporting channel. Our report command covers only behavior inside the Discord server; for cheating or toxicity in matches, players are directed to the official in-game report system.
- Player of the week. Every Monday one opted-in member is chosen from that week's competitive stats (combat score, win rate, KDA, ADR, matches played), with a minimum number of matches. It is announced with the real numbers, resets every week and is never shown as a rating or next to the official rank. If Riot considers it problematic, we will replace it with simple per-stat podiums.
- Branding. Own name, logo and design; no official Riot logos. Game assets only from the Public Content Catalog. The "isn't endorsed by Riot Games" disclaimer is on every page and in the bot.
- One production key, used for this single product only.
4. API usage
| API | Endpoint | When |
|---|---|---|
| ACCOUNT-V1 | /riot/account/v1/accounts/me | Once per linking, with the RSO token |
| ACCOUNT-V1 | /riot/account/v1/active-shards/by-game/val/by-puuid/{puuid} | Once per linking |
| ACCOUNT-V1 | /riot/account/v1/accounts/by-puuid/{puuid} | Once a day per player (Riot ID changes) |
| VAL-MATCH-V1 | /val/match/v1/matchlists/by-puuid/{puuid} | Adaptive: every 15 minutes for active players, down to once a day for inactive ones |
| VAL-MATCH-V1 | /val/match/v1/matches/{matchId} | Once per new competitive match, even if several members played it |
| VAL-RANKED-V1 | /val/ranked/v1/leaderboards/by-act/{actId} | EU, every 6 hours (official RR of linked Immortal and Radiant players) |
| VAL-CONTENT-V1 | /val/content/v1/contents?locale=it-IT | Once a day (Italian names of agents, maps, acts) |
| VAL-STATUS-V1 | /val/status/v1/platform-data | EU, every 10 minutes (maintenance notices) |
Estimated volume: about 800 requests per day with 30 linked players and 8,000 per day with 300, well below one request per second. All calls go through a single client that honors X-App-Rate-Limit, X-Method-Rate-Limit and Retry-After.
5. Data and security
- Stored data: PUUID, Riot ID, shard and per-match raw numbers (kills, deaths, assists, damage, shots, agent, map, tier, result) for opted-in players only.
- GDPR: data access, export and deletion through bot commands; members who leave the server are hidden at once and deleted after 90 days. Full privacy policy and terms (Italian).
- Planned stack: TypeScript / Node.js, PostgreSQL and Docker on a VPS in the EU behind HTTPS. The API key and RSO client secret stay on the server only; the database is not exposed to the internet; backups are encrypted and stored off-site in the EU.
- The linking flow is protected by the OAuth
stateparameter and signed cookies; linking tokens are single-use, short-lived and stored only as hashes.
6. Status and plan
- Done: product design and full specification, this website with the user flow, privacy policy, terms and visual identity.
- While waiting for approval: building the bot's foundations, the linking flow with a simulated login and the features that do not use Riot data, tested on a private development server. The public server opens only after approval, so that players never join a community without the stats it was built for.
- After approval: RSO integration first, well within the required 30 days; then match sync and stats, and a test with 10–20 players before opening publicly (about 6–8 weeks in total).
- A prototype with simulated data can be provided on request.
7. Developer
Andrei Nicolae Telea, junior cybersecurity specialist based in Piombino (Livorno), Italy. Currently attending "Cyber Security Expert", a 990-hour post-diploma technical program (IFTS, May 2026 – March 2027) on Linux, networking, security operations, SIEM, vulnerability management and GDPR. Diploma in Business Information Systems; more than six years in heavy industry, following strict procedures and safety protocols. Security and privacy by design are central to how Ascend is built.