Effective August 11, 2026

Privacy, kept local.

RecapShare Capture records the current browser tab with editable interaction metadata or a user-selected screen, window, or tab as video.

Data the extension processes

During an active recording, the extension processes the selected source's video and optional shared audio, optional microphone narration, and optional separate camera video. Current-tab mode can also process before/after click screenshots, sanitized page title and URL, pointer and interaction coordinates, viewport dimensions, navigation and key actions, and limited metadata about interacted elements. Screen, window, or tab-picker mode records video without page-element metadata.

Data the extension excludes

Typed form values are excluded by default. If the user explicitly enables “Record what I type,” change events may include up to 200 characters from non-password fields. Password values are never captured. The extension does not collect full DOM snapshots, browsing activity outside the recording, advertising identifiers, analytics, or telemetry.

Storage and transfer

Capture data is stored locally using Chrome extension storage and IndexedDB. For signed-in users, a ZIP package including screen video and any selected camera video is automatically synced to the configured HTTPS RecapShare server after recording stops unless the visible Auto-sync setting is turned off. A user can also use Sync now from review. A sync never deletes the local recording.

Account data

When a user chooses Connect with RecapShare, Chrome opens RecapShare's normal authorization page and uses the user's existing RecapShare browser session. The extension receives only a short-lived, one-use authorization code and exchanges it for RecapShare-specific access and rotating refresh tokens. It does not collect, store, or transmit a RecapShare password, and it does not access browser cookies, Chrome profile identity, or Google account data. Tokens, the returned account record, server URL, and last selected destination are stored locally so the user can remain connected. Authentication can be removed using Sign out.

Each installation creates a random local installation ID and a readable browser/platform label, such as “Chrome on Windows · A1B2C3.” This is not a hardware serial number or advertising ID. It is sent to the configured RecapShare server during target lookup and capture delivery so the source device can be identified, valid same-name destinations can be distinguished, and uploads can be audited.

Retention and deletion

Local recordings remain until the user clears the extension's data or removes the extension. Account tokens remain until sign-out, expiration, browser-data clearing, or extension removal. On sign-out, local tokens are removed immediately and the extension asks RecapShare to revoke the related token family when online. Downloaded files are controlled by the user. Server-delivered packages follow the RecapShare service's retention process.

Sharing and sale

RecapShare Capture does not sell personal information, use recording data for advertising, share it with unrelated third parties, or use it for eligibility decisions. Its use of information received from Google APIs follows the Chrome Web Store User Data Policy, including Limited Use requirements.

Security

The extension contains no remotely hosted executable code, CDN, analytics, or telemetry. Local files inherit the security of the user's browser profile and device, and transfers use HTTPS. Its one-time browser-session connection uses Chrome's Identity API and a short-lived PKCE authorization code; it never requires cookie access. Users should only record information they are authorized to capture.

Contact

For questions about RecapShare Capture or this policy, contact RecapShare at recapshare@fractionate.ai.

The public version of this policy is available at privacy-policy.recapshare.com.