Privacy

October 21, 2026

FightSet plays a Fightcade replay in the browser. The Chrome extension has one purpose: it adds a FightSet button next to that replay on fightcade.com.

Chrome extension

The extension places that button beside Fightcade’s View replay and Watch replay controls, and opens the same replay on fightset.com.

• It runs on fightcade.com so it can add the button. That match pattern is the only access it declares.
• It reads the replay link already on the control. It does not read a Fightcade account, messages, or password.
• It does not use storage, and it does not send the page to a server.
• The button opens https://fightset.com/ plus the game code and replay id, in a new tab.
• The toolbar icon does the same when the open tab is one of those replay links. Otherwise it opens the FightSet home page.
• The package contains the whole program. It does not download or run remote code.

The website

Opening a replay sends that game code and replay id to fightset.com. The server uses them to fetch the spectator stream from Fightcade and pass it through to the browser. There is no FightSet account.

Names on a match are looked up on Fightcade’s public profile API so the page can show the public rank and avatar. FightSet does not keep a copy of those profiles.

Game files needed to play stay in this browser, in IndexedDB, so the same game is not downloaded again. Volume, mute, and whether the input logs are open stay in this browser, in localStorage. Those values are not uploaded.

The player pages load Google Analytics, measurement ID G-Y5XYJ29967, to count visits. Google receives the usual analytics data described in Google’s privacy policy. This page does not load that tag.

Cloudflare hosts the site and may keep standard request logs. FightSet does not sell personal information.

Comments

Signing in with Discord lets you post on a replay. FightSet stores your Discord user id, username, display name, and avatar, plus the comment and when you posted it. The comment shows that name and avatar and links to your Discord profile. A time written like 1:23 jumps the replay to that moment, and an @name links to that person when FightSet knows them. You can delete your own comments. Discord handles the sign-in; their privacy policy covers that step.

Likes and views

Opening a replay adds one to its view count. That count is not tied to a person. The same Discord sign-in lets you like a replay; FightSet stores the like with your Discord user id so you can take it back. Comments and likes are stored against that replay’s game and replay id. When the replay card is known, FightSet also keeps the public names, countries, ranks, and score so the lists can show the match. The home page and the replay search list the most liked, most viewed, and most commented of those replays.

Clips

Saving a clip encodes the picture and sound in this browser and downloads an MP4. That file stays on the computer that saved it. FightSet does not receive the video. When Patreon membership is connected, FightSet checks the membership with the Discord user id from the sign-in before the save runs.

Contact

Questions about this page: github.com/elofight/fightset.