Privacy Policy
Introduction
Who we are
WHITE SPACE is a Discord bot, verification system, browser extension, kit storefront, and suite of web and desktop tools maintained by an individual developer (@cl5rr). This policy covers data collected by all services operating under wspacebot.com.
Scope
This policy applies to: the WHITE SPACE Discord bot, the web dashboard, the White Space Guardian browser extension, WS Accounts, and the BEATS API. By using any of these, you consent to the data practices described here.
Principle
The minimum data necessary to provide each feature is collected. Data is not sold to third parties. Data is not used for advertising.
WHITE SPACE Bot
Discord Interactions
When you interact with the bot via Discord, the following metadata is processed:
- Snowflakes: User IDs, Server IDs, Channel IDs, and Role IDs required for command execution.
- Message metadata: Timestamps processed to calculate cooldowns. Message content is stored only in these cases: Global Chat messages (deleted after 7 days), vote submissions (kept while the bot is in that server, oldest removed first), ticket channels (see section 7), message text a moderator attaches to a moderation case as evidence (see Moderation Cases), and, only if a server switches it on, short-lived encrypted copies for logging deleted and edited messages (see Server Logging).
- Transient message cache: To power features like spam detection, reactions on recent messages, and auto-moderation, the bot holds recently seen messages in volatile memory for up to approximately 15 minutes (at most 50 per channel), after which they are automatically evicted. This cache is never written to the database and is cleared entirely on restart.
- Audit log access: The Anti-Nuke system reads Discord audit logs in real time to identify executors of destructive actions. This data is used only for in-memory threat detection and is not stored beyond what is logged to your configured log channel.
Automod
If a server turns on automod, each message is checked in memory against the rules the server chose (spam, links, invites, capital letters). Blocked words and mention spam are handled by Discord's own AutoMod, with rules the bot creates in that server. Nothing from these checks is stored apart from the moderation case and log entry an action creates.
Global Chat
Before your first Global Chat message, a button-based challenge is presented. Your pass/fail result is processed in memory only and is not stored. Passing grants a 20-minute session token stored in memory, cleared on bot restart, and never persisted to the database.
Verification System
When a server uses verification, you open a link from that server and sign in with Discord. Only your Discord ID, username and account creation date are read. Your connected accounts and your list of servers are not. The server chooses which of these checks apply:
- Account and name: how old your account is, whether Discord has quarantined your username or noted that you left and rejoined, and whether your name contains a known phishing site, looks like a common scam pattern, or copies the server's name or a staff member's name.
- Safety lists: whether you are on WS Ban, on the server's own block list, banned in servers it shares bans with, or caught by a honeypot in the last 72 hours.
- Your connection: whether your IP address is a Tor exit or belongs to a datacenter or VPN range. This is checked against public lists the bot downloads, so your IP is not sent anywhere for it. Only if the server turns on the extra lookup is your IP also sent to proxycheck.io.
- Human check: Cloudflare Turnstile, which sees your IP address and browser signals to tell people from bots.
- Repeat accounts: your device and network are turned into codes using a secret that is different for every server, so a code means nothing outside that server and cannot be turned back into your IP. They are compared with the codes of members banned from that server in the last 30 days and of its other verified members. The codes are deleted after 30 days.
- Raids: if a raid is going on, verifying waits until it ends.
The result, with a plain reason for every check that failed or was flagged, is kept until 30 days after you leave the server, and staff see it in the server's verification log channel. If you are refused, you are told why.
Older verification system
Servers that have not switched yet still use the older system, which is being retired. It processes the following to calculate a Trust Score (a reputation score used to decide whether to grant you access to a server):
- Discord account signals: Your account age (derived from your User ID), Nitro/premium status, and public account badges/flags (such as Staff, Partner, HypeSquad, Early Supporter, and Active Developer). These contribute to your score.
- Third-party connections: Public metadata from accounts you explicitly authorize via Discord OAuth. This may include Steam, GitHub, Spotify, Twitch, YouTube, Reddit, Twitter/X, Battle.net, PlayStation, Xbox, Roblox, Epic Games, Facebook, Instagram, TikTok, Crunchyroll, and verified domains. Only public data such as the platform type, account name, and verification status is read. Credentials and private content are never accessed.
- Mutual servers: Your list of Discord servers is read once during verification to count how many servers you share with the bot (capped, and excluding servers you own or administrate). The count contributes to your score; the full server list is not stored.
- Browser fingerprint: A SHA-256 hash of device characteristics (User Agent, language headers, IP address, and client hints) stored as
ws_device_idin your cookies. Used to detect when one device is linked to multiple accounts (alt detection). A match with another member of the same server is flagged for that server's staff to review; it does not block you on its own. - IP address: Your IP is processed during verification. A keyed hash of it (made with a secret key that changes every 30 days, so it cannot be turned back into your IP) may be stored to detect shared-IP situations (potential alternate accounts). Hashed IP and device records are deleted 60 days after you were last seen. Your raw IP is also sent to our VPN/proxy detection subprocessor (proxycheck.io) to determine whether you are connecting through a VPN, proxy, or Tor. Verification through a detected VPN/proxy is blocked.
- Verification result: Your Trust Score, tier, the score breakdown, the connected accounts found, your pass/fail status, and (unless you have opted out) your hashed IP and device fingerprint are stored persistently. The result and breakdown are also posted to the server's configured verification log channel, where server staff can see it and may manually approve you.
Verification Privacy Controls
You can switch off recording of your network and your device for verification at wspacebot.com/privacy-center. With the newer system that turns off the repeat-account checks for you, and the server sees that you declined them. With the older system it turns off the matching alt-detection check, and the rest of the Trust Score is still calculated. Manual approval by a server administrator grants a temporary 5-minute verification window held in memory only.
Honeypot
If a server turns on the honeypot, posting in its marked trap channel, or posting the same message in three or more channels within 30 seconds, gets the sender removed from that server. A record of the catch (server ID, user ID, the action taken and what triggered it) is kept for 90 days, and the removal is also recorded as a moderation case. Message content is not stored: recent messages are compared in memory as one-way hashes and forgotten within a minute. If the server chose to share catches, your user ID is also kept on a network list for 72 hours, which other servers' verification may use to flag you for review.
Raid Shield
If a server turns on the raid shield and many people join within seconds, or Discord flags a raid, the user IDs of everyone who joins during the raid are kept so staff can hold, release, kick or ban them together. A record of the raid (those IDs, when it started and ended, and how many were removed) is deleted 30 days after the raid ends.
Server Logging
A server can choose to log events such as members joining and leaving, bans and timeouts, role and channel changes, voice activity, invites and threads. Entries are posted in that server's own log channels, which the server controls. A record of each event without any message text (the event type, the user IDs involved and when it happened) is kept for 30 days for the server's dashboard timeline. To see what a server has switched on, use
/privacyin that server.Only if a server switches on logging of deleted and edited messages, the text and attachment links of each message are kept encrypted (AES-256-GCM, with a key unique to that server) for 24 hours by default and 7 days at most. When a message is deleted or edited, its copy is posted to the server's log channel and erased from our storage; otherwise it is erased when the time runs out. Ticket channels and channels the server excludes are never copied, and no website page or API ever shows the stored text.
To help server owners see which channels are used, the bot counts messages per channel per day. Who sent them is never stored: active members are counted in memory using codes that change every time the bot restarts.
Moderation Cases
When a server's moderators, or the bot's automatic systems such as the honeypot or the warning ladder, warn, time out, kick or ban someone through WHITE SPACE, a numbered case is stored: the server ID, the member's and the moderator's user IDs, the action, the reason, how long it lasts and when it happened. The member may get a DM about it before it takes effect. If a moderator replies to or right-clicks a message when acting, that message's text and attachment links are saved with the case as evidence. Evidence is removed after the number of days the server chooses, 90 at most, leaving only the case. Cases are kept while the bot stays in the server and are deleted with the rest of the server's data.
Browser Extension
The White Space Guardian extension processes page content locally. It transmits only specific identifiers (User IDs or URLs) to the API to check against safety lists. No browsing history or passwords are transmitted.
WS Accounts
When you create a WS Account at wspacebot.com/login, the following is stored persistently:
- Credentials: Username (permanent) and a password stored as a scrypt-derived hash with a random salt. Passwords are never stored in plain text and are not readable by the Developer.
- Identity: Display name (up to 32 characters) and bio (up to 280 characters).
- User content: Social links, project entries, tile configurations, journal entries (public or private), and mood logs.
- Appearance settings: Avatar colors, eye style, wallpaper, custom background URL, custom cursor URL, and animations.
- Linked Discord ID: Optionally stored if you connect your Discord account. Not shared with third parties. If you add a Discord tile to your profile, visitors see your Discord avatar, name and bio from the WHITE SPACE server in that tile. Your Discord ID itself is never shown.
- Session data: A session cookie persisting for 7 days (30 days if "stay logged in" is selected). Cleared on logout.
- Security metadata: Last login timestamp, IP address, and a failed login counter used to enforce temporary lockouts.
BEATS
When you save a beat map via the BEATS editor:
- A unique map name, title, encoded beat data, your Discord User ID as creator, and timestamps are stored persistently.
- Saved beat maps are publicly accessible via the REST API at their named endpoint.
- Local drafts: Unsaved work is stored in your browser's localStorage under the key
beats_draft. This never leaves your device.
Game Account Linking
Some Roblox games made by the Developer let you link your Roblox account to your Discord account to receive rewards for boosting the WHITE SPACE server. When you link:
- Stored: Your Roblox user ID, your Discord user ID, and whether you currently boost the server. Kept until the link is removed.
- Confirmation code: A one-time code is sent to you by Discord DM and expires after 5 minutes. It is held in memory only.
- Checks: When you join a linked game, the bot checks whether you still have the booster role. Nothing else about your Discord account is read.
To remove a link, delete it at wspacebot.com/privacy-center.
Ticket System
When you open or participate in a ticket, the following is stored persistently:
- Ticket metadata: Ticket ID, Guild ID, Channel ID, creation timestamp, and status.
- Creator information: User ID, display name, and subject line.
- Message content: Full text of each message, including author User ID, display name, avatar URL, role color, bot status, and timestamp.
- Attachments: URLs and metadata for files or embeds sent in the ticket.
- Participants: A list of User IDs of all participants.
- Closure information: User ID, display name, and timestamp of the closing action.
Transcripts are accessible at wspacebot.com/tickets to the ticket creator and server staff. Staff may delete transcripts at any time, permanently removing all associated message data.
Storage and Retention
Volatile memory
Highly sensitive data is processed in-memory and never written to the database: Anti-Nuke tracking windows, quarantine states, Global Chat verification tokens, flood tracking states, and the short-lived message cache (recent messages held up to ~15 minutes for moderation features). All of this resets on bot restart.
Persistent database
Data stored in MongoDB is limited to what is necessary for long-term functionality: economy and leveling data, server configurations, verification records, the 30-day log timeline, encrypted message copies where a server enabled them, daily message counts per channel, WS Ban entries, Anti-Nuke audit logs, moderation cases, WS Account data, game account links, mood logs, ticket records, and BEATS beat maps.
Retention periods
Servers can shorten some of these, never lengthen them. A job runs every day, deletes what has run out and records how many rows it deleted, and server administrators can see its last run on the dashboard.
Data Kept for Per-server device and network codes 30 days Verification result Until 30 days after you leave the server Verification attempts (older system) 30 days Encrypted copies of messages, only where a server turned them on 24 hours by default, 7 days at most Event timeline for server logs 30 days Moderation cases While the bot is in the server; message evidence 90 days at most Honeypot network list 72 hours Honeypot catches 90 days Raid records 30 days after the raid ends Anti-Nuke log 90 days Daily message counts per channel 90 days Global Chat messages 7 days Closed tickets and transcripts 12 months, or sooner if staff or the ticket creator delete them Status page samples 91 days Dashboard session 7 days, or 30 if you choose to stay signed in Server configuration, levels, economy and everything else about a server While the bot is in the server Everything about a server after the bot is removed 30 days, unless the bot is added back first Game account link Until you remove it WS Account Until you delete it Removing the bot
When WHITE SPACE is removed from a server, everything about that server (configuration, flows, cases, verification records, economy, leveling, tickets, backups and logs) is deleted 30 days later, unless the bot is added back before then. The server owner can also remove the bot from the dashboard and have it all deleted straight away.
Your right to see and delete your data
At wspacebot.com/privacy-center you can see what is kept about you in each server, download all of it as a file, and delete your levels, economy, verification records, Global Chat messages, vote submissions and game account link, in one server or everywhere. Moderation cases, honeypot catches, tickets and WS Ban entries are kept for the servers' safety for the times above, and the page says so next to each. In a server,
/privacyshows what that server has switched on. You may delete your WS Account and all associated data at any time from the settings panel on your profile page.Third-Party Subprocessors
- Discord Inc.: The primary platform for the bot and OAuth.
- MongoDB Atlas: Cloud database provider.
- Groq Inc.: AI inference provider for the AI chat module. Only the prompt you type and the server's system prompt are sent, to generate the reply. WHITE SPACE keeps a count of your requests for the rate limit, not the prompts or answers.
- proxycheck.io: VPN, proxy, and Tor detection during verification, only in servers that turn on the extra lookup (and for the older verification system). Your IP address is sent to this provider to assess connection risk. No other personal data is shared.
- Cloudflare: Hosts the bot and the website, so every request to wspacebot.com and every Discord event the bot handles passes through it. It also runs Turnstile, the human check on the verification page, which processes your IP address and browser signals while you verify.
Security
The Service employs industry-standard security measures including encryption in transit (TLS/SSL), strict access control, input sanitization, keyed hashing of IP addresses and device fingerprints, and scrypt-based password hashing with per-account random salts. Passwords are never stored in recoverable form.
Contact
To see, download or delete your data, use wspacebot.com/privacy-center. For anything it does not cover, or questions about this policy:
- Discord: @cl5rr
- Support server: WHITE SPACE Community