Skip to main content

Where data is stored

Video files and information about those videos are stored separately. When investigating a problem, first identify which kind of data you need to inspect.

From video to search data​

videos stores the title, owner, file reference, transcript, processing state, and related metadata. The file itself is not stored in a DB row.

scene_embeddings enables semantic search of transcript segments. The API converts questions into numeric search vectors and finds similar scenes within permitted videos.

Questions and answers​

chat_logs.response stores segments and server-owned sources. retrieved_contexts retains deduplicated scene text and course metadata. Partial stream events are not stored as separate chat records.

The stream's done follows answer persistence. Responses without a course are not saved. Retired evaluation tables retain historical data; no new scores are written.

Other storage locations​

DataStorage or management
Browser login stateBetter Auth session and browser cookies
External API keys saved by usersEncrypted in the database
MCP API keys and OAuthapikey, oauth_*, and related tables
Undelivered jobsexternal_tasks
Worker execution recordsjob_executions
Transcription and visual-cache checkpointsvideo_transcription_* and video_visual_*
Visual caches for uploadsPrivate media/<file_key>.frames-v1.json and .focus-v1.bin objects in R2 / Garage

Related: Data dictionary, ER diagrams, Job delivery and recovery.