What Chudlock collects, why, where it goes and how long it stays. Short version: we use public match data, a Steam sign-in if you choose one, and ads from Google, which uses cookies.
Who we are
Chudlock (chudlock.com) is an independent fan project, not affiliated with Valve, run by Meowers Developments, a UK sole trader, of The Bristol Office, 2nd Floor, 5 High Street, Westbury-on-Trym, Bristol, BS9 3BY, England. For anything on this page, including requests about your data, email hello@chudlock.com.
Match data
Match and player pages are built from public Deadlock match data served by the community deadlock-api, including Steam names and avatars. Your browser fetches it directly from deadlock-api, so they see your IP address as with any website; their own policies apply. We don't store a copy of the pages you look up.
A player page works out more from that same public data, in your browser: rank points after each ranked game, progress towards ranked, weekly trends, and a match list you can filter. It also lists the Steam names of the players someone has played with or against three or more times, with their record together. We store none of it. To be left out of those lists, email hello@chudlock.com.
Top players
The top players page lists the top 100 of each region's in-game leaderboard, which Valve publishes, and a few well-known players we add by hand. For each we keep their Steam account ID, name and public matches from the last 30 days, taken from deadlock-api. To be left off, email hello@chudlock.com and we'll remove you and your matches.
We show some of those matches. Each hero page lists the latest ten games that listed players played on that hero, and a pro setup page lists that pro's own latest games. A game shows the hero, who won, kills, deaths and assists, the player's rank, every item they bought and when, the order they spent ability points, and the in-game build they had picked, if the match data says. Hero pages name the player, link to their player page and say where they place on the leaderboard. Search engines list hero pages, so those names can show up in search. The pages refresh every hour, and once you're off the list your games leave them within a few hours.
For some of those players, a pro setup page (for example Deathy's) shows the settings, gear and crosshair they've published themselves on their Twitch page or in their stream's chat commands, each with a link to where and when they posted it, and their Twitch picture, which your browser loads from Twitch. We don't show their real names unless they use them publicly. Players can ask us to correct or remove their page at hello@chudlock.com.
The leaderboards list the top 1,000 players on each hero by games, wins, win rate, rank and a set of single-game and career records, from deadlock-api's public scoreboards. We keep a copy of each board, refreshed every few hours, with the Steam name and avatar of the top 100. Street Brawl has its own boards, for each hero and across all heroes, refreshed daily, with the same Steam names and avatars. Emailing hello@chudlock.com takes you off these too.
Each hero also has a page of its best players, such as Haze's, with the Steam names of its top 100. Search engines list these pages, and each one's description names the player at #1. Once we've taken you off, search results catch up the next time the search engine visits the page.
Valve's ladder copies the ranked ladder Valve publishes, every hour: the top 1,000 of each region and a ladder for each hero. We keep each name exactly as Valve lists it, with its place and top heroes, and the places from earlier copies so the page can show who has moved since yesterday. When a ranked season ends we keep the last copy of each board. Valve lists names, not accounts, so we link a name to a Steam account and show that account's rank only when one account clearly owns the name; those matches are kept for up to a week. If you are signed in, the page looks your account up in these lists to show your places, and keeps nothing about the lookup. Emailing hello@chudlock.com takes you off, and we then leave out every ladder name your account has used.
The one-trick boards list players with at least half of their games on one hero, with their Steam name and avatar, their games and wins on that hero and their games in all, from deadlock-api's public scoreboards, rebuilt daily. Emailing hello@chudlock.com takes you off these too.
The rating boards rank up to 2,000 players by the Chudlock rating, overall and on each hero, with their Steam name and avatar, the rank of their newest game, their rating and its range, and the games behind it. The players are the best places we matched on Valve's ladder and the most active players on our hero boards. We read each one's public match history from deadlock-api every few days, work the rating out and keep only the result, not the games. Emailing hello@chudlock.com takes you off, and we then stop reading your history and drop your rating.
Live matches
The live matches page lists the top games being played now, from deadlock-api's watch list. Every player is shown only as their hero, pros included: no names and no account IDs. To work out each game's average rank we keep the latest rank of the players in these games for up to two hours; it is not shown against anyone.
Signing in with Steam
Sign-in uses Steam's own login page. Steam tells us your Steam account ID and nothing else: never your password or email. We keep you signed in with two cookies for up to 30 days: a signed session cookie (unreadable to scripts) and a small chudlock_signed_in marker that only tells the page whether to check your session. Signing out clears both. These are the only cookies we set ourselves, and both are needed for sign-in. Google's ad cookies are explained under Ads below. We also record which Steam account signed in, when you first and last did, and how many times, so we can see who uses the site.
In your browser
Some features save things on your own device and nowhere else: your practice goal and recent-match cache, and whether you've dismissed Rem. Clear your browser's site data to remove them.
Replay uploads
Replay uploads are closed. From earlier test uploads we keep facts about the match taken from the replay, and a record of the upload (the match, the Steam account ID and whether it succeeded). The files themselves are gone.
Highlights
Highlights are videos of your own finished games, made on our servers from the match's public replay, with the Chudlock mark on them. We keep each video, a still from it and what's in it (the match, the heroes, the moments and the game's rank) in storage on Cloudflare, against your Steam account ID. A video you don't save goes after about a week, unless people are watching its link. Saved ones last as your plan says, and you can delete them. We keep a record of who made which video after the video has gone, to deal with abuse reports. Heroes in a video are named by hero, not by player, unless the maker has a paid plan and turns on names: then it's their team's Steam names, and you can opt out of yours in your settings. If you're in a video and want it gone, email us and we'll take it down.
Quests
Quests are counted in your browser from your public match history, and counted again on our server when you claim one, so a quest can't be claimed without the games. Signed in with Steam, we keep against your Steam account ID: the quests you've claimed (which day, week and slot, not your matches), the title, frame and flair you choose to wear, and, if you take a personal quest, the habit it's about, the hero if it names one and when you took it. When a personal quest is finished we keep a short note of that habit's average before and during it. Your worn title, frame and flair, your weekly streak and your count of claimed quests are public: they show on your player page and Mastery, in the bots, and on a share image of your quests at an address that includes your account ID. A running personal quest is shown only to you. A worn flair also shows next to your name on leaderboards and match pages. For that we keep one list of who wears which flair, by account ID, and your entry is removed when you take your flair off. Rewards are cosmetic and are never sold.
If you switch on quest alerts in Discord, we keep with your Discord link whether you want a daily reminder by direct message, the server where a finished weekly quest is posted (one you've joined the party feed of), and which weekly quests were already announced. If a streamer switches quests on for their Twitch channel, we keep that setting and the weekly quests the bot already announced. Players who asked to be left off chudlock.com can't claim quests and show none. To delete your quest record, email hello@chudlock.com; unlinking Discord or removing the Twitch bot deletes the alerts.
Share cards
Chud of the Match links and images are public by design: anyone with the link sees the card, built from public match data.
Payments
Paid plans aren't on sale yet. When they open, Creem handles payments as merchant of record. Creem takes your card and billing details; we never see them. Creem tells us which Steam account paid and until when, and we keep that record for as long as it's needed for your plan and our accounts.
Usage counts
To see which parts of the site are used, we count page visits from everyone, signed in or not. Your browser keeps a random ID in its local storage (not a cookie) so we can tell a new visitor from a returning one. With each page it sends that ID, the kind of page (home, match, player and so on), how long the page was open in front of you, the site that linked you here, and whether you're signed in. For hero, build, item, leaderboard and patch pages we record which one. We never record which match, player or pro you look at. If the link you followed carries a campaign tag (utm_source, such as "discord"), we keep that tag too. Your browser also remembers where you first came from (that tag or site, or "direct") and sends it with each page, so we can see which links bring people who come back or sign in. From the request we add your country and whether you're on a phone or computer. The ID is never linked to your Steam account and we don't store your IP address with it.
When you're signed in, we also count the pages you open (by kind, as above) and steps such as signing in, uploading a replay and starting checkout. Each is stored with a scrambled ID made from your Steam account ID rather than the ID itself. Since 17 October 2026, the site owner can match that scrambled ID to your account on our private admin page, to see how signed-in people use Chudlock: when you were last here, on how many days, which kinds of page you used and which of those steps you took. Nobody else sees it, it isn't shared or used for ads, and Analytics Engine deletes it after three months. Steps counted before that date stay anonymous: we can tell how many different people did something, but not who.
To stop people faking visits, we limit how many new IDs one internet connection can get each day. For that we keep a scrambled form of your IP address, which can't be turned back into it, for two days, separate from the counts.
Page visits aren't counted, signed in or not, if your browser sends Global Privacy Control or Do Not Track, or if you turn counting off here. Turning it off also deletes the ID. The steps above are still counted on our server while you use those features.
Discord bot
The chudlock.com bot answers slash commands in Discord. When you use it, Discord sends us your Discord user ID, the server and channel IDs and what you typed; we use them to answer and don't keep them, except as below.
If you link your account on the bot's page, we keep your Discord user ID and the Steam account ID you signed in with, so /chud knows your games. Linking uses Discord's sign-in with only the "identify" permission, which gives us your user ID; we don't keep your Discord name, email or messages. If you switch Rem's notes on, we keep that setting; quest alerts are described under Quests. For a server's party feed we keep the server ID, the channel to post in, the Steam accounts of members who ran /party join (and which of them asked for every game to be posted) and of pros anyone there follows with /watch, and the newest match already posted. For the Monday recap we also keep the week's tally of members' posted games (each member's Steam name, games, wins and Chud %, and the week's lowest and highest Chud % games), and clear it once the recap is posted; pros' games aren't counted. Unlinking on the bot's page deletes your link and setting and takes you out of every feed; /party leave, /unwatch and /feed off remove the rest. Only the pros listed on chudlock.com with a Twitch channel can be followed, and their games are only posted when they played them live on Twitch: to check, we ask Twitch whether their channel is live (we keep a Twitch access token for that, not their data). Nobody else can be followed without joining a feed themselves, and players who asked to be left off chudlock.com can't be followed at all. Links the bot posts carry a tag naming the bot and command (and for feeds a short code for the server), counted with usage as above.
Twitch bot
Streamers can add the chudlock.com bot to their Twitch chat on the bot's page. Adding it uses Twitch's sign-in with only the "channel:bot" permission, which lets the bot chat there; we keep the channel's Twitch user ID and name, the Steam account the streamer signed in with, their auto-post settings (on or off, and which stats to show), their quests setting and the last game posted. Auto-posts are on when the bot is added. We don't keep their Twitch sign-in.
Twitch sends us the chat messages in those channels so the bot can see its commands. We ignore everything else and keep none of it; for a command we use the message and the chatter's Twitch ID to answer, then drop them. The bot only talks about the streamer's own Steam account, only about games they played while live (we ask Twitch whether the channel is live and when the stream started), and never names anyone else in the game. Removing the bot on its page, or disconnecting it on Twitch, deletes the channel's settings. Links the bot posts carry a tag naming the channel, counted with usage as above.
Cups and leagues
Anyone signed in with Steam can run a cup or a league season on the cups page, and anyone signed in can enter one. Cups keep the organiser's Steam account ID and name; for each person who signs up, their Steam account ID, their Steam name and rank badge as they were when they signed up, the team they are on (and its name, which they chose), whether they are a captain, and when they checked in. If you ask for Discord messages, or you sign up or check in through the Discord bot, we also keep your Discord user ID on that event, so the bot can message you about check-in and your matches; we don't keep your Discord name or anything you write there.
For every game an event plays we keep the result, the match ID, and the numbers read from that public match for each player (hero, kills, deaths, assists, souls, last hits, denies, damage and healing). These feed the event's bracket, tables and stat leaders, which are public on the event's page along with team rosters, player names and results. A lobby's party code is shown only to the two teams in the match and the organiser. Disputes keep the text a captain or the organiser wrote and the organiser's ruling, and are shown to the organiser and the captains involved. When an organiser connects a Discord channel, we keep that channel and server ID so results can be posted there.
Where deadlock-api makes a lobby for a match, we send it the lobby's settings (region, duplicate heroes, random lanes and the number of players needed), not names or accounts. Players who asked to be left off Chudlock can't take part, and are blanked from any event they were in. Leaving an event before it starts removes you from it. To be taken out of a finished event, or to have it deleted, email hello@chudlock.com.
Ads
Chudlock shows ads from Google AdSense to help pay for the site. Third-party vendors, including Google, use cookies to serve ads based on your earlier visits to this site or other websites. Google's use of advertising cookies lets it and its partners serve you ads based on your visits to this site and/or other sites on the internet. Google decides for itself how it uses what its ad cookies and scripts collect, such as your IP address and the page you're on, under its own privacy policy; see also how Google uses information from sites that use its services. None of this is linked to your Steam account by us.
In the UK, the EEA and Switzerland, Google's consent message asks before ad cookies are used, and lists every ad company involved so you can choose which may use your data. If you say no, you still see ads, but they aren't personalised. You can change your answer at any time with the "Privacy and cookie settings" link.
Wherever you are, you can turn off personalised ads from Google in its Ads Settings, and opt out of other ad companies' personalised-ad cookies at aboutads.info.
Some pages, such as the pro setups, have "Find on Amazon" links. They're Amazon affiliate links: if you buy through one, Amazon pays us a small commission, at no extra cost to you. As an Amazon Associate we earn from qualifying purchases. The links are plain links with no Amazon script on our pages; Amazon only sets its cookies once you're on its site. If you first reached Chudlock through one of our paid ads, your browser remembers that in its local storage, never sent to us, and those links aren't shown to you, as Amazon's rules require. Google's ad script isn't loaded for you either. We tell a paid-ad visit from the tag on our ad links, or from the click ID an ad platform adds to the link (Reddit, Google, Microsoft, Meta, TikTok, X, LinkedIn or Pinterest).
Who processes data for us
- Cloudflare hosts the site and stores sign-in records, uploads and highlight videos. Its network handles your IP address to serve and protect the site (for example, rate limits).
- Valve (Steam) handles sign-in.
- Discord carries the bot's commands and replies, and the account link if you make one.
- Twitch carries the Twitch bot's chat in channels that added it, and tells us which listed pros and channels are live.
- deadlock-api serves public match data to your browser, and to our servers for cups: sign-ups' names and ranks, finished matches, and, when it is switched on, the lobbies it hosts.
- Modal runs the servers that make highlight videos. A job receives the game's public replay and your choices, and sends back only the video.
- Google shows the ads and runs their consent message. For ads it decides itself how data is used; see Ads above.
Some of these are outside the UK and EU; they're used under their standard data-protection terms.
How long we keep things
- Sign-in cookies: up to 30 days, or until you sign out.
- The record of your sign-ins: a year after your last sign-in, or until you ask us to delete it.
- Highlight videos: about a week unless saved or being watched. Saved ones: as your plan says. The record of who made a video: up to 400 days.
- Uploaded replay files: until parsed, at most two days. Parsed results and upload records: while the site runs.
- Server logs (which can include your Steam account ID for sign-ins and uploads): a few days.
- Usage counts: three months.
- Cups and leagues: a year after the event ends or is cancelled, when its teams, players, results and stats are deleted. The organiser can delete an event at any time.
- Scrambled IP addresses used to limit new visit IDs: two days.
- Google's ad cookies and your consent choice: set and kept by Google; see how Google uses cookies.
Your rights
Under UK and EU data-protection law you can ask to see, correct or delete data about you, or object to how it's used. Email hello@chudlock.com from anywhere; tell us your Steam profile so we can find it. You can also complain to the UK Information Commissioner's Office (ico.org.uk) or your local authority. For data Google's ad cookies collect, you can also ask Google directly through its privacy policy.
Chudlock isn't meant for children under 13, and Steam accounts require users to be at least 13.
Changes
If this changes, we'll update this page and the date below. Big changes get a note on the site.
Last updated 2 November 2026.

