Privacy Policy
This policy explains what data ClanTracker (the Discord bot and website at clantracker.gg) collects, why, and what your rights are.
Data controller: ClanTracker is currently developed and operated by an independent developer, not (yet) through a registered legal entity. The best way to reach us for anything in this policy is the ClanTracker support server. If that changes — for example, if ClanTracker is later operated through a registered company — this page will be updated with those details.
1. What we collect and where it comes from
From you, when you register (/register):
- Your Riot ID (game name + tagline) and, resolved from it, your Riot PUUID (a Riot-issued account identifier) and game region.
From Discord:
- Your Discord user ID and username/tag; the server (guild) ID and name; the display name you use in a server (to label you in posts); channel IDs that admins configure for posts; slash-command interactions you send the bot. Not your messages — the bot cannot read channel conversations.
From our game-data provider (Valorant match data):
- Your competitive match history — on registration up to roughly one year back, then continuously as you play. Stored per match: map, mode, timing, scores, agents, and per-player performance (kills, deaths, assists, damage, headshots, economy/buy values, round-by-round kill events), plus your rank/RR at the time of a match.
Derived by us from the above:
- Aggregated statistics (KD, ACS, win rates, clutch records), win/loss streaks, head-to-head "rivalry" records between registered clanmates, play-session timings, rank history over time, and end-of-act summaries.
Generated content and quality records:
- The AI-written headlines/summaries posted to your server, stored together with the statistical match context used to generate them, so we can evaluate and improve output quality. A server-level log of notable events (streak milestones, awards, rank changes) is kept for the bot's "memory" features and auto-deleted after 90 days.
Payments (anyone who pays for a server's Premium):
- Handled by Stripe. For a subscription we store its status and identifiers linked to the Discord server. For a one-time payment (a month pass or a chip-in) we store your Discord ID and display name, the amount, the date and Stripe's payment reference, linked to the Discord server. Your name and amount are shown to that server's members on its billing page, and the bot thanks you by name in the server. We never receive or store card numbers.
Website:
- Beta applications: your email address, Discord username, group size, and consent to contact you. Older applications may also include a server or group name. We also record the application time, source page, status, delivery references, the version of this policy shown when you applied, and, if you arrived through a campaign link, its campaign tags (for example utm_source=tiktok) and the referring website’s domain. We also store your answers to the form’s questions about how often your group plays together and whether someone can add the bot to your Discord server. Once you set up or register the bot, we link your application to that Discord server by your Discord username. We use these to review your request, send your invite, and understand which groups get set up successfully. A keyed hash of the requester’s IP address helps limit abusive submissions.
- Beta emails: if we invite your group, we send an invite email from beta@clantracker.gg. We record whether each email was accepted, delivered, bounced or marked as spam, and whether the invite link was opened. We don’t use tracking pixels. Every email has a link to stop beta emails or delete your application.
- Feedback: what you send through our feedback page: your Discord username, whether you are a server admin or a player, your answers to the questions (scores, choices and anything you write), and an optional Discord username or email if you agree to be contacted.
- Server dashboard: if you log in to the dashboard with Discord, we receive your Discord user ID, username, avatar and the list of servers you are in, to show you the servers where you may change ClanTracker’s settings. If you manage none, we use your Discord username to check whether you are on the beta waitlist; a message you choose to send us from there is stored with your Discord ID and username, like feedback. We don’t store that list or your Discord login token. A sign-in cookie that expires after 12 hours keeps you logged in; it is used for nothing else. When you save server settings we record your Discord ID and username as that server’s setup contact.
- Setup progress: for each Discord server, when the bot was added or removed, when setup was completed, when the first and second players registered and when the first recap was posted. These are stored as pseudonymous events tied to the server or application ID, never your email, username or Riot ID.
- Website traffic: we use Vercel Web Analytics to count page views and estimate visitors on public pages. Aggregate reports include page paths, referring sites, approximate location, browser, operating system and device type. Vercel uses a request-derived hash instead of third-party cookies. Our integration removes query strings and fragments from the page URL before sending it, sends no custom events, and does not read or send form fields. Test pages and local previews are excluded. See Vercel’s analytics privacy information.
- Some rendered images load game art from valorant-api.com.
2. What we use data for (and legal bases)
| Purpose | Legal basis (GDPR) |
|---|---|
| Detecting and posting your matches, stats, leaderboards, recaps in your server | Performance of a contract (you asked for this by registering) |
| Generating AI commentary from match statistics | Performance of a contract |
| Billing paid subscriptions | Performance of a contract; legal obligations |
| Evaluating AI output quality, tracking service costs, debugging | Legitimate interest (running and improving the Service) |
| Enforcing limits and preventing abuse | Legitimate interest |
We do not use your data for advertising and we do not sell it.
3. Who sees your data
- Your Discord server: match summaries, statistics, streaks, rivalry records, and recaps about registered players are posted publicly in channels chosen by that server's admins. Anyone in those channels can see them. This visibility is the product.
- Enemy players in your matches are never named in commentary — they are referred to only by the agent they played.
Beta applications: application details are stored in our access-controlled database. A notification in the operator’s Discord channel includes the Discord username, group size and application reference, plus a group name if one was supplied on an older form. Your email address is not included in that Discord notification. Feedback is stored the same way; its operator notification includes your answers, but not your name or contact details.
Processors we use to run the Service:
- Supabase — database hosting
- Discord — message delivery and bot platform
- Anthropic — AI text generation: match statistics and registered players' display names are sent to the Claude API to write summaries; Anthropic does not use API data to train its models by default
- Stripe — payment processing
- Vercel — website and API hosting, and aggregate website analytics
- Resend — sending beta emails: your email address, Discord username and the email content are sent to Resend to deliver them, and Resend reports delivery and bounces back to us
- A third-party Valorant data API — source of match data (queries include your Riot ID/PUUID)
Some providers process data outside the EU (e.g. in the United States) under standard contractual clauses or equivalent safeguards. We may also disclose data if required by law.
4. How long we keep it
- Match and statistics data: kept while your account is linked, so long-term features (season recaps, rivalry history) work.
- Server event log (bot "memory"): 90 days, then automatically deleted.
- AI output/quality records: kept until reviewed and periodically cleared.
- Billing records: as long as legally required.
- Beta applications, beta emails and notifications: retained while the beta runs and to follow up on requests. You can delete your application yourself with the link in any beta email, or email support@clantracker.gg.
- Feedback: deleted automatically after two years, or earlier on request.
- Setup progress events: deleted automatically after 400 days.
/unregisterimmediately stops tracking for that server and removes the link, but does not by itself erase stored history (so rejoining doesn't wipe your clan's shared records). For full erasure, see below.
5. Your rights
If you are in the EU/EEA (and in many other places), you can ask us to access, correct, export, restrict, or delete your personal data, and you can object to processing based on legitimate interest. To exercise any of these — including full deletion of your match history and identifiers — email support@clantracker.gg or reach out via the ClanTracker support server from a way we can verify (e.g. the Discord account in question). We respond within one month. You can also complain to your country's data-protection authority.
If someone registered your Riot account without your permission, contact us and we will unlink and remove it.
6. Age
The Service is not for children under 13 (or the higher digital-consent age in your country, e.g. 16 in the Netherlands). We do not knowingly process such users' data; contact us if you believe we are.
7. Security
Data is stored in an access-controlled database with row-level security. No internet service is perfectly secure, but we take reasonable measures appropriate to the data involved.
8. Changes
We will update this policy as the Service evolves — including when account linking moves to Riot Sign-On (which will change how registration works but not what gameplay data we store). Material changes will be announced via the website and/or Discord.
Questions: support@clantracker.gg or the ClanTracker support server.