Legal Documents

1. Who We Are

EmberStream Studio LLC, a Michigan limited liability company (“Company,” “we,” “us,” or “our”), is the independent software studio that develops and operates YourBot, a multi-tenant Discord bot platform and plugin marketplace for Discord communities and developers. Our registered contact for privacy matters is legal@emberstreamstudio.com.

This Privacy Policy applies to YourBot, its associated web dashboard at yourbot.gg, the AI-assisted Start Your Server and Plugin Builder tools and all related services.

2. Scope & Who This Policy Covers

This policy applies to:

• Server Administrators: Discord server owners and moderators who add YourBot to their server and access the web dashboard.
• Server Members: Discord users who interact with YourBot’s features within a server where it is deployed.
• Website Visitors: Anyone who visits yourbot.gg.
• Plugin Developers: Third-party developers who use the Developer SDK and publish plugins to the marketplace.

Because YourBot operates within Discord’s platform, your interactions with Discord are also governed by Discord’s Privacy Policy.

3. Information We Collect

3.1  Data Collected Automatically Through Discord

When YourBot is active in a Discord server, we receive and process the following data from Discord’s API:

• Discord User IDs: Unique numeric identifiers assigned by Discord, together with associated public profile data such as your username, display name and avatar identifier. We do not collect Discord passwords, and we do not receive your email address from Discord.
• Guild (Server) IDs: The unique identifier for each Discord server where YourBot is installed.
• Channel IDs: Identifiers for channels where YourBot features are configured or active.
• Role IDs: Server role identifiers used by services such as Group Finder and Analytics. While a member is in a server, Analytics keeps the list of roles that member currently holds so that reports can include or leave out chosen roles.
• Voice Session Metadata: Join/leave times, channel IDs and duration for voice sessions, plus whether the member was muted, deafened or in the AFK channel, used to power Analytics. We do not record voice audio.
• Message Metadata: For Analytics, a record of each message with its ID, channel, author and time, whether it was a reply and how many attachments, embeds, stickers and mentions it had, but never its text. Analytics also records reactions (who reacted to whose message and with which emoji), the titles of threads and which messages reached the starboard. When a Server Administrator runs the Analytics setup, the same message metadata is read from the server’s existing history, going back up to one year. Message text is stored only in the cases listed under Message Content below.
• Message Content: We store the text of messages only in these cases: ticket transcripts (Section 3.2); Sentinel moderation records, which hold a short excerpt of the message that triggered a rule, the messages around a moderation case or a member report and, where a Server Administrator turns on the message log, deleted and edited messages with their attachments; messages written in a Group Finder listing’s web chat; and questions asked in tickets on our own support server, which we keep for 180 days to improve our help answers. While the Sentinel message log is on, recent messages are also held for up to 72 hours so that a later edit or deletion can be recorded. Scheduled Announcements store the text a Server Administrator writes for them.
• Screen Share Activity: Whether a screen share occurred during a voice session, along with start and end timestamps. No screen share content is captured or stored.
• Member Events: Join, leave and profile update events used for cohort tracking, daily membership snapshots and the safety features described in this policy.
• Invite Records: Which invite a member joined through and who created it. Analytics records this for each join unless a Server Administrator turns invite tracking off, and marks joins that look fake (for example a very new account, a member who left within minutes or an account inviting itself) so that administrators can leave them out of invite counts. Sentinel can keep the same invite details in its join log, Welcome records the invite used and Giveaways records who invited whom when a giveaway rewards invites.
• Presence Data: Only when the Presence intent is on for the bot. The Analytics service stores it only when a Server Administrator turns on status tracking or activity tracking. Status tracking stores server-wide counts of members online, idle, busy and offline at five-minute marks. Activity tracking stores the name of the game, stream or music a member is showing and its start and end time. Custom status text is never stored. Members can stop their activity from being recorded with the Hide my card control on their stats card. Three other features use presence: Analytics member status counter channels show how many members are online, idle, busy or offline, the Voice {activity} placeholder puts the game or stream a member is showing into the name of the voice room created for them and Group Finder smart pings, when a server turns them on, message members who are playing the game a new group is for.
• Guild Membership Records: A record of which servers an account has been a member of, including join and leave times and the most recently seen username, display name and avatar identifier. We also keep a history of the usernames and display names an account has used, which is not tied to one server. These records power safety tooling such as detection of ban evasion and duplicate accounts and let our staff find an account by an earlier name. The names on a server’s membership record are removed when that server’s data is purged or when you make a verified deletion request; the name history is removed on a verified deletion request; the numeric record is retained for security as described in Section 9.
• Cached Display Names: Temporarily cached to provide readable dashboard interfaces. Display names are refreshed on activity, purged after 90 days of inactivity and are not used for profiling.
• Moderation Profiles: When the Sentinel moderation service is enabled, per-server moderation history including warnings, actions taken and moderator notes. Sentinel also computes automated per-server risk scores from moderation history and account signals (such as account age and join patterns) to help Server Administrators screen joins and prevent raids and ban evasion. It keeps a join log with each joining account’s username, avatar identifier, creation date, risk score and any automatic action taken. Where a Server Administrator turns on ban evasion detection, it also keeps a profile of each banned account (username, display name, avatar identifier and account creation date), built from the server’s ban list.
• Server Backups: While Sentinel is enabled it backs up the server’s structure automatically, checking every hour and saving a new backup when something changed, so that an administrator can restore the server after an attack or a mistake. A backup holds the server’s settings, roles, channels and permission overwrites, emojis, stickers and images, the list of which members hold which roles (for servers of up to 25,000 members) and the server’s ban list with ban reasons (up to 10,000 bans). Backups do not contain messages.
• Verification Records: When a Server Administrator turns on the Welcome verification gate with a removal deadline, we keep a record of members who still need to verify, with their join time and the reminder and removal deadlines the administrator configured. The record is closed once the member verifies, leaves or is removed and is deleted about seven days later. The pending answer for an image captcha is held for ten minutes.
• Welcome Records: The Welcome service keeps a log of joins, leaves and verifications for 180 days, including the invite used and the roles a member held when they left. It also keeps each member’s welcome quest progress and rewards.
• Voice Rooms: For the Join-to-Create Voice service, each temporary room’s owner, name, lifetime and peak member count, the room preferences a member saves (preferred name, user limit, locked or hidden) and the members and roles a room owner has allowed or blocked.
• Stats Cards: Analytics can draw a card of a member’s activity in a server. A member can ask for their own card or another member’s, and a card can be opened through a share link. Members can turn their own card off with the Hide my card control.
• Service & Plugin Activity Logs: Audit logs recording service toggles, plugin installations, configuration changes and administrative actions.

3.2  Data You Provide Directly

• Service & Plugin Configuration Data: Settings and preferences entered via the web dashboard or bot commands, stored per server.
• Ticket Content: When a ticket closes, the messages in it are saved as a transcript: the text, each author’s username, display name and avatar address, attachment file names, embeds and reactions. The form answers, internal staff notes and staff action log of a ticket are stored with it.
• Messages You Send to the Bot (Tickets by DM): Where a Server Administrator has turned on Tickets by DM, a direct message you send to the bot is passed, once you confirm the server, into a support ticket on that server. It then becomes part of that ticket and its transcript, and the answers of that server’s staff are delivered to you by direct message. A message that is waiting for you to confirm is held for up to 30 minutes and then deleted.
• Group Finder Activity: Listings you create, including role requirements and description, the groups you join (and, for a listing shared with other servers, the server you joined from and any note you add), messages you write in a listing’s web chat, which are deleted 24 hours after the listing closes, thumbs-up or thumbs-down ratings between players, no-show marks and reports.
• Survey Responses: Responses submitted via Ticket surveys, if enabled by the Server Administrator.
• Events & Giveaways: Your sign-ups, attendance and any feedback you leave for Beacon events, the weekly availability you enter and an attendance reliability score that Beacon works out from your sign-up history; and your giveaway entries, each kept with a snapshot of your username and avatar identifier. A giveaway’s public spectator page shows the usernames and avatars of recent entrants and of winners unless the Server Administrator turns that page off.
• AI Prompts & Generated Content: The community description you give Start Your Server, the server description you give the Sentinel AI setup, the plugin description and follow-up instructions you give the Plugin Builder, and the designs, moderation configurations, plugin code and dashboard layouts generated from them, which we store so you can review, revise and apply them.
• Referral Codes: A referral code you apply at checkout, and the code we generate for you if you share YourBot with others.

