Privacy Policy
Last updated: November 7, 2026
This policy explains what information debug ("we", "us") collects through the debug Discord server and bot, the debug loader and the debug website (debug.luxe), why, and what you can do about it. We collect as little as we can to run debug, and we never sell your information.
1. What we collect
Your Discord account. When you sign in to the loader with Discord, we receive your Discord user ID, username and avatar (Discord's "identify" permission only: not your email, servers or messages). In our server, the bot sees what any Discord bot in a server sees, such as your user ID, names, roles and when you joined.
Your access. The games you have access to and until when, the keys you redeemed and when, and who gave or removed access. This is how the loader knows what to unlock.
Access requests. When you press Request access, we keep what you write in the form (who sent you and what you want to play), when you asked, whether staff approved or denied it and why, and the key made for you. Staff see it next to whose invite you joined with and when your Discord account was made. Once a month the bot asks members with access whether they still use debug: we keep your answer (or that you didn't answer) and, if you send it, your feedback, which only staff read.
Your downloads. When you download a mod, we record that your account downloaded it, and your copy is stamped with your Discord ID and a personal licence. This lets us trace a leaked copy back to the account it came from. We also count downloads per account to stop abuse.
Owners' Steam accounts (crowns). If you're one of debug's owners, your loader sends the Steam account signed in on your PC, so other players' trainers can show a crown over you in game. We keep it only for owners; for everyone else the loader's message is thrown away. Other loaders only ever receive these accounts as salted, deliberately slow hashes, never the plain IDs.
Loader sign-in. A sign-in token on your PC so you stay signed in. We keep only a scrambled (hashed) copy of it on our server, and it expires after 30 days.
debugvox (called ClipThat before 2.0). debugvox signs in with Discord the same way the loader does, and keeps its sign-in token on your PC, encrypted for your Windows account. We keep whether you've unlocked it and how (invites, a key or staff). To count your invites we use the invite records described under Moderation: who joined with your link, whether they verified and whether they're still here. debugvox records and plays audio only on your PC; none of it is sent to us. If you turn on its voice commands, the microphone you pick is listened to by Windows' own speech recognition on your PC, only to spot the phrases you set; the audio isn't kept or sent anywhere. If you turn on its voice changer, your microphone is changed on your PC as you talk and played into the device you pick (it reaches other people only through your own voice chat); it isn't recorded, kept or sent to us. Its mic tools (noise reduction, the noise gate, EQ and compressor) also run on your PC only: the noise reduction is an AI model on your PC (Studio, the default, downloads its model, about 16 MB, once from debug's own file server, stage.debug.luxe, which sees your IP address like any download), and your voice never leaves your PC for it. With the Sonar option, while the voice changer is on debugvox points your Sonar microphone at a silent device (or mutes it) and gives it back after, through Sonar's controls on your PC; to find a silent device it listens to your virtual audio devices for a moment, on your PC only, and keeps nothing. If you use Browse sounds, what you type is sent through our server to Freesound.org to search its free sound library (we don't keep your searches), and the sounds you preview or add are downloaded from Freesound. AI voices also run on your PC only: the first time you turn them on, debugvox downloads the AI model (about 58 MB) from Hugging Face and from debug's own file server (stage.debug.luxe), which see your IP address like any download, and after that your voice is changed on your PC without being sent anywhere. Text to speech uses Windows' own voices on your PC. Clip videos are made on your PC and saved in debugvox's clips folder; they go only where you paste them. If you turn on the phone soundboard, only a phone that has the link with its secret code from the QR code can use it; the phone can press debugvox's buttons and send text to be spoken. Since 5.6.2 the page goes through our server by default, so it works on any network: what the page shows (your clip and sound names, voices and settings) and the buttons you press pass through our server and are held in memory only while the phone soundboard is on, never saved; a clip you watch or save on your phone is sent once and deleted from our server after 10 minutes. With "This Wi-Fi only" picked, debugvox answers on your own network and nothing passes through us. If you share a voice to the most used voices board, we keep and show its name, its settings (as a voice code) and your Discord display name, in the debug Discord and in debugvox's Popular voices window. When you paste a voice code into debugvox while signed in, the code is sent to us: if it's a shared voice, we note that you've used it, once, to rank the board (your ID isn't shown to anyone); any other code is thrown away straight away.
debugvox 4.0. These run on your PC only and nothing from them is sent to us: auto-clip listening for laughs (a small AI model inside debugvox hears what you hear, only to spot laughing); transcripts, if you turn them on (a speech model writes down what's said in your clips so you can search them; the model is downloaded once from Hugging Face); screen clips, if you turn them on (the last seconds of your screen are kept in debugvox's own folder and overwritten as you go; since 4.3, if you choose, your mic is kept the same way so a clip can carry what you said); the Stream Deck plugin and OBS overlay, which talk to debugvox on your PC and nothing else; and Test my setup, which plays a quiet sound into your mic and reads which apps on your PC are recording from it. With Twitch on, debugvox reads your channel's public chat the way any visitor can, without signing in, and nothing from it is sent to us. These go through our server, only when you use them: Share a link uploads that clip's video to us and anyone with the link can watch it; we keep it, with its name and your Discord display name, for 30 days or until you or staff take it down. Play through the bot sends that clip's sound to us so the debug bot can play it into your voice channel; it's deleted from our server as soon as it has played. Send to someone passes a clip or sound to a person in your voice channel; it waits on our server for at most 15 minutes and is deleted once they have it. So people in your voice channel can send to you, debugvox lets us know while it's open (you can turn that off in Settings). Staff see these clips: since 28 October 2026, every clip that goes through our server like this (a shared link, a clip played through the bot, a clip sent to someone) is also posted with your Discord name in a private channel only staff can read, so they can take a link down or stop someone sharing. Those posts are kept like other moderation logs. Clips that never leave your PC (the replay, your favorites, the session timeline, screen clips you don't share) are never seen by us. Crash reports, only if you agree (ask, always or never, in Settings): the error, your debugvox and Windows versions and your Discord ID, with file paths cut down to file names; staff can read them. Updates download the new debugvox from our server, which sees your IP address like any download.
debugvox 4.2. The session timeline, if you turn it on, keeps what debugvox hears (the call and your game) for the time you pick (an hour unless you change it) in debugvox's own folder on your PC, with laughs, loud moments, your clips and game moments marked on it; older parts are deleted as they get too old, and Settings can delete all of it. Nothing of it is sent to us. Captions are made on your PC from the transcript. Game triggers, if you turn them on, read what your game reports on your PC only: Counter-Strike 2 and Dota 2 send it to debugvox through a file debugvox writes in the game's folder when you press Set up, and League of Legends answers on your PC while you play; nothing is sent to us. The voice keyboard, live knobs and MIDI controllers work on your PC only. Hear it on the debug Discord's voice board: our bot plays a shared voice on a sample voice (made by debugvox, not anyone's real voice) and keeps that sound file for the next person who asks.
debugvox 5.0 (the Studio). Your Studio projects, and copies of the sounds and music you put in them, are kept in debugvox's own folder on your PC; the videos you export go in your clips folder. Nothing of them is sent to us unless you press Share a link (see above).
debugvox 5.2. Separate sound tracks, on unless you turn them off (Settings, Audio): Windows records each app you hear (your game, Discord, music) on its own, and debugvox keeps the last seconds of each in memory on your PC, like the replay. A clip keeps those tracks so you can turn each app up or down, and favorites keep them in debugvox's own folder. Nothing of it is sent to us. Screen clips can record any one of your screens, or all of them. Search runs on your PC.
debugvox 5.3. Backups to your debug account, on unless you turn them off (Settings, Backup): a couple of minutes after you change something, debugvox sends us your settings (without your audio devices, keys and the other things that belong to that PC), your voices, your hotkeys and your sounds (each sound file once), with your PC's name, so you can bring them to another PC. We keep one backup for each PC you use (up to 3, and up to 100 MB of sounds), for your account alone; staff have no view of them. Delete them any time in debugvox (Settings, Backup, Your backups), and turning the switch off stops new ones. Nothing you recorded goes in them: no clips and no videos. Backup files are made on your PC and stay wherever you save them. The session's video, if you turn it on (Clips page, Session): your screen, your mic (if your screen clips keep it) and your game's own sound are kept beside the session timeline in debugvox's own folder on your PC, for as long as the session timeline keeps its sound (8 GB at most), and deleted as they get old. Highlights are made from it on your PC. To offer highlights when a game closes, debugvox notes which app is in front of your screen; that stays on your PC.
debugvox 5.5. Your webcam in screen clips, off until you turn it on (Settings, Behaviour): while your screen is being recorded for clips, debugvox keeps the last seconds of your camera in its own folder on your PC (so your camera's light stays on), deletes them as they get old, and puts your camera in a corner of the screen clips you save. Nothing of it is sent to us unless you share a clip. Rhythia: with React to my games on, debugvox reads Rhythia's own replay and score files on your PC while Rhythia is open, to see when you pass a map, get a full combo or beat your best score. While Rhythia is open and its runs are clipped, debugvox records your screen (and your webcam, if it's on) for those clips even when screen clips are off, and stops when you close Rhythia. All of that stays on your PC.
debugvox 5.6.2. Record games, on unless you turn it off (Settings, Behaviour): while a game is open, debugvox keeps the last seconds of that game's window in its own folder on your PC, overwritten as you go, so a clip made while you play has its video; nothing is recorded when no game is running, and none of it is sent to us unless you share a clip. "Clip that", on unless you turn it off: Windows' own speech recognition listens, on your PC, to what debugvox hears (your game and voice chat) only to spot the words "clip that"; the audio isn't kept or sent anywhere. Bringing your Medal clips over reads the clip list and clip folder Medal keeps on your PC; debugvox points at those files where they are and sends nothing to us or to Medal. Moments from debug's games: debug's mods can write a line to a file on your PC when something happens in your game (a win, a boss, a death), and debugvox reads it there. Post to #clips shares the clip as a link (as above) and our bot posts it in the debug Discord's #clips channel with your Discord name and the game it was clipped in, where everyone in the server can see it; taking the link down deletes the post too.
debuglens. To ask for it, you press Request debuglens in the debug Discord and say why you want it (and, if you like, your VR setup): that goes to staff and the owners as a card in a private channel, and we keep the request, who decided and when, and whether you have debuglens. The app runs on your PC. To check that an owner let you in, it signs in with Discord like the loader and asks our server whether your account may use it; nothing else about you or your PC is sent to us. Everything it shows is read on your PC and stays there: your FPS (Windows' own graphics events, read by Intel's PresentMon), how busy and how warm your CPU and graphics card are, your RAM, your ping (it pings 1.1.1.1, or the address of the server your game is connected to), what's playing (Windows' media controls) and debugvox. In VR it shows your screens and windows in the headset, and moves your mouse and types for you while you point at them. Notifications in VR are read from Windows' own list of notifications on your PC (and from apps that send to XSOverlay), shown in your headset and then forgotten: they are never stored or sent anywhere. You can turn them off, or leave out apps, in its VR settings. The watch's other tools also work on your PC only, and nothing from them is sent to us: Volume reads and changes each app's volume in Windows' mixer; Discord presses the mute, deafen and leave buttons in your own Discord app through Windows' accessibility interface and reads whether they're on; SteamVR changes SteamVR's own settings on your PC; screenshots are saved in your Pictures folder (Pictures\debuglens); Apps keeps the apps you picked in debuglens's settings on your PC and starts them the way the Start menu does. Updates download the new debuglens from our server, which sees your IP address like any download.
Your Discord profile card. While you use the loader, debugvox, debuglens or the debug assistant, they can show what you're doing on your Discord profile, the way games and apps like Medal do (for example "R.E.P.O. with debug" or "Clipping Rhythia"). Each app writes a small note on your PC saying which app it is, its version, what it's doing and which game is open; one of them sends those notes to our server, which answers with the words and picture to show, and that app gives them to the Discord app on your PC. Our server doesn't keep the notes or who sent them, and the game's picture comes from Discord's own list of games. It's on unless you turn off the Discord profile switch in any of the apps' settings (one switch turns it off for all of them).
Tickets and community. What you write in tickets (kept as a transcript when the ticket closes), bug reports and the files you attach to them, suggestions, game requests and votes, vouches, giveaway entries and polls.
Bug reports from the loader. If you press Report a bug in the loader, it sends what you write, the log files you choose to send, and technical details about the game's install: which versions are installed, whether the game and Steam are running, whether the mod's files are in place, and the trainer's own health report. You see the list of files before anything is sent.
Moderation. Like most Discord servers, our bot keeps a moderation log: warnings, timeouts, kicks, bans, which invite you joined with, and messages that are edited or deleted in our server. This keeps the community safe and lets staff handle reports.
Voice. The bot can play music in voice channels. A few staff members can control it with spoken commands; for those people only, their speech is turned into text on our own computer (nothing is sent to an outside service), only to run the command, and the audio isn't kept. Nobody else's voice is processed.
The website. debug.luxe doesn't use ads, analytics or tracking cookies. It remembers a couple of display settings in your own browser (local storage) and asks our server for public information such as the loader's latest version. Like any website, our host (Cloudflare) handles the network requests, including your IP address, to deliver the site and protect it.
Network information. Our servers see the IP address a request comes from and use it briefly to limit abuse (for example, too many tries at a key). We don't build a profile from it.
2. Payments
debug has been free since 27 October 2026 and doesn't take payments. Before that, payments were arranged with staff in a ticket; we never received or stored card numbers, and we keep only what we needed to give access (for example, which game was bought and that it was paid).
3. Why we use it
- to give you access and keep the loader and mods working;
- to protect debug's work from leaking and reselling, and to stop fraud and abuse;
- to run support, bug reports, the community and its safety tools;
- to follow the law and handle disputes.
4. Who we share it with
Only with services we need to run debug: Discord (where the community and sign-in live) and Cloudflare (the website and the connection to our server). We may share information if the law requires it, or to protect debug and our users. We never sell it or use it for advertising.
5. How long we keep it
We keep your account and access records while you use debug, and records needed to stop abuse (keys, leak traces, bans, chargebacks) for as long as they're needed for that. Ticket transcripts and moderation logs are kept so staff can look back at past reports. Server logs and rate-limit data are short lived.
6. Your choices
- Sign out of the loader any time; that ends your sign-in on our server.
- Turn off the Discord profile card in any debug app's settings; it stops showing for all of them.
- Ask us, through a Support ticket, what we hold about you, to correct it, or to delete it. We'll delete what we can; some records (for example, of a ban, a chargeback or a leaked copy) may have to be kept to protect debug.
- Depending on where you live (for example, the EU, UK or California), you may have further rights under your local privacy law, which we'll respect.
7. Children
debug follows Discord's minimum age, and isn't meant for children under 13. If you think a child under 13 has given us information, open a ticket and we'll remove it.
8. Security
We keep data on our own server, store sign-in tokens only as hashes, and limit who on staff can see what. No system is perfectly secure, but we take reasonable care.
9. Changes
If we change this policy, we'll update the date at the top and post it in our Discord.
10. Contact
Privacy questions or requests: open a Support ticket in our Discord (discord.gg/yHn7WbmEWD).