Privacy policy

EpisodePilot is a remote recording studio for podcasts and video interviews. This page explains what we collect, why, who else handles it, and how to remove it.

What we collect

• Account: your name, email address and a hashed password; the workspaces you belong to and your role in each.
• Recordings: the audio and video each participant records in their browser, the files we render from them, and their transcripts and suggested clips.
• Guests: the display name a guest types and, if the host invites them by email, that address.
• Billing: your plan and subscription status. Card details go straight to our payment processor; we never see or store them.
• Courses (EpisodePilot Academy): the courses you enroll in, your progress in each lesson (position, completion, playback speed), and which course steps you have done in the product (for example “show created”), so a lesson can mark itself done when you actually do the step. Course purchases, when offered, are processed by our payment processor like any other payment.

YouTube

EpisodePilot uses YouTube API Services so a workspace owner or admin can publish a recording or clip to their own YouTube channel. By connecting a channel you agree to the YouTube Terms of Service. Google's handling of your data is described in the Google Privacy Policy.

When you connect a channel we request two permissions: to upload videos (youtube.upload) and to read your channel's name and ID (youtube.readonly), so the app can show where your videos will go. We store the channel ID, the channel name and the access tokens Google issues. Tokens are encrypted at rest and never sent to your browser. For each video you publish we keep the title, description and privacy you chose, and the YouTube video ID and link so you can open it; every day we check with YouTube that the video still exists and drop the link if it does not.

We do not read, analyse or store anything else from your YouTube account, and we do not share YouTube data with anyone. The channel name is refreshed from YouTube every day.

Removing access: press Disconnect in Settings; we revoke the tokens at Google immediately and delete them, the channel details and the video IDs and links at once; the titles and descriptions you wrote stay as your record. You can also revoke access from your Google account at security.google.com/settings/security/permissions; we detect that within a day and delete the same data then. Deleting data here never deletes videos already on YouTube.

Who else handles your data

We use these providers only to run the service:

• Cloudflare R2 stores recordings and exports.
• LiveKit carries the live call between participants and records a backup of it into our storage.
• Stripe processes payments.
• Resend delivers invitations, reminders and billing emails.
• Google (YouTube) receives the videos you choose to publish.

Transcription runs on our own server; recordings are not sent to a third-party AI service. We show no advertising and no third party serves content in the app.

Cookies and browser storage

We set the cookies needed to sign you in and protect the sign-in form, and one measurement cookie of our own, described below. While a participant records, the browser keeps the recording in its own storage (IndexedDB) until the upload finishes, so a dropped connection loses nothing; the result of the tech check is kept for the browser tab (session storage) so it is not repeated. We use no advertising cookies and no third-party analytics. Choosing a language on the Academy pages sets a small ep_lang cookie with just that choice.

Measurement cookie (ep_aid): a random identifier, signed so it cannot be forged, kept for 90 days and renewed when you visit. It lets us know which page, link or campaign brought a visitor (for example a course link shared on Instagram) and, if you later create an account or sign in, connect those visits to it. We record the page, the campaign tags in the link, the website you came from (its name only, not the full address) and whether you use a phone, tablet or computer. Measurement never stores your IP address (it is held for about a minute only to limit abusive requests), we do not fingerprint your device, and we share none of this with anyone. It is never set on guest recording pages. Visits not linked to an account are deleted after 12 months; measurement events after 24 months.

Your choice: measurement is on. Don't measure my visits — this removes the cookie now and remembers the choice (in an ep_consent cookie) for a year.

Keeping and deleting data

Recordings stay until a workspace owner or admin deletes them; deleting a recording deletes its files from storage. To delete your account or a workspace and everything in it, contact us below. Deleting an account also removes its link to any measured visits and to course progress.

Contact

Questions about this policy or requests to access or delete your data: hola@episodepilot.app.