3.3  Usage & Analytics Data

• Feature Usage Events: Which bot commands are used, by which account and when. The individual records are deleted after 90 days and daily totals are kept to improve service quality.
• Dashboard Page Visits: While you are signed in, we count the dashboard pages you open so we can see which features are used and improve them. For each day we keep your Discord User ID, the server you have selected (if any), the kind of page (such as the Plugins page, never its full address) and how many times you opened it, with the first and last time that day. Pages of our public website and staff pages are not counted. Our staff see these records as totals in our usage reports and per account in our internal audit log, which they use for support and security. They are kept for 400 days, included when you export your data and deleted when you delete your account.
• Public Website Analytics: If you accept the cookie consent banner, Google Analytics collects usage statistics for our public website pages, such as pages visited, referrers, browser and device type and approximate location derived from your IP address. Google discards IP addresses from EEA, UK and Swiss visitors before logging. This runs only on our public pages, never inside the authenticated dashboard and never if you decline. One page shown after sign-in uses the public website layout and is treated as a public page: the server picker at /start.
• Advertising Measurement: If you accept the cookie consent banner, the X (formerly Twitter) and Reddit advertising pixels record visits to our public website pages so we can measure whether our ads on X and Reddit lead to visits. These run only on our public pages, never inside the authenticated dashboard and never if you decline.
• Error & Diagnostic Logs: Crash reports and error traces used solely for debugging and stability improvements.
• Login & Security Records: When you sign in to yourbot.gg with Discord we record your IP address, browser user-agent, a random device identifier (the mmo_did cookie), your username and avatar identifier and the login time. This applies to every sign-in, including one made from a server’s verification, appeal, giveaway or Group Finder page. These records are used for account security and for fraud and abuse detection, including finding duplicate accounts, and are retained for up to 24 months. Where two accounts are flagged as likely duplicates, the signals that matched (which can include a shared IP address) are kept with that finding as described in Section 9.

3.4  Data We Do NOT Collect

3.5  Marketplace & Developer Data

• Reviews & Ratings: When you submit a review or rating for a marketplace plugin, your Discord User ID is associated with that review.
• Installation & Entitlement Records: Records of plugin installations and subscription entitlements tied to your server or account.
• Developer Account Data: For plugin developers, we store your Discord User ID, plugin metadata and revenue records associated with your developer account. We also store the profile you choose to fill in (such as display name, bio, location, pronouns, skills and links to your other accounts), which is public only if you turn on a public profile. For each version of the Marketplace Developer Agreement you accept, we keep a record of the time, IP address and browser user-agent. If you connect GitHub, we store the repository, the branch to deploy from, the GitHub account or installation it belongs to and an encrypted access token.
• AI Credit Wallet: If you use the paid AI tools, a prepaid credit balance and a ledger of every purchase, hold, charge and refund, kept as a financial record.
• Payout Account Status: For developers who monetize plugins, a reference to their Stripe Connect account, its country and whether it can accept charges and payouts. Stripe holds the identity and bank details itself.

3.6  Third-Party Plugin Data Handling

Third-party plugins published to the marketplace operate within a sandboxed environment but may collect data within the scope of their declared capabilities. All third-party plugins are required to provide a privacy disclosure during the review process. EmberStream Studio is not responsible for data handling practices of third-party plugins beyond enforcing our marketplace review requirements.

3.7  Payment Data

Payments are processed by Stripe. We never store payment card numbers or CVV codes. The data we receive from Stripe includes transaction IDs, subscription status, billing dates, the last four digits of your payment method and the billing name, email address and postal code you provide at checkout. We use billing contact details to answer billing and support requests, and we retain them and payment method fingerprints for fraud prevention and abuse detection, for example detecting duplicate accounts used to evade bans. For details on how Stripe handles your payment data, please refer to Stripe’s Privacy Policy.

3.8  AI Features & Our AI Provider

Start Your Server, the Plugin Builder and the Sentinel AI setup generate their results with large language models provided by Anthropic, PBC (United States). When you use one of these tools we send Anthropic only what that tool needs:

• Start Your Server: Your description of the community, your follow-up instructions and, when you redesign an existing server, a snapshot of its structure: category, channel and role names and identifiers, which YourBot services are enabled and which other bots are installed. If you choose to run the optional history scan (Scan my server), we also send short excerpts of the messages and pinned panels those other bots posted in your server and a count of their recent moderation actions from the audit log; the scan results are kept for 24 hours. The scan keeps only posts made by other bots and discards messages written by members, but a post by another bot can itself repeat something a member wrote or a member’s name (a logging bot’s record of a deleted message, for example), and such a post can be part of an excerpt. No member list or moderation records of your members are sent.
• Plugin Builder: Your plugin description, your interface brief, your follow-up instructions and, when you edit an existing plugin, its current source code and dashboard layout.
• Sentinel AI setup: The description of your community and moderation goals that you type, and the strictness level you choose.

Anthropic processes these requests under its commercial API terms, which do not allow it to use your inputs or the generated output to train its models, and it retains them only for the limited period its API data retention policy allows. We never send member lists, moderation history or billing details to an AI provider, and we never send your members’ own messages. The only Discord message content we send is the other bots’ posts described above, which can quote a member, and only when you run the history scan. We do not use any of your data to train models of our own.

4. Discord Privileged Intents & Permissions

YourBot uses the following Discord privileged intents to deliver its features:

• Message Content Intent: Used for moderation rule evaluation, ticket transcript generation and command handling. Message content is stored only in the cases listed under Message Content in Section 3.1.
• Guild Members Intent: Used for analytics cohort tracking, moderation profiles, role-based features and the safety features described in this policy, including membership records used to detect ban evasion. Member data is processed only within servers where YourBot is installed.
• Presence Intent: Requested by the shared bot only when we have switched it on and Discord has enabled it for our application. A custom bot requests it only if its owner turns it on. It is used only by built-in services: Analytics (status tracking, activity tracking and member status counter channels), Voice (the {activity} placeholder in room names) and Group Finder (smart pings, when a server turns them on). Status tracking records how many members were online, idle, busy or offline at each five-minute mark as server-wide counts, never per member. Activity tracking records the name of the game, stream or music a member is showing and when it started and ended. Custom status text is never recorded. Members can stop their activity from being recorded at any time with the Hide my card control on their stats card. Marketplace plugins never receive presence data.

These intents are used solely for the declared functionality described in this policy. We do not use privileged intent data for advertising and we never sell it. Automated evaluation of member data is used for the security and safety features described in this policy, such as moderation risk scoring and ban evasion detection. Outside those features it is limited to labels shown to Server Administrators: Analytics marks joins that look like fake invites and Beacon works out an attendance reliability score for event sign-ups.

5. Discord Developer Policy Compliance

In accordance with Discord’s Developer Policy, we affirm the following:

• We do not use Discord data for profiling users for advertising or data brokering purposes.
• We do not sell or license Discord user data to any third party.
• We do not use message content or member data for machine learning or artificial intelligence model training.
• All Discord API data is subject to strict purpose limitation and is used only as described in this policy.
• Where data is used for service improvements, it is aggregated before analysis.
• Where you use our AI features, only the information described in Section 3.8 is sent to our AI provider, never member lists or your members’ own messages.

6. How We Use Your Information

We use the data we collect for the following purposes only:

• Service Operation: To provide, run and maintain YourBot’s features and the web dashboard.
• Feature Delivery: To power specific service features, e.g., using voice session timestamps to calculate analytics or Guild IDs to isolate data between tenants.
• Analytics & Insights: To provide Server Administrators with actionable data about their community’s activity.
• Service Improvement: To identify bugs, optimize performance and inform feature development through aggregated usage patterns, such as the dashboard page visits described in Section 3.
• Security & Integrity: To detect abuse and fraud (including duplicate accounts used to evade bans), enforce our Terms of Service and protect our infrastructure. When an account is banned from the YourBot platform, we may notify Administrators of servers where that account is present that a platform ban exists. The reason for a platform ban is never shared with servers.
• AI Features: To generate the server designs, moderation configurations, plugin code and dashboard layouts you ask for, and to charge the credits that pay for them.
• Referral Program: To apply a referral discount at checkout, credit the referrer once the conditions in our Terms of Service are met and detect referral abuse.
• Legal Compliance: To comply with applicable laws, regulations and valid legal requests.

