Privacy Policy
Updated November 1, 2026.
Looking for setup instructions? Read the Documentation.
Giveaways
When enabled by a server manager, Relayed stores giveaway settings, prize text, host and entrant Discord user IDs, channel/message IDs, entry timestamps, deadlines, saved message designs, winner IDs and delivery status. Entrant IDs support unique entries and winner selection; public giveaway messages show totals and selected winner mentions. Leaving a giveaway removes that entry record; settings, ended giveaway records and associated entries otherwise remain until removed through applicable server-data/deletion processes. This feature does not collect payments or deliver prizes.
ER:LC time, weather and username automation
When a server manager enables these optional tools, Relayed stores the selected time zone, public location label and coordinates, automation settings, latest execution/error status and exact-ID username protection outcomes. Weather coordinates are sent server-side to MET Norway to retrieve forecasts; Discord credentials and ER:LC API keys are not sent to the weather provider. Select a public city location rather than a private address. Enabled username protection processes online Roblox usernames and numeric IDs to ban matching all/other-prefixed accounts, including legitimate usernames. Unconfirmed attempts are retained for review. Automation events and shift pause intervals follow the record retention and deletion practices below.
Pending ER:LC command notifications
When command logging is enabled, Relayed may retain pending ER:LC command events, including the executor reported by ER:LC, command text and execution timestamp, until Discord delivery succeeds. This allows notifications to recover after delivery failures and process restarts. Delivery state and event hashes prevent ordinary duplicate delivery. These records follow the retention and deletion practices below.
Imported settings and records
Server managers may import supported settings, historical moderation records and completed shifts, including Discord and Roblox identifiers, usernames, reasons and timestamps. Relayed stores normalized records and one latest recovery snapshot of the selected data and prior server settings. Raw uploaded files are not retained by the import feature. Import activity is audited. These records and snapshots follow the retention and deletion practices below.
Scam Catcher warning channel
When the server owner enables Scam Catcher, Relayed processes messages in the configured warning channel to trigger a kick, ban or soft-ban. Event records retain message ID, Discord user ID, configured action, timestamp, outcome and error details without separately storing message text in those records. Incidents are sent to the server's configured private Anti-Nuke log channel. A DM is attempted before removal. Soft-ban requests deletion of the preceding 24 hours of the user's messages in that server and then removes the ban; a failed unban requires staff review. Any non-exempt message can trigger the trap, including a legitimate mistake. These records follow the retention/deletion practices below.
Department workspaces
Department workspaces check Discord membership roles to grant access and store department configurations, permission roles, quota settings, shift timestamps and corrections, arrest and scene report text, evidence URLs, leave dates and reasons, reviewer decisions, and audit entries associated with Discord user and server IDs. Department members and server managers can view department reports, evidence links, duty activity, and a roster showing Discord names, IDs, department roles and duty status. Leave reasons are restricted to the requester and authorized reviewers. Evidence files remain with their external hosts; Relayed stores the supplied URLs. Do not submit unnecessary sensitive personal information. Department records follow the retention and deletion practices below. Department report answers, review decisions and reasons, and up to ten prior correction revisions may be stored. Rank-based goals are computed using configured Discord roles. Department record profiles are restricted to the member or authorized reviewers/managers.
Who this covers and how to contact us
This policy covers the Relayed Discord bot, relayedbot.xyz dashboard, staff workspace, support assistant and hosted custom bot service operated by the Relayed team. For privacy questions, access requests, corrections, deletion requests or suspected misuse, contact the team privately through Relayed support server. Do not post credentials, identity documents or payment information in public channels.
Account and server information
Discord sign-in provides your Discord ID, username, display name and avatar. Relayed checks your server memberships and management permissions to decide which dashboards you may use. It stores settings, server/channel/role IDs, enabled modules, message designs, published-message references, draft history and activity records. Authentication tokens are used for sign-in and permission checks. Essential session cookies and browser draft storage support the service. IP addresses may be processed temporarily for request limiting; the hosting provider may retain operational access logs. Unfinished editor drafts may be kept in browser storage and privately in the backend for your Discord account and server, including form values, message designs, selected roles/channels, open sections and page position. Draft recovery does not publish to Discord. Credential fields and staff/support access-code fields are excluded from the draft snapshots. Current draft markers and history remain subject to the retention and deletion practices below.
Moderation, AutoMod and Anti-Nuke
Moderation cases can contain target and acting staff IDs/names, action, reason, channel, time and relevant action details. Points-based Auto Punish retains violation references, point totals, counting-window timestamps and fired punishment steps. Anti-Nuke uses audit events, action counts, member/role IDs and configured exceptions; quarantine records retain removable roles needed for release, trigger details and outcomes. Optional punishment and quarantine notices are sent through Discord DMs. Discord-native AutoMod rules are configured through Discord. Custom unsafe-link checks process message text and edits against locally stored domain lists; Relayed does not visit submitted URLs or send messages to the blocklist provider. Removal activity records do not repost the full dangerous URL. General channel conversations are not stored as a message archive. Filters can make mistakes and do not detect every unsafe site or action. Optional Anti-spam keeps recent message IDs, channel references and counting timestamps in memory for up to two minutes to remove bursts. It does not separately retain message text in the counter. Counters reset on restart; audit entries may retain the acting member ID, count and deletion outcome.
Tickets, participants and transcripts
Ticket records retain the requester, selected panel/option, handling and notification roles, channel, status, claim/closure details, opening request text, custom question answers and added participants. A ticket participant can add another server member, giving that person access to the existing conversation and future replies. Authorized transcript actions fetch up to the latest 500 messages from the Relayed ticket channel and produce a text file containing available message text, authors, timestamps, embed text and attachment links. On closure, Relayed archives to the configured private ticket-log channel, attempts to DM the requester and then deletes the ticket channel. If archival fails, the channel remains for recovery. The ticket record remains. Discord hosts exported transcript attachments and DMs; downloaded files and copies kept by recipients are controlled by those recipients. Server ticket blacklist settings retain blocked role/user IDs. Ticket close requests retain requester/staff IDs, the supplied reason, message ID, expiry and accept/deny status under the same retention practices.
Applications and community staff records
Applications retain the applicant's Discord identity, selected application, questions, answers, submission/review status, reviewer and optional decision reason. DM application progress is saved to continue across restarts. It has a two-hour submission deadline; expiry prevents submission, while removal of an expired draft may occur when it is next accessed or replaced rather than at the exact deadline. Submitted applications remain until removed. Staff management retains promotions, demotions, infractions, relevant Discord IDs, optional Roblox username, rank changes, reasons, acting staff and timestamps. Shift and staff-access records include requests, approval/revocation and duty times. Managers may export retained staff records. These tools are for community administration, not real-world employment, credit, housing or similar eligibility decisions. Do not request unnecessary sensitive information in forms. Per-form eligibility settings retain blocked role/user IDs and cooldown durations; last successful submission timestamps are retained to enforce reapplication cooldowns.
Member events and role features
Server member join/leave events support configured welcome/goodbye messages, join roles and eligible support-server Plus-role synchronization. Role-button interactions add or remove selected roles. Relayed does not maintain a separate complete archive of member join/leave events or use online presence/activity tracking. Discord permissions and role hierarchy determine what can be changed.
ER:LC, sessions and staff access
Authorized managers can provide an ER:LC private-server API key. Relayed sends it to the official ER:LC API to authenticate status, player/queue and permitted command-log requests, and manager-requested in-game commands. Player lists are processed to calculate counts; the integration does not retain a complete historical player roster or locations. Recent command logs cached for display may contain player names/IDs, command text and timestamps. Commands executed through Relayed are retained with the requesting Discord ID and time. Session/vote records retain announcements, goal/deadline, participants and activity needed to run the feature. Staff join codes are permanent until rotated; private code seed/configuration and staff approval records are retained. A code alone does not grant approved workspace access. Disconnecting ER:LC removes the saved per-server key, and removal of the bot stops that guild's ongoing polling. Optional in-game command logging sends ER:LC-provided executor names/IDs, command text and game timestamps to the configured private Discord channel. Optional mass-command alerts mention only the selected Discord member. Relayed retains a bounded list of delivered-event fingerprints, delivery counts/timestamps, configuration IDs and safe operational errors to reduce duplicate posts and support retries. Discord-hosted copies remain until removed by server staff. The approved staff moderator workspace displays current ER:LC player usernames, Roblox IDs, team, callsign and game permissions from cached API snapshots. Moderators may save server-scoped punishment reasons, evidence links, actor IDs and timestamps, and confirmed or unconfirmed execution results. Optional private Discord channels receive copies. Request identifiers and results are retained to reduce duplicate game actions; data is not used to infer Discord-to-Roblox identity links. Entered moderation usernames are sent to Roblox public username lookup to resolve account IDs/display names; resolved IDs are sent to Roblox thumbnail lookup. Results are cached for five minutes; headshots load from Roblox CDN. This does not link Roblox to Discord identities.
Server visibility, statistics and support invites
Authorized Relayed support personnel can see connected server names, IDs, cached member counts and server/join dates. Private operational statistics show aggregate ticket counts, recorded moderation timestamps and command-activity totals/rankings. Command telemetry stores recognized command names, times and group counts, not command arguments or the invoking user's identity in that aggregate counter. It begins when tracking is enabled and can include failed/denied requests. Member totals may include bots and count a person in several servers; they are not unique-person totals. The statistics display does not show ticket content, punishment reasons or punished-member identities. For support only, authorized personnel may retrieve or generate a temporary invite when Discord permissions allow; invite generation does not automatically join a person and is not used for advertising. Server managers control those permissions and can revoke invites. Service-wide totals include connected Relayed and active online custom bot, count each Discord server ID once, and use the relevant bot’s isolated aggregate activity records.
Custom Bot
For approved hosted customer bots, Relayed retains the customer's Discord ID, authorized server/application IDs, bot name/artwork references, encrypted bot token, hosting status, trial/expiry dates, associated billing identifiers and operational records. Bot data/processes are separated per hosted customer setup. Approved first-start migration copies the same server's supported settings and re-encrypts supported integration credentials; it does not transfer Discord ownership of messages already posted by another bot. Stopping, trial expiry or suspension preserves setup and records; it does not itself delete them. Customers can request deletion through private support. Never supply a Discord user password or user-account token. For new self-service purchases, verified Stripe subscription status binds hosting access to the purchaser and chosen Discord server. Temporary capacity reservations and subscription status are retained for fulfillment and oversell prevention. Discord bot-token and selected-server checks precede paid automatic startup. Billing/customer identifiers are not exposed to other customers. Connection checks use the encrypted saved token or privately supplied replacement with Discord to verify the same bot identity and approved-server access. Safe diagnostic outcome messages and check timestamps may be retained; tokens are never included in diagnostic messages.
Ask Relayed and OpenAI
The optional Ask Relayed assistant sends the question you submit, up to six recent conversation messages and maintained public product documentation to OpenAI to generate guidance. It is not automatically supplied private server settings, ticket transcripts, application answers, staff records, API keys or billing records. Do not paste such information into help chat. The request disables storage as a retrievable API response, but OpenAI may retain API data according to its service and abuse-monitoring policies. Relayed does not use Discord API message content to train models. Relayed keeps usage/spending counters and a hashed account identifier to enforce limits, rather than saving the help-chat conversation in its database. Conversation context is held in the current browser page and cleared on reload. AI guidance can be inaccurate and cannot perform account actions.
Payments and recipients
Stripe hosts payment checkout/subscription management and processes payment/billing information under its policies. Relayed retains Stripe customer, subscription, checkout and event references linked to the purchasing Discord account and server, payment state, period dates and payment-risk events for private review. It does not store card numbers or security codes. Relevant data is processed by Discord, ER:LC, Stripe, OpenAI when help chat is used, and the hosting provider as needed for these features. Configured server managers/staff, ticket participants and log/transcript recipients receive the information required for their functions. Relayed does not sell personal information or use it for advertising.
Storage, access and security
Server records are stored in the backend database. Discord OAuth tokens, stored ER:LC keys and custom bot tokens are encrypted in their relevant storage paths; startup credentials may also exist in private hosting configuration. This is not a claim that every database field, log, export or backup is encrypted. Dashboard access is checked server-side, state-changing requests use origin/CSRF checks, and private feature access depends on configured roles and current permissions. Operator/hosting access and recipient copies have separate access boundaries. No service can guarantee complete security. Report suspected unauthorized access privately through support. Custom hosting records may include approved server IDs, payment references, payment dates and access expiry. Billing references remain restricted to the operator; each approved server retains separate settings and records.
Retention and deletion
Dashboard sessions stop being valid after seven days; sign-in state expires after ten minutes. Expiry is an access limit and does not imply immediate physical deletion of every expired database row. Server settings, cases, tickets, applications, staff/session records, aggregate activity and relevant billing records remain until removed by the operator or through a verified deletion request, subject to applicable obligations. There is currently no universal automatic deletion period for all historical records. Removing a bot, closing a ticket, cancelling a subscription or stopping custom bot hosting does not alone erase stored history. We may verify your identity or authority before responding to access/correction/deletion requests. Backups, Discord-hosted messages and recipient-held exports may have separate retention and removal processes; third-party or recipient copies cannot be recalled by Relayed.
Your choices and policy changes
You can disable modules, sign out, change role/channel permissions, remove the bot, rotate staff codes, disconnect ER:LC, manage billing or request access/correction/deletion through private support. Removing the bot does not cancel a subscription. Avoid sharing private material with AI help. This page describes current features and will be updated with a revised date when practices materially change. The documentation explains configuration steps and feature limits.
Shift Logging and weekly activity requirements
When enabled, Shift Logging records staff Discord IDs, duty start/end times, cumulative hours, weekly hour adjustments, correction reasons/actors, tracked-role enrollment dates, and weekly aggregate message counts across channels the bot can see. Message text is not stored by the counting feature. It also retains monitoring/check markers and automatic weekly staff infractions for missed configured targets. Server Members events and roster requests support staff eligibility checks. Counts are buffered for up to a minute; detected monitoring gaps over five minutes cause the affected weekly evaluation to be skipped. These records remain until operator removal or a verified deletion request. Configured logs and optional correction/infraction DMs may contain activity totals and reasons; recipients control copies of those Discord messages. These are community administration tools, not real-world employment or other eligibility decisions.
Partnership advertisements
When configured staff initiate a partnership request inside a Relayed ticket, Relayed stores the ticket requester and initiating staff Discord IDs, ticket and destination channel IDs, selected ping, posting format, optional instructions, submitted advertisement text, source/review/published message IDs, status and timestamps. Message Content access is used to collect the requester’s next ticket message for review. Only an authorized initiating staff member can approve publication to the selected destination in that server. Requests have a 48-hour usable deadline; expiration does not itself erase stored records. Copies posted to Discord remain subject to Discord and recipient/server controls. Do not submit sensitive information in advertisements. The module also stores configured posting defaults and response templates, review/denial/change reasons, advertisement fingerprints, parsed Discord invite codes, verified partner-server IDs and invite-check warnings for duplicate protection and staff review. At most five Discord invite codes are looked up through Discord when an ad is submitted; unrelated external websites are not fetched. The latest 30 request summaries are available to authorized server managers. These records follow the retention and deletion practices below.
Custom message designs and interactions
Custom message and session-announcement designs may contain Components V2 text, image/link URLs, button/dropdown labels, emojis and private response text. Relayed stores saved designs in server settings and a snapshot with each published message reference so current controls keep their published behavior. Dropdown and response-button interactions process the selected option and Discord interaction context to return the configured answer privately. Custom-message and session information controls do not create a separate interaction-history record; session votes retain voter IDs and timing separately. Discord hosts posted messages and interactions; externally hosted image/link destinations have their own privacy practices. In the Relayed support server, submitting the review form publishes your Discord identity, star rating, written feedback and timestamp in the feedback channel. Review drafts, submission references and recent-submission timestamps are stored to handle delivery, duplicate prevention and spam controls. A form expiry prevents submission; it does not imply immediate deletion of stored records. Do not include sensitive information in a public review.
Custom commands
Server managers store custom command names, aliases, response designs/references, allowed role/channel IDs, destinations and cooldown settings. Prefix execution processes message text when Message Content access is enabled; slash execution processes the supplied name and arguments. Variables use the invoking Discord identity, server/channel context and supplied arguments to prepare configured replies. Command usage audit records retain the actor ID, command name and timestamp, without separately recording argument text in that audit entry. Delivered messages may include supplied text and are hosted by Discord. Copies of interactive messages/panels retain message/channel references and a design/route snapshot so controls remain functional across restarts. Deleting or disabling a command does not delete existing posted copies or their snapshots. Unfinished wizard drafts are stored locally in the browser. Cooldown/burst counters are held temporarily in process memory. These records follow the retention/deletion practices in this policy.
Roblox log headshots
The staff workspace may send recorded subject Roblox user IDs to Roblox’s public thumbnail API to retrieve avatar headshots. Requests are batched and cached briefly in memory. Returned public Roblox CDN images display in staff logs; Discord credentials, reasons, evidence and private log text are not sent to the thumbnail provider.