Privacy Policy

Last updated: July 23, 2026

This policy explains what data Brawl Planet processes, why, and what rights you have. It covers the website at brawlplanet.com (the "site") and the Brawl Planet Discord bot (the "bot"). In short: we run analytics to understand how the site is used, we display and archive publicly available Brawl Stars player statistics, and we do not sell data or show ads. This page is provided in English only.

Who we are

Brawl Planet is a fan-made Brawl Stars statistics site, operated from the Netherlands (the "we" in this policy). We are the controller for the processing described here. You can reach us at contact [at] brawlplanet.com or through the feedback form on the site.

Brawl Planet is not affiliated with, endorsed, sponsored, or specifically approved by Supercell, and Supercell is not responsible for it.

Website visitors: analytics and cookies

We use analytics to understand which pages are used and to find problems. There are two levels, and only the second one involves cookies:

  • Analytics without cookies (always on). PostHog (hosted in the EU) records page views, the page you came from, approximate location derived from your IP address, device and browser type, interface language, and specific product events such as searches. PostHog also captures your clicks automatically: when you click a link or a button, it records that element's visible text, its link target and where it sits in the page, so that we can see which parts of the site people use without having had to add tracking code to each one in advance. Text you type into a field is not recorded by this automatic capture. On player profile pages the recorded text can include in-game player names and player tags, including those of other players listed in a battle log; these are the public in-game names that the game itself shows to everyone. Our contact address is excluded from this capture. Search terms and player tags you type into the site's search boxes are also included in the explicit search events and page URLs we record, and error reports are sent here too. Google Analytics 4 (Google) also runs here, in a cookieless mode (Google Consent Mode with storage denied): it records page views without setting any cookie and without a persistent identifier, so it cannot recognize your browser across visits. Vercel Speed Insights (Vercel, our hosting provider) collects anonymous page performance measurements. To measure how many distinct people visit, PostHog stores a random, first-party identifier in your browser's localStorage. It is not a cookie, is used only on this site, is never shared with anyone else for their own purposes, and lets us recognize a returning browser for our own visitor counts. It sets no marketing or cross-site identifiers. This falls under the analytics exemption to the consent requirement (Article 11.7a(3) of the Dutch Telecommunicatiewet); the legal basis for the processing is our legitimate interest in understanding and improving the site (Article 6(1)(f) GDPR). If you decline the banner, this identifier is not stored: PostHog then keeps its identifiers in browser memory only and a full reload starts fresh.
  • Cookie-based analytics (only with your consent). If you accept the consent banner, Google Analytics 4 switches on cookies (named _ga and _ga_*) and PostHog moves its identifier into a cookie starting with ph_, so both can recognize your browser across visits. If you decline, neither sets these cookies, Google Analytics stays off, and PostHog falls back to the memory-only mode described above (no stored identifier). The legal basis is your consent (Article 6(1)(a) GDPR), which you can withdraw at any time by clearing this site's cookies and site data in your browser: the banner will then ask again on your next visit, and the site works fully without these cookies.

Besides the analytics identifier described above (which is sent with analytics events), the site stores a few values only on your own device (localStorage): your answer to the consent banner (analyticsConsent), so we do not ask again on every page; whether informational banners were dismissed; and your recent player lookups (player tag and in-game name) so the players page can show them again. These localStorage records are not uploaded merely because they are stored. If you open a recent lookup, its player tag becomes part of the requested profile URL and can therefore appear in the page-view analytics described above. You can remove the local records by clearing site data.

Our hosting provider (Vercel) and our cloud provider (Google Cloud) keep short-lived technical server logs, which can include IP addresses, for security and reliability. The legal basis is our legitimate interest in operating the service securely (Article 6(1)(f) GDPR).

Feedback form

If you send feedback, we receive the category you picked, your message, the page you were on, and, only if you choose to provide it, your email address. Submissions are delivered through Formspree, a US-based form service. We use this data solely to read and respond to your feedback (legitimate interest, Article 6(1)(f) GDPR).

Player profiles and battle history

The site and the bot can look up any Brawl Stars player by player tag. This section is the information notice for the players whose data is processed (Article 14 GDPR), who may be different people from our visitors.

