Privacy Policy

Introduction

This Privacy Policy describes how Team Respawn ("we", "us", or "our") collects, uses, and protects information when you use teamrespawn.net and related website features (the "Website"). Team Respawn is a fan and content-creator site for strategy RTS games. We aim to be transparent about what we store and what we do not.

Last Updated: 4 November 2026

Accounts and personal data

Browsing the Website needs no account. There is one optional account feature — /account — and everything below in this section applies only if you choose to sign in. Outside of that and other voluntary features such as the contact form, we do not intentionally collect names, email addresses, phone numbers, or similar private contact details through the site.

Signing in with Discord. Discord is the only sign-in method; there is no password and no email sign-in. When you sign in we receive, and store, your Discord account ID and the email address on your Discord account. Authentication is handled by Supabase, which hosts the account records on our behalf.

Connected game accounts. During sign-in you are asked to grant Discord's "connections" permission. We use it once, at that moment, to read which Xbox and Steam accounts you have connected in Discord, and we store the account names and — for Steam — the SteamID64. That is how the Website proves a gamertag or game profile is yours before letting you claim it. We do not store your Discord access token. The stored list is refreshed each time you sign in, so removing a connection in Discord removes it here too.

Servers you manage. Sign-in also asks for Discord's "guilds" permission, which lists the Discord servers you are in. We store only the servers you own or can manage (their ID, name and icon), so the Storehaus alert dashboard can show them. Like connections, the list is read once at sign-in and refreshed each time you sign in. If you set up Halo Wars 2 alerts for a server, we store that server's ID and name, the channel ID you chose, which alert types it receives, and which account made each change.

Claimed profiles and co-play roster. If you claim a Halo Wars 2 gamertag or an Age of Empires IV / Age of Mythology profile, we store that claim against your account. For Halo Wars 2 we also derive a "people I play with" roster from public match data for your claimed gamertag, together with any pins, hides, or nicknames you set on it. All of this is built from public match records and is visible only to you.

Session cookies. Signing in sets two strictly necessary cookies, tr_access andtr_refresh, which hold your session tokens. They are HttpOnly (not readable by page scripts), same-site, and sent over HTTPS in production. They exist solely to keep you signed in — they are not used for advertising or cross-site tracking. Signing out clears them.

Other account settings. If you sign in, we also store the things you choose to save against your account: favorite leaders, videos, and blog posts; display preferences (such as time zone, time format, default playlist, and Classic or Compact views); per-game squads you set up; your tracker layout choices; and, if you opt in, a newsletter subscription. For the newsletter we use the email address on your Discord account, taken from your verified session, and you can change that choice on your account page. These are visible only to you and are not used for advertising.

You can stop using the account feature at any time by signing out, and you can ask us to delete your account data through the contact form.

We do not sell personal data. We do not license visitor data to data brokers.

Information we process

Public game identifiers and Halo Wars 2 stats

When you look up Halo Wars 2 stats, we process public gamertags and related public match/statistics data from game services so we can show profiles, match history, meta pages, integrity summaries, and similar features. We may temporarily store that public game data to operate the site reliably. Stored data may include gamertags, match information, season and campaign stats, achievements derived from public play, and community-wide meta aggregates.

Gamertags are public identifiers used in Xbox / Halo services. We may analyze gamertag and match activity in aggregate (for example, to understand which leaders, maps, or content topics are popular) so we can improve guides, videos, and site tools. That analysis is about public game activity across the community, not about selling private profiles.

Search and usage events

Profile searches and similar requests may create short-lived operational records used to run and protect the Website. These are tied to public gamertags and service operation, not to your signed-in account.

Tournaments (beta)

If you create or join an HW2 tournament on the Website, we store tournament configuration, participant gamertags, bracket/match state, and organizer-provided notes or rules. Organizer admin passwords are stored in a non-reversible form. We may keep limited technical records needed to prevent abuse; we do not treat those as public profile data.

Game trackers and progress

