Trust

Security at YourBot

Last reviewed July 22, 2026

This page describes the security controls that protect YourBot communities today. It is reviewed after major platform changes. Found something? security@yourbot.gg

YourBot runs third-party code on behalf of your community, so isolation is the core of the design. Marketplace plugins run in locked-down containers, bot tokens are encrypted with per-server keys and every tenant is quota-limited so no one server can degrade another. Everything on this page describes controls that are enforced in production, not a roadmap.

1. Marketplace Plugin Sandbox

Every marketplace plugin executes inside its own Docker container with:

  • No network access. The container is started with networking disabled. All outbound HTTP goes through a platform proxy that enforces an allowlist and per-tenant quotas.
  • A read-only filesystem with a small size-capped scratch space.
  • No root. Plugin code runs as an unprivileged user (uid 65534) with syscalls filtered by seccomp.
  • Hard CPU and memory caps, so a runaway plugin is throttled and killed rather than affecting neighbours.
  • Tenant data isolation. A plugin can only reach the data of the server it is installed on, through the platform API. It cannot read other tenants.

2. Marketplace Review Lifecycle

Publication to the marketplace is gated in layers:

  • Automated checks on every submission. Each version passes a static validator before it can publish. Validation errors block publication for everyone, established developers included.
  • Human review for new developers. A new developer’s plugin is reviewed by a person before it can first reach your server.
  • Trusted publishing for established developers. Developers with a track record who publish from public repositories can release updates without waiting on the queue. Any release that trips a validation warning or changes its dashboard surface is routed back to human review.
  • A kill switch. Any plugin can be disabled platform-wide at once if a problem is reported.

The functional review behind the marketplace quality chip is described on the quality standards page.

3. Bot Tokens and Secrets

  • Custom bot tokens are encrypted at rest with AES-256-GCM using per-server keys and are never displayed back in plaintext.
  • The bot requests only the Discord privileged intents it uses: Server Members and Message Content. The Presence intent is not requested.
  • Service-to-service calls inside the platform are authenticated with HMAC.

4. Platform Isolation and Availability

  • Per-tenant token-bucket quotas and circuit breakers keep one busy server from starving others.
  • Components degrade gracefully: a cache or queue failure falls back rather than taking the bot down.
  • Uptime and incident history are public on the status page.

5. Data Handling

We do not sell personal data, run ads or use dark patterns. What we store, why and for how long is documented in the Privacy Policy, including GDPR export and erasure.

6. Responsible Disclosure

If you believe you have found a vulnerability in YourBot, email security@yourbot.gg with steps to reproduce. We read every report and will respond. Please give us a reasonable window to fix the issue before public disclosure, test only against servers and accounts you own and never run denial-of-service or destructive tests against the live platform.

Machine-readable contact details are published at /.well-known/security.txt.

7. What We Do Not Claim

YourBot has not yet undergone an independent third-party security audit and holds no compliance certifications. The controls above are built, enforced and verified internally against the running platform. When an external audit happens, its scope and date will be published here.