ZoomCast Privacy Policy

Last updated: July 5, 2026

ZoomCast is a screen-recording and video-editing tool that runs entirely in

your browser.

What we collect

Nothing. ZoomCast has no servers, no accounts, and no analytics.

Recordings, webcam video, microphone audio, and edits are stored only in your browser's local storage (IndexedDB) on your device. They are never uploaded anywhere. Deleting a project (or the extension) deletes the data.
Click and cursor positions captured during a recording are used solely to direct camera zooms and generate step guides, and are stored with the project on your device.
Exports are saved directly to a location you choose on your computer.

Auto-captions (optional): if you enable "Auto-captions from narration" while recording, speech recognition is provided by your browser (Chrome's Web Speech API). Depending on your Chrome version and language, Chrome may process that audio on Google's servers under Google's privacy policy. Disable the toggle on the record screen to keep everything on-device.
AI voiceover (optional): text-to-speech runs entirely on your device. The first use downloads the open-source Kokoro voice model (~90 MB) from the Hugging Face CDN; that download contains no data about you or your recording, and your script never leaves your machine.
AI assist (optional, off by default): the "Write script with AI" and "Publish kit" buttons send text metadata only — the labels and timestamps of elements you clicked, and your caption/transcript text — to Anthropic's Claude API, using an API key you create and paste in. Your video, audio, and screenshots are never sent. The key is stored only in your browser's local storage and requests go directly from your browser to Anthropic (no ZoomCast server exists). Anthropic processes those requests under Anthropic's commercial terms. If you never connect a key, no AI requests are ever made.

Pro license check: activating a Pro key (and a weekly background re-check) fetches a static revocation list from demotonight.com so leaked keys can be disabled. The request contains no personal data, no usage data, and no information about your recordings — and if the list is unreachable (offline, blocked), your license keeps working.

Access to websites (<all_urls> host permission): used solely to inject the click logger *into the single tab you choose to record, only while recording* (and re-inject it if that tab navigates mid-recording). No script runs on any other page or at any other time. It does not read page content, form values, or browsing history.
Tabs / scripting / storage: used to open the recorded tab, start the logger, and save your projects locally.

Questions: bknn0922@gmail.com