The Website offers checklists, maps, and progress trackers for a number of single-player and campaign games.If you are not signed in, your tracker progress and settings (for example which items you have ticked and your map or route choices) are stored only in your own browser. We do not receive them, and clearing your browser data removes them.

If you are signed in, tracker progress is saved to your account so it follows you between devices. We store the progress data for each game you track (such as completed items and notes you enter) and when it was last updated, against your account. It is visible only to you, is not shown publicly, and is not used for advertising or sold. Tracker progress is not combined with other users' data, and we do not use it to profile you.

To apply the retention rule below, we record when you last visited the Website while signed in. You can delete any tracker's saved progress, or all of it, at any time from Account → Settings → Your tracker data.

RetroAchievements (optional)

If you choose to link a RetroAchievements account on your account page, we store the RetroAchievements username you give us, a short-lived verification code used to confirm the account is yours, and a snapshot of that account's public profile and achievement activity (such as points, rank, and games and badges earned), which we fetch from RetroAchievements and display only to you on your account page. That information is already public on RetroAchievements. We refresh the snapshot when you view or refresh it. You can unlink RetroAchievements at any time from your account page, which deletes the stored username, verification data, and snapshot. We never ask for, or store, your RetroAchievements password.

Xbox (connected automatically)

If your Discord account has exactly one Xbox account connected, signing in to the Website connects that Xbox account for you, so you do not have to do anything. If you have several, you pick one on your account page. We look up the account's Xbox ID through OpenXBL, a third-party service that reads Xbox Live, and store the Xbox ID, your gamertag, your gamerscore, and a snapshot of your achievement progress for the games the Website tracks (with your recently played titles and their art). For the achievement trackers we also keep, for an hour at a time, the names of the achievements you have and have not unlocked in that game, so the tracker can offer to tick them. Nothing is ever ticked for you automatically, and we only read from Xbox: we never write to your account and never ask for your Microsoft password.

Public by default. Your gamertag, gamerscore and the progress snapshot may be shown on public Team Respawn pages, such as Xbox leaderboards. You can turn that off at any time on your account page, and your data then stays visible only to you. Xbox's own privacy settings still apply: if your Xbox profile hides your achievements, we cannot read them and nothing is shown. You can disconnect Xbox at any time on your account page, which deletes the stored Xbox ID, gamertag, snapshot and achievement names immediately and stops it from connecting itself again. We keep a record that you disconnected, so that it does not reconnect on your next visit; it holds only your account ID and the date.

Premium and Patreon (optional)

Premium is paid through Patreon; we never see or store your card or payment details. If you link Patreon to your account, we store your Patreon user ID and display name, when you linked it, and whether your membership currently entitles you to Premium (its source, tier, status, and when it ends). We receive membership updates from Patreon so that Premium starts and ends on time, and we check your membership against our campaign's member list periodically. We use the Patreon sign-in only once, to confirm which Patreon account is yours, and do not keep your Patreon access token.

This is visible only to you and is not used for advertising. You can unlink Patreon at any time on your account page, which deletes the stored link and the Patreon entitlement immediately. Extra tracker playthroughs and their names are stored like the rest of your tracker progress, and are kept if Premium ends until you delete them.

Contact form

If you use the contact form, you voluntarily provide a name, email address (so we can reply), a message, and optionally a Discord username or gamertag. We use that information only to respond to your inquiry. Submissions are delivered to Team Respawn via Discord (using our Storehaus bot) and are not stored as Website account profiles. We may keep limited technical records (such as rate-limit counters) to prevent spam and abuse.

Hosting and analytics

Our hosting and security provider (Cloudflare) may process technical request data as part of delivering and protecting the Website. When enabled, we use Cloudflare Web Analytics, a privacy-oriented traffic measurement tool that does not rely on marketing cookies. It helps us understand approximate page views, referrers, and similar high-level traffic patterns.

When configured, we also use Microsoft Clarity (via the official Clarity library) for optional behavioral analytics: session insights, heatmaps, and engagement signals that help us improve content and tools. Clarity may set analytics cookies only after you accept them in our cookie preference control. Microsoft processes that data under its own privacy terms.

