Privacy
Your server data stays with your GuardBot.
This development-preview policy describes the dashboard architecture as implemented. It will be reviewed before public release and updated if the product's data handling changes.
What the website handles
Discord sign-in supplies your Discord user identifier, username, avatar reference, and the servers where you currently have permission to manage the server. The site keeps sign-in state in a short-lived, encrypted, host-only cookie. OAuth access and refresh tokens are not retained after the callback finishes.
Pairing stores only the relationship needed to route an authorized connection: the Discord server identifier, GuardBot installation identifier, pairing owner identifier, reconciliation version, and timestamps. One-time pairing-code hashes exist only until they are redeemed or expire.
What is not stored in the cloud
Configuration, messages, statistics, moderation records, wake history, and dashboard activity are not persisted in the dashboard database, Durable Objects, or the licensing service. Those operational records remain in the database on the machine running GuardBot. Dashboard responses live only in the active browser session and its memory cache.
Connections and infrastructure
Cloudflare runs the website, the minimal pairing database, and a hibernating wake and relay service. The wake WebSocket is a data-free doorbell. A separate short-lived management relay carries authorized requests and responses without persisting their contents, and closes after inactivity or its reconnection grace period. Convex is used for GuardBot licensing only.
Cookies
The dashboard uses a necessary encrypted sign-in cookie and a small theme-preference cookie. It does not use advertising or cross-site tracking cookies. Logging out removes the sign-in cookie; the theme preference can be cleared with your browser's site-data controls.
Control and deletion
Log out to end the website sign-in session. Use the dashboard unpair action or/dashboard unpair in Discord to remove the cloud pairing relationship and revoke local dashboard authority. Removing GuardBot's local database is controlled by the person who operates that installation. See the support page for the current self-service steps.