We do not use your data for any purpose unrelated to operating, securing and improving our services, except in two cases: measuring our own advertising on our public website, which happens only with your consent as described in Section 3.3, and where you have given us separate written permission, such as a signed video or testimonial release. We do not use data we receive from Discord for advertising. Automated evaluations of accounts (such as moderation risk scores) exist for the security and anti-abuse purposes described in this policy; the only others are the fake-invite label and the attendance reliability score described in Section 4. Platform-level account decisions such as platform bans are made by human staff; automated server-level actions (such as raid protection or acting on a platform ban when an account joins) run only under rules the Server Administrator has configured.

7. Legal Basis for Processing (GDPR)

YourBot is operated from the United States. For users in the EEA, the UK or other jurisdictions that require a legal basis for data processing, we rely on the following legal bases:

• Contractual Necessity: Processing required to deliver the services requested under our Terms of Service, including generating the designs, moderation configurations and plugin code you ask our AI features for.
• Legitimate Interests: Processing for analytics, service improvement and the security and anti-abuse measures described in this policy (such as ban evasion detection and moderation risk scoring) where our interests do not override your fundamental rights.
• Legal Obligation: Processing required to comply with applicable laws.
• Consent: Where we request optional data not covered above, we will seek your explicit consent. This includes the optional Google Analytics cookies and the optional X and Reddit advertising pixels on our public website, which are set only after you accept the cookie consent banner and can be withdrawn at any time via Cookie Settings.

8. Data Storage & Security

8.1  Infrastructure

All persistent data is stored in secured, encrypted databases hosted on managed cloud infrastructure. Operational caching uses dedicated in-memory stores within the same environment. Our infrastructure is designed for multi-tenant isolation: each Discord server’s data is logically separated.

Two supporting services run on a server we operate outside that environment and are reached through Cloudflare: our status page and the service that matches questions in tickets on our own support server to help articles. The text of a message in one of those tickets is sent to that service to find a matching article. Messages from other servers are never sent there.

8.2  Security Measures

• Encryption in transit (TLS/HTTPS) for all data communications.
• Encryption at rest for database storage.
• Role-based access controls limiting which systems and personnel can access data.
• Regular security reviews and dependency audits.
• Rate limiting and backpressure mechanisms to protect service stability.

No system is completely secure. If you believe a security incident has occurred, contact us immediately at legal@emberstreamstudio.com. If we determine that a security incident has resulted in unauthorized access to personal data, we will notify affected Server Administrators or users and any regulators we are required to notify without unreasonable delay, consistent with applicable data breach notification laws.

8.3  Data Location

Data is stored on managed cloud infrastructure, which may involve servers in the United States or other jurisdictions. Where personal data of individuals in the EEA, the UK or Switzerland is transferred to the United States, our service providers (including Google Cloud, Stripe, Anthropic for the AI features, Google LLC for optional website analytics and X Corp. and Reddit for optional advertising measurement) rely on recognized transfer safeguards such as Standard Contractual Clauses or certification under the EU-US Data Privacy Framework. If you require specific data residency, please contact us.

9. Data Retention

• Active Server Data: Retained while YourBot is installed in a Discord server. After removal, data is retained for a 30-day grace period and then deleted by a daily job, with these exceptions: records we retain for fraud and abuse prevention (such as membership history signals used to detect ban evasion), the financial and audit records described below, some per-server records the daily job does not yet remove (such as each member’s lifetime activity totals, the ticket and giveaway blocklists, welcome quest points, Group Finder ratings, marketplace reviews and saved AI server designs) and images uploaded to our image host, such as card backgrounds. Deleted data can remain in our database backups for up to 14 days.
• Analytics Data: Raw event data, including invite records, presence status samples and activity sessions, is retained for 90 days unless the server’s setting says otherwise. Server Administrators may configure a retention period between 7 and 365 days depending on their plan, and running the Analytics setup with a history import raises the setting to the longest period the plan allows (up to 365 days) so that the imported history is kept. Hourly summaries and per-member daily summaries are kept for twice the retention period. Daily server totals and each member’s lifetime message and voice totals are retained while the bot remains installed. The retention job runs only while Analytics is switched on: if a server turns Analytics off, what was already recorded stays until Analytics is turned back on or the server’s data is deleted.
• Website Analytics Data: Google Analytics data about public website usage is retained for 2 months, the shortest retention period Google Analytics offers.
• Advertising Measurement Data: Data collected by the X and Reddit advertising pixels is retained by X Corp. and Reddit under their own retention policies. The attribution cookies they may set on our site expire after 30 days (X) and 90 days (Reddit).
• Ticket Transcripts: Retained until deleted by a Server Administrator. Administrators may delete transcripts at any time using the dashboard’s data management tools, and all transcripts are deleted with server data after bot removal. Copies of a transcript that were posted to a Discord channel or sent by direct message stay in Discord.
• Error & Diagnostic Logs: Application logs are typically retained for 30 days. Plugin crash reports are automatically deleted after 90 days.
• Moderation History: Cases, warning points, risk profiles and the join log are retained while the bot is installed and are deleted with the server’s data or on a server data deletion request. The messages captured around a case are deleted after 30 days unless the Server Administrator sets another period. Message log entries are deleted after the period the administrator sets (30 days by default, at most 365). Copies of deleted images saved by the message log are stored on our image host and are deleted once the entries that show them have been deleted; a copy that our content delivery network has already cached can stay reachable at its address for about 30 days after that. Ban evasion profiles are deleted 30 days after the account is unbanned or when the server turns the feature off.
• Server Backups: Sentinel keeps the 24 most recent automatic backups plus the latest one from each of the last 7 days, up to 10 manual backups and the 3 most recent backups taken before a restore. Older ones are deleted as new ones are saved, and all are deleted with the server’s data.
• Guild Membership Records: The numeric membership record (server, account and join and leave times) is retained for security and ban evasion detection. The usernames, display names and avatar identifiers stored on it are removed when a server’s data is purged after bot removal and on a verified deletion request. The history of usernames and display names an account has used is not tied to a server and is kept until a verified deletion request.
• Marketplace Data: Retained while a subscription is active. Purchase history is retained as required for financial record-keeping.
• Login & Security Logs: Login records (including IP address, browser user-agent and device identifier) are retained for up to 24 months. Findings of our duplicate-account detection, including the signals that matched such as a shared IP address, are kept for as long as they are needed for abuse prevention and currently have no fixed deletion date. Records of a developer accepting the Marketplace Developer Agreement, with the IP address and browser user-agent, are kept as proof of the agreement.
• Cached Display Names: Refreshed on activity and automatically purged after 90 days of inactivity, or sooner when server data is deleted.
• AI Designs, Builds & Credits: Saved server designs are kept until you ask us to delete them. Plugin build history is retained until you delete it. An unfinished saved build is kept for at least 30 days after its last change and may be deleted after that. The credit ledger is retained as a financial record.
• Verification Records: Closed when the member verifies, leaves or is removed by the gate and deleted about seven days later. The Welcome log entry that a member verified is kept for 180 days.
• Administrative Audit Logs: Records of administrative actions taken in the dashboard are retained for 2 years.
• Referral Records: Referral codes and redemption records are retained while the referral program runs and for as long as the related billing records must be kept.

Server Administrators may request deletion of all data associated with their server by contacting legal@emberstreamstudio.com. We process such requests within a reasonable timeframe, subject to legal retention obligations.

10. Data Sharing & Third Parties

We do not sell, trade or rent personal data to any third party. We may share data only in these limited circumstances:

