The Vault (backups)

The server structure

• Server: name, icon, banner, invite splash, description, system channel, rules channel, AFK channel and timeout, verification level, content filter, default notifications, language.
• Roles: name, colour, icon, displayed separately, mentionable, permissions and position.
• Categories and channels: type (text, voice, announcement, forum, stage, media), name, topic, NSFW, slowmode, bitrate, user limit, forum tags, permissions (per role and per member) and position.
• Emojis and stickers: the files are copied to our storage, because platform links eventually expire.
• Webhooks: name and avatar only, never the token.

The Dispatch.IO configuration

Every server setting: general configuration, enabled modules, logs, welcome and goodbye, anti-raid, banned words, tickets, level settings, reaction roles, temporary voice channels, scheduled polls and giveaways, suggestions, automations, custom commands, message studio, social networks and RSS feeds, linked channels (the groups the server belongs to), bump, music settings.

Channels, roles and emojis used in the configuration are saved by name and position, not by ID: on restore, they are linked to the new channels and roles, even on another server.

Members (checkbox)

For each member: their roles, nickname, XP and level, and ongoing sanctions (timeout, temporary ban). This is what lets the bot give a returning member their roles back.

What is never saved

• messages (including rules posted by hand: create them in the message studio instead, Creation › Embeds or Containers, so their settings are saved and you can send them again);
• invites, integrations, threads and scheduled events;
• history: closed tickets, past sanctions, statistics;
• secrets (API keys, tokens) and payment data.

1. Open Forge › Vault and click Create a backup.
2. Give it a name (by default, the date and time).
3. Choose what it contains: Structure, Dispatch.IO configuration, Members. All three are ticked by default.
4. Confirm. The bot reads the server: a few seconds for a small server, one to two minutes for a very large one.

From Discord, the /backup create [name] command does the same (see Forge commands).

The Vault list shows for each backup: its name, date, origin (manual, scheduled, before a change, anti-raid), what it contains, its size and who created it. The counter at the top shows the slots used ("3/10").

With Basic or Ultimate, the Vault can make backups on its own:

Set it up in Forge › Vault › Settings, under Scheduled backups: turn on the switch, choose the day (Basic) and time, and what the backup contains. Scheduled backups count towards the server's slots: when none are left, the oldest automatic backup is replaced, never a manual one.

With Basic or Ultimate, Forge automatically takes a backup (a snapshot) just before:

• a restore;
• applying a template;
• applying an AI studio result (generation or assistant change).

This snapshot is what the Undo button uses at the end of an application. Without a plan, Forge offers to make a manual backup just before, if a slot is free: accept it, it's your only way to undo afterwards.

With Ultimate, the bot keeps a lightweight copy of the server structure in memory, updated on every channel or role change. When the channel deletion or mass ban anti-raid protection triggers (see Anti-raid and security):

1. the server's state just before the attack becomes a Vault backup, with the "anti-raid" origin;
2. the owner receives a direct message and a notification: "14 channels and 6 roles deleted by X. Restore?";
3. the Restore button opens the list of changes directly, already filled in with what was deleted.

Export: in the Vault list, a backup's ⋯ menu, Export. You download a .dispatch file containing the whole backup. Keep it wherever you like: it stays valid even if you delete the backup from the Vault or the bot leaves your server.

• Without members: the file isn't protected. Anyone can import it, like a template.
• With members: Forge asks you for a passphrase and encrypts the file with it. Without it, nobody can read the file, us included: write it down, it can't be recovered.

Import: Forge › Vault › Import a file, choose the .dispatch file (and type the passphrase if it has one). The backup is added to the server's Vault, on any platform: a file exported from Discord can be imported on Fluxer or Stoat. It takes a slot like a manual backup.

• Encryption: each backup is encrypted (AES-256-GCM) with its own key. Member data is never readable in plain text on our servers.
• Images: emojis, stickers, icons and banners are copied to our storage, so they can be recreated even if their original link is gone.
• If the bot leaves the server: backups are kept 30 days (Free) or 90 days (Basic and Ultimate). The owner gets a message 7 days before deletion. Inviting the bot back is enough to get them back.
• Deletion: the owner can delete a backup at any time (⋯ menu, Delete); it is erased permanently.
• A member's data: a member can ask for their data to be removed from backups, see the privacy policy.

• Restore and apply: put a backup back on the server.
• Dispatch Forge: who can do what, limits per plan.
• Forge commands: /backup create, /backup list, /backup restore.