Privacy Policy
Last updated: 22 October 2026
This policy explains what the G33G33BOT Discord bot and the website g33g33.com collect, why, where it goes, how long we keep it, and what you can do about it. We wrote it in plain English. If anything is unclear, e-mail us at privacy@g33g33.com.
Short version
- We store only what the bot needs: your listening history, likes and dislikes, your privacy and voice choices, and per server the saved playlists, the current or stopped queue and the server settings (volumes, voice opt-in mode, DJ role).
- To protect the bot against abuse, input that looks malicious and the moderation actions taken are kept in a security log for 30 days.
- We never record or keep your voice. Voice control is opt-in by default: only if you opt in on a server is a short clip of your speech sent to a speech-to-text service, and the clip is deleted right after. A server manager can turn the opt-in off for their server;
/voice optoutstill stops it for you on every server, until you opt in again on a specific server. - We do not sell your data, show ads, or use trackers. The website sets no cookies.
- You can see your data with
/profile showand/history, and delete it at any time with/profile clear.
Who we are
G33G33BOT and g33g33.com are run by G33G33.com ("we", "us"), based in the Netherlands. We are the controller of the personal data described here.
Contact: privacy@g33g33.com
What the bot stores
The bot keeps its data in a few files on our own server. Everything is linked to Discord IDs (numbers), not to your name or e-mail address. The bot does not read the content of your chat messages.
| What | Details | How long |
|---|---|---|
| Listening history | For each track you request (with /play, /search, a voice command, by loading a playlist or your likes, or as the starting track of /radio): title, artist, link, video ID, source, length and time. Tracks that autoplay, radio and moods add by themselves, and /foryou recommendations, are not included. Stored per Discord user ID, across all servers. | The last 300 requests are kept; older ones are removed automatically. Until you delete them. |
| Likes and dislikes | The tracks you liked or disliked (same details as above). | Up to 100 of each. Until you remove them or clear your profile. |
| Your choices | Whether your profile is public or private (private by default), the servers on which you opted in to voice control, and whether you opted out of voice control (an opt-out counts on every server). | Until you change them or clear your profile. A voice opt-out is kept even after /profile clear, so the bot keeps ignoring your voice. |
| Saved playlists | Per server: the playlist name, when it was saved, the Discord user ID of the member who saved it, and the tracks (title, link, search text, video ID, length, thumbnail link, uploader, source). | Until the playlist is deleted with /playlist delete. |
| Current queue | Per server: the tracks in the queue (title, link, video ID, and the search text used to find a track, for example for Spotify tracks or voice requests) and who requested each one (Discord user ID), the playback position, the voice and text channel IDs, and player settings (volume, loop, autoplay, effects, whether voice listening is on). Used to continue after a restart or an accidental stop. | Removed when the queue is empty or the bot leaves; a saved queue older than 24 hours is deleted at the next start. |
| Stopped queue | Per server, the same details as the current queue, saved when someone uses /stop or the bot leaves an empty voice channel, so /restore or the ▶ Continue button can bring the music back. | Usable for 24 hours. After that it is ignored, and deleted the next time the bot looks it up or saves a newer one. |
| Server settings | Per server: the music volume, the volume of spoken replies, whether voice control needs an opt-in, and the DJ role. No personal data. | Until the server's data is deleted on request. |
| Security log | When input looks like abuse (for example spam, prompt-injection or shell-injection text, links to private network addresses, @everyone mentions) or is rejected by the input checks (for example a search text that is too long, or a button that no longer exists): the time, the server ID and name, your Discord user ID, the command name and option or the button ID, which rule was triggered and why, and a cleaned-up excerpt of the flagged or rejected input of at most 120 characters. A voice command is only stored here when it was addressed to the bot and flagged; when a transcript is rejected (for example because it is too long), only that fact is stored, never what was said. Also the moderation actions taken (warnings, cooldowns, timeouts, bans, member blocks). Normal commands and failed commands are not stored here. | 30 days, then deleted automatically. Not deleted by /profile clear, because they are needed to prevent abuse. |
| Bans, timeouts and member blocks | The Discord user or server ID that is banned or timed out, until when, the reason and who did it; for a block by a server manager also the server ID and the manager's user ID. | Until the ban or block is lifted or the timeout ends. |
| Recent usage | Per server, the last 50 uses of the bot: who used which command (no search text or other arguments), shown to server managers with /moderation usage. | Only in memory; entries older than 24 hours are dropped, and everything is gone when the bot restarts. |
| Spoken reply cache | Short texts of the bot's spoken replies (up to 60 characters, for example “Skipping song.” or “I play Hello from Adele.”) together with the generated audio, so a repeated reply does not have to be generated again. Not linked to a Discord user ID. | In memory only, never written to disk. Limited to a few MB; the oldest entries are dropped automatically, and everything is gone when the bot restarts. |
| Technical logs | Errors and events. When a voice command is recognised, the log records your Discord user ID, the recognised text and the command. Speech that is not a command is not logged. | Logs are rotated automatically: only the most recent 50 MB of log text is kept, older entries are deleted. |
The bot does not store recordings of your voice, the content of your messages, your IP address, your e-mail address or payment details.
Voice control
Voice control ("hey bot, play …") is off until someone runs /voice join or turns listening on in a voice channel. Even then:
- By default the bot only listens to members who opted in on that server with
/voice optin(running/voice joinyourself also opts you in there). An opt-in on one server does not count on other servers. Members who did not opt in are not captured at all; the bot may post a one-time hint in the text channel. - A server manager can turn the opt-in requirement off for their server (
/settings set voice-optin off). On such a server the bot listens to everyone in its voice channel while listening is on, except members who opted out./voice statusshows which mode a server uses. /voice optoutstops capture of your voice at any time, on every server, whatever the server's setting, and removes your opt-ins. Only an explicit/voice optinon a specific server makes that one server hear you again; all other servers keep ignoring you.- When an opted-in member speaks, the bot cuts out a short clip (only speech, at least a fraction of a second, filtered for noise), converts it to a 16 kHz mono audio file and sends it to the speech-to-text service. The file is deleted from our server right after the text comes back.
- The wake word ("hey bot") is recognised after transcription. That means anything an opted-in member says in that voice channel while listening is on can be sent for transcription, not only commands. Only text that contains the wake word (or a common speech-to-text spelling of it at the start, such as "hey bought") and a command is acted on and logged. If the bot hears "hey bot" at the start of a sentence but not a command, it only answers "Sorry, I didn't catch that"; what you said is not posted or logged.
Anyone who may control playback can turn listening off for everyone in that channel with /voice listen enabled:false. The operator can also configure the bot to run speech recognition and spoken replies locally, in which case no voice data or reply text leaves our server.
What we send to other services
To do what you ask, the bot has to talk to other services. They receive only what is listed here. We never send your Discord user ID, name or e-mail address to them, and they see our server's IP address, not yours.
| Service | What it receives | When | Why |
|---|---|---|---|
| Speech-to-text service: Groq (USA), or OpenAI (USA), depending on the operator's configuration | Short audio clips of opted-in members' speech | Only while voice listening is on | To turn your voice command into text |
| Text-to-speech: the same Groq or OpenAI service and, as a fallback, Microsoft Edge text-to-speech (Microsoft) | The text of the bot's spoken reply, for example “Playing No Woman No Cry by Bob Marley” or “Skipping song.” | After a voice command, when spoken replies are on | To answer you out loud |
| YouTube (Google) | Search terms, YouTube links and video IDs, and for /foryou the names of your most-played artists | When you play or search for music, for autoplay, radio and moods, and for /foryou | To find and stream the music and to find similar tracks and recommendations |
| Spotify | Spotify links you share | When you play a Spotify link | To read the track list; the songs themselves are then searched on YouTube |
| SoundCloud | SoundCloud links you share | When you play a SoundCloud link | To stream that track or playlist |
| LRCLib and lyrics.ovh | Artist and song title | When you use /lyrics | To find the lyrics |
| SponsorBlock | The first 4 characters of a hash of the YouTube video ID (so SponsorBlock cannot tell which video it is) | When a YouTube track starts | To skip sponsor segments, intros and outros |
| Discord | Everything the bot shows or says in your server | Always | The bot runs on Discord; Discord's own privacy policy applies |
Each service handles the data under its own terms and privacy policy. Some of them are located outside the European Economic Area, mainly in the United States. Where the law requires it, these transfers rely on the EU-US Data Privacy Framework or on the European Commission's standard contractual clauses.
The website
g33g33.com is a static website. It uses no cookies, no analytics and no trackers, and loads nothing from other websites. It is hosted by Cloudflare (Cloudflare Pages). Like any web host, Cloudflare processes your IP address and technical request data to deliver the site and protect it against attacks; see Cloudflare's privacy policy. The share buttons on the home page are plain links: nothing is sent to WhatsApp, Telegram, X, Reddit or Facebook unless you click one, which opens that site in a new tab (its own privacy policy applies there). “Share” and “Copy link” use your device's share menu and clipboard; we do not see what you share. If you e-mail us, we use your e-mail only to answer you and delete it when it is no longer needed.
Why we may use your data (legal bases)
- To provide the bot (history, likes, playlists, queues, music search, lyrics, spoken replies): this is needed to give you the service you ask for (GDPR article 6(1)(b)).
- Voice control: based on your consent, given with
/voice optinor/voice joinon that server (article 6(1)(a)). You can withdraw it at any time with/voice optout.
- Logs and security: our legitimate interest in keeping the bot running, fixing bugs and preventing abuse (article 6(1)(f)). This includes the security log, bans, timeouts and member blocks.
We do not use your voice to identify you, and we do not make automated decisions about you that have legal or similarly significant effects. To protect the service, the bot can automatically pause your access for a short time (by default from 30 seconds up to one hour) when it detects spam or malicious input; the bot owner is told about longer pauses and reviews them. If you think this happened by mistake, e-mail us.
Your rights
Under the GDPR you have the right to access, correct, delete and receive a copy of your data, to object to its use, to restrict it, and to withdraw your consent. In the bot:
- See your data:
/profile show,/history,/like list,/dislike list. - Delete your data:
/profile clear(withconfirm:true) deletes your history, likes, dislikes and privacy setting straight away. Only a voice opt-out is kept, so the bot does not start listening to you again. Security-log entries are not deleted by/profile clear: they are kept for 30 days to prevent abuse, then deleted automatically. - Keep your profile private: profiles are private by default;
/profile privacylets you choose. - Stop voice capture:
/voice optout.
For anything else — a copy of your data, deleting your name from saved playlists or queues, or deleting the data of a whole server after you removed the bot — e-mail privacy@g33g33.com. We answer within one month. You also have the right to complain to a data protection authority; in the Netherlands that is the Autoriteit Persoonsgegevens (https://autoriteitpersoonsgegevens.nl).
Children
You must meet Discord's minimum age to use the bot. If you are under 16, ask a parent or guardian before you turn on voice control.
Security
The data is stored on a server we manage, is accessible only to the operator, and is not shared with anyone except as described above. No method of storage or transfer is completely secure, but we take reasonable measures to protect it.
Planned changes
Things we are working on that will change this policy before they go live:
- Accepting the Terms: the bot will ask you to accept the Terms of Service before first use. We will then store which version you accepted, when, and your Discord user ID.
- Premium: paid features will involve a payment provider (for example Discord). We will describe what is shared before you can buy anything.
Changes to this policy
When we change this policy we update the date at the top. For important changes we will also announce it in the bot or on this website before the change takes effect.
Contact
Questions or requests about privacy: privacy@g33g33.com