Last updated: 3 August 2026

Privacy Policy

This policy explains how ASH Esports collects and uses personal data when you use our website, dashboard, recruitment forms, Discord-connected features, and team tools.

Data We Collect

When you sign in with Discord, we may receive and store your Discord account ID, username, display name, email address, avatar, OAuth tokens, and related sign-in metadata needed to operate your account.

When you use team and recruitment features, we may collect application answers, game preferences, Riot IDs, Ubisoft usernames and platforms, game-connection verification status and reviewer identity, rank snapshots, Rainbow Six Siege ranked history and operator performance returned by R6 Data, team memberships, roles, availability, practice days, champion pools, coaching notes, match bookings, scrims, results, uploaded avatars or logos, reviewer notes, and dashboard activity created through the service.

If you choose to import a custom game with the League Companion, we store game identifiers and timing, Riot IDs or PUUIDs where available, teams, champions, builds, spells, runes, performance statistics, objectives, result information, replay metadata, and the selected replay file. League Client credentials and local file paths remain on your computer.

If you create or use a team invitation or member referral, we store the link creator, intended team where applicable, creation and expiry or revocation times, the account that used the link, and the claim time. Secret link tokens are stored as one-way hashes rather than readable URLs.

Our hosting provider processes request and security information needed to deliver and protect the service. Vercel Web Analytics records aggregated page-view information such as the page, referrer, approximate location, browser, operating system, and device type. ASH redacts query strings and dynamic user or team identifiers before analytics events are sent.

Purposes and Lawful Bases

We use personal data to provide the website and dashboard, authenticate users, manage teams and staff access, process recruitment applications, match and verify game connections, run coaching and availability tools, publish results and roster information, protect the service, investigate issues, and communicate with players, applicants, staff, and community members. Invitation and referral records are used to grant the requested team access, attribute genuine new-member referrals, prevent self-referral or duplicate credit, and provide account holders with referral history.

Depending on the activity, we rely on performance of a contract or steps requested before entering one, our legitimate interests in operating and securing the organisation and its competitions, consent where you have a genuine choice, and compliance with legal obligations. Where we rely on legitimate interests, we balance those interests against the effect on the people concerned. You may object to that processing.

We do not use the website to make decisions about you based solely on automated processing that produce legal or similarly significant effects. Recruitment and roster decisions are made by authorised people.

Public Profiles

A member profile may publicly show an alias or name, country, avatar, biography, quote, organisation or game role, team membership, verified game connections and ranks, Rainbow Six Siege ranked and operator statistics, Twitch channel, and achievements. Rainbow Six statistics are published only while the linked identity is staff verified and the member is on an active non-tryout Rainbow Six roster. Exact age and free-form location are not returned by the public profile API and are shown on the profile page only to the profile owner or an authorised moderator.

Public visibility is used to present current ASH rosters, staff, competitive history, and achievements. Ask an ASH administrator to correct or remove optional public profile information. Some minimal historical result or hall-of-fame information may be retained where ASH has a documented overriding reason, but each request is assessed individually.

Discord Usage

We use Discord OAuth scopes for identity, email, and guild joining. Where our Discord bot is configured, it may add you to the ASH Esports Discord server, create or remove team roles and channels, send direct messages about relevant team, recruitment, or event activity, and post or update result messages through webhooks.

Messages or profile information you share in Discord may be visible to other Discord users according to the server, channel, role, and Discord settings in place. Discord processes data under its own privacy policy, and ASH Esports cannot control Discord's independent handling of data.

Sharing and Processors

We share data only where needed to run ASH Esports services. This may include Discord, Riot Games APIs, R6 Data for Rainbow Six Siege profile matching and statistics, Twitch, Vercel hosting, Vercel Analytics, Vercel Blob storage, database providers, configured webhook or form integrations, and authorised ASH staff or team managers. A successful Riot or R6 Data lookup confirms that an identity exists; it does not by itself prove ownership. Where automatic League icon verification is unavailable, an authorised administrator must complete a separate ownership check before marking a connection verified.