• Cloud Hosting: Google Cloud Platform (United States) provides our hosting and managed database infrastructure under contractual data-protection obligations.
• Business Email: Google Workspace (United States) hosts our business email under contractual data-protection obligations.
• Website Analytics: If you accept the cookie consent banner on our public pages, Google LLC (United States) processes aggregate usage statistics for our public website through Google Analytics. No analytics script is loaded if you decline. Google Analytics never runs on authenticated dashboard pages, advertising features are disabled and we do not send your Discord account to Google Analytics as an identifier. Google Analytics does record the address of each public page viewed, and two kinds of public page have a Discord ID in their address: a server’s public Group Finder page (that server’s ID) and a developer’s public profile when it is opened by its numeric address (that developer’s ID). You can read how Google uses this data at policies.google.com/technologies/partner-sites.
• Advertising Measurement: If you accept the cookie consent banner on our public pages, X Corp. (United States) and Reddit, Inc. (United States) process visit data through their advertising pixels so we can measure the performance of our ads on X and Reddit. No pixel scripts are loaded if you decline and the pixels never run on authenticated dashboard pages. Like Google Analytics, the pixels receive the address of each page viewed.
• Payment Processor: Stripe (United States) processes payments on our behalf. We do not directly store payment card data.
• AI Provider: Anthropic, PBC (United States) processes the prompts and server or plugin details described in Section 3.8 to generate results for the AI features, only when you use them, and may not use that data to train its models.
• Cloudflare: Cloudflare, Inc. (United States) carries traffic to the two supporting services described in Section 8.1, so the text of a ticket message on our own support server and the IP address of a visitor to our status page pass through its network. Where a Server Administrator adds the optional bot check to the Welcome verification page, Cloudflare Turnstile runs in the member’s browser to perform it.
• Content Delivery & Embedded Content: Some dashboard pages load a charting or emoji-picker script from the jsDelivr content delivery network, our setup videos are loaded from YouTube in its privacy-enhanced mode only when you press play, the Social pages show game and service icons from Steam, GitHub and Google’s icon service and marketplace listings can show images that their developers host elsewhere. Your browser requests these files directly, so each of those hosts receives your IP address.
• Discord: YourBot runs on Discord, so everything the bot posts or does in a server passes through Discord. If you connect Linked Roles, we send Discord whether you are a subscriber, your plan tier, how long you have subscribed, whether you are a plugin developer and how many plugins you have published, so that servers can grant roles from it.
• Game Companion Pairing: If you pair a Rust+ companion account for a plugin that uses it, we pass the pairing token you obtain from Facepunch Studios back to Facepunch’s companion service and register a push endpoint with Google Firebase and Expo to receive the pairing.
• Third-Party Plugin Developers: Plugins published by third-party developers may receive limited data within the scope of their declared capabilities and approved permissions. Developers are bound by the Marketplace Developer Agreement, which they accept in the developer portal.
• Legal Requirements: We may disclose data when required by law, court order or government authority, or to protect our rights or safety.
• Business Transfers: In the event of a merger, acquisition or asset sale, your data may be transferred. We will provide notice.

11. Cross-Server Data Sharing

The Group Finder network feature lets servers share listings with other participating communities. A shared listing carries its title, description, role requirements and server ID, and its member list shows the display names of the members who joined together with the name of the server each cross-server member joined from. The web chat of a shared listing is open to the members who joined it, including those from other servers.

Sentinel can share bans between servers when their administrators choose to. Ban sync works across the servers one owner runs, and a ban network links servers with different owners once each has asked to join and the network’s owner has approved it. A participating server is told that an account is banned on another participating server, with that server’s name and the ban reason, and can flag, kick or ban that account according to the mode its administrator chose. A server that takes on a shared ban also receives the account’s names and avatar identifier so that its own ban evasion detection can recognize the account.

Separately, Server Administrators may be told that an account in their server is banned from the YourBot platform, without the reason. No other private member data is shared across servers. Server Administrators control whether their server takes part in Group Finder networks, ban sync and ban networks and may opt out at any time through the dashboard.

12. Temporary & Cached Data

During normal operation, we process certain ephemeral data that is not permanently stored:

• Voice Room State: Temporary state used to manage dynamic voice channels while they exist. The stored records of the Voice service are described under Voice Rooms in Section 3.1.
• Event Queue: Events we receive from Discord, including the text of messages, pass through a short-lived queue on their way to the services that are switched on for a server. The queue holds a limited number of recent events and drops the oldest as new ones arrive.
• Session Data & Rate-Limiting Counters: Used to manage active sessions and enforce rate limits.
• Cached Configurations: Server configurations cached in memory for fast response times.

This data is short-lived: it expires on its own, is dropped as newer data arrives or is cleared when a service restarts, and it is not kept in long-term storage.

13. Service Diagnostics & Monitoring

To maintain service reliability, we collect diagnostic data including:

• Request traces and performance metrics used for debugging and optimization.
• Structured logs containing event types, timestamps and error codes.
• Discord User IDs or Server IDs may appear in error contexts when necessary for troubleshooting.

Diagnostic data is used solely for debugging and maintaining service quality. It is subject to the retention periods described in Section 9 and is never used for profiling or marketing.

14. Multi-Tenancy & Data Isolation

YourBot is a multi-tenant platform serving multiple Discord servers. Each server’s data is logically isolated: Server Administrators and members can only access data associated with their own server.

EmberStream Studio staff may access data across tenants solely for operating, debugging and maintaining the service and for investigating abuse. Such access is governed by internal access controls, and opening a server’s settings or an account’s details in our staff tools is recorded in an audit log.

15. Your Privacy Rights

Depending on your location, you may have the following rights:

• Right of Access: Request a copy of the personal data we hold about you.
• Right of Rectification: Request correction of inaccurate data.
• Right of Erasure: Request deletion of your personal data, subject to legal retention requirements.
• Right to Restriction: Request that we limit processing of your data in certain circumstances.
• Right to Data Portability: Receive your data in a structured, machine-readable format.
• Right to Object: Object to processing based on legitimate interests.
• Right to Withdraw Consent: Withdraw consent at any time where processing is consent-based.
• Right to Complain: If you are in the EEA, the UK or Switzerland, you may lodge a complaint with the data protection authority where you live or work.

To exercise any of these rights, contact legal@emberstreamstudio.com. We respond within 30 days. We may require verification of your identity, which may include your Discord User ID. If we decline a request, you may ask us to review that decision.

When we carry out a verified deletion request we keep a small number of records: a marker that the account was erased and any platform moderation record for it (with names and free text removed), the numeric membership record used to detect ban evasion, payment and AI credit records we must keep as financial records and a log entry showing that the erasure took place.

15.1  California Residents

EmberStream Studio LLC is a small business that does not currently meet the thresholds that make the California Consumer Privacy Act (“CCPA”), as amended by the California Privacy Rights Act (“CPRA”), applicable to a company. We nonetheless voluntarily extend the following disclosures and rights to California residents:

• Categories of personal information collected: identifiers (Discord User IDs, usernames and display names, server identifiers, internet protocol addresses and device identifiers); commercial information (subscription and purchase records); internet or other electronic network activity (feature usage events and activity in Discord servers as described in Section 3); and inferences drawn from that activity for safety purposes, such as moderation risk scores. If you accept the cookie banner on our public website, internet activity on those pages is also disclosed to Google LLC acting as our analytics service provider and, through their advertising pixels, to X Corp. and Reddit, Inc. If you use the AI features, the prompts and generated content described in Section 3.8 are disclosed to Anthropic acting as our service provider.
• Sale and sharing of personal information: We do not sell personal information for money. If you accept the cookie banner, the X and Reddit advertising pixels described in Section 3.3 disclose visit data from our public pages to X and Reddit so that we can measure our ads. California law can treat a disclosure of that kind as a “sale” or as “sharing” for cross-context behavioral advertising. It happens only if you accept the banner, and you can opt out at any time by opening Cookie Settings and choosing Decline.
• Minors: We do not knowingly collect or sell personal information of minors under 16.

To exercise these rights, including the right to know, delete or correct your personal information, contact legal@emberstreamstudio.com. We will not discriminate against you for exercising these rights.

15.2  Do Not Track & Global Privacy Control

