Trust center
A security bot asks for a lot of permission. This page explains what we do with it: what we store, who can reach it, and what happens when something breaks.
Messages never touch disk
The rebuild cache keeps recent messages in memory only. A restart clears it.
Dashboard follows Discord permissions
You only see servers you own or hold Administrator or Manage Server on.
No public bot API
The bot's API answers only the website, using a shared secret over the server-to-server link.
Signed, httpOnly cookies
Login sessions are HMAC-signed and unreadable to page scripts. OAuth uses a state check.
Humans approve the blacklist
Reports start as pending. Nothing is enforced across servers until our staff approve it.
Every staff action is logged
License issues, moves, revokes and blacklist decisions go to an internal activity log with who did them.
Data we hold
| Data | Why | Where | Kept |
|---|---|---|---|
| Server settings | Run your configuration | Bot database | Until deletion is requested |
| Channel and role snapshots | Rebuild after deletion | Bot database | Until deletion is requested |
| Incident logs | Your forensic history | Bot database | Until deletion is requested |
| Recent messages | Replay into rebuilt channels | Memory only | Until the bot restarts |
| Verification records | Prove who passed the gate | Bot database | Until deletion is requested |
| License records | Billing and support | Bot database | As long as needed for billing |
| Dashboard login | Know who you are | Your browser cookie | 7 days |
We do not store payment card or bank details, and we do not sell or share data for advertising. Full details are in the Privacy Policy.
Infrastructure
- Discord: the bot runs on Discord's gateway and API.
- Bot host: a dedicated game and bot hosting panel (Pterodactyl) runs the bot and its SQLite database.
- Vercel: hosts this website and the dashboard. It holds no database.
- Cloudflare: runs the Turnstile human check on the verification page.
That list is our complete set of subprocessors. Changes are announced in the support server before they take effect.
Reliability
- Snapshots of every channel and role are taken when the bot starts and refreshed on every change, so a rebuild uses the latest version.
- Containment does not depend on the website. If the dashboard is down, the bot keeps protecting servers.
- If the bot restarts, protection resumes as soon as it reconnects to Discord; settings and snapshots survive the restart.
- The bot depends on Discord's API. If Discord itself has an outage, the bot cannot act until Discord recovers.
We do not publish an uptime percentage yet. Outages and maintenance are announced in the support server.
Security practices
- All traffic to the website uses HTTPS.
- Secrets such as the bot token live in host environment variables, never in source code.
- Every dashboard request is checked against the servers your Discord account can manage.
- Verification links are signed to one server and one user and expire after 15 minutes.
- License keys are bound to the buyer's Discord account and shown masked on the dashboard.
- Inputs are validated on the bot side, not only in the browser.
Found a vulnerability? See the Security Policy.
Incident response
If we confirm a security incident that affects your data, we notify affected server owners through the support server and, where we can, by direct message, as soon as possible and within 72 hours of confirming it. The notice says what happened, what data was involved, and what we are doing about it.
Your requests
Server owners can ask us what data we hold for their server, or ask us to delete it. Anyone can ask what we hold about their own Discord ID. Open a ticket in the support server; we verify that you own the server or the account before acting.