What we keep, and who sees it.

Recaps are reachable by anyone holding their link. Your notes are not. We never see your card. Nothing is sold, and nothing is used to train a model.

A sermon you bring. If you paste a YouTube link we fetch the video’s transcript and its public details — title, channel, publish date. If you upload audio or video, Mux stores the recording and its captions; we keep the recap and transcript. Either way we keep the transcript we produce and the summary, key points, questions and applications generated from it.

An account, if you make one. Your email address, and a password if you set one. You can generate one recap without an account; saving them and generating more needs a sign-in.

What you write and how you file it. Private notes on a recap, your own titles for sermons, the shelves you create, and which shelf a sermon sits on.

A subscription, if you take one. If you subscribe, we store Stripe’s identifiers for the customer and the subscription on your account, plus the plan status. We never receive your card number — that goes to Stripe directly and never touches this server.

Your IP address. Used to enforce one signed-out recap per network, so clearing cookies cannot mint another. The address is stored for that purpose.

Running this site means handing parts of your data to other companies. Each one is listed here because you deserve to know whose hands it passes through:

• Vercel — hosting; sees every request to the site.
• PostHog— product analytics (page views, the subscribe funnel, and a few in-app events). Session replay is off, so a recap page’s transcript is not recorded.
• Supabase — the database and sign-in.
• Mux — ingest, storage, playback, and captions for a recording you upload.
• Supadata — fetches transcripts for YouTube links.
• Groq — transcribes YouTube sermons that have no captions. A different provider can be configured; whoever it is, they receive the audio.
• Anthropic — receives the transcript and writes the recap.
• Stripe — takes payments and holds your card details.
• Trigger.dev — runs the transcription and analysis in the background.
• Resend — delivers the message you send from the contact page.
• Cloudflare— runs the domain’s DNS, and carries that message the last step into the inbox that answers it.

We don’t sell your data, and we don’t share it with anyone beyond the list above except where the law requires it.

This is the part worth reading twice. A recap can be opened by anyone who has its link. There is no sign-in check on a recap page. The address contains a random identifier, so it isn’t guessable. Subscribers can also browse confirmed YouTube sermons on Explore. Uploads and anything that did not pass that check stay at their link only. A link, once shared or pasted somewhere public, works for whoever finds it, permanently, until the recap is deleted.

Treat a recap link the way you’d treat an unlisted video. Your private notes are different: they are only shown to you, unless you deliberately create a share link for them, and revoking that link closes it again.

If you upload a recording of a sermon, remember that the transcript of it is served alongside the recap under the same rule. Uploads are never listed on Explore.

Recaps and their transcripts are kept until they’re deleted. Removing a recap from your library takes it off your shelves but keeps your notes and filing, so re-saving restores them — it is not a deletion. To have the underlying recap, transcript and any uploaded media erased, ask, and it will be.

Stripe identifiers on an account are removed if you ask us to delete the account. Stripe keeps its own copy of the billing history under its own policy.

The IP address stored for the one signed-out recap (the anon_recaps row) is kept until that recap is deleted or you ask us to remove it. Claiming it into an account does not delete the row — it stays so the same network cannot mint another signed-out recap.

Use the contact form and ask for a copy of what’s held about you, a correction, the deletion of your account and its contents, or the removal of a specific recap. No particular wording is needed. Expect a reply within a few days, from a person.

SermonRecap isn’t built or intended for children under 13, and accounts aren’t knowingly created for them. If you believe a child has made one, write and it will be removed.

If this page changes in a way that affects what happens to data already collected, the date above changes with it. Small corrections and clarifications may be made without notice.