We do not track visitors across third-party websites ourselves. The optional analytics cookies and advertising pixels described in this policy run only on our own public pages and only if you accept the cookie banner, and X and Reddit may be able to connect a visit recorded by their pixel with an account on their service. You can withdraw consent at any time by opening Cookie Settings and choosing Decline. We do not currently respond automatically to Do Not Track or Global Privacy Control browser signals. Because nothing optional loads until you accept the banner, declining it has the same effect.

16. Children’s Privacy

Our services are not directed to individuals under the age of 13, and we do not knowingly collect personal data from children under 13. Discord itself requires users to be at least 13 years old. If we become aware we have collected data from a child under 13, we will promptly delete it. Accounts we determine belong to children under 13 are terminated and their personal data is deleted. Contact legal@emberstreamstudio.com if you believe this has occurred.

17. Discord Platform & Third-Party Policies

When using YourBot, you are also subject to:

• Discord’s Terms of Service
• Discord’s Privacy Policy
• Discord’s Developer Policy

EmberStream Studio LLC is an independent developer and is not affiliated with or endorsed by Discord Inc. We are responsible only for data processing within our own systems.

18. Cookies & Web Dashboard

For full details on cookie usage and to manage your preferences, see the Cookies section below.

19. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. When we make changes, we will update the “Last Updated” date above, post the revised policy on our website and for material changes provide notice via our Discord community or dashboard notification. Continued use of our services following notice of changes constitutes acceptance of the updated policy.

This policy is written in English. Where we provide a translation it is for convenience, and if a translation differs from the English text, the English text controls to the extent the law allows.

20. Contact & Data Controller Information

For personal data processed about Server Members through a Discord server where YourBot is installed, the Server Administrator determines the purposes of that processing and EmberStream Studio LLC processes the data as a service provider on the administrator’s behalf. For data about website visitors, dashboard accounts, developer accounts and billing, EmberStream Studio LLC is the data controller.

Server Administrators who need a data processing addendum for their community can request one at the legal address below.

If you have questions, concerns or requests regarding this Privacy Policy, please contact:

• Legal: legal@emberstreamstudio.com
• General: support@emberstreamstudio.com
• Website: yourbot.gg
• Discord: discord.gg/yourbot

We aim to respond to all privacy inquiries within 30 days.

1. Acceptance of Terms

By accessing, installing, configuring or otherwise using YourBot or any related service operated by EmberStream Studio LLC (“Company,” “we,” “us,” or “our”), including the YourBot bot and its associated web dashboard, you (“User,” “Server Administrator,” or “you”) agree to be legally bound by these Terms of Service (“Terms”) and all incorporated policies.

If you are accepting these Terms on behalf of a Discord server, guild or organization, you represent that you have the authority to bind that entity and its members to these Terms. If you do not agree to any part of these Terms, you must immediately discontinue use of all our services.

We may update these Terms from time to time. For material changes we will provide advance notice through the dashboard, email or our Discord community before the changes take effect, and we will update the “Last Updated” date above. Changes to Section 19 (Governing Law & Dispute Resolution) do not apply to disputes that arose before the change took effect. Continued use of our services after the effective date of a change constitutes your acceptance of the revised Terms.

2. Description of Services

YourBot is a multi-tenant Discord bot platform operated by EmberStream Studio LLC, offering modular built-in services, a web-based administration dashboard, a developer SDK and a plugin marketplace for Discord communities.

Services provided under the YourBot platform include, but are not limited to:

• Service & Plugin Ecosystem: Modular architecture with a marketplace for discovering, installing and managing both built-in services and third-party plugins on a per-server basis.
• Developer SDK & Portal: Tools for third-party developers to build, test, publish and monetize plugins within a sandboxed runtime environment.
• Web Dashboard: Per-server administrative interface for configuring services and plugins, managing permissions and reviewing analytics.
• AI-Assisted Tools: Start Your Server, which designs and builds a server layout from your description, the Plugin Builder, which writes and edits marketplace plugins from a description, and the Sentinel AI setup, all described in Section 2.2.

2.1  Built-in Services

The following services are included with YourBot out of the box and can be enabled or disabled per server through the web dashboard:

• Analytics: Server-activity tracking covering messages, reactions, voice time, member events, invites, leaderboards, threshold-based role rewards, counter channels, shareable stats cards, cohort retention and configurable alerts. Processes message, reaction and voice-session metadata, member join/leave events, invite records and role assignments.
• Scheduled Announcements: Timezone-aware scheduler for one-off and recurring messages to designated channels, with graceful catch-up after platform downtime. Stores message content, target channel IDs and recurrence schedules.
• Beacon Events: Guild-event scheduling for raids, dungeon nights, PvP and other activities, with role-based sign-up slots, multi-status RSVPs, waitlists, attendance reputation and pre-event reminders. Stores event metadata, attendee user IDs, attendance history and optional event feedback.
• Giveaways: Random-winner giveaways with weighted entries, per-role and server-booster multipliers, eligibility gates (account age, server tenure, roles, minimum messages) and a public spectator page that streams the live drawing and shows the usernames and avatars of recent entrants and winners. Stores entries, draws and winner records; draws use cryptographic OS entropy.
• Group Finder: Looking-for-Group listings with role-based slots, activity templates, saved searches with alerts, ready-checks, a web chat for each shared listing, player ratings and optional cross-server discovery via opt-in networks. Stores listings, slot/member assignments, chat messages, ratings, no-show marks, watchers, reports and per-user moderation history (such as suspensions).
• Sentinel Moderation: Automod and case management with a rule engine whose conditions cover word matching, spam, mentions, links, attachments, account age, phishing, staff impersonation, risk scores and more, an optional AI setup that drafts a configuration from your description, a warning-points ledger, time-decayed user-risk scoring, raid protection, automatic server backups, an optional log of deleted and edited messages, ban evasion detection, ban sync and ban networks (Section 6.4) and an appeals workflow. Records moderation cases, point-ledger entries, watchlist data, join logs, message context used for rule evaluation and backups of the server’s structure, member roles and ban list.
• Social & Patches: Polls external feeds (Twitch, YouTube, Kick, Bluesky, RSS, Reddit, Steam patch notes, Riot, Apex, Fortnite, Minecraft, Guild Wars 2, Final Fantasy XIV, GitHub releases, Atlassian Statuspage service status and others) and posts new items to a Discord channel with optional role pings. Stores subscription configurations, dedup keys for posted items and source credentials where required.
• Tickets: Support-ticket system with admin-built panels, modal intake forms, staff teams, SLA policies, ticket channels or threads, claim and assignment workflows, internal notes, canned responses, transcripts and CSAT surveys. Stores ticket metadata, form submissions, internal notes, full conversation transcripts on close and a staff-action audit log. Where a Server Administrator turns on Tickets by DM, members can also open a ticket by writing to the bot in a direct message and staff answers are delivered to them by direct message; those messages are part of the ticket’s conversation and transcript.
• Join-to-Create Voice Channels: Automatically creates a personal voice channel when a member joins a designated lobby and deletes the channel when it becomes empty, with configurable name template, user limit, bitrate and optional ownership permissions. Stores per-channel ownership and configuration; does not store voice content.
• Welcome: Member-onboarding system with templated welcome and goodbye messages, generated welcome cards, auto-roles, welcome DMs, an optional verification gate (button, image captcha or web page) for new members, milestone celebrations, a multi-task welcome quest, first-message celebration and reaction-role menus. Stores welcome event records, quest progress and rewards, pending verification records and role-menu definitions.

Built-in services are part of the core platform and are available to every server on the shared bot at no cost. A paid subscription, as described in Section 13, adds a custom bot identity, marketplace access and the other Premium features. Service availability and capabilities may evolve as the platform develops.

We continuously develop new features and may modify, add or remove services at any time. Feature availability may depend on your enrolled tier or plan, and specific features become subject to these Terms only when made available to your account. Feature names and capabilities may evolve as the platform develops.

2.2  AI-Assisted Tools

Start Your Server, the Plugin Builder and the Sentinel AI setup use large language models from a third-party AI provider, identified in Section 3.8 of our Privacy Policy, to turn your description into a proposed server design, plugin or moderation configuration. Generated output is a proposal: Start Your Server shows you the changes it would make and applies them only when you approve, the Sentinel AI setup is validated and previewed before it is applied, and the Plugin Builder produces code that must pass the platform validator and your own review before it is committed. You are responsible for reviewing generated output before you apply, publish or rely on it.

