Privacy Policy

Audio recordings and transcripts

When a Game Master uses the session-recording feature, an audio file is uploaded to a temporary processing location, converted to a text transcript by a third-party speech-to-text provider, and then the audio is permanently deleted from our systems. We do not retain the audio recording. We retain the resulting transcript, associated with the session, for as long as the campaign exists or until it is deleted, and treat it like other text you create in Storywright.

• What we store: the transcript text (and optional timing segments), the session it belongs to, and processing metadata (duration, timestamps). Not the audio.
• Where audio is processed: a transient object-storage location and the speech-to-text provider named below. Audio is deleted from the transient location immediately after transcription, and we direct our speech-to-text provider to delete its copy immediately after transcription as well.
• Retention: audio — none (deleted after transcription; a daily sweep also discards any recording uploaded but never transcribed). Transcript — for the life of the campaign, deleted on campaign or account deletion.
• Training: we do not use recordings or transcripts to train AI models.

Sub-processors for audio and transcripts

• AssemblyAI (speech-to-text), which processes the audio to return text. We direct AssemblyAI to delete its copy of the audio and transcript immediately after transcription, and the account is configured with AssemblyAI's no-training and zero-retention options.
• Anthropic (text drafting), which processes transcript and session text — never audio — when a GM or player asks Storywright to draft a recap, journal entry, or similar text. Anthropic's API terms do not permit training on our data.