What GameMaster processes during tabletop play.

Microphone and voice

The player app asks the host to confirm that everyone at the table agrees before microphone activation. Live microphone audio is sent to configured realtime voice and AI providers so the GameMaster can listen and respond. The app is designed to avoid storing raw audio unless a deployment explicitly adds that capability.

Text, memory, and uploads

GameMaster stores room data needed for play: player labels, transcripts or transcript summaries, campaign memory, uploaded books, indexing status, vector-search mappings, and session metadata. Uploaded books are processed for retrieval inside the owning room.

Providers

Depending on configuration, session data may be sent to providers used for realtime voice, speech, language models, embeddings, LiveKit media transport, and Qdrant vector search. Provider logs and retention are controlled by those providers and the deployment settings.

Adaptive gameplay personalization

When enabled, GameMaster uses ordinary gameplay activity—such as in-game choices, meaningful contributions, scene participation, and interaction with established story elements—to maintain uncertain gameplay-preference hypotheses. It does not use personality tests and is not intended to infer mental health, sensitive traits, intelligence, beliefs, or emotions as facts. Silence is treated as ambiguous and is never sufficient by itself to classify engagement.

Players can disable personalization, exclude a room, minimize transcript excerpts, choose the detailed-observation retention period, export a readable preference summary, reset learned preferences, or delete their stored profile from the play page.

Retention, export, and deletion

Retention is configurable by the deployment. Authenticated players can request export or deletion of account-owned game data. Deletion removes or anonymizes owned rooms, uploads, vectors, memory, logs, and active sessions where the system can safely identify ownership.