Privacy & Data Handling
How Chronicle handles your data — what's collected, stored, and how to request deletion.
Overview
Chronicle is designed with a simple data philosophy: collect only what's needed, process it, and give you control.
For the complete legal document, see our Privacy Policy.
What Chronicle Collects
During Recording
When you start a recording with /start-session, Chronicle captures voice audio from the channel. This audio is:
- Transcribed into text using AI speech-to-text
- Analyzed to extract campaign entities (NPCs, locations, quests, etc.)
- Deleted — raw audio files are not stored permanently
Campaign Data
Chronicle stores the structured results of its analysis:
- Campaign names and metadata
- NPC, location, quest, and item entries
- Session summaries and transcripts
- Relationships between entities
- Player-provided details (via commands)
Discord Metadata
Standard bot interaction data:
- Server (guild) ID
- Channel IDs used with Chronicle
- User IDs of command users
- Command inputs
Third-Party Services
| Service | Purpose | Data Shared |
|---|---|---|
| OpenAI | Transcription & AI analysis | Audio (transcription), text (analysis) |
| Notion (optional) | Wiki sync | Campaign entities and summaries |
Data Storage
- All campaign data is stored in PostgreSQL databases
- Data is scoped to your Discord server — other servers cannot access it
- We use encrypted connections and standard security practices
Data Deletion
You can request deletion of all data associated with your server:
- Email our support address (listed on the Support page) with subject "Data Deletion Request"
- Include your Discord server (guild) ID
- We will delete all associated data within 30 days
Alternatively, open a ticket in our Discord support server.
What Chronicle Does NOT Do
- ❌ Store raw audio permanently
- ❌ Record without explicit
/start-sessioncommands - ❌ Share data between Discord servers
- ❌ Sell or monetize your data
- ❌ Use your data for advertising
- ❌ Train AI models on your campaign data