AI output can be wrong, incomplete or unsuitable for your community, and the same description can produce different results each time. We do not guarantee the accuracy, quality or fitness of any generated design, configuration or code, and Section 15 applies to it. Subject to the rights of third parties and to our AI provider’s terms, you own the designs and code generated for you, and we do not use your prompts or output to train models. A generated plugin that is published to the marketplace is governed by the Marketplace Developer Agreement like any other plugin. AI features are metered as described in Section 13.9 and are subject to the Acceptable Use rules in Section 10.

3. Plugin Marketplace & Third-Party Plugins

3.1  Marketplace Overview

YourBot hosts a marketplace where third-party developers may publish plugins for use by Server Administrators. Server Administrators choose which plugins to install on their servers. Marketplace plugins go through our review process before publication; however, they are provided by independent developers and not by EmberStream Studio LLC. Server Administrators are responsible for evaluating plugin trustworthiness, reviewing requested capabilities and accepting any third-party plugin terms before installation.

3.2  Third-Party Plugin Responsibilities

Third-party plugins may have their own terms of service and data-handling practices. By installing a third-party plugin, the Server Administrator accepts the plugin developer’s terms in addition to these Terms. EmberStream Studio LLC is not responsible for the behavior, data handling or content of third-party plugins.

3.3  Plugin Sandboxing & Capabilities

All marketplace plugins run in a sandboxed environment with limited, permission-based access to platform features. Plugins must declare the capabilities they require, such as sending messages, reading channels or managing roles. Server Administrators review the requested capabilities before approving installation.

3.4  Plugin Reviews & Ratings

Users may submit reviews and ratings for marketplace plugins. Reviews must be honest and comply with the Acceptable Use provisions in Section 10. We reserve the right to remove reviews that violate these Terms.

3.5  Revenue Sharing

Developers who publish or monetize plugins through the marketplace are subject to the Marketplace Developer Agreement, which governs revenue sharing, payouts, tax reporting and related obligations. It is presented in the developer portal and must be accepted before creating, publishing or monetizing a plugin. If these Terms conflict with the Marketplace Developer Agreement with respect to plugin development, publication, monetization or payouts, the Marketplace Developer Agreement controls for that subject matter.

4. Developer SDK & Publishing

4.1  SDK License

The YourBot SDK (yourbot-sdk) is open-source software provided under the MIT License, and your use of the SDK code is governed by that license. Access to the platform services (the marketplace, publishing pipeline, sandboxed runtime and developer APIs) is a limited, non-exclusive, revocable grant under these Terms and the Marketplace Developer Agreement.

4.2  Plugin Capability System

Plugins must declare all required capabilities at the time of submission. Plugins may not request capabilities beyond what is necessary for their stated functionality.

4.3  Sandboxed Runtime

All plugins execute within a sandboxed runtime environment. Any attempt to escape, circumvent or undermine the sandbox constitutes a violation of these Terms and may result in immediate plugin removal and account termination.

4.4  Publishing Requirements

All published plugins must pass our review pipeline before becoming available on the marketplace. Submissions must include accurate descriptions, complete capability declarations and a privacy disclosure if the plugin collects or processes user data.

4.5  Developer Conduct

Plugin developers must not introduce malicious code, collect data beyond their declared purposes or mislead users about the functionality of their plugins.

5. Custom Bots

5.1  Custom Bot Tokens

YourBot supports running under a custom Discord bot token provided by the Server Administrator, allowing the service to operate under a server’s own bot identity.

5.2  Token Security

You are solely responsible for the security and confidentiality of any custom bot token you provide. EmberStream Studio LLC is not liable for any unauthorized use, compromise or abuse of your bot token.

5.3  Compliance

Use of the custom bot feature must comply with Discord’s Developer Policy and Terms of Service. You are responsible for ensuring that your custom bot meets all applicable Discord requirements.

6. Cross-Server Features & Network Federation

6.1  Group Finder Networks

The Group Finder feature supports network federation, allowing group listings to be shared across multiple participating Discord servers.

6.2  Data Sharing Consent

By enabling cross-server features, Server Administrators consent to sharing listing data (including titles, descriptions, role requirements, server identifiers and the display names of the members who joined a group) with other participating servers. No other member data is shared without explicit configuration by the Server Administrator.

6.3  Network Participation

Server Administrators may opt in to or out of network federation at any time through the web dashboard.

6.4  Ban Sync & Ban Networks

Sentinel can share bans between servers when their administrators choose to. Ban sync works across the servers one owner runs, and a ban network links servers with different owners once each has asked to join and the network’s owner has approved it. A participating server is told that an account is banned on another participating server, with that server’s name and the ban reason, and can flag, kick or ban that account according to the mode its administrator chose. Both features are off until a Server Administrator turns them on and can be turned off at any time.

7. Rate Limits, Quotas & Fair Use

Our services enforce rate limits and usage quotas to ensure fair access and maintain platform stability. Automated actions, API calls and bot commands are subject to per-minute and per-day limits that vary by plan tier. Circumventing, bypassing or abusing rate limits is a violation of these Terms. We may adjust limits at any time to preserve service quality.

8. Eligibility

To use our services you must:

• Be at least 13 years of age, or the minimum legal age required in your jurisdiction to enter into binding agreements.
• Have a valid Discord account in good standing and comply with Discord’s Terms of Service and Community Guidelines.
• Not be located in a country or region subject to comprehensive US sanctions or listed on any US government denied-party list, and not otherwise be barred from receiving services under applicable law.

Server Administrators who configure YourBot represent that they have the requisite permissions within that server to authorize the bot’s functionality and data processing on behalf of their members.

9. Accounts, Access & Server Administration

9.1  Discord Authentication

Access to the YourBot web dashboard is authenticated via Discord OAuth2. You are responsible for maintaining the security of your Discord account credentials. We are not liable for any loss or damage arising from unauthorized access to your Discord account.

9.2  Server Administrator Responsibilities

Discord server owners and administrators who add YourBot to their server (“Server Administrators”) are responsible for:

• Informing server members that YourBot is present and collecting operational data as described in our Privacy Policy.
• Configuring services, plugins and features in compliance with applicable law and Discord’s policies.
• Managing access permissions for the web dashboard and bot commands within their server.
• Any use of the services by members of their Discord server.

9.3  Account Termination

We reserve the right to suspend or terminate access to our services for any server or user at our sole discretion, including for violations of these Terms, without prior notice.

9.4  Termination by You

You may stop using the services at any time by removing YourBot from your server and canceling any active subscriptions through the dashboard. After removal, server data is handled as described in Section 9 of the Privacy Policy (a 30-day grace period, then deletion). Termination does not entitle you to a refund of fees already paid except as described in Section 13.5 or as required by law.

10. Acceptable Use

You agree to use our services only for lawful purposes. The following are prohibited:

• Discord Policy Violations: Using our services in any way that violates Discord’s Terms of Service, Developer Policy or Community Guidelines.
• Reverse Engineering: Attempting to reverse engineer, decompile or otherwise derive source code from our software or services, except to the extent such activity is expressly permitted by applicable law (such as interoperability research permitted under 17 U.S.C. § 1201(f)).
• Automated Abuse: Using scripts or tools to abuse, overload, stress test without authorization, or circumvent rate limits or security features.
• Unauthorized Resale: Reselling, sublicensing or commercially exploiting access to our services without explicit written authorization.
• Harmful Content: Using our services to store, transmit or facilitate content that is illegal, harassing, threatening or defamatory.
• Interference: Taking any action that disrupts, degrades or impairs the integrity or performance of our infrastructure or services.
• Impersonation: Impersonating EmberStream Studio LLC, its staff or other users.
• Data Harvesting: Collecting data from our services in ways not permitted by these Terms or our Privacy Policy.
• AI Feature Abuse: Using Start Your Server, the Plugin Builder or the Sentinel AI setup to generate malicious code or content that violates Discord’s policies or these Terms, or attempting to extract our system prompts or circumvent the safeguards of our AI provider.