Third-party content and media

Pages may load media or embeds from third-party providers (for example image hosts, YouTube, Twitch, or Discord). Those services process data under their own policies when your browser requests their resources.

Cookies, advertising, and preferences

The Website does not run a first-party advertising network, does not load third-party ad-network scripts, and does not set advertising cookies on our domain. We do participate in affiliate programs with Humble Bundle and Green Man Gaming, tracked through Impact. When you click an affiliate link, your browser first stays on teamrespawn.net at a /go/… path. Our server records the click with Impact and then sends you to Humble Bundle or Green Man Gaming. The store may set its own cookies (including Impact’s irclickid on the landing URL) to attribute a purchase. We do not load Impact JavaScript or hidden impression pixels on our pages, and we do not send your browser through Impact’s sjv.io tracker.

Featured deal banners are hosted on this Website. Clicks on those images go through our first-party /go/… redirect to Humble Bundle or Green Man Gaming.

We use the following analytics approaches:

• Cloudflare Web Analytics — privacy-oriented traffic measurement without marketing cookies (when enabled).
• Optional Microsoft Clarity analytics cookies — used for session insights and heatmaps so we can understand journeys (which pages and tools people use) and improve the site. You can accept or decline these cookies via the on-site banner, and you can reopen that choice anytime with Cookie preferences in the footer.

We may add advertising in the future in low-friction areas of the site. If we do, we will update this policy and any consent controls as needed.

How we use information

• Operate Website features (stats lookup, meta, tournaments, blog, video database, Storehaus marketing stats, contact form, game deals, and related tools)
• Keep the Website reliable and responsive
• Understand community interest so we can create better guides, videos, and site experiences
• Reply to voluntary contact-form inquiries
• Detect abuse, spam, and integrity issues related to public match data
• Comply with law and protect the Website and our community

What we do not do

• Sell personal data
• Require a Website account to browse content or look up public HW2 stats
• Claim ownership of Microsoft game data or imply Microsoft endorsement

Third-party services

• Hosting and security providers — deliver and protect the Website; they may process technical request data under their own policies. Cloudflare Web Analytics (when enabled) measures privacy-oriented traffic metrics.
• Microsoft Clarity — optional behavioral analytics (session insights / heatmaps) when you accept analytics cookies. See Microsoft’s privacy documentation for how Clarity processes data.
• Supabase — hosts account records (sign-in, claimed profiles, saved tracker progress, and preferences) on our behalf.
• Discord — the only sign-in method. We receive your Discord ID, email address, and (once, at sign-in) your connected Xbox / Steam accounts and managed servers, under Discord's own terms and privacy policy.
• RetroAchievements — if you link an account, we read its public profile and achievement data through the RetroAchievements API. Their service is governed by their own terms and privacy policy.
• OpenXBL — if you have an Xbox account connected in Discord, we look up its public Xbox profile and achievements through the OpenXBL service. We send it your gamertag and Xbox ID. Xbox data remains subject to Microsoft’s terms.
• Microsoft / Halo services — public Halo Wars 2 statistics used to power lookups. Game data remains subject to Microsoft’s terms and rights.
• Media and community platforms — such as image hosts, YouTube, Twitch, or Discord when pages load their content, link to them, or when we deliver a contact-form message through Discord (Storehaus bot).
• Humble Bundle, Green Man Gaming, and Impact — affiliate storefronts and click tracking when you use Game Deals or other buy links. Those companies process the click (and any purchase) under their own privacy policies.
• Patreon — handles Premium memberships and payments under its own privacy policy, if you choose to pledge or link your account.

Data retention

Public game and match data used by the Website are kept only as long as needed to operate features. Tournament records remain while the tournament feature needs them. Operational records may be deleted on a schedule.

