Data CCapture processes
When the user explicitly starts a recording, CCapture can process:
- the selected tab, window, or screen video;
- optional tab/system audio, microphone audio, and camera video;
- normalized click positions;
- scroll activity, page path changes, focused element bounds and generic roles;
- modifier-based keyboard shortcuts such as Ctrl+C or Command+Shift+P;
- the recorded tab's page title and sanitized hostname/path, without query strings or URL fragments;
- project titles, editing decisions, presets, and exported video settings;
- optional subtitle text generated by Chrome's on-device speech recognition from a local project audio track.
CCapture does not record typed values, password values, clipboard contents, cookies, the Chrome browsing-history database, DOM text, authentication tokens, or unmodified keystrokes. It processes only the current recorded page's title, sanitized hostname/path, and route-path changes as described above; it does not read previously visited pages from Chrome history.
Storage
Media is stored in the browser's Origin Private File System. Project metadata is stored in IndexedDB and preferences are stored with chrome.storage.local. Recording status uses chrome.storage.session.
Nothing is uploaded by this open-core release. CCapture makes no analytics or telemetry requests. Exported videos leave browser storage only when the user downloads them.
Automatic captions set processLocally=true. Chrome may download a language pack when the user requests it, but CCapture never enables cloud recognition and never sends project audio or recognized text to a remote service.
Retention, sharing, and access
Projects remain on the user's device until the user deletes them in the project library or removes the extension's site data. Deleting a project removes its IndexedDB document and associated OPFS media after confirmation.
CCapture does not sell, transfer, or share project data with the developer, advertisers, data brokers, analytics providers, or other third parties. Because there is no backend, the developer and other humans cannot access locally stored recordings or project metadata. A user can choose to share a downloaded export independently of CCapture.
Permissions
- activeTab and scripting: collect privacy-safe interaction positions only in the tab the user chose to record.
- tabCapture: record the selected active tab after a user action.
- offscreen: keep local tab media recording alive after the popup closes and host Chrome's getDisplayMedia() screen/window selection through the DISPLAY_MEDIA reason.
- Camera and microphone permission is requested only after a click in CCapture's compact local device-setup window. Its camera preview and microphone level are not stored; all temporary tracks stop when the window closes.
- sidePanel: optionally show a camera monitor beside current-tab recordings. It never requests device permission; its low-resolution preview stream is not stored and stops when monitoring ends.
- storage and unlimitedStorage: preserve local projects.
- downloads: save an export chosen by the user.
CCapture does not request permanent access to all websites.
Chrome Web Store Limited Use
CCapture's use of information received through Chrome extension APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. User data is used only to provide the extension's disclosed single purpose: recording and locally editing a user-selected source into a product-demo video. It is not used for advertising, profiling, credit assessment, or any unrelated purpose.
User control
The project library shows locally stored recordings and their approximate size. Deleting a project permanently removes its IndexedDB document and OPFS source files after confirmation.
For privacy or security questions, open an issue in the project repository used to distribute your build.