Privacy policy
The Daily Bot for Slack. Effective 9 October 2026.
The Daily Bot is run by Lucas Delvoye as an independent project. This page says what the bot stores, why, for how long, and how to get it removed. It is written to be read, not skimmed past.
What the bot collects
- Installation data. When a workspace installs the bot, Slack gives it a bot token, the workspace id, the bot user id, and the id of the person who installed it. The token is what lets the bot post. It is stored and never shown to anyone.
- Channel configuration. For each channel where someone runs
/daily-add: the channel id, the timezone, the schedule and message for each game, when summaries go out, and the id of the person who set it up. - Game results. When someone replies in the thread under one of the bot's daily posts and the reply parses as a result for that game, the bot stores the Slack user id, the display name at that moment, the score, the rarity label, the pasted text, and the time.
- Messages the bot receives but does not keep. Slack sends the bot every message posted in channels it is a member of. The bot looks only at whether a message is a reply in a thread under its own post. Anything else, including every top-level message, every edit, and every reply in other threads, is discarded immediately and never written anywhere. Slash command payloads carry ids and the command text; they are processed and not stored.
- Error reports. When something fails, an error report goes to Sentry, an error-tracking service. Reports can include workspace, channel, and user ids and the error message. They do not include message text.
The bot does not collect email addresses, does not read direct messages, and does not store any message content other than the pasted results described above.
How it is used
Only to run the feature: posting the daily link, recognising results, reacting to them, and building daily, weekly, and all-time leaderboards for the channel they were posted in. Nothing is sold, shared with advertisers, or used to train any AI or language model.
Where it is stored
On servers rented from Railway in the United States, in a Postgres database that only the bot can reach. Traffic between Slack and the bot is encrypted. Error reports are stored by Sentry.
How long it is kept
- While the bot is installed, results and configuration are kept so that all-time leaderboards work.
- When a workspace uninstalls the bot or revokes its token, the token is invalidated immediately and the workspace's configuration and results are deleted automatically 30 days later. Reinstalling within those 30 days keeps the history.
- Error reports expire according to Sentry's retention, currently 90 days.
Seeing, exporting, or deleting your data
Email delvoye02lucas@gmail.com from an address on the workspace in question, or ask the person who installed the bot to do so. You can ask for a copy of what is stored about you or your workspace, have a specific result removed, or have everything for the workspace deleted ahead of the 30-day schedule. Expect a reply within two business days. Workspace admins can also simply uninstall the bot from Slack, which starts the automatic deletion.
Changes
If this policy changes in a way that matters, the effective date above changes and the previous version stays available on request.
Contact
Lucas Delvoye, delvoye02lucas@gmail.com.