How privacy actually works here

Local by default

When you record with the browser extension, the video is written directly to your computer — in your browser’s local storage. It is never sent to a server as part of recording. When you stop recording, the extension opens a local editor page that reads the video straight from your device — there is no upload step involved in that handoff. On a shared computer, takes you make while signed in stay with that account. Guest takes (made while logged out) stay visible only while you are logged out, until someone attaches them to an account.

No account required for editing

The editor works without signing in. Trimming, cutting sections, adding text overlays, and exporting a finished file all happen in your browser. Captions and music mixing also stay on-device — they are included on Pro and Max. You can use the editor and download your video without ever creating an account.

Explicit upload

The only way a recording leaves your device is if you click Share in the editor. That action is the sole trigger for uploading — nothing is uploaded automatically when you record, save, or export. If you’re not signed in yet, clicking Share will ask you to log in or create an account first; the upload only happens after that.

User-controlled sharing

Once you choose to share a recording, you control exactly who can access it:

• Share links are private links only you can generate — never something anyone could guess or find.
• You can require a password before anyone can view the recording.
• You can set an expiration date after which the link stops working.
• You can choose whether viewers are allowed to download the file.
• You can revoke a link at any time, immediately disabling it.

No accidental indexing

Shared recordings are links you send to someone. The page is marked so search engines don’t index it, and there is no public directory of shared recordings.

Chrome extension

The extension injects the recorder overlay into the http(s) page you are on, writes WebM to this browser’s origin-private file system, and opens the editor without uploading. Tab capture may use a capture handle so RecBaba can attach cursor effects to the tab you picked. Nothing in that path leaves your device.

Data deletion

You can delete an individual recording at any time — this removes the file from storage immediately, not just the entry in your recordings list. You can also delete your entire account from Settings, which deletes every recording you’ve uploaded, removes brand-kit logos from storage, and ends all of your sessions. For technical and abuse-prevention reasons, a short grace period applies to full account removal before the record of your account itself is permanently erased.

Accounts and Google Drive

You can sign in with Google or with an email and password. Google sign-in identifies you; we never store your Google password. Email and password accounts store a one-way hash of the password, never the password itself. Saving a recording to Google Drive is a separate, explicit action that asks for a narrow permission (access only to files this app creates in your Drive). The file is uploaded from your browser to Google; we never receive a copy. We store an encrypted Drive refresh token so we can mint a short-lived access token in your browser when you save. It is never used to browse or read your existing Drive files, and disconnecting it revokes that access with Google and deletes the stored token.

AI after Share is a later choice

Recording, editing, and on-device captions never send audio to a transcription API. After you click Share, Generate AI on Pro+ sends extracted audio from that uploaded file to a speech-to-text provider (OpenAI by default, Groq as a configured fallback). Summary and chapters, on Pro and Max, are written from the ready transcript and use monthly AI minutes. You can hide the insights card on a link. Editor captions remain a separate, on-device tool.