guildsave.app

Security & privacy

What Guild Save stores, what it never stores, and who can see it.

What we store

  • Snapshots: the structure of a server: channels, categories, roles, permission overwrites and settings. Never messages, never member lists.
  • Verifications: the member’s Discord ID, the result and its reasons, a one-way hash of the IP address, the browser’s user agent and the time.
  • Verified members: name and avatar, plus a Discord access token that lets Guild Save add them to a new server if the community moves. Tokens are stored encrypted at rest (AES-256-GCM).
  • Your login: Discord ID, name and avatar, and a session cookie that lasts 14 days.

IP addresses

IPs are never stored in plain text. We keep a one-way hash (SHA-256 with a secret key). It shows that two accounts came from the same connection, but the IP can’t be read back from it. The dashboard never shows IPs or hashes.

Messages

Snapshots never contain messages. For support and abuse cases our team can read channel messages through the bot, only in channels the bot can see. Every access is logged internally with server, channel and number of messages.

Who sees what

  • The owner of a server sees its snapshots, verifications and settings in the dashboard.
  • Other members and other server owners see nothing of it.
  • Our team, for support, abuse cases and running the service.

Deleting data

Delete single snapshots in the dashboard. To delete everything about a server, remove the bot and ask us on Discord: we delete its snapshots, verifications and stored tokens.

Report a security issue

Found a vulnerability? Please tell us privately first, on Discord, and give us time to fix it before going public.