What we process: the data the official Brawl Stars API publishes about a player: player tag, in-game name, profile icon, trophies and progression statistics, club membership (including the club's member list), the brawler collection, and the recent battle log. Battle log entries also include the player tags, in-game names, and brawlers of teammates and opponents in those matches.

Where it comes from: the official Brawl Stars API operated by Supercell, which exposes this data for every player of the game. We do not collect real names, email addresses, or any data players have not already made available through the game.

What happens on a lookup: when someone views a player's profile page or runs the bot's player commands, we fetch the current profile live, and we begin archiving that player's battle history in the background (the API itself only exposes the latest 25 battles). Archived battle history is stored in our public data bucket and is retrievable by tag. We stop updating a player's history 90 days after their profile was last viewed. Player profile pages are excluded from search engine indexing.

Why we may do this: our legitimate interest (Article 6(1)(f) GDPR) in providing game statistics to the Brawl Stars community, based on gameplay data that is already publicly retrievable by anyone through the official API, is pseudonymous (a tag and a self-chosen in-game name), and does not concern private life.

Your choices as a player: if you do not want your profile tracked on Brawl Planet, email contact [at] brawlplanet.com with your player tag. We will stop archiving your battle history and delete the stored history and tracking records. You can also object to this processing at any time (Article 21 GDPR).

Aggregate statistics are anonymous: the win rates, pick rates, tier lists, and map statistics on this site are computed from match data that contains no player tags or names (team compositions are stored only as one-way hashes). Nothing on those pages can be traced back to an individual player.

Discord bot

The bot only receives slash-command interactions from Discord; it cannot read your messages or DMs. For each command we process: the command and its options (for example a player tag, mode, or brawler name), your Discord user ID, the server (guild) ID, and your Discord interface language. This is necessary to answer the command (Article 6(1)(b) GDPR).

For usage statistics we record one event per command in PostHog (EU): the command name, server ID, language, response time, and outcome. Your Discord user ID is never stored for this; it is replaced with a salted one-way hash so we can count distinct users without being able to identify them. Command options are not sent to analytics. Technical logs (which include the command options, such as a typed player tag) are kept in the EU for a limited period. The legal basis for analytics and logging is our legitimate interest in operating and improving the bot (Article 6(1)(f) GDPR).

Discord itself processes your data as an independent controller under its own privacy policy.

Who we share data with

We do not sell personal data and we do not run ads. Three things belong in this section: the service providers we rely on, the game API our player data comes from, and the one category of data we publish openly.

Service providers (processors) we need to run Brawl Planet:

  • Google Cloud (US; data stored and processed in the EU): backend processing and storage.
  • Vercel (US): website hosting and performance measurement.
  • PostHog (US; data hosted in the EU): product analytics.
  • Google (US): Google Analytics.
  • Formspree (US): feedback form delivery.

Where a provider processes data in the United States, transfers rely on the EU-US Data Privacy Framework and/or the European Commission's Standard Contractual Clauses. Everything else is stored and processed in the EU.

Supercell (Finland) operates the official Brawl Stars API. It is the source of all player data on this site, and it receives a player tag whenever that player's profile is looked up here. Supercell is an independent controller for its own processing.

Published openly: the archived battle history described above is stored in a public cloud storage bucket, which means anyone who knows or guesses a player tag can download that player's stored history directly, not only through this website. That is deliberate: it is the same data the official API already exposes, and it is how both the site and the bot read it. It is a publication rather than a transfer to a processor, and it is the one place where personal data leaves our own systems for an open audience. It ends for a given player when their history is deleted on request.

How long we keep data

  • Analytics events: up to 3 years, then deleted or fully aggregated.
  • Feedback submissions: up to 2 years.
  • Bot technical logs: up to 90 days.
  • Player battle history: archiving stops 90 days after the profile was last viewed; stored history remains available so long-term statistics keep working for returning players, and is deleted on request (see above).
  • Raw match data used for aggregate statistics: contains no player identities and is kept as long as needed for the statistics.
  • Server logs at our hosting providers: kept briefly.

Your rights

Under the GDPR you have the right to:

  • access the personal data we hold about you (Article 15);
  • have inaccurate data corrected (Article 16);
  • have your data erased (Article 17);
  • restrict processing (Article 18);
  • data portability (Article 20);
  • object to processing based on legitimate interest, including the player tracking described above (Article 21);
  • withdraw consent at any time, without affecting past processing (Article 7(3)).

To exercise any of these rights, email contact [at] brawlplanet.com. You also have the right to lodge a complaint with your data protection authority; in the Netherlands that is the Autoriteit Persoonsgegevens.

Children

The site and bot do not require an account and are not designed to collect data from anyone. The player statistics we display are limited to pseudonymous in-game data (player tags and self-chosen in-game names) from the official API, which does not reveal a player's age or identity. Parents or guardians can request removal of a child's tracked profile using the contact address above.

Security

All traffic to the site, the bot, and our backend is encrypted (HTTPS). Backend systems run in Google Cloud's EU region with access restricted to the operator. No system is perfectly secure, but we keep the amount of personal data we hold deliberately small.

Changes to this policy

We may update this policy as the service evolves, for example when features are added. The date at the top shows the latest revision; meaningful changes will be visible on this page. Also see our Terms of Service.