Sayweek Discord bot – for server administrators

This page is for the administrator of the Discord server who approves, reviews or documents the Sayweek bot for an audit. The bot is an idea source of Sayweek: it suggests post ideas from the conversations of a chosen channel, and a person approves them.

What is this bot?

• Its name is Sayweek. It is a real bot user on the server: it shows up in the member list with an “APP” tag and its own role (Sayweek), which you manage like any other role.
• It is Sayweek's own Discord application. The bot token lives on Sayweek's server as a secret environment variable; no token is stored per customer, and we never ask for access to the installing user's account.
• It does not hold a real-time (gateway) connection to Discord: once a day (after 07:00 in the workspace's time zone), or when someone clicks “Run now” in Sayweek, it fetches the new messages of the chosen channels over REST.

Exact permissions

• OAuth2 scope: bot only (no applications.commands, no slash commands, no identify or guilds).
• Permissions integer: 66560 = View Channel + Read Message History. Nothing else.
• Not requested: Send Messages, Manage Messages (delete), Manage Channels, Manage Roles, Kick / Ban, Moderate Members, Manage Webhooks, Mention Everyone, Administrator.
• Privileged intents: Message Content only – without it, Discord gives apps empty message text. The Server Members and Presence intents are not used.
• Installation uses an OAuth2 code: the server the bot was added to is taken from Discord's token response, not from the browser's address bar.

What it reads – and never reads

• Only the channels picked in Sayweek (at most 5), and only messages sent after the moment they were picked – never older history.
• One run looks at new messages of the last 14 days at most, at most 300 messages per channel.
• It skips: messages of bots and webhooks (Sayweek's own notifications too), system messages, messages of excluded users, messages with excluded keywords or built-in sensitive words (contract, price, salary, health, legal matters, password…), and spoiler (||…||) parts.
• It never reads: direct messages, other channels, the member list, profiles, roles or presence, voice channels, and it never downloads attachments.
• It never writes to the server, never reacts, never deletes and never mentions anyone.

What reaches the AI

• The message text is anonymised on Sayweek's server first: the names of authors and mentioned people, user names, the server's name and client names are replaced by placeholders; e-mail addresses, links, phone and account numbers and street addresses are masked; mentions and channel references are removed.
• Only this anonymised text of at most 300 characters and the date are sent to the AI model (Anthropic Claude) – no message id or user id.
• The finished idea is checked again: if it contains a known name, contact details, an address, an amount or a verbatim quote of a message, it is dropped.
• Nothing is published automatically: every idea goes to the Sayweek ideas list, where a person reviews it, and only an approved idea becomes a post.

What is stored, and for how long

• The id and name of the server and of the picked channels, the id of the last processed message per channel (so nothing is read twice), the exclusions and the numbers of the last run.
• Message text is not stored. Only the finished, anonymised idea, with the original message's link and day (the link only opens for people who can see the channel on the server).
• Discord ideas nobody reviewed are deleted after 30 days. On disconnect, every unreviewed idea from the server is deleted at once; posts already approved stay.
• The data is kept in the EU (Frankfurt); adding the connection, saving channels and exclusions, and disconnecting are recorded in Sayweek's activity log.

Limiting it to one channel

The bot only reads the channels picked in Sayweek, but you can also lock the others in Discord, so the permission itself covers one channel only:

• Server Settings → Roles → the Sayweek role → Permissions: switch off View Channel (the role then sees no channel by default).
• The chosen channel → Edit Channel → Permissions → Add members or roles → Sayweek → View Channel and Read Message History: allowed (green tick).
• If a category or channel is private, give the Sayweek role the same explicit permission there – without it the bot has no access, and Sayweek shows a “the bot can't see the channel” error.
• Check: in the channel's Permissions page (advanced view), only these two permissions are green for the Sayweek role.

Removing it

• In Sayweek: Settings → All integrations → Discord → “Disconnect”. The bot then leaves the server by itself (unless another Sayweek workspace reads the same server).
• In Discord: Server Settings → Integrations → Sayweek → Remove; or right-click the Sayweek bot in the member list → Kick. The bot then sees nothing, and Sayweek reports an error on its next run.

Audit and logging

• Discord's audit log (Server Settings → Audit Log) shows who added the bot and when (“Bot added”), the creation of its role, every permission change and the removal.
• Reading (fetching messages) does not appear in Discord's audit log – Sayweek shows it on the connection's “Last run” line (how many messages were read, how many became ideas).
• For your records: application name Sayweek, scope bot, permissions integer 66560, privileged intent: Message Content, processor: Sayweek (with Anthropic as a sub-processor) – details on the sub-processor list at sayweek.com.
• Once the bot is in more than 100 servers, Discord grants the Message Content intent only to verified apps after a separate review – if it is missing, the bot gets empty text and Sayweek reports it as an error.

This description as a PDF, for your audit records