11. User Content

11.1  Your Ownership

You retain all ownership rights to content you and your server members create or provide through our services, including Discord messages, configuration settings, ticket content and LFG listing information.

11.2  License to Us

By using our services, you grant EmberStream Studio LLC a limited, non-exclusive, royalty-free license to access, store, process and display your content solely to the extent necessary to provide and operate the services. This license terminates when your data is deleted in accordance with our Privacy Policy.

11.3  Content Standards

You are solely responsible for all content submitted through our services. You represent and warrant that you have all rights necessary to submit such content and that it does not violate any applicable law or third-party rights.

12. Intellectual Property

All software, code, design, logos, trademarks, product names and documentation associated with EmberStream Studio LLC and YourBot™ are our exclusive intellectual property and are protected by applicable law.

Nothing in these Terms grants you any right, title or interest in our intellectual property. You may not use our trademarks, logos or branding without prior written consent. Feedback and feature suggestions you provide may be used by us freely without obligation or attribution.

12.1  Copyright Complaints (DMCA)

We respect copyright and respond to notices that comply with the Digital Millennium Copyright Act, 17 U.S.C. § 512. If you believe content on our services (including marketplace plugins, listings, reviews or other user content) infringes your copyright, send a notice containing the elements required by 17 U.S.C. § 512(c)(3) to legal@emberstreamstudio.com with the subject line “DMCA Notice”. We will remove or disable access to material identified in a valid notice, notify the user who posted it and accept counter-notices under 17 U.S.C. § 512(g). We terminate the accounts of repeat infringers in appropriate circumstances.

13. Fees, Plans & Payments

13.1  Free Plan & Beta Access

YourBot's open beta has ended. The shared bot and all ten built-in services remain available to every server at no cost. Premium features, described in Section 13.2, require an active paid subscription for that server, and Section 13.8 describes how any trial converts to a paid subscription. The AI tools described in Section 2.2 are metered as described in Section 13.9. The Plugin Builder also requires you to hold an active Premium subscription; the other AI tools are available on the free plan. Server configuration and data are retained in accordance with our Privacy Policy while a server is unsubscribed.

13.2  Paid Plans

A YourBot Premium subscription is priced per server and adds, for that server, a custom bot identity (your own bot name and avatar), access to marketplace plugins and any other feature the pricing page marks as Premium. It also gives the account that subscribes the allowance of free Start Your Server designs shown on the pricing page: one allowance for each account, however many servers it subscribes. The allowance is not shared with other people who manage those servers. All ten built-in services remain available with or without a subscription. The price, billing frequency and any trial terms are shown before you subscribe. By subscribing, you authorize us to charge the applicable fees to your designated payment method. Fees are exclusive of taxes unless stated otherwise and any applicable taxes may be added at checkout. If a renewal payment fails we may retry the charge and suspend Premium features until payment is completed. When a subscription ends, the shared bot takes over from the custom bot identity straight away, marketplace plugins on that server stop until you subscribe again and plugin subscriptions tied to that subscription are canceled; the built-in services keep running. Unused free Start Your Server designs stay with your account and can be used again once it holds an active subscription.

13.3  Payment Processing

All payment transactions are processed by Stripe, a PCI DSS-compliant third-party payment processor. We do not directly store, process or transmit payment card data. By subscribing to a paid plan, you agree to Stripe’s Terms of Service.

13.4  Marketplace Purchases

Purchases of third-party marketplace plugins are also processed through Stripe. Plugin developers receive their share of revenue in accordance with the Marketplace Developer Agreement.

13.5  Refunds

We do not offer refunds for partial billing periods unless required by applicable law. For third-party marketplace plugin purchases, you may submit a refund request from your licenses page or the plugin’s page in the dashboard. Requests are reviewed by the plugin developer and are escalated to our staff if the developer does not answer promptly; our staff may review any request and staff decisions are final. Approved refunds are returned to your original payment method and the associated plugin entitlement is revoked. Charges for AI features are handled as described in Section 13.9.

A refund covers the charge it is issued for and does not by itself cancel a plugin subscription. If you do not want a refunded plugin subscription to renew, cancel it as described in Section 13.7.

13.6  Pricing Changes

We may change the price of YourBot subscriptions at any time. The price shown when you subscribe is the price you pay until we change it. If the price of your subscription changes, we will give you advance notice by email or dashboard notification before it takes effect, the new price applies starting with your next renewal after that notice, and if you do not agree you can cancel before the renewal date and you will not be charged the new price. If your subscription is canceled or lapses and you subscribe again, the price in effect at that time applies. Prices for third-party marketplace plugin subscriptions are set by their developers; if a plugin subscription price changes we will give you advance notice by email or dashboard notification before it takes effect, the new price applies starting with your next renewal after that notice, and if you do not agree you can cancel before the renewal date and you will not be charged the new price.

13.7  Automatic Renewal & Cancellation

Paid plans and marketplace plugin subscriptions renew automatically at the end of each billing period (monthly or yearly, as selected at checkout) and your saved payment method is charged the price that applies to your subscription under Section 13.6 until you cancel. You can cancel at any time from the billing page in your dashboard, which opens our payment provider’s self-service portal, or by emailing support@emberstreamstudio.com. Cancellation takes effect at the end of the current billing period and you keep access to paid features until then. We do not charge cancellation fees.

13.8  Free Trials & Beta Access

If you start a subscription with a free trial or beta access that converts to a paid plan, the trial terms and the price you will pay after the trial ends are shown before we collect payment details, and your subscription converts to a paid subscription automatically at the end of the trial unless you cancel before then. Before your trial converts to a paid subscription we send a reminder to your YourBot notifications in the dashboard. If you cancel before the trial ends you will not be charged, and if no valid payment method is on file when the trial ends the subscription is canceled instead of charged.

13.9  AI Credits & Usage-Based Charges

Start Your Server, the Plugin Builder and the Sentinel AI setup are paid for with prepaid AI credits held in a wallet on your account and denominated in US dollars. Credits are bought in packs through Stripe. Before each metered action we show its cost, or the most it can cost, and nothing is charged until you start the action. The Plugin Builder also shows the model in use. Where a hold is placed for the maximum cost, the finished action is charged only for the tokens the model actually used, the unused part of the hold is returned to your wallet. A Start Your Server design that fails is refunded in full, and so is a Sentinel AI setup draft that fails or has nothing Sentinel can apply. A Plugin Builder build that fails before it produces anything is refunded in full; one that stops part-way is charged only for the tokens it used, and its partial work is saved so you can resume it. Our rates include a margin over what our AI provider charges us and may change at any time; the rate that applies is the one shown when you start the action.

We may add a small complimentary credit to a new wallet and may offer some AI features without charge for a period. Complimentary credits and free allowances, such as the free Start Your Server designs included with Premium, have no cash value and may be changed or withdrawn at any time. Purchased credits are not transferable and cannot be redeemed for cash. Credit purchases are final except where applicable law requires a refund; contact support@emberstreamstudio.com if a purchase was made in error.

13.10  Referral Program

While the referral program is running you can share a personal referral code or link. A new customer who applies your code receives the discount shown on the referral page on a monthly Premium subscription, and you receive the reward shown there as a credit toward your own subscription once the referred customer has paid their second monthly invoice. Yearly plans and marketplace plugin purchases are not eligible, each customer can be referred only once and you cannot refer yourself or accounts you control. Referral rewards are capped per month and in total, are reversed if the referred customer’s payment is refunded in full or disputed and are withheld where we detect abuse. We may change the discount, reward and caps or end the program at any time; rewards already unlocked are honored.

A referral counts only if the referred customer has not held a YourBot subscription or trial before and their Discord account is not newly created. To receive a reward you must hold an active paid YourBot subscription of your own when the reward unlocks.

14. Service Availability & Modifications

EmberStream Studio LLC aims to maintain high service availability, but does not guarantee uninterrupted or error-free operation. We reserve the right to perform maintenance, modify or remove features, or suspend the services entirely with reasonable advance notice where practicable. We are not liable for any damages arising from service interruptions.

15. Disclaimer of Warranties

