thrumeCapture is a choice.
Choose your screen/window and optional microphone/camera. Debug sources require explicit setup and selection. Review visible screen content and logs for sensitive information; capture controls are not a guarantee that every secret will be removed.
Storage and enhancement are different.
Recordings upload to cloud storage for playback and sharing. Voice cleanup runs on your Mac. Optional Voice+ model files download from Hugging Face; that download does not send your recorded audio there. Hosted transcription and external assistant access are separate choices.
Choose the audience.
Workspace membership, project access and guest links serve different audiences. Review the sharing settings and whether debugging logs are included. Revoke links that are no longer needed.
Understand viewing activity.
People permitted to manage a recording can see opens, playback and watch time. Signed-in workspace viewers may appear by name; guests appear as Anonymous viewer. Guest viewing uses a browser identifier specific to that recording, which remains until browser storage is cleared. The guest label does not mean no activity is collected. Clearing browser storage does not delete activity already saved by Thrume.
Enable hosted AI deliberately.
Hosted AI starts off. A workspace owner or administrator can enable it in Settings → Workspace, allowing relevant audio and evidence to go to Cloudflare Workers AI for transcription, summaries and suggested titles. New published recordings may then process automatically. Turning it off cancels queued/running jobs; a request already sent may finish, but cancelled jobs cannot save new results. Previously saved results remain. Local voice enhancement and connecting MCP do not turn hosted AI on.
Know where assistant context goes.
MCP sends authorized evidence to the client you approve. Its provider’s processing and retention policies apply to the exported content. Disconnecting prevents future access but does not remove copies already retrieved.