1. About this policy
CSRL (Clutch Series Rocket League) is an independent, volunteer-run Rocket League community serving the EU region. It is mainly managed from the United Kingdom. CSRL, acting through its administration, is responsible for deciding how the personal information covered by this policy is used (the data controller).
This policy covers the CSRL website and community, account and competition services that link to it. It applies to players, prospective players, team representatives, volunteers and people who contact us. Discord, Epic Games and other independent services have their own privacy policies for their services.
The public website currently provides information about CSRL. The full player and competition website is in development; descriptions of those features apply when you use them, including during testing.
For privacy questions or requests, email clutchseriesrl@gmail.com. Our contact page explains what to include.
2. Key points
- We use account and participation information to identify players, assess eligibility, organise competition and maintain player records.
- Player profiles and competition pages are public. They can include a player’s display name, self-reported age band, country or region, linked gaming display names, ranks, achievements and team information.
- Discord membership and relevant roles can supply player information before someone signs in to the website.
- Epic account linking confirms the identity of the account being linked. CSRL competition verification remains a separate review.
- You can ask for access, correction, account unlinking or deletion by email. The 12-month inactivity review does not require you to wait before making a request.
3. Information we collect and its sources
Accounts and community membership
From Discord, we receive identifiers, usernames, display names, avatars, CSRL server membership and relevant roles, including age-band and verification roles. Member synchronisation can create an unclaimed CSRL player record before a member signs in or completes player setup.
When you link Epic, CSRL requests Basic Profile access and retains the Epic account ID and display name, the associated Discord account, Main/Alt classification and link or verification details. We use temporary authorisation information to complete linking. Sign-in takes place with the relevant provider; CSRL does not ask you to submit your Discord or Epic password to us.
Player profiles and eligibility information
You or authorised staff may provide a player name, profile image, country, region, age band, Tracker profile links, gaming-account details and history submitted for verification. Profiles can also contain appearance preferences, badges, roles, achievements and team membership. An age band may come from the role you select in Discord or information supplied during player setup; it is self-reported, rather than independent proof of age.
Ranks, progression and competition
We receive rank information through the configured game-account rank service and information submitted by players or staff. Records can include account identifiers, MMR (skill rating), rank, division, game mode, season and the date and time of a reading. We use readings to produce progression graphs, observed-highest ratings and achievements. These are recorded observations, rather than a guarantee that every match or earlier peak has been captured.
Captains, teammates, staff and competition participants may supply roster details, invitations, entries, availability, match information, results and disputes that relate to you. We also record membership and participation dates needed to maintain those records.
Messages, applications and uploads
We collect enquiries, application answers, support or moderation reports, relevant staff notes and evidence supplied with them. This may include information about another person, such as the subject of a report. Uploads include the file and associated information such as the uploader, filename, file type and size.
Where community activity achievements are enabled, the CSRL bot reads eligible messages in configured community channels to calculate activity counts. That counting feature keeps counts and related dates, rather than an archive of message bodies. Messages submitted as support requests or evidence are handled separately.
Donations and supporter recognition
If you use an available donation feature, we record the associated account, amount, currency, payment status, transaction references and supporter-display preference. The payment provider handles payment details. Public supporter recognition may include your display name, avatar, donation total and supporter tier when you choose non-anonymous recognition.
Website and technical information
Browsers and hosting services process information such as IP addresses, requested pages, browser details, request times and security or error information when delivering and protecting the website. The full website also stores login sessions and relevant preferences or drafts in your browser.
4. Purposes and legal bases
The legal basis depends on why we use the information:
- Accounts, eligibility and competition
- We use identity, membership, age-band, account and participation information to maintain player records, check eligibility, organise teams and events, review verification submissions and preserve accurate results. We rely on our legitimate interests in administering a fair, accountable community and its competitions.
- Player services and communications
- We use profile choices, rank readings and activity records to provide profiles, progression and achievements, and to send relevant account, roster, tournament, rating or support notifications through the website or Discord. Our basis is our legitimate interests in providing the community features people use and keeping participants informed.
- Support, moderation and security
- We use enquiries, reports, evidence, technical records and administrative history to answer requests, resolve disputes, investigate misuse, prevent duplicate or conflicting account links, protect the service and record important staff actions. Our basis is our legitimate interests in community safety and reliable administration, or a legal obligation where a specific law requires the processing.
- Optional payments and consent-based features
- Where you make a payment, we rely on our legitimate interests in administering the voluntary support you request, and on legal obligations for any records required by law. Where a particular optional use requires consent, we ask for it separately and explain how to withdraw it.
Legitimate interests are subject to your rights and interests, with particular care for younger players. This policy is a notice about processing; it is not blanket consent. Choosing to link an account does not authorise unrelated uses of your information.
You can browse public information without linking an account. Identity and eligibility information is needed for features such as claiming a player record, verification and competition entry. If required information is missing, we may be unable to provide that feature. Optional profile customisation is not required for ordinary browsing.
Automated checks may calculate ratings, award achievements, identify account conflicts or indicate whether an entry meets configured requirements. Those checks can affect which features or entries are available. You can ask staff to review an incorrect record or disputed eligibility decision.
5. Public profiles and competition records
The public website is intended to help people follow CSRL players, teams and competitions. Public information can include display names and images, country or region, self-reported age band, linked gaming display names and Tracker links, ranks and MMR, progression, achievements, community roles, membership dates, team rosters, fixtures and results.
A player page may link to a Discord profile. That link contains the player’s Discord user ID. Public content can be viewed or copied by other people, so avoid adding private contact details, a home address or school information to a public name, image or profile field.
Applications, report evidence, private support correspondence, staff notes and account-administration records are handled for administration rather than as public profile content. They may still need to be shared with relevant staff or participants to deal with a request or dispute.
7. Cookies, browser storage and security
These public information pages use local images and styles, without sign-in, application cookies, advertising tags or tracking scripts. Hosting infrastructure can still process technical requests and security information.
The full website uses a necessary session cookie to maintain sign-in. The current session can renew with activity and expire after up to 30 days of inactivity. Browser storage can also hold preferences, cached information and saved drafts, including staff spreadsheet drafts. Signing out ends the website session but does not delete the underlying player record or persistent account links.
External fonts and embedded YouTube or Twitch content can contact their providers when the relevant page or content loads. Those services may use their own cookies or similar technologies. They are not included on these public information pages. Browser settings may restrict cookies or external content, which can affect the associated feature.
CSRL uses access controls to restrict administrative functions and separates private report evidence from public profile content. Administrative exports and configured backup copies may contain identifying information. They are part of the information that must be protected and considered when handling a privacy request. No online service can guarantee absolute security; please report suspected misuse of your CSRL information to our contact address.
8. Retention, unlinking and deletion
We retain personal information for the purposes described in this policy, rather than for an unlimited period simply because someone joined CSRL. The appropriate period depends on active participation, the need to maintain an account or competition record, outstanding requests or disputes, security requirements and any legal record-keeping obligation.
CSRL administration reviews identifying player records after 12 months without CSRL participation or account activity and removes or anonymises information that is no longer needed. The review considers known account activity, competition participation, ongoing team or community involvement and whether there is an unresolved administrative need. Routine background rank checks do not, by themselves, count as participation. This is a manual review, not automatic deletion on a fixed date. You can request deletion sooner.
Support, moderation and administrative records are reviewed according to whether the request, dispute, security or accountability purpose still requires them. Any justified retention must be limited to that purpose. Backups, staff-held exports and records held in connected CSRL systems are included when considering retention or a deletion request.
Epic and Discord account data
To request deletion of connected-platform account data, contact CSRL administration at clutchseriesrl@gmail.com. Requests are handled promptly and securely in accordance with the relevant platform requirements and applicable law, including data in account records and copies under CSRL’s control. The inactivity-review interval does not delay such a request. Any legally required exception is limited to what the law requires.
Signing out, unlinking and deleting a CSRL profile
- Signing out ends your website session. Your player record and persistent account links remain.
- Unlinking removes a connected-account association. It does not, by itself, erase every related historical record.
- Deletion is a request to remove personal information, including identifying profile and account details, subject to the applicable rights and obligations described here.
To request deletion of your CSRL profile or other personal information, email clutchseriesrl@gmail.com. Tell us which profile, account link or information the request concerns; we will clarify the scope with you if necessary. Removing a CSRL record does not delete your underlying Discord or Epic account.
Competition history
Where possible, CSRL preserves non-identifying competition results while removing a departing player’s identifying information. Removing an ID or replacing a name does not guarantee anonymity: other details can still identify someone. We consider that context when handling a request. Preserving competition history is not a general exception to platform-account deletion requirements or your legal rights.
9. Your rights and choices
Depending on the circumstances and applicable law, you can:
- request access to your personal information and a copy of it;
- ask us to correct inaccurate or incomplete information;
- request deletion or restriction of a use of your information;
- object to processing based on legitimate interests;
- request certain information in a portable form; and
- withdraw consent where it is the basis for a use, without affecting earlier lawful processing.
Email clutchseriesrl@gmail.com with the request and your CSRL or Discord username or ID if known. You do not need to use a particular form or legal wording. We may make proportionate checks to confirm which records belong to you; do not send passwords, sign-in codes or access tokens.
CSRL administration handles requests manually. We normally respond without undue delay and within one calendar month. If a lawful extension or other exception applies, we explain the reason and timing. Where a request cannot be fulfilled in full, we explain the decision and available next steps.
How we provide a copy of your information
After proportionate ownership checks, CSRL administration gathers the personal information relevant to your request from the systems and records under CSRL’s control. Depending on what we hold, this may include your profile and connected-account details, rank observations, participation records, applications, correspondence and personal information about you in relevant staff records.
We provide an accessible copy in a commonly used format, such as a readable PDF and CSV files for structured records, with relevant attachments where appropriate. We also explain the purposes, sources, recipients and retention information relevant to the response. Tell us if you need a different accessible format.
A member of the administration reviews the response before it is sent, including whether information about other people needs to be removed or a specific exemption applies. We arrange a suitable secure delivery method with you, such as protected electronic delivery. If information is withheld, we explain the reason where permitted. This is a staff-assisted process; you do not need an automated export tool to make a request.
You can raise a concern with the team or contact the UK Information Commissioner’s Office, or the data-protection authority relevant to you. The authority can explain its complaint procedure.
10. Age requirements and younger players
CSRL is intended for participants aged 13 and over. We use self-reported age bands to assess whether participants meet that minimum age requirement and to apply relevant participation rules. The age band selected through Discord can be shown on the player’s website profile.
An age-band role or a CSRL verification state is not independent verification of someone’s age. Our participation rule does not replace any additional parent or guardian authorisation required by local law for a particular use of information.
We take younger players’ interests into account when considering how information is used. If you believe a child under 13 is participating, or a young player’s information is being used inappropriately, contact us privately. Players and parents or guardians can also use the same address for privacy requests.
11. Updates to this policy
We keep this notice under review and update the date when it changes. Where a change materially affects how personal information is used, we provide an appropriate additional notice and obtain any further permission required before the new processing takes place. Changes do not remove rights that apply to information already collected.