Only when you start it
Nothing runs in the background. It acts only after you start a session from the popup, and only in the tab you selected.
Chrome extension · privacy policy
DemoBot Recorder privacy policy
DemoBot Recorder is an optional Chrome extension that records one tab you pick, so you can demo things our cloud recorder can't reach. This page explains exactly what it captures, where that data goes, and what it never touches.
Tab video + step timings
A WebM capture of that tab and a timing manifest of the scripted steps that were replayed.
No tracking, ever
No analytics, telemetry, ads, browsing history, or cookies. No credentials are captured.
Goes to your workspace
Uploads travel over HTTPS to the DemoBot origin you configured, using your own API key.
What DemoBot Recorder is
DemoBot turns a script you write into a narrated product demo video — AI voiceover, music, subtitles, and hosted streaming — from your account at app.getdemobot.com. DemoBot Recorder is an optional Chrome extension (Manifest V3) that moves one step of that pipeline, the screen capture, into your own browser. That lets you record demos of sites our cloud recorder cannot reach: localhost, VPN-only internal tools, sites with bot protection, and pages inside your own logged-in session. Everything else — narration, encoding, and hosting — still happens server-side in your DemoBot account.
This page supplements the main DemoBot privacy policy at getdemobot.com/privacy, which covers your account and server-side data. This page is specifically about the extension.
What the extension collects
The extension does nothing in the background. It only acts when you explicitly start a recording or a planning session from the extension popup, and only in the single tab you selected. While a recording is running, Chrome displays its standard debugging banner on that tab, so you always know it is active.
During a session you started, the extension handles:
- A video capture of the selected tab (WebM), uploaded over HTTPS to your own DemoBot workspace.
- A timing manifest of the scripted interactions that were replayed — clicks, keystrokes of script-defined text, scrolls, and navigation timings.
- Screenshots of the selected tab, during a planning session only, relayed to the DemoBot planning service acting on your behalf.
In Chrome Web Store terms, that is "website content" and "user activity" — and nothing else. Our store data disclosures say the same thing.
What the extension doesn't collect
- No browsing history.
- No data from tabs other than the one being recorded.
- No keystroke logging outside of script replay.
- No analytics, telemetry, ads, or tracking of any kind.
- No cookies read or written by the extension.
- No passwords or credentials. Demo steps that would type credentials are filtered out of extension recordings by design — you record inside your already-signed-in session instead.
What stays on your device
Two things are kept in Chrome extension storage on your own machine: the DemoBot API key you enter, and your DemoBot app origin. They are never transmitted anywhere except to your own DemoBot origin, as an authentication header. Deleting the extension deletes them.
Chrome permissions, and why each one exists
| Permission | Why the extension needs it |
|---|---|
activeTab |
To act on the single tab you selected when you start a session — and no other. |
tabs |
To let you choose which tab to record and to follow navigation timings inside that tab during the session. |
tabCapture |
To record the video of that tab, which becomes the WebM capture uploaded to your workspace. |
debugger |
To replay the scripted clicks, keystrokes, and scrolls precisely and take planning screenshots. This is why Chrome shows its debugging banner while a recording runs. |
offscreen |
To run the capture and encoding work in a background document so the recording is not interrupted by popup or UI changes. |
storage |
To keep your API key and DemoBot app origin locally on your device. |
scripting |
To run the step-replay logic inside the selected tab during an active session. |
| Host access to all URLs | Because your product can live on any domain, including localhost and internal hostnames. The extension still only touches the tab you selected, during an active session. |
What you can turn off, cancel, or delete
- Cancel a recording at any time. Closing the tab or clicking Cancel aborts the capture.
- Delete your videos from your DemoBot account. Deleting a video in DemoBot removes the hosted copy.
- Remove your API key from the extension whenever you like.
- Uninstall the extension. That deletes the API key and app origin stored on your device.
For account and server-side data, see the main DemoBot privacy policy at getdemobot.com/privacy.
Children
The service is not directed to children under 13.
Changes to this policy
If this policy changes, we will update this page and change the effective date at the top of it.
Contact us
Questions about the extension, or about data it captured for you? Write to us and a human will answer.
Email: [CONTACT EMAIL — fill in before publishing]
Main policy: getdemobot.com/privacy
Effective date: 2026-07-27
— same content, markdown
The policy as Markdown.
Identical wording to the page above, ready to paste into a repo, a docs site, or the Chrome Web Store listing notes.
# DemoBot Recorder — Privacy Policy **Effective date:** 2026-07-27 This policy covers the **DemoBot Recorder** Chrome extension. It supplements the main DemoBot privacy policy at https://getdemobot.com/privacy, which covers your account and server-side data. ## 1. What DemoBot Recorder is DemoBot (https://getdemobot.com, app at https://app.getdemobot.com) turns a script you write into a narrated product demo video — AI voiceover, music, subtitles, and hosted streaming. DemoBot Recorder is an optional Chrome extension (Manifest V3) that moves one step of that pipeline, the screen capture, into your own browser. That lets you record demos of sites our cloud recorder cannot reach: localhost, VPN-only internal tools, sites with bot protection, and pages inside your own logged-in session. Everything else — narration, encoding, and hosting — still happens server-side in your DemoBot account. ## 2. What the extension collects The extension does nothing in the background. It only acts when you explicitly start a recording or a planning session from the extension popup, and only in the single tab you selected. While a recording is running, Chrome displays its standard debugging banner on that tab. During a session you started, the extension handles: - A video capture of the selected tab (WebM), uploaded over HTTPS to your own DemoBot workspace. - A timing manifest of the scripted interactions that were replayed — clicks, keystrokes of script-defined text, scrolls, and navigation timings. - During a planning session only: screenshots of the selected tab, relayed to the DemoBot planning service acting on your behalf. In Chrome Web Store terms, that is "website content" and "user activity" — and nothing else. Our store data disclosures say the same thing. ## 3. What the extension does not collect - No browsing history. - No data from tabs other than the one being recorded. - No keystroke logging outside of script replay. - No analytics, telemetry, ads, or tracking of any kind. - No cookies read or written by the extension. - No passwords or credentials. Demo steps that would type credentials are filtered out of extension recordings by design — you record inside your already-signed-in session instead. ## 4. Where captured data goes, and who sees it Captured data goes only to your own DemoBot workspace — the origin you configured in the extension, which defaults to app.getdemobot.com — authenticated by your API key. Server-side, recordings are processed into demo videos and hosted for you on Cloudflare Stream, acting as a processor and CDN. We do not sell your data, we do not share it with third parties for advertising, and we do not use it for anything unrelated to producing your demo videos. ## 5. What stays on your device Two things are kept in Chrome extension storage on your own machine: the DemoBot API key you enter, and your DemoBot app origin. They are never transmitted anywhere except to your own DemoBot origin, as an authentication header. Deleting the extension deletes them. ## 6. Chrome permissions, and why each one exists | Permission | Why the extension needs it | | --- | --- | | `activeTab` | To act on the single tab you selected when you start a session — and no other. | | `tabs` | To let you choose which tab to record and to follow navigation timings inside that tab during the session. | | `tabCapture` | To record the video of that tab, which becomes the WebM capture uploaded to your workspace. | | `debugger` | To replay the scripted clicks, keystrokes, and scrolls precisely and take planning screenshots. This is why Chrome shows its debugging banner while a recording runs. | | `offscreen` | To run the capture and encoding work in a background document so the recording is not interrupted by popup or UI changes. | | `storage` | To keep your API key and DemoBot app origin locally on your device. | | `scripting` | To run the step-replay logic inside the selected tab during an active session. | | Host access to all URLs | Because your product can live on any domain, including localhost and internal hostnames. The extension still only touches the tab you selected, during an active session. | ## 7. Your controls - Cancel a recording at any time. Closing the tab or clicking Cancel aborts the capture. - Delete your videos from your DemoBot account. Deleting a video in DemoBot removes the hosted copy. - Remove your API key from the extension whenever you like. - Uninstall the extension. That deletes the API key and app origin stored on your device. For account and server-side data, see the main DemoBot privacy policy at https://getdemobot.com/privacy. ## 8. Children The service is not directed to children under 13. ## 9. Changes to this policy If this policy changes, we will update this page and change the effective date at the top of it. ## 10. Contact us Email: [CONTACT EMAIL — fill in before publishing]
Record it locally. Ship it anyway.
Localhost, internal tools, logged-in flows — capture them in your own browser and let DemoBot do the narration, encoding, and hosting.