Saved tracker progress is deleted after one year without signing in. The year runs from your last visit to the Website while signed in, and any signed-in visit restarts it. About a month before deletion, the Storehaus Discord bot sends you a direct message warning you, unless you have switched that warning off in your account settings or Discord does not allow the bot to message you. The deletion date is set when that warning is first due and is at least four weeks away; if the message cannot be delivered, the bot tries again each day until it gets through, and the date does not move. This applies to every tracker, including ones added in future.

Other account data (preferences and claimed profiles) is kept while your account exists. Account deletion is handled manually: send a request through the contact form and we will delete your account and its saved data. Unlinking RetroAchievements, Xbox, or Patreon removes that data immediately. Progress stored only in your browser is never held by us and is cleared by clearing your browser data.

Your choices

• You can choose not to search gamertags, use optional tools such as tournaments, or submit the contact form.
• You can accept or decline optional Clarity analytics cookies via the banner, or change that choice later with Cookie preferences in the footer.
• You can use every tracker without an account; progress then stays in your browser only.
• You can delete any tracker's saved progress, or all of it, from your account settings, and switch off the Discord warning sent before inactive tracker data is deleted.
• You can turn on a public profile at teamrespawn.net/profile/your-handle from your account settings. It is off unless you switch it on. Anyone with the link can then see your Discord display name and avatar, your handle, your linked game profiles and their public stats, your tracker progress (percentages, not the items ticked), your Xbox and RetroAchievements summaries if you show them, your daily game streaks and scores, and whether you are a Premium supporter. You choose which sections it shows, and you can switch it off or remove it at any time; changes can take a few minutes to reach every visitor. Profiles are marked not to be indexed by search engines.
• While your public profile is on and "Show my activity" is left on, the member feed (teamrespawn.net/feed) and your profile list what you do on the site: tracker progress and milestones (percentages, not the items ticked), your daily game results (the number of guesses, never the guesses), Halo Wars 2 matches of your verified gamertag (result, leader, map), and blog posts you favorite. The site feed only includes profiles with "Help people find it" on. To build it, we keep a log of these events for every signed-in account (not only those with a public profile), so the feed can include your recent activity as soon as you switch it on. Each event is deleted after 90 days. Nobody sees the log unless the settings above allow it, and switching the profile or "Show my activity" off hides it again within about a minute.
• You can unlink RetroAchievements, Xbox, or Patreon, hide your Xbox data from public pages, change your newsletter choice, or sign out from your account page, and ask us to delete your account through the contact form.
• Browser controls can block third-party embeds or clear site data.

Children's privacy

The Website is not directed at children under 13. We do not knowingly collect personal information from children under 13.

Changes

We may update this Privacy Policy from time to time. The "Last Updated" date above reflects the latest revision. Material changes related to cookies or advertising will be reflected here when those features change.

Contact

Questions about this policy or Website privacy practices can be sent via our contact form or raised in the Team Respawn Discord: https://discord.gg/TeamRespawn.

Introduction

This Privacy Policy describes how the Storehaus RTS Discord Bot ("the Bot", "we", "us", or "our") collects, uses, and protects information when you interact with it on Discord. We are committed to protecting your privacy and being transparent about our data practices.

Last Updated: October 2026

Information We Collect

Discord Data

When you use the Bot, Discord automatically provides certain information through their API, including:

• User ID: Your unique Discord user identifier
• Username and Display Name: Your Discord username and server display name
• Guild/Server ID: The unique identifier of the Discord server where you use the Bot
• Channel ID: The unique identifier of the channel where commands are used
• Message Content: The content of slash commands and interactions you send to the Bot

Important: While Discord provides this information to the Bot, we do not store or log Discord user IDs, guild IDs, usernames, or any personally identifiable information (PII) for general Bot commands such as game stats, lookups, and AI questions. The only exceptions are the server alert settings described below and the moderation records the Bot keeps for the Team Respawn Discord server (see Moderation Records).

Exception: server alert settings. If a server admin turns on Halo Wars 2 cheating or boosting alerts on the Storehaus alert dashboard on teamrespawn.net, that server's ID and name and the chosen channel ID are stored there, so alerts can be posted to it. They are removed when an admin turns alerts off. See the website privacy policy for the sign-in data that dashboard uses.

