Privacy Policy

Scope

This policy describes how the RecordWeb Presentation Cursor Chrome extension handles data while a user records a Google Slides presentation with RecordWeb.

Data the extension handles

• Normalized pointer coordinates and timestamps during an active recording session.
• The Google Slides tab identity and presentation URL or identifier needed to bind RecordWeb to the tab the user explicitly shared.
• A random, opaque Capture Handle used to verify that the browser picker and cursor tracker refer to the same tab.
• Temporary extension connection and tab identifiers needed to start, pause, resume, stop, and finalize cursor capture.

The extension does not read slide text, passwords, form entries, authentication cookies, or a user's general browsing history.

How the data is used

The extension uses tab identity and the Capture Handle to verify the selected Google Slides tab, focus it when recording starts, and provide in-tab recording controls. RecordWeb uses the time-aligned cursor trajectory for playback and to synchronize it with the session's video and audio sources. Participants can export these sources and send them to a research team for human-computer interaction (HCI) analysis.

Storage and transmission

Cursor samples are sent through Chrome extension messaging to the RecordWeb page open in the same browser. The extension itself does not sell the data, use it for advertising, or send it to analytics providers.

RecordWeb stores a completed cursor trajectory locally with the recording. When recording finishes, RecordWeb automatically attempts to upload the recording and available source assets, including the cursor trajectory, to Vercel Blob. Associated recording metadata is stored in Neon Postgres. If the upload fails, the local recording remains available for recovery. Network transfers use HTTPS.

Uploaded files use Vercel Blob public URLs. RecordWeb limits access to recording pages through account permissions, but anyone who obtains a file URL may be able to access that file directly.

RecordWeb does not automatically send recordings to the research team. When a participant exports and sends recording files to the team, researchers may inspect the raw cursor, screen, camera, and audio data contained in those files for the study. That handoff is separate from RecordWeb's automatic cloud save. The study obtains written participant consent separately; RecordWeb does not collect or store that consent form.

Retention and deletion

Temporary tab mappings, Capture Handles, and live cursor samples are held only for the active browser session and are cleared when the session is disconnected, the tab closes, or the extension service worker is reset. Local recording backups remain in browser storage until removed or the browser's site data is cleared. Users can delete uploaded recordings using RecordWeb's cloud recording controls.

Permissions

The extension requests access only to the production RecordWeb website and Google Slides presentation pages. Google Slides access is required to publish the Capture Handle, track pointer movement, and display session controls. RecordWeb access is required to exchange session commands and cursor samples.

Third parties and limited use

Data is used to provide the synchronized recording and HCI analysis workflow described above. It is not transferred for advertising, credit assessment, surveillance, or sale. Service providers process data for RecordWeb authentication, recording storage, and metadata persistence. Participants may separately send exported files to the research team for the disclosed study purpose.

RecordWeb's use and transfer of information handled by the extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Contact

For privacy questions or deletion assistance, contact the developer through the support contact published on the RecordWeb Chrome Web Store listing.