Privacy policy.

We collect three categories of information:

• Account data. Your first name, last name, email address, and password hash (or a Google account identifier if you sign in with Google). This is the minimum we need to identify you across visits.
• Session content.The audio, and where you opt in, the video, of each session you record. The transcripts of those sessions, including both your turns and the agent's. The clip-worthy moments the agent captures and any links or notes you paste during a call.
• Usage data. Session count and duration, timestamps, the device and browser you use, and basic diagnostic events from the recording pipeline so we can tell when something fails.

We do not collect anything from your microphone or camera outside of an explicit session you have started. We do not read other tabs, files on your device, or anything in your browser history.

Account data is used to sign you in, keep your sessions attached to you, and bill the right person if you upgrade.

Session content is the product. We use it to generate transcripts, rank clip-worthy moments, build the persistent memory the producer carries across sessions, and let you download or revisit anything from past calls.

Usage data is used to keep the service running, fix bugs, and decide what to build next. Aggregate counts may be reported in public materials. Individual usage is not.

To make myselfpod work we share specific pieces of your data with a small number of vendors, each contractually bound to process it only on our instructions:

• The AI producer voice and conversation logic is provided by our voice-agent vendor. The audio of your calls and the text transcripts pass through their infrastructure to generate the responses you hear.
• OpenAI processes your transcripts to rank clip-worthy moments, generate session titles, and update the memory paragraph the producer reads at the start of each call. OpenAI does not train its models on this data.
• Recordings, transcripts, and exported highlight files are stored in encrypted object storage. Our database vendor holds the row-level metadata that points at those files.
• When you paste a link mid-call, the page at that URL is fetched by a scraping vendor on your behalf so its text can be passed to the agent as context.

We do not sell your data. We do not share it with advertisers. We do not use your session content to train any general-purpose model.

Session recordings, transcripts, and highlights are retained for as long as your account is active so you can return to them. The persistent memory paragraph is editable and deletable from Settings at any time. If you delete a session from your dashboard, the recording, transcript, and highlights are removed within thirty days.

If you close your account, all session content and account data are deleted within thirty days, except for records we are legally required to keep.

Data is encrypted in transit. Recordings are stored in access-controlled object storage. Database access uses short-lived service credentials and never travels through your browser. We follow the principle of least privilege for internal staff: only the people who need to debug a specific incident can read user content, and only with your context.

No service is invulnerable. If we discover a breach affecting your data we will tell you, in plain language, what happened and what to do.

You can:

• View, edit, or wipe the producer's memory of you in Settings → Memory.
• Download every recording, transcript, and highlights file from each session's page.
• Delete a single session from the session page, which removes its recording and derived files.
• Close your account and have everything erased by emailing the address at the bottom of this page.

Depending on where you live, you may have additional rights under your local privacy law (GDPR in the EU, CCPA in California, and similar). We honor those rights for everyone, regardless of jurisdiction. Use the contact email below.

We use cookies for authentication and a small set of local preferences (sidebar collapse state, last-used sign-in method, last-used recording mode). We do not use third-party analytics cookies and we do not track you across other sites.

myselfpod is not directed at children under 16 and we do not knowingly collect personal information from them. If you believe a child has created an account, contact us and we will remove the data.

When we change something material we will update the effective date at the top of this page and email registered users a short summary of what changed. Continued use of myselfpod after the effective date constitutes acceptance of the updated policy.