PodReportBack home
Privacy during beta

How PodReport handles URLs, reports, and emails

This page summarizes the current beta behavior in plain language. It is meant to help you decide what to submit while PodReport is still evolving.

What you submit

When you submit a public YouTube URL, PodReport uses it to fetch video metadata, transcripts, timestamps, thumbnails, descriptions, and other source material needed to generate the report. Do not submit private, confidential, sensitive, or access-restricted videos.

Generated reports are public in beta

Reports are saved to the shared library by default so they can be reopened, searched, and shared. Public report pages are served by PodReport, while direct anonymous database reads are not intended as a public interface.

Account information

Your email address is used for authentication, account ownership, generation consent, bookmarks, viewed state, account requests, and reopening reports connected to your account.

Service providers

PodReport relies on services such as Supabase for authentication and storage, OpenAI-compatible AI generation, Vercel hosting, YouTube metadata/transcript access, and managed transcript fallbacks when needed. Submitted source material may be processed by these providers to generate the report.

Retention and requests

Generated reports and account activity may be retained during beta to keep the library working and debug product quality. Signed-in users can submit account deletion, data export, and report removal requests from the Account & Data page.

Beta expectations

This is an early product. Data handling, retention periods, private report controls, and automated deletion/export flows may change as the service matures.

Simple rule for beta

Use public podcast URLs you are comfortable seeing in a shared beta library. If a video, source, or topic is sensitive, wait until private report controls are available.