Passion Calendar
Last updated 7 October 2026

Privacy policy

This policy describes the personal Passion Calendar bot maintained by Firekat and this informational website.

Data the bot accesses

Why this data is used

The bot uses the permitted Discord data to identify the owner's selected raid runs and their schedule. Calendar data is used to add and update those runs and prevent duplicate entries. The bot does not access Gmail, Google Drive documents, contacts or other Google services.

Processing and third parties

Discord screenshot content and nearby message text are sent to OpenAI's API for extraction. The bot requests that Responses API results are not stored by setting store=false; this does not eliminate any provider retention applicable to API processing. Refer to OpenAI's privacy policy for its practices.

The bot does not send Google Calendar event data or Google authorization tokens to OpenAI. Extracted raid details, character roster evidence and Discord source links are sent to Google when creating or updating calendar events. Visibility of those details follows the owner's calendar-sharing settings. Discord and Google process API requests under their own policies: Discord privacy policy and Google privacy policy.

The bot does not sell personal data, use it for advertising, or use Google user data to train AI models. Its use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Storage and retention

The current deployment stores configuration, authorization tokens, extraction results, synchronization state, previews and logs on the owner's PC. Image bytes are processed in memory; the bot does not intentionally save downloaded setup images to disk. Cached results and logs remain until the owner deletes them. The 14-day catch-up window limits rescanning, not stored-data retention. Calendar events remain in Google Calendar until removed by the owner.

Control and deletion

The owner can stop the bot at any time, remove its Discord channel access, revoke its Google authorization through Google account connections, and revoke the API credentials. Local caches and logs can be deleted after stopping the bot. Deleting local files does not remove calendar events; those must be deleted separately. Deleting synchronization state may cause data to be reprocessed if the bot is restarted.

Security

Credentials are entered locally and are not part of this website or the downloadable unconfigured source package. The owner's local files are not encrypted by the bot itself and must be protected using device security and access controls.

This website

These pages contain no login form, analytics scripts or advertising trackers added by the project. The hosting provider may process request metadata such as IP addresses and browser information for delivery and security.

Contact and changes

For questions or requests concerning data processed by the bot, contact Firekat through the Discord server where the bot is installed. This policy will be updated when the bot's processing or hosting changes.