Privacy notice
Clanware Replays. Last updated: 8 November 2026.
Clanware Replays lets you watch official Clanware matches again, from any angle, on this website. This page says what we keep about you when you play in or watch one, who can see it, and how to have it removed. See also the terms.
Who runs it, and how to reach us
Clanware Replays is run by Clanware. For anything about your data, open a ticket in the Clanware Discord server and say it is a privacy request.
Responsible: Clanware. Discord server for tickets: discord.gg/kjDpVBPbKS.
What a replay records
While you play in a recorded match, the game server writes down about 20 times a second:
- where your character is and which way it faces;
- your health, whether you are holding or swinging your sword, and whether you are running, jumping or falling;
- the camera position and the point you are aiming at, about 10 times a second. These are as reported by your own game, so they can be wrong or edited by a modified client;
- kills, and when you are knocked out: where, which way you faced, and which way the hit came from;
- moments such as a round starting or an objective being taken, and when you leave.
For each player the replay also keeps: your Roblox user ID, your display name, your avatar's body colours and rig type, your sword skin, your team side, and your clan tag and clan ID. For League matches it also keeps the Roblox user IDs of everyone on the two rosters, so that rostered players can be kept from watching their own match live.
We never record chat or voice. Nothing anyone types or says is stored.
We show your Roblox avatar headshot. It is fetched from Roblox when a viewer first needs it, and a copy is kept for up to 7 days.
If you save a clip in game (up to 20 a day), the clip keeps your user ID as the person who made it, as well as the 30 seconds it shows.
Who can see what
| Who | What they see |
|---|---|
| Anyone with the replay code | A finished match: movement, kills, display names, avatar colours, clan tags and headshots. Never your user ID. |
| Signed-in viewers, during a live match | The match 90 seconds behind real time, so it cannot help anyone still playing. A clan member is only shown their own clan's side. Players in the match, and everyone on its rosters, cannot watch it live. |
| Casters | The same 90-second delay as everyone else. |
| Referees and Clanware staff | Live almost as it happens, to run the match fairly. Staff can also see who watched a live match: their user ID, whether they watched as a viewer, caster or staff, which side they were shown, and when they first and last watched. |
| Review rooms | People you share a finished replay with see each other's display names (never user IDs) and the arrows and circles drawn on it. Rooms have no text. A room ends an hour after the last person leaves. If the host saves a review, the drawings are kept as long as the replay, with the host's user ID. |
| The public | Replays are not listed and cannot be searched. Anyone given a code can open the finished replay. |
Signing in
You only need to sign in to watch a match while it is being played, or to join a review room. Signing in uses your Roblox account. Roblox tells us your user ID and display name; we do not get your password, email address or age. Roblox only lets accounts aged 13 or over sign in to apps like this one, so under-13s can watch finished replays with a code but cannot sign in.
When you sign in:
- we keep your user ID and when you agreed to this notice and the terms;
- we ask Clanware's own league system which clan you are in and its ally, to decide which side you may see live. We keep the answer in memory for a short while and never write it down;
- if the game has made you a caster or referee, we hold your user ID and that role until the game stops listing you. The game sends the list every 5 minutes;
- your browser holds a signed pass with your user ID, display name, role, clans, and when it was issued and when it ends (at most 8 hours). It is kept for that browser tab only and goes when the tab closes. A short-lived cookie (10 minutes) is set while you sign in, to stop someone else finishing your sign-in. There are no other cookies.
How long we keep things
- 30 days after a match is recorded, its replay is deleted automatically, with its clips, saved reviews and watch log.
- Pinned files. Clanware staff can pin a replay or clip to keep it past 30 days, for example as evidence in a Justice case. It stays until staff unpin it, and is then deleted at the next clean-up.
- Backups. Each night we copy the database and pinned files to private, encrypted off-site storage, and delete copies older than 35 days. A backup can still hold something already removed from the site until that backup is deleted.
- Caches: a copy of a finished replay may sit in a cache for up to a day after it changes.
- Your visit: like any website, our server and Cloudflare, which carries the traffic, see your IP address. The replay service holds it in memory for about a minute to limit abuse and does not write it down.
Ask for your data to be removed
Open a ticket in the Clanware Discord (see above) with your Roblox username or user ID. When we remove you:
- you are cut out of every recording, pinned ones too, and your knock-outs go with you. Others' replays keep working;
- your name becomes “Removed player” and your colours, clan tag and user ID are cleared;
- clips you made, your saved reviews, your watch log entries, your sign-in agreement and your cached headshot are deleted;
- any sign-in pass you still hold stops working. To make that stick, we keep your user ID for 9 hours (longer than any pass lasts), then delete it;
- copies in backups and caches go when they expire (see above).
Roblox also tells game creators when someone asks Roblox to delete their data, and we act on those requests in the same way, without you needing to ask us.
What we don’t do
- We don’t sell data or show ads.
- We don’t use trackers or analytics.
- We don’t record chat, voice, or anything outside the match.
This is a plain-language notice. If it changes, the date at the top changes too.