Legal

Privacy Policy

Last updated: August 11, 2026

Overview

ChannelPulse ("ChannelPulse," "we," "us") makes a desktop app that transcribes calls in real time, gives you live talking-point suggestions, and runs self-guided mock interview practice. This policy explains what data the app and website collect, how it's used, who we share it with, and the choices you have. It applies to the desktop app (macOS and Windows) and to channelpulse.us.

Plain-language summary: we process what you say and see during a call so the app can transcribe it and suggest what to say next, we store your account, profile, and saved conversations in our database, and we use a small number of named subprocessors (listed below) to do that — we do not sell your data.

What we collect

  • Account & profile: your email address (we use one-time codes, not passwords), and anything you add to your profile — role, background, résumé/files you upload, and personas you create.
  • Audio & transcripts: while you're actively listening in the app, system audio (and your microphone, if you enable it) is captured and sent for transcription. The resulting transcript, and any AI-generated suggested replies, are saved to your account so you can review them later.
  • Screenshots you take: the app can capture a screenshot on request (e.g. to attach context to a question, or to include in a bug report) — this only happens when you trigger it.
  • Practice sessions: mock interview transcripts, your answers, and the scores/feedback generated for them.
  • Billing: your subscription status and plan. Card details are collected and stored by Stripe directly — we never see or store your full card number.
  • Usage & device data: basic product-analytics events (e.g. which features you use), app version, and OS, so we can fix bugs and improve the product.

How we use it

We use the data above to:

  1. Transcribe live audio and generate the suggested-reply/coaching content the app shows you.
  2. Run mock interview practice sessions and generate scores, feedback, and model answers.
  3. Personalize responses using your profile, files, and chosen persona.
  4. Sync your conversations, memories, and settings across devices where you're signed in.
  5. Process payments and manage your subscription.
  6. Diagnose bugs, secure the service, and improve features — using aggregated or de-identified data wherever practical.

We do not sell your personal data, and we do not use your call transcripts to train third-party foundation models — the AI providers we use process requests to generate a response and do not use ChannelPulse customer content to train their own models under our agreements with them.

Recording other people on your calls

This one's on you, not us: ChannelPulse transcribes whatever audio is playing on your device, which usually includes other people — an interviewer, a colleague, a client. Many places require the consent of everyone on a call before it can be recorded or transcribed (sometimes called "two-party consent" or "all-party consent" laws), and rules vary by state, country, and by the platform you're calling on (some video-call terms of service also restrict recording).

You are solely responsible for knowing and following the recording/consent laws that apply to you and for getting consent from other participants where it's required — for example, by telling them at the start of the call that you're using a notetaking tool. ChannelPulse is not a substitute for legal advice on this; if you're not sure what applies to your situation, check with a lawyer in your jurisdiction.

Third parties (subprocessors)

We rely on a small number of specialist providers to run the service. Each only receives what it needs to do its job:

  • Supabase — our database, authentication, and file storage. Your account, profile, conversations, files, and sync data are stored here.
  • Deepgram — converts captured audio into text (speech-to-text and speaker labeling).
  • OpenAI — generates suggested replies, mock-interview questions/scoring, and chat answers from transcripts and your profile/files.
  • Firecrawl — performs web searches and page scraping when a feature needs current information (e.g. researching a company or role).
  • Stripe — processes payments and manages subscriptions. Stripe has its own privacy policy governing the payment details you give it directly.
  • PostHog — product analytics (which features get used, crash/error signals) to help us improve the app.

ChannelPulse is managed-only — there's no option to route your data through your own third-party API keys instead, so this list is the complete set of processors your data can reach through the app.

Privacy Mode

By default, the floating notes window behaves like any other app window — visible in screen shares, recordings, and your dock/taskbar. If you'd rather it not be, turn on Privacy Mode (the eye icon in the window's toolbar, or Settings → Privacy Mode) — it excludes the window from screen shares and recordings, and hides the dock/taskbar icon, for your own personal privacy on your own device. Privacy Mode doesn't change what data is sent to our servers or subprocessors — it only affects what's visible on your own screen to others.

Retention & deletion

We keep your account data and conversation history for as long as your account is active, so you can look back at past calls and practice sessions. You can delete individual conversations, files, and personas from within the app at any time. To delete your entire account and associated data, email us (see Contact below) and we'll process the request within a reasonable time, subject to what we're legally required to retain (e.g. billing records).

Your rights

Depending on where you live, you may have rights to access, correct, export, or delete your personal data, and to object to or restrict certain processing (for example, under the EU/UK GDPR or the California Consumer Privacy Act). To exercise any of these, contact us — see below. We'll respond within the timeframe required by applicable law.

Children's privacy

ChannelPulse is not directed at children and isn't intended for anyone under 16. We don't knowingly collect personal data from children. If you believe a child has provided us data, contact us and we'll delete it.

Security

See our Security page for how we protect your data in transit and at rest, and how to report a security issue.

Changes to this policy

We may update this policy as the product changes. If we make a material change, we'll update the "Last updated" date above and, where appropriate, notify you in the app or by email.