Command Usage Data

When you use Bot commands, we may temporarily process:

• Command Input: The parameters you provide to commands (e.g., search queries, player IDs, questions)
• Command Type: Which command was executed
• Timestamp: When the command was executed

We also keep aggregate, anonymous slash-command usage counts (command name and total count only) for public platform stats on the Storehaus marketing page on teamrespawn.net. These counters do not include Discord user IDs, guild IDs, channel IDs, or usernames. Approximate Discord install counts shown on that page come from Discord and are shown only as totals.

Query Logs (Halo Wars 2 AI Feature)

For the /hw2ask command, we log queries to improve the service quality.These logs do NOT include any user-identifying information. We only store:

• The question text
• Query type and confidence level
• Response metadata (model used, response time, sources referenced)
• Timestamp

We explicitly do NOT store:

• Your Discord user ID
• Your username
• Server or channel information
• Any other personally identifiable information

Moderation Records (Team Respawn Server Only)

The Bot also runs moderation for the Team Respawn Discord server (server ID 321075308105302016). This applies only to that server. In any other server, the Bot does not run moderation commands and keeps no moderation records.

When Team Respawn moderators use moderation commands (such as /strike, /mute, /kick, /ban, or /notes), or when the Bot mutes a member automatically after repeated strikes, we store a record that includes:

• Member User ID: The Discord user ID of the member the action is about
• Moderator User ID: The Discord user ID of the moderator who took the action, or who later removed it
• Server ID: Always the Team Respawn server ID
• Action: The type of action (strike, mute, unmute, kick, ban, unban, note, or strike removal)
• Reason: The reason or note text written by the moderator
• Timestamps and Durations: When the action happened and, for mutes, how long it lasts
• Username Snapshot on Ban: The banned member's Discord username and display name at the time of the ban, so moderators can still tell who a ban list entry is
• Active Mute Details: While a member is muted, the roles taken away during the mute, so they can be given back when it ends

Moderation history from the tool the Team Respawn server used before Storehaus has also been imported in this format.

Server Audit Log (Team Respawn Server Only)

In the Team Respawn server only, the Bot posts audit log messages to dedicated log channels for moderators. These posts can include member joins (with the invite used) and leaves, role and nickname changes, voice channel activity, channel changes, and message edits (the content before and after) and deleted messages (their content). The /report command also sends a member's report, and any attachment, to a moderator channel. These are posted as Discord messages; the Bot does not save them in its own databases.

How We Use Information

Service Provision

We use the information provided by Discord to:

• Process and respond to your commands
• Provide game statistics and information
• Answer strategy questions through our AI-powered features
• Ensure proper command functionality

Analytics and Improvement

We use anonymized query logs to:

• Improve response quality and accuracy
• Understand common questions and topics
• Monitor service performance
• Identify areas for improvement
• Display anonymous lifetime command totals on the Storehaus website

All analytics are performed on anonymized data without any user identifiers.

Server Moderation (Team Respawn Only)

We use Team Respawn moderation records and audit log posts to:

• Enforce the Team Respawn server rules and apply strikes, mutes, kicks, and bans
• Track repeat behavior, including automatic mutes after repeated strikes
• Give back a member's roles when a mute ends
• Let moderators look up a member's history and the server's ban list
• Share a weekly summary of moderation actions with Team Respawn staff

Moderation commands and records are only available to members with Team Respawn moderator or staff roles.

Data Storage

What We Store

• Query Logs: Anonymized questions and response metadata (no user IDs)
• Aggregate Command Counts: Command name and lifetime invocation totals only (no PII)
• Game Data: Public game information (units, civilizations, statistics)
• AI search material: Processed public game data used to answer strategy questions
• Moderation Records: Team Respawn server only. Member and moderator user IDs, actions, reasons, timestamps, and username snapshots on ban (see Moderation Records)

What We Do NOT Store

