Data & permissions

What Calenbot stores and which Discord permissions it uses

This explains what Calenbot needs to work. It is a technical product explanation, not a Terms of Service or Privacy Policy.

Permissions requested when you add the bot

View Channels

Used to copy the channel audience when an event is created. Later channel-permission changes do not automatically change who can view the event.

Send Messages

Used to post event confirmations and reminders.

Server member information

Used to show participant choices, expand roles, and determine event visibility.

When you log in to the web app

Discord OAuth identify and guilds scopes provide your user ID, display name, avatar, server list, and administrator status. Calenbot does not store Discord access or refresh tokens. Web sessions expire after seven days and are deleted when you log out.

Information stored for events and calendar subscriptions

• Event title, description, location, time, and recurrence
• Associated Discord server and channel IDs
• Users or roles selected as participants
• Server member IDs, display names, avatars, and roles used for participant choices (stored in KV for 10 minutes)
• Server member IDs and role IDs used for visibility checks (stored in D1 and updated on the next complete member-list fetch; members confirmed to have left are removed)
• Notification settings and delivery records
• A random personal calendar subscription token

Controls available to you

• Create, edit, and delete events
• Turn server notifications on or off
• Choose servers for your personal calendar
• Regenerate your subscription URL. This invalidates the current URL and any older subscription URLs for individual servers
• Log out of the web console

This page is a technical description of the data and permissions the product currently uses.