thrumeContact the operator
Thrume is operated by Antler Digital. Contact team@antler.digital about privacy or your information.
What this notice covers
This notice covers the Thrume website, beta applications, accounts, Mac recorder and hosted recording service. When an organization records or shares information about you, it also decides why to capture that content, whom to invite and who may view it. Contact that organization about its recording decisions. Use our privacy contact above for questions about Thrume’s handling of information or help identifying the appropriate workspace contact.
Applications, accounts and service messages
We use your name, email address, workspace or company name, selected use case and optional application notes to verify your email, review the application and communicate the decision. We also keep verification and delivery metadata, the administrator’s decision, and the version and timestamps of verified agreement acceptance. Account, workspace, membership and invitation information supports sign-in, recorder connection and access control. The beta sends verification, application-received, administrator-review, approval and decline messages as applicable.
Recording content and debugging evidence
The service stores and delivers the content your workspace creates or enables: screen video, selected audio or camera content, screenshots, captured debugging events, transcripts, summaries, titles, comments and annotations. Debug sources are selected during recording and can include browser console events, supported request metadata, selected application logs, log files and command output. Recordings and logs can contain information about other people. Choose sources carefully and review content before sharing. Redaction of some credentials and URL values does not guarantee that all sensitive information has been removed.
Recording access and viewing activity
New recordings begin as private drafts. Workspace membership, project permissions and guest-link settings determine later access. People allowed to manage a recording can view activity such as opens, playback, watch time, watched portions and completion. Signed-in viewers may be identified by name. Guest activity is displayed as Anonymous viewer and can use a browser identifier specific to the recording to recognize return visits; that display label does not mean no activity is recorded. A recipient can forward a guest link, so review its expiry, audience and whether logs are included.
Voice enhancement on your Mac
Voice enhancement runs locally on your Mac. Optional Voice+ downloads model files from Hugging Face, which receives the network request needed to deliver those files. That model download does not upload your recorded audio to Hugging Face. An enhanced recording can subsequently upload to Thrume for playback and sharing, according to your recording workflow.
Thrume-hosted AI
Hosted transcription, summaries and suggested titles are off until a workspace owner or administrator enables them. When enabled, relevant audio and recording evidence can be sent to Cloudflare Workers AI. Depending on the requested feature, this can include transcripts, screenshots and selected logs. New published recordings may process automatically after opt-in. Turning hosted AI off stops new requests and cancels queued or running transcription and summary jobs. A provider request already sent may finish, but a cancelled job cannot save new output or start follow-up AI processing. Output saved before opt-out remains in the recording unless separately removed.
External assistants and MCP
MCP uses separate authorization. An approved client can retrieve evidence permitted by your account and request supported frame or clip processing. The assistant and its provider handle what they retrieve under their own terms and settings. Revoking the connection stops future authorized access; it cannot retract content already retrieved. Connecting an external assistant does not enable Thrume-hosted AI. Review the assistant provider’s policies before authorizing a client.
Service providers and technical information
Thrume uses Cloudflare infrastructure for hosting, application data, media storage, processing and transactional email, and Cloudflare Workers AI when hosted AI is enabled. Optional Voice+ downloads contact Hugging Face. External MCP clients are selected and authorized separately. These services receive the content or technical information needed for their part of the workflow. Requests carry technical connection information such as an IP address. Thrume also keeps connection, authorization, security, abuse-prevention and operational records needed to run and protect the service. Contact the privacy address above for questions about provider arrangements relevant to your workspace.
Cookies and browser storage
Thrume uses cookies for sign-in and authorization and browser storage for preferences and recording viewing activity. Clearing sign-in cookies signs you out. Clearing browser storage resets saved preferences and a guest viewing identifier; it does not delete records already stored by the service.
- The __Host-thrume-login cookie protects a sign-in attempt for up to 10 minutes.
- The __Host-thrume-session cookie maintains a browser session for up to 12 hours and is removed on sign-out.
- The __Host-thrume-consent cookie protects MCP authorization for up to 10 minutes and is cleared after consent completes.
- Motion, display and recording preferences remain in browser storage until changed or cleared.
- The guest viewing identifier is specific to a recording and persists in that browser without a built-in expiry until its storage is cleared. If browser storage is unavailable, identification is limited to the page visit.
Recording expiry and deletion
A recording’s video expiry is shown in the app and is separate from the duration of beta account access. Expiry can stop video playback while non-video evidence remains. Deleting a recording removes access through Thrume, revokes its guest links and starts cleanup of associated content. Physical cleanup can take additional time. The service retains limited recording, deletion and audit records so that deletion can be tracked and removed content is not inadvertently restored. This does not delete your Mac’s local copy or copies already held by recipients or external assistants.
Other records and requests to remove information
Application, decision, agreement-acceptance and email-delivery records are currently retained to administer the beta and record access decisions and agreements; they do not currently have an automatic purge schedule. Account, viewing, authorization, security and support records support operation of the service and investigation of issues. Contact us to request review or removal of information you no longer need us to hold. We assess the request in the context of your identity, workspace authority, security needs and applicable requirements. Cleanup of infrastructure records or backups may follow separate provider processes. We do not treat removal of a browser identifier or revocation of access as deletion of stored information.
Your controls and privacy requests
You can manage sharing and authorized assistant connections in the app. Workspace owners and administrators control hosted AI. Use the privacy contact above to ask about access, correction, deletion or a copy of personal information, or if you cannot use the product controls. Depending on the law that applies, you may also have rights to restrict or object to processing, withdraw consent where processing relies on consent, or complain to a relevant regulator. We may need information to verify identity or identify the responsible workspace before handling a request. Include only what is needed to explain the request; never send passwords or sign-in codes.
Support correspondence and changes to this notice
When you contact support, we use the information you provide to investigate your question and respond. Review any screenshots, recordings or logs before sending them. We identify the effective date and version of this notice. Material changes to how the beta handles information will be communicated to affected account emails. The archived publication linked to an application acceptance preserves the notice presented at that time.