• Discord user IDs (except in Team Respawn moderation records)
• Discord usernames or display names (except the snapshot saved when a member is banned from the Team Respawn server)
• Guild/Server IDs and Channel IDs (except a server's alert channel, set on the alert dashboard, and the Team Respawn server ID on moderation records)
• Message content (except anonymized questions for /hw2ask). Team Respawn audit log posts are Discord messages, not Bot database records.
• Any personally identifiable information for users outside the Team Respawn server's moderation records

Where data is kept

Bot operational data (anonymized query logs, aggregate command totals, game reference data, and related AI search material) is kept on infrastructure controlled by the Bot operator. Anonymous aggregate command totals may also appear on the Storehaus marketing page on teamrespawn.net. Team Respawn moderation records are kept in a private database on the same infrastructure. Team Respawn moderators and staff can view them through Bot commands. Audit log posts and reports stay in the Team Respawn server's Discord channels. Bot operational data is not shared with third parties except as described below. We do not sell Discord user data.

Third-Party Services

The Bot uses the following third-party services:

Discord

• Purpose: Bot platform and command processing
• Data Shared: Command interactions, plus moderation, audit log, and report posts in the Team Respawn server (handled by Discord's infrastructure)
• Privacy Policy:Discord Privacy Policy

aoe4world.com API

• Purpose: Fetching Age of Empires IV statistics and player data
• Data Shared: Public player IDs and game statistics (publicly available data)
• Privacy Policy:aoe4world.com Terms

LLM Providers (Groq, Cloudflare, OpenRouter, Cerebras)

• Purpose: Generating AI-powered responses for strategy questions
• Data Shared: Anonymized questions (no user identifiers)
• Privacy Policies:
  • Groq Privacy Policy
  • Cloudflare Privacy Policy
  • OpenRouter Privacy Policy
  • Cerebras Privacy Policy

Data Retention

• Query Logs: Retained indefinitely for analytics and service improvement
• Discord Data: Not stored for general commands; only processed temporarily during command execution
• Game Data: Retained as long as the Bot is operational
• Moderation Records: Retained indefinitely while the Bot runs moderation for the Team Respawn server, so moderators can see a member's full history. Strikes that moderators remove are marked as removed, not deleted. Active mute details (such as the roles taken away) are deleted when the mute ends.
• Audit Log and Report Posts: Not stored by the Bot; they stay in the Team Respawn server's Discord channels until staff delete them

Your Rights

For most Bot features we do not store personally identifiable information, so traditional data subject rights (such as data deletion requests) do not apply in the same way. However:

• Anonymized Query Logs: If you have concerns about specific queries, you can contact us on Discord
• Moderation Records: If you are or were a member of the Team Respawn server, you can contact us on Discord to ask what moderation records we hold about you, or to ask for a record to be corrected or deleted. We may keep records we need to enforce an active ban or keep the server safe.
• No User Tracking: Outside of Team Respawn moderation records, we cannot track or identify individual Discord users from Bot storage because we don't store user identifiers

Security

We implement reasonable security measures to protect the data we store:

• Local storage of databases and files
• No transmission of user identifiers to game data or AI providers
• Anonymized logging practices for query logs
• Moderation commands and records restricted to Team Respawn moderator and staff roles

However, no method of transmission or storage is 100% secure. While we strive to protect your privacy, we cannot guarantee absolute security.

Children's Privacy

The Bot is not intended for users under the age of 13. Discord's Terms of Service require users to be at least 13 years old. We do not knowingly collect information from children under 13.

Changes to This Privacy Policy

We may update this Privacy Policy from time to time. The "Last Updated" date indicates when changes were made. We encourage you to review this policy periodically.

Contact

If you have questions or concerns about this Privacy Policy or our data practices, contact us in the Team Respawn Discord: https://discord.gg/TeamRespawn.

Compliance

This Privacy Policy is designed to comply with:

• Discord's Developer Terms of Service
• General data protection principles
• Best practices for privacy-first bot development