We do not sell personal data. Some roster, event entry, tournament team, Riot ID, verified Ubisoft profile, game statistics, result, hall of fame, avatar, and team information may be shown publicly where it forms part of ASH Esports community or competition activity.

Normal Scrim Vault imports are restricted to authorised members of the selected team. Imports deliberately sent to Timmy's test sandbox are kept out of that production vault, but their unlisted analysis pages, including player statistics and the game summary, can be viewed by any signed-in ASH user who receives the link. Replay files use long random public Vercel Blob URLs; the analysis page does not publish that URL.

International Transfers

Some providers and their sub-processors may process data outside the UK or European Economic Area, including in the United States. ASH must use an applicable adequacy decision or contractual safeguards such as approved data-protection clauses where the law requires them. You can ask for information about the safeguard relevant to your data.

Retention

We keep personal data only while it is needed for the purpose described, to resolve a dispute, protect the service, preserve proportionate competition records, or meet a legal obligation. The period depends on the record and the person's relationship with ASH.

ASH is formalising concrete deletion periods for accounts and OAuth tokens, unsuccessful recruitment applications, reviewer and coaching notes, availability, event registrations and evidence, logs, analytics, public profiles, and backups. Until those periods are approved and automated, records are subject to manual review and deletion requests. This is an operational limitation, not permission to keep data indefinitely.

League replay records carry a 180-day expiry. ASH must run the configured deletion process to remove the corresponding Blob object; deleting a database record alone does not remove an object from Blob storage.

Your Data Rights

You can update some profile information in the dashboard. You can also disconnect from ASH community spaces by leaving Discord or contacting ASH staff about access changes. Removing data may affect your ability to use team tools, recruitment, or dashboard features.

Depending on where you live and the lawful basis involved, you may have rights to be informed, access, correct, delete, restrict, object to processing, receive portable data, withdraw consent, and complain to a regulator. California residents may also have applicable rights to know, correct, delete, opt out, limit certain sensitive-data uses, and receive equal service. ASH does not sell personal data.

Contact an ASH Esports administrator to make a request. We will verify that the request concerns your data, search relevant systems and processors, and explain any lawful exception. UK residents may complain to the Information Commissioner's Office. You may also complain to the data-protection authority where you live or work.

Cookies and External Media

Authentication uses cookies that are necessary to sign you in, keep the session secure, and return you to the requested page. Vercel Web Analytics is configured without advertising cookies and uses a daily, non-cross-site visitor hash for aggregated measurement.

The Twitch player is blocked until you choose “Load Twitch player”. Loading it connects your browser directly to Twitch, which may use cookies or similar technologies under Twitch's own policy. ASH stores that player choice in your browser so it can honour it on later visits. Clearing site storage resets the choice. ASH does not currently use advertising or cross-site tracking pixels.

Security

We use access controls, authentication, role-based permissions, provider-managed hosting, and operational safeguards to protect personal data. No online service is perfectly secure, so you should keep your Discord account secure and report suspected account misuse or data issues promptly.

Children

Account profile ages are restricted to 13 or over, but age entry alone is not a verified parental-consent mechanism. ASH Esports is intended for people who are old enough to use Discord, Riot services, and the relevant games and competitions in their region. If ASH learns that a child was registered below an applicable age threshold without the authorization the law requires, the account and associated processing must be reviewed promptly. Contact ASH staff if you believe this has happened.

Controller and Contact

ASH Esports determines why and how the processing described in this policy takes place and acts as the data controller for it. For privacy questions, objections, or rights requests, contact an ASH Esports administrator through the ASH Discord server or the channel where you normally communicate with ASH staff. ASH must publish its accountable legal identity and a monitored privacy address before treating this notice as production-complete.

We may update this policy as our services or legal obligations change. The updated version applies from the date shown at the top, and material changes should be brought to affected users' attention.