Privacy policy

Draft · last updated 15 November 2026

Ward Master is a web application for the staff of esports teams (League of Legends today; more games will open later): coaches, analysts and managers record scrims and official matches, player and champion statistics, draft preparation, opponent scouting and the team calendar.

This policy explains which personal data Ward Master processes, why, for how long, who it is shared with and what rights you have under the General Data Protection Regulation (EU) 2016/679 (GDPR). The cookie policy and the terms of service complete it.

1.Who is responsible for your data

The data controller is Pietro Castaoro, a private individual. For anything concerning your personal data write to privacy@wardmaster.gg. There is no data protection officer (DPO): it is not required for a service like this one.

For the player, opponent and match data that a team's staff enters or imports into Ward Master, the organization using the service decides what to record and why; Ward Master processes that data on its behalf to provide the service (see why we process it).

2.Which data we process

Ward Master only processes the data needed to run the service. There is no profiling, no advertising and no sale of data.

  • Your account and how you sign in. You sign in with Discord, with Google or with email and password. For every account we keep the email, name, language, sign-up date, date of the last sign-in and the access status (no request, pending, approved, rejected, suspended). With Discord we receive your user id, username, display name and verified email and we keep the id and the username; if you create the account with Discord, the display name and email also become the account's name and email. With Google we receive the account id, name and verified email and we keep the id and the email; if you create the account with Google, the name becomes the account's name. We don't keep avatars, profile pictures, friends, servers or contacts. Your password, if you set one, is stored only as a bcrypt hash. If you turn on two-step verification we keep the secret key that generates the codes and the recovery codes (these only as hashes). We also keep the last team you opened, to open it again at your next sign-in.
  • Your access request. The game, role, team, organization, league, links and contact you write in the form, with the decision taken on it. The details are in the section The access request. If you opened a partner's link before sending it, also which partner it was.
  • Discord for whoever runs an organization. During the test phase, owners and admins of an organization must link a Discord account to use the app, so the controller knows who is behind each organization (except in the controller's own organization). From Discord we only keep the data listed above (id and username). Invited players and staff don't have to link it. If the staff links the roles of the team's Discord server to Ward Master roles, the Ward Master bot reads, in that server, the roles of people who already used Discord in Ward Master (Discord id and roles only), to give or remove access to the team.
  • The emails we send you. From the noreply address of wardmaster.gg we send invitations, links to confirm your email address or reset your password, and the notice that your request was approved. The links are single-use, we keep only their hash and they expire after 1 hour (password) or 2 days (email confirmation).
  • Your organization and team. Organization and team names, your role in them (owner, admin, coach, analyst, player), the splits, the language you prefer, the active team.
  • Players entered by the staff. For each player on the roster: in-game name, optionally the real name, position, Riot IDs and summoner names used to match replays, links to public profiles (op.gg, lolpros), active or substitute status, champion pool, focus points, availability and notes written by the staff. For a game other than League of Legends, also the accounts of that game (Riot ID, SteamID64), ranks and links to public profiles (tracker.gg, VLR.gg, FACEIT, Leetify, HLTV, Steam, Liquipedia).
  • Player check-ins. A player can say, for an event or for the day, how tired they are, their mood and their confidence (from 1 to 5), with an optional note. A check-in is always optional and only the player writes it; the player and the team's staff see it, never the other players, and the player can delete it at any time. Because this data can say something about how a person is doing, it has its own legal basis (see why we process it).
  • Opponents entered by the staff. Team name, players' in-game names, positions, Riot IDs, links to public profiles and scouting notes. Opponents' drafts may also be imported from Leaguepedia (lol.fandom.com), a public wiki of competitive matches. For another game, links to public profiles of that game.
  • Match data from replays and other sources. Games come from replay files (.rofl) uploaded by the staff or by the companion, from Leaguepedia, from CSV files or are typed by hand. Depending on the source they include: game ids, dates, duration, side, result, picks and bans, per-player statistics (champion, kills, deaths, assists, gold, damage, vision, items) and the in-game names of the ten participants, including the opposing team.
  • Match data from replay files. Replay files (.rofl) uploaded by the staff, or sent automatically by the optional companion program from the Replays folder, are read in memory to extract the same statistics as above. The replay file itself is never stored: only the game metadata and the per-player statistics are kept.
  • Your work in the app. Draft plans, draft log, strategy map boards, lessons (including the photos you paste in, stored in the database), VOD review notes (a YouTube, Twitch or local file link plus timestamped notes), calendar events, tasks, tryout candidates the staff adds by hand (name, role, contact, notes), invitations (with the invited person's email, when given), the feedback messages you send us from the app, public share links, personal availability links and the calendar link (stored only as hashes) and API tokens for the companion (stored only as SHA-256 hashes).
  • Ask (beta, trial teams only). The question the staff writes on the Ask page and the results of the searches needed to answer it go to Groq, which writes the answer (see Processors): for example names of opponents and players, champions, game results and stats, calendar events, focus points, check-in averages without the notes, name, role and status of tryout candidates. Never e-mails, contacts or accounts. Ward Master keeps only the questions Ask did not understand and the ones that were rated, with the rating and the reason, and a count of the day's questions without any text, for the daily limits.
  • Technical data. Session identifiers and preferences (see the cookie policy); the time of your last activity; the organization's activity log (who did what, with the name and email of the person acting, visible to owners and admins); with a feedback message also the page, language and browser (user agent) you send it from; for the attempt limits only a hash of the email, account or IP address; the country an access request or a new organization comes from, which the hosting provider derives from the IP address (the address itself is not stored); the server logs of our hosting provider (IP address, requested URL, date, user agent), kept for a short time for security and diagnostics.

3.The access request

During the test phase Ward Master is access on request: after the first sign-in, whoever wants to create an organization fills in a form and waits for the controller to approve it. Whoever joins through an invitation link doesn't need to make a request.

  • What the form asks: the game your team plays (League of Legends, or another game: the request then waits on that game's waiting list until it opens), your role (coach, manager, analyst or other), the name of the team and of the organization, the league (for League of Legends an ERL or a tournament, for the other games a league or tournament), 1 to 3 links that show who you are (for example an op.gg profile for League of Legends, or the team's page) or the choice "I don't have a link", and a Discord or Twitter/X contact (optional if you signed in with Discord).
  • Who reads it: only the controller, as platform administrator, on the administration page, together with your account data (name, email, sign-in method, sign-up date, last sign-in). Other organizations and other users don't see it.
  • The notice to the staff: each new request sends a short message to a staff-only channel of the Ward Master Discord server, with the game, the role, team and organization name, league, number of links and the country the request comes from (derived by the hosting provider from the IP address). The message contains no email, names of people, contacts or links. In the same way, when a new organization is created, the channel receives its name, country and language.
  • The partner link: some partners (for example a league that tells its teams about Ward Master) have a link of their own. If you open it, you land on the access page with the partner's code in the address (no cookie is set), and the request you send from there records which partner it came from; the notice to the staff names the partner too, so the request is reviewed as soon as possible. The decision is still taken by a person, as for every request. The partner never sees your request, your name or your team: at most we show it aggregate numbers about its link (opens, requests, approved requests, teams and the people on them), where numbers from 1 to 2 are shown as "fewer than 3".
  • The decision: the controller approves or rejects the request and can add an internal note, which is never shown to you. With the decision we keep the date and the name of whoever decided. The decision is always made by a person, never by an automated system. If the request is approved we send you an email in your language; if it is rejected we don't write to you and you see it the next time you sign in. Each account can send only one request.
  • Suspension: the controller can suspend an account, for example if it breaks the terms of service. Suspension immediately ends the sessions, revokes the API tokens and invitation links created by that account and prevents signing in with any method and making a new request. The account's organizations and their other members are not touched. A suspended account can be reactivated.
  • The log: decisions and suspensions are recorded in an internal log with the date, the name of whoever decided and the name of the account.

You can write to the controller at any time, even if you have no link to give: the Discord and X contacts are on the request page, and the email privacy@wardmaster.gg always works.

4.Applying to a tryout from a link

A team can publish a link to its tryouts. You can apply without an account: you write your name, the role and your Discord name; a player adds the Riot ID and, if they want to, links to Twitter/X, Leaguepedia or Liquipedia and a stats site; for another game, a player adds instead an account of that game (Riot ID or SteamID64) and, if they want to, the rank and links to their profiles on that game's sites; staff add a link to their work and, if they want to, to Twitter/X. A league or team and a message are optional. These details go to the staff of that team and to nobody else: they are not shown to other teams or on public pages. The team decides what to do with them, as for its other candidates.

  • Linked account. If you are signed in when you apply, the application stays linked to your account and you find it in Settings → Profile.
  • One application per person. The same Discord, Riot ID, account of the game or account can apply only once to the same tryout.
  • Limit on submissions. To stop spam we keep a hash of your IP address, tied to that tryout, for at most 24 hours; nothing else about your connection.
  • Deleting. When you apply you get a personal link that deletes the application and what the staff wrote about it; with an account you can also do it from Settings → Profile. The staff can delete a candidate at any time. Otherwise the application stays until the team deletes it.

5.The public page "Who's with us"

On Who's with us Ward Master thanks the teams that use it and the communities and partners that make it known. Each entry is a public name, a logo if there is one, a country if they want, and a link. We add an entry only after a written yes from whoever appears there (a team's or community's manager, an organizer, a coach or a creator with the public name they choose), and we write down when and where they said yes. That note is never shown.

  • Nothing is paid, in either direction, to be on the page.
  • What is published: only the name, the logo, the country, the kind of partner and the link they agreed to. Never an email, a real name they didn't choose or data of the app's teams.
  • Leaving the page: ask on Discord or by email and the entry is hidden or removed at once, logo included. You can withdraw your yes at any time.

6.Why we process it and on which legal basis

  • To provide the service you asked for (creating and maintaining your account, signing you in, showing your team's data, importing matches, sending share links and service emails): performance of a contract, Art. 6(1)(b) GDPR.
  • To keep the service secure (sessions, access control per team, hashed tokens, logs, abuse prevention): our legitimate interest in a safe service, art. 6(1)(f) GDPR.
  • To decide who gets in during the test phase (access request and its notice to the staff, the Discord requirement for whoever runs an organization, account suspension): our legitimate interest in knowing who uses a service still in testing and in protecting it from abuse and from people who want to copy it, Art. 6(1)(f) GDPR.
  • To know which partnerships bring teams to Ward Master (the partner a request came from and the aggregate numbers we show that partner): our legitimate interest in knowing whether a partnership works and in telling the partner, without names, what it brought, Art. 6(1)(f) GDPR.
  • To record players, opponents and match data chosen by the staff: the organization using Ward Master decides this processing for its legitimate interest in preparing and analysing its own competitive activity, art. 6(1)(f) GDPR; most of this data concerns public competitive games. The organization is responsible for informing its players.
  • For fatigue, mood and confidence check-ins: the player's explicit consent, given by filling in the check-in and withdrawn by deleting it, Art. 6(1)(a) GDPR and, if this data is considered data concerning health, Art. 9(2)(a) GDPR. Nobody has to fill it in and not doing so has no consequence in the app.
  • To know how many visits the site gets (visits, page views and referring site, only as daily totals, without cookies and without storing IPs or other visitor data): our legitimate interest in understanding whether the service is used, Art. 6(1)(f) GDPR.
  • To show who is with Ward Master on the public page (name, logo, country and link of whoever said yes): your consent, art. 6(1)(a) GDPR, which you can withdraw at any time.
  • To answer Ask questions (the searches on the team's data and sending them to Groq to write the answer): performing the service requested by the person asking, Art. 6(1)(b) GDPR, and the organization's legitimate interest in preparing its games with its own data, Art. 6(1)(f) GDPR; for check-in averages, the same consent of the player as in the point above.
  • To answer your requests and comply with the law (requests about your rights, legal obligations): art. 6(1)(c) and (f) GDPR.

We never process your data for marketing, profiling or automated decisions with legal effects.

7.Who receives your data

The application and the database are in the European Union. The following providers process data on our behalf or receive it to deliver part of the service; some are based outside the EU:

  • Vercel Inc. (hosting and application servers, region Frankfurt, Germany): runs the application and keeps the technical logs. Ward Master uses Vercel's free plan, for which Vercel offers no data processing agreement (DPA): Vercel processes this data under its own terms and privacy policy. If we move to a paid plan with a DPA, we will update this page. From the IP address Vercel also derives the country, which we use only in the staff notices described above.
  • Neon Inc. (PostgreSQL database, region Frankfurt, Germany): stores all application data. Neon acts as a processor under its Data Processing Agreement.
  • Discord Inc. (sign-in and notices): when you sign in or link Discord, Discord tells us who you are; we only receive the data listed in the section Which data we process. We also use Discord for the notice of new access requests and organizations on the Ward Master server (see The access request) and, only if your team's staff sets it up, to send messages to the team's Discord server (event reminders, imported games, shared reviews). Discord processes your Discord account under its own privacy policy as an independent controller.
  • Google LLC (sign-in): when you sign in with or link Google, Google tells us who you are; we receive only the id, name and verified email. Google processes your Google account under its own privacy policy as an independent controller.
  • Groq, Inc. (the model behind Ask, servers in the United States): receives the question written on the Ask page and the results of the searches needed to answer it (see What data we process), only from trial teams and only when the staff asks a question. Ward Master uses Groq's free plan. Under its terms (Services Agreement, section 4.2) Groq uses questions and answers only to provide the service, does not use them to train models and processes personal data under its Data Processing Addendum; with Zero Data Retention turned on it does not keep them even in its logs.
  • Resend (sending emails, servers in the European Union, Ireland): receives the recipient's address and the text of the email to deliver it, and acts as a processor. We don't use open or click tracking.
  • Upstash (reminder scheduling): when a team has Discord reminders on, we ask Upstash's QStash service to call Ward Master at the time of the reminder. It receives only Ward Master's address with the event id and the time: no names, emails or content.
  • cron-job.org (scheduled jobs): calls a few technical pages of Ward Master at fixed times (reminders, daily numbers, pro data). It receives no personal data.
  • Riot Games (Data Dragon): champion icons are copies served by Ward Master. Only the item and ability icons of the Toolkit, and the icon of a newly released champion not yet copied, are loaded by your browser directly from Riot Games' public servers (ddragon.leagueoflegends.com), which therefore receive your IP address as with any image taken from another site. Ward Master does not use the Riot Games API and sends Riot no data about your account.
  • op.gg (public profiles): the "Open on op.gg" links open op.gg in a new tab with that player's Name#TAG. Nothing is sent until someone clicks; from then on op.gg's own terms and privacy policy apply.
  • Leaguepedia / Fandom (public scouting data): read-only queries of public match data; no personal data about you is sent.
  • YouTube and Twitch (video): the player loads from their servers only on pages where the staff added a video; in lessons you first see only the video's preview image, taken from YouTube, and the player starts when you press play. From there their terms, privacy policy and cookies apply.

Apart from the video players, pages load no analytics, advertising or social scripts and no fonts from Google: fonts are served by Ward Master. When a provider processes data outside the European Union, the transfer relies on the European Commission's standard contractual clauses or on the EU-US Data Privacy Framework.

We do not sell or rent personal data and we do not share it with anyone else, except where the law requires it.

8.How long we keep it

  • Account data: as long as your account exists. You can download a copy and delete the account yourself from Settings → Profile at any time.
  • When you delete your account: your account, sessions, sign-in methods, access request, notifications, feedback and check-ins are deleted at once. An organization where you are the only member is deleted with everything in it; if you are the only owner of an organization with other members, you first give the owner role to someone else. What belongs to a team (your roster entry, matches, plans, notes you wrote) stays with the organization, no longer linked to your account. Your name stays in the activity logs until they expire, and the deleted data disappears from backups within their window.
  • Access request: as long as your account exists; it is deleted with the account. If it is rejected, 180 days after the decision we automatically erase everything you wrote (team, organization, league, links, contact) and the internal note; only game, role, outcome, dates and the partner, if any, remain, so the account stays rejected and the partner's numbers don't change.
  • Partner link: the partner's code is not stored in your browser (no cookie); the partner recorded on the request is kept as long as the request.
  • Activity log (of the organizations, and the one of decisions and suspensions): 24 months, then it is deleted automatically. An organization's log is also deleted with the organization; if your account is deleted, the name you had at the time of the action stays in the log until it expires.
  • Notices on the Ward Master Discord server: they stay in the staff channel until deleted by hand; they contain no emails, names of people or contacts.
  • Sessions and account links: a session lasts 30 days from sign-in or until you sign out; the temporary cookies of signing in with Discord or Google and of two-step verification 10 minutes; password links 1 hour and email confirmation links 2 days. Expired ones are deleted from the database the next day.
  • Attempt limits (sign-ins, sign-ups, forgotten password, codes, tryout applications): only a hash of the email, account or IP address, deleted after 24 hours at the latest.
  • In-app notifications: only the most recent ones of each person and never beyond 180 days.
  • Team data (players, opponents, matches, plans, notes, candidates, check-ins): as long as the team or organization exists, or until the staff (or the player, for their check-ins) deletes it. Deleting an organization deletes all its teams and their data.
  • Feedback: as long as your account exists; you can ask for its deletion earlier.
  • Ask: the questions it did not understand and the rated ones, with the rating and the reason, as long as the team exists (the ones rated as wrong and the ones not understood are also read by the controller to improve Ask); the count of questions to the model, without any text, 30 days. Groq does not keep questions or answers.
  • Share, availability and calendar links: until they expire or are revoked by the staff.
  • Entries of the "Who's with us" page (name, logo, link, date and place of the yes): until you ask us to remove them; removing an entry also deletes its logo.
  • Server logs: a few days at most, according to the hosting provider's default retention.
  • Backups: database backups are kept for a limited time by the database provider and then overwritten; deleted data also disappears from them within that window.

9.Your rights and how to exercise them

Under articles 15 to 22 GDPR you have the right to:

  • access the personal data we hold about you and get a copy;
  • rectify inaccurate data (your name and language can be changed in Settings → Profile; the rest on request);
  • erase your data ("right to be forgotten"), unless we must keep it by law;
  • restrict the processing while a request is being examined;
  • receive your data in a portable format;
  • object to processing based on our legitimate interest;
  • withdraw the consent you gave (check-ins, the "Who's with us" page) at any time, without affecting the past;
  • lodge a complaint with a supervisory authority, in particular the one of the EU country where you live or work (in Spain the Agencia Española de Protección de Datos).

You can download a copy of your account's data and delete your account yourself at any time from Settings → Profile → "Your data". To delete it you type your email and your password (or sign in again, if your account has no password) and, if it is on, a two-step verification code. For the other rights write to privacy@wardmaster.gg from the email address of your account, or ask the owner of your organization. It is free and we answer within one month.

If you are a player whose data was entered by your team's staff, you can also contact the organization, which decides what is recorded about you; we help it to answer.

10.How we protect your data

  • All traffic is encrypted (HTTPS).
  • Session cookies are httpOnly, same-site and secure; sessions are random 32-byte identifiers that expire after 30 days.
  • Passwords are stored only as bcrypt hashes; owners and admins of an organization can turn on two-step verification (codes from an authenticator app).
  • Every piece of data belongs to a team: each request checks that you are a member of that team before reading or writing.
  • API tokens for the companion are stored only as hashes; replay files are read in memory and never saved.
  • Secrets live only in the hosting provider's environment variables, never in the code.
  • For support, the controller, as platform administrator, can open the app as another user for at most 2 hours ("View as"), for example to reproduce a problem; a bar shows it the whole time.

11.Minors

Ward Master is a tool for team staff and is not meant for children. We don't ask for your age; whoever signs in with Discord or Google is also subject to the minimum age those services require, and every access request is read by a person before it is approved. In Spain a person can consent alone to the processing of their data from age 14 (Art. 7 of Organic Law 3/2018, LOPDGDD; in other EU countries up to 16): below that age don't apply to a tryout or fill in check-ins without a parent's permission. The staff can add players of any age to the roster; the organization is responsible for having the right to do so and for informing the players and, where needed, their parents.

12.Changes to this policy

We may update this policy when the service changes. The date at the top always shows the current version; significant changes will be announced in the app. This page is a draft that is still being reviewed by the controller.

13.Contact

Pietro Castaoro · privacy@wardmaster.gg.