Safety & Privacy
Safety & Privacy
How Cubevate keeps you, your keys and your community safe. And what is still up to you.
You are the developer
Cubevate is a tool. You, the person who builds, runs and shares a bot, are the developer and are responsible for what it does. Make sure your bot follows the Discord Developer Terms of Service, the Discord Developer Policy, the Discord Terms of Service and the Community Guidelines, plus the rules of every server it joins. Cubevate does not host, run, monitor or control your bot. The full Terms of Use are on the Cubevate download page (open “Terms of Use and Liability Disclaimer”).
The Safety Center
The Safety page checks your blocks for things that could hurt people or break Discord’s rules, like open ban buttons, mass private messages, scam-like text and risky code. Warnings are marked serious, be careful, or good to know. It only warns. It never stops you, and its warnings are not legal advice.
Good habits for moderation bots
- Warn first, punish second. Give a clear reason in every kick, ban and time-out (it shows in the server’s audit log).
- Only let moderators start moderation blocks. Use Is allowed to… or Has a role.
- Tell people the rules and how to appeal.
- Never DM people who did not ask. Never mass-DM.
- Test first with Pretend mode in Live mode.
- Never ask for passwords, tokens or payment details. Never pretend to be Discord.
- Only keep the personal information you really need.
Your secret key
- The key you paste on My server goes only to Discord (discord.com) and stays on your computer.
- It is never saved inside your bot file, backups, share files or template files, unless you choose to put it in the download zip.
- Only tick Remember my bot’s secret key on your own computer. You can press Forget it in Settings, Data & backups at any time.
- Only use bot keys. Never use a personal account key. That is against Discord’s rules.
- If a key leaks, press Reset Token on the developer page right away.
Files from other people
Bot files, templates, looks and backups are read as plain information and rebuilt from scratch. Anything unknown is thrown away.
- Look files can only change colours, sizes and fonts. Their custom CSS stays off unless you switch it on.
- Custom code blocks inside a bot file are never run just by opening the file. You get a warning first, and nothing runs until you start the bot or a live test yourself.
- The Cubevate page is only allowed to talk to Discord (when you use My server or Live test) and to Google Fonts (if you pick a font). The browser itself blocks everything else.
Careful: Even so, read a template before you use it. A template made by someone else can contain blocks that kick, ban, send private messages or run code.
What Cubevate stores
Your bot, looks and settings are saved automatically on your computer (in the desktop app, in your own user folder on this computer; in a browser, inside the browser). Nothing is sent to any Cubevate server. See the Privacy Policy for the website itself.
What the Dashboard keeps
The Dashboard tabs keep their data on your bot’s host, in hidden memory boxes (their names start with an underscore). Server stats are only counts: how many people joined or left and how many messages were written, never what was written. Giveaways and polls keep who joined or voted on your host only, and only your key can read them. Mod log notes are private to you. The Mod log reads your server’s audit log, so give your bot the View Audit Log permission only if you want it. Closing a ticket from the Dashboard deletes the channel, so Cubevate asks you first. The Economy and Achievements pages keep coins, shop items and badges in your bot’s memory on your host. Welcome, roles and custom command settings are kept there too. Levels and XP, the Invite tracker (invite link names, join times and who invited whom), the list of what the bot did, your notes on memory boxes and the command settings are kept in the same way. The Invite tracker needs the Manage Server permission. All of it is included in Backup & restore, and none of it is sent to Cubefem.