Privacy

Effective August 3, 2026.

This page describes what the hosted Event Scheduler instance, the Discord bot and this website, stores and why. The short version: server settings and Discord IDs, nothing about any person.

What the bot stores

When a server sets up the bot and creates events, the bot keeps in its database:

• The server's settings from /setup: the stream URL, timezone, default event length, and default event title, keyed by the server's Discord ID.
• For each schedule run: the Discord IDs of the source message, the created events, and the published announcement. IDs only. No schedule text, no titles, and no user IDs.

What the bot does not do

• It reads messages only when someone explicitly runs a command on them. There is no passive scanning.
• It stores nothing about any person. Undo and Publish permissions are checked against Discord live, and nothing about who pressed what is kept.
• No analytics, no tracking, no advertising identifiers.
• Nothing is sold or shared with third parties.

Where data lives

In a Cloudflare D1 database as part of a Cloudflare Workers deployment. Cloudflare's infrastructure keeps standard operational logs.

The calendar feed

Each server's feed URL contains an unguessable token, which is the only access control on the feed. The token is derived from a server-side secret rather than stored. Anyone who has the URL can read the server's scheduled events. Share it accordingly.

The website

event-scheduler.com is a static page on GitHub Pages. It sets no cookies, runs no analytics, and makes no third-party requests; the fonts are served from the site itself. GitHub receives standard web server logs when you load it.

Deletion

Undo deletes the events a run created, and the bot prunes its records of events that no longer exist. Removing the bot from a server ends all collection. To have a server's stored data deleted, open an issue on GitHub.

Changes

Changes to this policy will be posted at this address.