OUR SERVICES ARE PROVIDED “AS IS” AND “AS AVAILABLE,” WITHOUT WARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. Some jurisdictions do not allow exclusion of implied warranties; in such cases, exclusions apply to the fullest extent permitted by law.

16. Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, EMBERSTREAM STUDIO LLC AND ITS OFFICERS, DIRECTORS, EMPLOYEES AND AGENTS SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES (INCLUDING LOSS OF PROFITS, DATA OR GOODWILL) ARISING OUT OF OR IN CONNECTION WITH YOUR USE OF OR INABILITY TO USE OUR SERVICES.

In no event shall our total aggregate liability for all claims exceed the greater of (a) the total fees paid by you to EmberStream Studio LLC in the twelve (12) months preceding the claim, or (b) one hundred US dollars ($100.00).

Nothing in Sections 15 or 16 limits or waives any right or remedy you have under the Michigan Consumer Protection Act or any other applicable consumer protection law that cannot lawfully be limited or waived, and these limitations do not apply where prohibited by law.

17. Indemnification

You agree to indemnify, defend and hold harmless EmberStream Studio LLC and its officers, directors, employees and agents from and against any claims, liabilities, damages, losses, costs and expenses (including reasonable legal fees) arising out of or related to your use of our services in violation of these Terms, content you submit, your violation of applicable law or third-party rights, or actions taken by your server members through features you have configured.

18. Third-Party Services & Discord

Our services operate on and integrate with Discord, Inc.’s platform. Your use of Discord is governed entirely by Discord’s own Terms of Service, Privacy Policy and Developer Policy. EmberStream Studio LLC is not affiliated with, endorsed by or responsible for Discord’s platform. Payment processing is provided by Stripe; your use of Stripe is governed by Stripe’s own terms and policies. Marketplace plugins are developed and maintained by independent third-party developers who are solely responsible for their own products. The AI features described in Section 2.2 are generated with models provided by Anthropic, PBC, and we are not responsible for the availability of that service. Our services also rely on third-party infrastructure providers; we are not responsible for their availability, security or policies.

19. Governing Law & Dispute Resolution

19.1  Governing Law

These Terms, and any dispute arising out of or relating to these Terms or our services, are governed by the laws of the State of Michigan and the applicable federal laws of the United States, without regard to conflict-of-law principles. Subject to Section 19.3, the exclusive venue for any dispute that is not subject to arbitration shall be the state or federal courts located in the State of Michigan, and both parties consent to personal jurisdiction and venue there.

19.2  Informal Resolution

Before initiating any formal legal proceeding, you agree to contact us at legal@emberstreamstudio.com and make a good-faith effort to resolve any dispute informally within thirty (30) days.

19.3  Binding Arbitration

If informal resolution fails, any dispute arising out of or relating to these Terms shall be resolved by binding arbitration administered by the American Arbitration Association (“AAA”) under its Consumer Arbitration Rules then in effect. These Terms evidence a transaction involving interstate commerce, and the Federal Arbitration Act, 9 U.S.C. § 1 et seq., governs the interpretation and enforcement of this Section 19. Any arbitration hearing will be conducted by videoconference or telephone unless the arbitrator determines an in-person hearing is necessary, in which case it will be held at a location determined under the AAA Consumer Arbitration Rules that is reasonably convenient for you. Payment of filing, administration and arbitrator fees is governed by the AAA Consumer Arbitration Rules. Either party may instead bring an individual claim in small claims court if it qualifies. Judgment on the arbitral award may be entered in any court of competent jurisdiction.

19.4  Class Action Waiver

YOU AND EMBERSTREAM STUDIO LLC AGREE THAT EACH MAY BRING CLAIMS ONLY IN YOUR OR ITS INDIVIDUAL CAPACITY, AND NOT AS A PLAINTIFF OR CLASS MEMBER IN ANY PURPORTED CLASS OR REPRESENTATIVE ACTION. BY AGREEING TO ARBITRATION, YOU AND EMBERSTREAM STUDIO LLC EACH ALSO WAIVE THE RIGHT TO A TRIAL BY JURY.

19.5  Arbitration Opt-Out

You may opt out of the arbitration agreement in Section 19.3 and the class action waiver in Section 19.4 by emailing legal@emberstreamstudio.com within thirty (30) days of first accepting these Terms, stating your name, your Discord User ID and that you decline arbitration. Opting out does not affect any other provision of these Terms.

19.6  Severability of This Section

If the class action waiver in Section 19.4 is found unenforceable as to a particular claim or request for relief, then that claim (and only that claim) shall proceed in the courts identified in Section 19.1 rather than in arbitration, and the class action waiver shall not be severed from the arbitration agreement under Section 20. All other claims remain subject to arbitration.

20. General Provisions

These Terms, together with the Privacy Policy and any supplemental terms you accept (such as the Marketplace Developer Agreement), constitute the entire agreement between you and EmberStream Studio LLC regarding the services. If any provision is found invalid or unenforceable, it will be modified to the minimum extent necessary, and remaining provisions continue in full force. Our failure to enforce any provision does not waive our future right to do so. You may not assign your rights without our prior written consent. We are not liable for delays caused by circumstances beyond our reasonable control. By using our services you consent to receive agreements, notices and other communications from us electronically, by email or through the dashboard or our Discord community, and you agree that electronic communications satisfy any legal requirement that a communication be in writing. Sections 11.2, 12, 15, 16, 17, 19 and this Section 20 survive any termination or expiration of these Terms or of your access to the services.

These Terms are written in English. Where we provide a translation it is for convenience, and if a translation differs from the English text, the English text controls to the extent the law allows.

21. Contact Us

For questions regarding these Terms, please contact:

• Legal: legal@emberstreamstudio.com
• General: support@emberstreamstudio.com
• Website: yourbot.gg
• Discord: discord.gg/yourbot

Essential cookies

Set by YourBot itself, needed for the site and dashboard to work or to keep accounts safe, and not subject to consent.

Preference cookies and browser storage

Browser storage entries stay on your device and are never sent to us.

Optional cookies (consent required)

Optional cookies are set only on pages that use our public website layout and only after you accept the consent banner. They are never set if you decline and they never run on dashboard pages. One page shown after sign-in uses the public layout and follows the same choice: the server picker at /start. To withdraw consent, open Manage Cookie Settings on this page and choose Decline, which stops the scripts and removes their cookies.

Optional analytics

We use Google Analytics to understand how our public website is used. The analytics script loads only after you accept the consent banner. If you decline, no analytics script is loaded and no analytics data is collected. If you change your mind, use the Manage Cookie Settings button above: declining removes the analytics cookies and stops collection immediately. Analytics never runs inside the authenticated dashboard. We configure Google Analytics with advertising features disabled and a 2 month data retention period, and Google discards IP addresses from EEA, UK and Swiss visitors before logging. You can also opt out in any browser with the Google Analytics opt-out add-on: tools.google.com/dlpage/gaoptout

We also use the X (formerly Twitter) and Reddit advertising pixels to measure whether our ads on X and Reddit lead to visits to our public website. Like analytics, the pixels load only after you accept the consent banner, never load if you decline and never run inside the authenticated dashboard. To stop them, open Manage Cookie Settings on this page and choose Decline, which also removes their cookies. X and Reddit may also set or read cookies of their own on their own domains when their pixel loads, which can let them connect a visit with an account on their service; those cookies are governed by their policies.

What we don’t use

The authenticated YourBot dashboard does not use tracking or advertising cookies. The only optional cookies are the Google Analytics cookies and the X and Reddit advertising pixel cookies described above: set only on our public pages and only if you accept the consent banner. We do not sell cookie data. The Google Analytics cookies are read by Google Analytics on our behalf and the X and Reddit pixel cookies let X and Reddit tell that a visit came from one of our ads. All of them exist only if you accept the banner.

Controlling cookies in your browser

Every browser lets you block or delete cookies and site data from its settings. Blocking the essential cookies signs you out of the dashboard and stops forms from submitting; blocking the preference entries only means your theme and language are not remembered between visits.

More detail

For the full breakdown of how cookies and storage tie back to your account data, see the Privacy Policy above. For questions about cookies specifically, contact legal@emberstreamstudio.com.