Chrome Web Store Policy

PRIVACY POLICY

This policy applies to LensFlow Companion and the associated LensFlow dashboard.

Effective date

June 6, 2026

LensFlow Companion is built to record, relay interactions, and export recordings. It is not designed to collect data for advertising or resale.

Collect

Authentication, capture, and local project data.

Product operators and service providers that run the app.

Delete

Local data stays until you clear it or remove the extension.

Details

WHAT THIS EXTENSION DOES WITH DATA

This policy covers extension-to-dashboard sync, recording state, optional companion media, local storage, and the third-party services used by the deployment.

What We Collect

Account information you provide when you sign in or sign up through the site or dashboard, such as your name, email address, and authentication state.
Recording and capture data needed to run the extension workflow, including tab and window selection, capture mode, recording state, screen and tab media, optional camera and microphone media, and related session identifiers.
Interaction data that the extension relays during recording, such as pointer movement, clicks, normal form typing, focus events, and rrweb session events when the Pro workflow is active. Password fields and obvious authentication, payment, and one-time-code inputs are excluded or masked before capture.
Technical and operational data such as extension version, protocol version, side panel sizing, permission state, local error state, and browser-generated identifiers needed to keep the dashboard and extension in sync.
Local project data stored in browser storage, including IndexedDB, local storage, and extension storage used for transfer and persistence.

Why We Collect It

To provide the LensFlow Companion recording workflow, including capture startup, recording control, interaction relay, and export handoff.
To let the dashboard and extension stay synchronized while a session is active.
To process and debug capture, import, and export failures.
To maintain local project state and improve reliability for recording and editing features.
To enforce product rules, permissions, and access controls where needed.

Who Receives It

The extension communicates with LensFlow-controlled services when you use the dashboard, sign in, submit the waitlist, or use server-assisted export features.
Depending on the feature path you use, data may be processed by service providers that operate the product, including hosting, authentication, billing, waitlist, and export infrastructure.
Those providers may include Google Chrome, Clerk, Vercel, Stripe, Redis, and RunPod or equivalent infrastructure providers used by the deployment.
We do not sell extension data and do not use it for third-party advertising profiles.

Retention And Deletion

Local project data remains in your browser until you delete it, clear site data, uninstall the extension, or overwrite it with new work.
Temporary transfer records such as `lensflow_transfer` are removed after the studio imports them.
Companion media stored in IndexedDB is kept only until it is imported or explicitly deleted by the workflow.
If server-side export or account data is enabled for your deployment, retention follows the operational need to deliver the feature and troubleshoot failures, plus any legal or accounting obligations that apply.

Your Choices

You can choose not to grant camera, microphone, screen, or tab permissions. If you do not grant them, the related recording features will not work.
You can remove the extension or clear browser storage to delete locally stored data.
You can stop using the dashboard or sign out to end active account sessions.