Privacy policy

Last updated: April 29, 2026

ClipCabinet is a screen-recording tool that turns recordings into structured, searchable context for AI assistants. This page explains what data we collect, why, and where it goes. We’ve tried to write it in plain language; if anything is unclear, email us at the address in your account settings.

What we collect

  • Recordings you start.When you click “Record,” we capture the browser tab you choose (video and audio), upload it to your own ClipCabinet account, and process it on the server. We do not access your microphone, webcam, or screen at any other time.
  • Account info. Your email address and name as provided to our authentication provider when you sign up.
  • The URL of the recorded tab. Captured once at the start of recording so we can later let you filter your library by source domain (e.g., figma.com). Only the tab you choose to record; never anything else you have open.
  • API tokens you generate. Stored as a SHA-256 hash; we cannot recover the plaintext. Used to authenticate the browser extension and any MCP-compatible AI client you point at your library.
  • Comments and tags you add. Whatever text you type into a comment, tag, or rename action.

What we don't collect

  • We do not record any browser tab passively. The extension records only when you explicitly click “Start.”
  • We do not collect your browsing history, page content from tabs you haven’t recorded, or any signals about what you do outside of an active recording session.
  • We do not run analytics, ad-tracking, fingerprinting, session-replay, or any third-party telemetry SDKs.
  • We do not sell your data. We do not share it with advertisers. We do not use it to train any AI models beyond the per-recording processing described below.

Where your data goes

We use a small set of sub-processors to operate the service. Each only sees the slice of data it needs to do its job:

  • Cloudflare R2 — stores your recording files (video, audio, frame thumbnails). Private bucket with access via short-lived signed URLs.
  • Railway — runs the web app, the worker that processes recordings, and the MCP server.
  • Postgres on Railway — stores recording metadata (titles, summaries, transcripts, comments, embeddings).
  • Clerk — handles authentication. Stores your email and any profile info you provide at sign-up.
  • Deepgram — receives the audio track of each recording to produce a transcript. Audio is sent over a secure connection and is not retained by Deepgram for training per their API terms.
  • Anthropic— receives sampled video frames to generate captions, plus the transcript and captions to extract artifacts (URLs, errors, code, tickets) and produce a summary. API requests are not used to train Anthropic’s models per their standard API terms.
  • OpenAI— receives the recording summary, individual transcript turns, and frame captions to produce embedding vectors for search. API requests are not used to train OpenAI’s models per their API terms.

How long we keep it

We keep your recordings, transcripts, and metadata for as long as your account exists. If you delete a recording in the app, the underlying files in storage are deleted on a best-effort basis at the same time. If you delete your account, all associated data is removed.

Your controls

  • Delete a recording from its detail page kebab menu. Cascades to transcripts, frames, artifacts, comments, and the underlying object storage.
  • Disable a public share linkfrom the recording’s share dialog. The link stops working immediately.
  • Revoke an API token from /settings/tokens. Any client using that token loses access immediately.
  • Delete your account by emailing the support address. We will respond within 7 business days.

Browser extension specifics

The ClipCabinet recorder Chrome extension only activates when you click its icon and start a recording. Specifically:

  • The recorder uses Chrome’s standard getDisplayMediaprompt to request access to a tab. You always pick which tab; Chrome shows you exactly what’s being shared.
  • The in-page HUD overlay (pause / finish / discard) is injected into the recording tab so you can control the in-progress capture as you navigate. Injection happens only during an active recording session and is removed when you stop.
  • Locally on your machine, the extension stores your server URL and API token in chrome.storage.localso you don’t have to re-enter them. These values never leave your device except as part of authenticated uploads to the server you’ve configured.

Changes

If we change this policy in a way that meaningfully affects what we collect or who we share it with, we will update the date at the top and notify active users via the email on file.

Contact

For privacy questions, account deletion, or data-export requests, email the support address shown in your account settings.