Messages
The text of a message is encrypted with AES-256 before it is stored, using a key that is kept separately from the database. Embeds, poll text, forwarded messages and attachment names are stored without that encryption, and so is the log history. See behaviour for how long each is kept.Files
Copies of attached files are compressed where that helps, then encrypted with AES-256 before they are stored. Each file has its own key, derived from the file’s Discord IDs and size. The key is not stored with the file. Files are held with an object storage provider that deletes every file after a fixed time. A copy is also deleted as soon as the log that contains it has been delivered. The code that stores and encrypts files is open source: quark-bot-discord/file.Logs on the web
The log viewer shows text and file names only. Deleted files are re-posted to your Discord log channel and are never served from quark.bot. Opening a log loads embed images, stickers and emoji from Discord’s servers. Images hosted elsewhere are not loaded.Who can see your data
- In Discord: whoever can see your log channels. That is up to you.
- On the web: people who manage the server in Discord, and anyone they have given dashboard access. Every change to that list is logged.
- Through the API: anyone holding one of your server’s API tokens. Create them only when you need them, and revoke them from Settings when you do not. See the API reference.
Services that receive message data
- PluralKit: only if you turn on PluralKit Compatibility. The ID of a deleted message is sent to PluralKit to check whether it was proxied.
- Discord: logs are delivered to the channels you choose.
- An object storage provider: holds the encrypted copies of files.