tabCapture
Captures the tab, window, or screen once you start a recording. Only active while recording.
Effective and last updated July 28, 2026.
Click & Record is built so your recordings never have to leave your computer. This page explains, plainly, what the extension and this website store, where it stays, and the two specific, user-initiated cases where anything crosses the network.
chrome.storage.sync is never used.Everything Click & Record creates is stored locally, inside your browser profile, using standard web storage — the same storage any website uses, just scoped to the extension. Nothing here is synced by Chrome, and nothing is sent to a server we operate, because we don't operate one.
| Data | Stored in | Leaves your device? |
|---|---|---|
| Recording video/audio (screen, tab or window, plus mic and webcam if enabled) | IndexedDB (demo-recorder database) | No |
| Click positions and timestamps (drive the automatic zoom) | IndexedDB, inside the recording record | No |
| Subtitles (on-device transcription output) | IndexedDB, inside the recording record | No |
| Network requests & console messages (optional QA capture, off by default) | IndexedDB, separate log store | No |
| Webcam overlay clip (if enabled) | IndexedDB, separate store | No |
| Recording name, subtitle model choice, other preferences | localStorage | No |
| In-progress recording & permission state | chrome.storage.session / chrome.storage.local | No |
| Light/dark theme choice for this website | localStorage, scoped to clickandrecord.tech only | No |
Subtitles are generated by a Whisper speech-to-text model running inside the browser via WebAssembly (ONNX Runtime). The model is configured with remote model loading disabled, so once the model files are cached locally, transcribing a recording involves no network request at all — your audio is never uploaded anywhere, including to us, to generate captions.
If you click Save to Drive, Click & Record asks you to sign in with
Google and requests the drive.file scope — the narrowest scope
Google offers. It only grants access to files the extension itself creates; it
cannot see, list, or modify anything else already in your Drive. The upload goes
directly from your browser to Google — we don't operate a server in the middle
and never see the file ourselves. Once a recording is in your Drive, Google's own
privacy policy governs it from there.
Click & Record's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Chrome requires every extension to declare, up front, everything it can access. Here's what each one is for.
tabCapture
Captures the tab, window, or screen once you start a recording. Only active while recording.
scripting
Injects the click listener into the page you're recording, so a click can trigger a zoom. Runs only on tabs you're actively recording.
webRequest
Powers the optional network-log feature used for bug reports. Off by default — nothing is read unless you turn on QA capture.
storage
Lets recordings, logs, and preferences persist in the browser instead of memory that disappears when a tab closes.
offscreen
Runs the recording, compositing, and transcription pipeline in a hidden document — Chrome doesn't allow that work directly in the background service worker.
identity
Used only if you click "Save to Drive." Otherwise it's never invoked.
Access to all sites
Required by Chrome for tabCapture, scripting, and webRequest to work on whichever page you choose to record — there's no fixed list, since you can record anything.
Recordings and logs stay in your browser's local storage until you remove them — by deleting the recording in the editor, clearing the extension's site data in Chrome, or uninstalling the extension. There's no cloud copy for us to separately retain or delete, because we never receive one. If you saved a copy to Google Drive, deleting it there is handled through Drive itself.
Click & Record is not directed at children under 13, and we do not knowingly collect information from them. Since the extension doesn't collect information from anyone in the first place, this is largely academic — but we state it plainly.
If this policy changes, we'll update the date at the top of this page. Material changes — anything that changes what's collected or where it goes — will be reflected here before they take effect.
Questions about this policy or how Click & Record handles data can go to privacy@clickandrecord.tech.