Clipflow Recorder Privacy Policy

Effective date: July 22, 2026

This Privacy Policy explains how the Clipflow Recorder Chrome extension collects, uses, stores, and protects data when you use it with Clipflow.

Clipflow Recorder is designed for workflow recording. It helps users capture a selected browser workflow and turn that recording into Clipflow videos, help articles, screenshots, guided demos, and step-by-step documentation.

Summary

Clipflow Recorder does not record or upload page content, audio, video, clicks, or DOM data while it is idle.

Recorder data is collected only after you start a recording from Clipflow, grant the required Chrome permissions, and choose what to share in Chrome's native share picker.

When page context capture is enabled, Clipflow Recorder may request access to the selected target site so it can capture click context and page structure during that active recording. You should record only content that you have the right to capture and process.

Data We May Collect During a Recording

During a user-started recording, Clipflow Recorder may collect the following data:

• Screen recording video from the tab, window, or screen that you choose in Chrome's native share picker.
• Microphone audio if you choose to enable microphone capture.
• Page URL, tab title, and browser context for the workflow being recorded.
• Click, scroll, focus, keyboard, form submit, and other interaction metadata.
• Element metadata such as selectors, roles, labels, bounding boxes, text hints, and timing data.
• Page context data when page structure capture is enabled, including DOM snapshots, HTML, visible text, CSS/style references, DOM mutations, canvas placeholders, video placeholders, and open shadow DOM content.
• Technical logs needed to diagnose recording, extension, upload, processing, and reliability issues.

Clipflow Recorder does not intentionally collect this data when no recording is active.

Data We Do Not Intentionally Collect While Idle

When the extension is installed but no recording is active, Clipflow Recorder does not intentionally collect:

• Screen video.
• Microphone audio.
• Click or keyboard activity.
• DOM snapshots.
• Page HTML.
• Page text.
• Form interaction metadata.

The extension may store limited local state in Chrome, such as pending recording requests, preferences, and session state needed to continue a user-started recording flow.

Sensitive Input Handling

Clipflow Recorder is designed to reduce collection of sensitive values:

• Password field values are masked.
• Values that look like bearer tokens, long secret-like strings, email addresses, or payment card numbers are masked where detected.
• When page structure capture is disabled, DOM snapshots and input values are not uploaded as page structure data.

No masking system is perfect. You should avoid recording pages that contain sensitive, confidential, regulated, or third-party personal data unless you have the right to capture and process that data.

How We Use Recording Data

Clipflow uses recording data to provide requested product functionality, including:

• Creating and editing workflow videos.
• Generating help articles, screenshots, guided demos, and step-by-step documentation.
• Linking video moments to clicks, page states, and editable workflow steps.
• Transcribing, summarizing, formatting, and processing recording content.
• Debugging recording, upload, extension, and processing failures.
• Improving product reliability, security, and quality.

Clipflow does not sell recording data.

Clipflow does not use customer recording content to train public foundation models. If Clipflow uses AI services to process a recording, those services are used to provide the requested Clipflow functionality, such as transcription, summarization, documentation generation, and video editing.

When Data Is Collected

Recorder data is collected only when:

• You start a recording from Clipflow.
• You grant the required Chrome extension permissions.
• You choose a source to share through Chrome's native share picker.
• You enable optional page context capture if click and DOM context are needed.
• The recording remains active or is being stopped and uploaded.

The extension may remain installed while idle, but it does not record or upload page content while idle.

Where Data Is Sent

Recording data is uploaded over HTTPS to official Clipflow origins:

• https://www.clipflow.chat
• https://clipflow.chat

Production builds of Clipflow Recorder validate API origins and reject localhost or non-Clipflow API origins.

Chrome Extension Permissions

Clipflow Recorder requests Chrome permissions that support user-started recording workflows.

storage

Stores recorder preferences, pending recording requests, permission flow state, and session state needed to continue an active user-started recording.

tabs

Lists normal HTTP/HTTPS browser tabs so you can choose which tab to record. It also helps focus the selected target tab and send recording status updates back to the Clipflow page.

activeTab

Supports user-initiated access to the active tab when Chrome requires the user to invoke the extension before tab capture can start.

scripting

Injects the recorder content script into the selected target tab after you grant site access. This is used to show the countdown/recording UI, collect active-recording page context, and coordinate stop/upload signals.

tabCapture

Captures a selected Chrome tab video stream after you start a recording and choose a source.

desktopCapture

Opens Chrome's native share picker so you can choose a tab, window, or screen to record.

offscreen

Uses a Manifest V3 offscreen document to manage recording streams and MediaRecorder while the service worker coordinates the recording lifecycle.

optional_host_permissions: <all_urls>

Allows Clipflow Recorder to request access to a third-party target site only when you choose that site for recording. This access is used during active recordings to capture clicks and optional page structure for generating editable workflow steps.

host_permissions

Allows the extension to communicate with official Clipflow web app and API origins:

• https://www.clipflow.chat/*
• https://clipflow.chat/*

Sharing and Subprocessors

Clipflow may use subprocessors to host, store, transcribe, analyze, or process recordings. These subprocessors may include cloud hosting, storage, database, observability, authentication, payment, transcription, and AI processing providers.

Clipflow may disclose data when required by law, to protect security, to enforce agreements, or with your consent. Clipflow does not sell personal data.

Retention and Deletion

Clipflow retains recording data for as long as needed to provide the service, support your workspace, comply with legal obligations, resolve disputes, enforce agreements, and maintain security and backups.

Workspace owners or authorized users may request deletion of recordings and related generated assets. To request deletion or privacy assistance, contact:

support@clipflow.chat

Security

Clipflow uses technical and organizational safeguards designed to protect recording data, including HTTPS transport, API origin validation, Chrome permission gating, access controls, and sensitive input masking patterns.

No system can guarantee absolute security. You are responsible for choosing what to record and for avoiding unnecessary capture of sensitive or regulated information.

Your Responsibilities

You are responsible for ensuring that you have the rights and permissions needed to record a website, product workflow, meeting, screen, audio source, or third-party system.

You should notify participants and obtain consent when required by law, contract, company policy, or platform terms.

Changes

Clipflow may update this Privacy Policy from time to time. Material changes will be reflected by updating the effective date and, where appropriate, by providing additional notice.