Skip to main content
Privacy Policy

How information is handled in the sermon archive

Misppelled Ltd operates Sermon Registry and is the data controller for personal data processed through it. This notice explains what we collect, why, the lawful basis for each use, which production providers support the service, and the rights you hold.

Who we are

Sermon Registry is operated by Misppelled Ltd (“Misppelled”, “we”, “us”, “our”), a company registered in England and Wales under company number 17447906. Misppelled Ltd is the data controller responsible for personal data processed through the Sermon Registry service. Sermon Registry is a trading name of Misppelled Ltd, not a separate company.

Our registered office is shown on the legal information page. Privacy enquiries and requests about your data can be sent to [email protected]. We have not appointed a Data Protection Officer, as we are not required to.

Information we collect

We collect information submitted through the authenticated sermon importer, church listing, church correction and sermon report forms. A sermon submission privately records the submitting account's opaque user ID in the sermon's source metadata; that ID is available to administrators for provenance and is not displayed publicly or copied onto the church profile. A member may separately store a private discovery profile containing an intended use, up to three topics, a language, format, time preference and optional public church identifier. If private progress is explicitly enabled, we also store bounded reading or playback progress and completion timestamps. If you explicitly choose email updates, Resend stores your confirmed account email address, independently chosen email categories, and any church, denomination, sermon topic, language or location preferences you provide. If a church administrator adds money to their church's balance or spends it, we also hold the billing records described under Church balances and payments below.

Our lawful bases for using your data

Under the UK GDPR we must have a lawful basis for each thing we do with personal data. Ours are:
  • Contract — creating and running your member or church-administrator account, storing My Library and your saved items, doing the paid work a church asks for (such as importing, clipping and translating sermons), and sending the transactional emails the account depends on.
  • Consent — analytics cookies, session recordings and click tracking, newsletter categories and preferences, optional private progress tracking, and sending a question to Ask Reg. Each is off until you switch it on, and you can withdraw at any time without affecting anything we did before you withdrew.
  • Legitimate interests — keeping the service secure and free from automated abuse, monitoring errors and availability, maintaining the public directory, counting page views as anonymous totals for church reports, counting anonymous page visits without cookies when you reject analytics, and contacting churches about their listing. We balance these against your rights, and you can object at any time.
  • Legal obligation — keeping unsubscribe and suppression evidence so we can show that an opt-out was honoured, and keeping billing and payment records for tax and accounting.

Sermon submissions

When a signed-in member submits a public YouTube sermon URL through My Library, the URL and importer-generated sermon data are stored in the directory database. The same source, content, duplicate, caption and transcription checks used by the administrative YouTube importer run once before editorial review. Approved sermon content is published publicly and may be indexed by search engines; the submitting user ID remains private. Submissions may be corrected, rejected or removed during review.

Published content is public

Published sermon entries and church listings are publicly accessible. Preacher names, church names, scripture references, tags, and other metadata included in published entries are visible to visitors and may be indexed by third-party search engines.

Logs and analytics

Google Cloud application logs and Better Stack availability checks are used to run and monitor the service. For analytics we use Google Analytics 4 (GA4), which shows us how many people visit and where they come from, and PostHog, on its EU Cloud, which shows us how the site is used so we can fix what is confusing or broken. Neither runs on our staging site. Nothing is measured until you make a choice on the cookie banner, and you can change that choice at any time with Cookie settings in the footer. Cookie names and how long they last are listed in the Cookie Policy.
  • If you accept — GA4 and PostHog record the pages you visit, where you came from (the referring website and any campaign tags in the link, such as utm_source), and how fast pages load (Core Web Vitals). PostHog also records what you click, including repeated “rage” clicks and clicks that do nothing, builds heatmaps of where people click and scroll, notes when you leave a page, and makes a screen recording of your visit. Anything you type into a form is always hidden in recordings, and on account and admin pages all text is hidden in recordings and the labels of what you click are not sent. PostHog keeps a profile for each visitor under a random ID; when you sign in, that profile is linked to your account’s ID number (your Supabase user ID) and coarse status, such as whether My Library is switched on. GA4 is given the same account ID so it can count one person across devices. Your approximate location (such as country and city) is worked out from your IP address, but PostHog does not store the address itself.
  • If you reject — GA4 and Trustpilot do not load, and no analytics cookie or ID is saved on your device; only your choice itself is remembered. PostHog still counts the visit anonymously: which pages were viewed, how long they stayed open and how fast they loaded. To tell one visit from the next without a cookie, PostHog’s servers use a one-way code made from your IP address and browser details that changes every day, so a visitor cannot be followed from one day to the next. There are no recordings, no click tracking and no profile. We rely on our legitimate interest in knowing how many people use the site for this counting, and you can object to it by emailing us.
  • Trustpilot — on the live site, accepting also loads Trustpilot’s review-invitation script (invitejs.trustpilot.com), which lets us invite churches to review Sermon Registry. Trustpilot receives your IP address and browser details when it loads, as any website does; we do not send it any account, page or search information.
  • What is never sent — page addresses reach both services without their query string or the part after “#”, so the words of a search in the address are not sent. Neither service is sent the contents of forms, finder answers, email addresses, names, your progress or listening history, newsletter choices, or error messages. When you arrive from a link we tagged ourselves, such as a church website’s sermon box or one of our emails, only which kind of link it was is sent.
PostHog events are kept for up to 12 months and screen recordings for up to 30 days. PostHog traffic passes through relay.sermonregistry.com but is processed by PostHog as our analytics processor. Our own devices are left out of analytics altogether. When a search returns no results, we separately record only an anonymous keyed fingerprint, broad length and filter categories, and an aggregate count for up to 90 days; we do not store the search words, IP address, account, browser details, cookies, or result identifiers.

Natural-language search

If you explicitly use natural-language search or the optional text field in Find a Sermon, the words you enter are sent to Anthropic solely to interpret them as bounded archive filters. Sermon records, candidate results and transcripts are not sent for this purpose, and the model does not choose or rank results. Structured quiz choices and standard keyword or filter search do not use Anthropic. The optional text is not stored in a member discovery profile.

Ask Reg

If Ask Reg is available and you choose to use it, you first confirm, with a box that is not ticked for you, that your question will be sent to two providers. Your browser remembers that confirmation, and you can withdraw it at any time on the Ask Reg page or here.
  • What is sent. The words of your question go to Voyage AI (part of MongoDB, Inc.) to turn them into a search, and, with up to eight matching passages from published sermons, to Anthropic, whose Claude model writes the answer. Your name, email address, account and IP address are not sent to either.
  • What we keep. Nothing of the question or the answer. We keep daily totals of questions and their cost for 14 days, and for each answer a cost record (the tokens used, the price and how long it took) with the rest of our AI cost records. Our server logs note only which kind of answer was given, how many sermons it drew on and how long it took. To limit how often one person can ask, we count questions against a one-way hash of your IP address, or against your member account, for no more than a day. The text of Ask Reg is hidden from analytics clicks and screen recordings.
  • What the providers keep. Anthropic deletes API inputs and outputs within 30 days and does not use them to train its models; it may keep them for up to two years if its automated systems flag them under its Usage Policy, or longer where the law requires. We have opted out of Voyage AI using what we send for training, and with that opt-out Voyage AI deletes the text immediately after it has been processed.
  • Lawful basis. Your consent (UK GDPR Article 6(1)(a)). A question about faith can reveal your religious beliefs, which is special category data, so we rely on your explicit consent for that too (Article 9(2)(a)). Please don’t include names, health details or anything else that identifies you or another person.

Church balances and payments

Churches can use Sermon Registry free of charge, and pay as they go for some work from a prepaid balance, as described in the prices on our Manage a Church page. Only an approved church administrator can add money to a church’s balance or spend it, on behalf of their church.
  • Payments — Stripe processes every payment on its own secure checkout page and shows receipts and invoices on its own billing page. You enter card details directly with Stripe; we never see or store them. We give Stripe the church’s name and the administrator’s email address to create the church’s billing record, and Stripe may collect a billing name and address. Stripe also uses payment data for fraud prevention and its own legal obligations, as described in its privacy policy.
  • What we keep — the Stripe customer identifier, each amount added to the balance and when, any free credit we give, and a record of each piece of paid work (which sermon was imported, clipped or translated, what was held and charged, and whether it was one of the month’s free imports). These records belong to the church’s account, not to an individual.
  • Support messages — when an administrator sends us a support message, we keep it, the administrator’s email address and our replies so we can help.
  • Social clips — when a church pays for clips, and for our own social media, we send the public YouTube link of a sermon, and the part of it to clip, to Opus Clip, which makes short clips from it. No account or personal details are sent.
  • Translations — when a church pays for a translation, the sermon’s published title, summary, key points and transcript are sent to Google Cloud Translation to be translated. No account or personal details are sent.

Page-view totals and church reports

To show churches how their sermons and church page are found, the live site counts page views of public sermon and church pages without cookies or any identifier. For each view we store only a daily total for that page and the kind of site the visitor came from (a search engine, social media, another page on Sermon Registry, typed in, or another website) — never the address of that site, your IP address, your browser details or your account. So that one visitor refreshing a page is not counted repeatedly, your network address is turned into a one-way keyed value for up to an hour and then discarded; it is never stored with the totals. Views are not counted at all from browsers that send a Do Not Track or Global Privacy Control signal, or from automated crawlers.

Church reports also show totals drawn from My Library: how many times the church’s sermons were saved or marked finished, and how many members saved the church. They never show who did any of these things, and any number from 1 to 4 is shown only as “fewer than 5” so a small total cannot point to a person.

Security and abuse prevention

Cloudflare Turnstile may be used on submission and authentication forms to distinguish legitimate use from automated abuse. Upstash Redis may be used for rate limiting. Client network addresses are validated and converted to a one-way, keyed value before rate-limit storage; raw addresses and challenge tokens are not included in application logs. Security checks may temporarily prevent a submission when we cannot verify it safely.

Error and availability monitoring

Sentry is used for application error and performance monitoring. Request bodies, transcripts, form values, email addresses, cookies, authorisation headers, challenge tokens, and IP-related headers are removed before events are sent. Better Stack checks only public pages and health endpoints. Sentry does not record sessions; the only screen recordings are PostHog's, described under Logs and analytics.

Accounts and transactional email

Member and administrative identities are managed through Supabase. A member can explicitly activate My Library to keep saved sermons, completed sermons and saved churches across devices. A private discovery profile ranks recommendations from the choices the member directly saves. Saved items and partial progress do not influence the order; completed sermon IDs are used only to exclude sermons the member has already finished. Private progress is disabled by default and, when explicitly enabled, supports resume controls and member-owned insights. These records are not public, are never shared with churches as individual records, and are not automatically added to newsletters; a church sees only the anonymous totals described under Page-view totals and church reports. If you accept analytics, PostHog records feature outcomes and screen recordings of account pages, but all text on account pages is hidden in those recordings and the labels of what you click are not sent, so PostHog is not given your discovery choices, private progress, sermon history or newsletter selections. Members can turn progress tracking off, clear activity while retaining saved items, or delete the entire account. Church-management information remains separately collected and administered through the Church Admin account type.

Transactional email

Resend delivers necessary transactional messages through Supabase custom SMTP and the Resend API, including signup verification, password recovery, church-management requests and decisions, sermon moderation outcomes, contextual church corrections and sermon reports, material church-profile changes, and failed YouTube imports. Resend processes the recipient address and limited message content to deliver these emails. Correction and report details are emailed to an approved church administrator when available, otherwise to one of our superadministrators. Church-connection explanations, sermon transcripts and raw processing errors are not included. Transactional recipients are never automatically enrolled in newsletters or added as marketing Contacts. Click/open tracking is disabled.

Prospective-church outreach

We maintain an internal outreach workspace for contacting churches about the directory and inviting an authorised representative to claim or improve a church profile. This is not the newsletter system: outreach history and suppression choices are kept in separate records, and a church contact is not enrolled in newsletter categories merely because outreach has taken place.
  • Where the data comes from — the contact details we hold are collected from the church’s own publicly available website, listing or published directory entry. We do not buy contact lists.
  • What we hold — the church name, a public contact address, the outreach messages sent, and whether the contact asked us to stop.
  • Why we may do this — our legitimate interest in building an accurate public record of preaching and in giving churches control of their own listing. We have weighed this against the recipient’s interests and limited the contact accordingly.
  • Your right to object — you can tell us to stop at any time, by using the unsubscribe option in the message or by emailing [email protected]. We will stop and keep a minimal suppression record so the request is not undone by a later import. You can also ask us to correct or delete the contact details we hold.

Newsletter preferences and consent

The newsletter is currently a waiting list rather than an active campaign. Resend is the sole newsletter record. A member's confirmed account address is added as a Resend Contact only when the member explicitly saves at least one email category in My Library Preferences. Product updates and the future Sermon digest are independent Resend Topics; optional church, denomination, sermon-topic, language and location choices are Contact properties. These are explicit selections and are not inferred from private library activity. Members can change their choices or unsubscribe from everything in My Library Preferences, while email unsubscribe links remain available without signing in. Church-administrator and member newsletter audiences remain separate Resend Segments. Open and click tracking are disabled. No newsletter or marketing campaign is currently sent by this system.

New-sermon emails

On a church or preacher page you can ask to be emailed when that church or preacher has a new sermon. A visitor's request is not stored: we email a signed confirmation link through Resend, and only following that link saves the request. A signed-in member's address has already been verified, so their request is saved straight away. Each saved request holds the email address, the church or preacher it is about, the site language it was made in, and when it was confirmed and last emailed, in a private Supabase table that only our servers can read. Once a day, anyone with a new sermon to hear about receives one email listing them. Every email links to stop that alert or all of them without signing in, and mail apps' one-click unsubscribe works too. These alerts are separate from the newsletter: they never add you to a newsletter category, and stopping them keeps only the stopped record so a later request starts afresh. Open and click tracking are disabled.

Third-party links and media

Sermon Registry links to and embeds content from external platforms such as YouTube, MapTiler, and church websites. Loading or following this content may connect your browser to those providers, which operate under their own privacy policies. YouTube players use its privacy-enhanced domain. Player loading, including as a player approaches the screen, can contact YouTube before you press Play. Automatic watch-progress saving requires your separate activity-tracking choice. Book covers on recommended resources are fetched from Open Library by our own servers, so your browser does not contact Open Library to show them. If you follow a link marked "Affiliate link" to Amazon, Amazon may set its own cookies to record that you came from Sermon Registry; that happens on Amazon's site, under Amazon's privacy notice, and we receive no personal information about you, only a total of qualifying purchases. We do not control the content or data practices of external sites.

Retention

Published directory records are retained while they remain useful to the archive. Private library, preference and progress state is retained until the member clears the relevant record or deletes the account. Find a Sermon keeps structured choices in the visitor's browser for no more than seven days so they can choose whether to import them after signup; the optional free-text answer is excluded. Deleting an ordinary member account removes its Supabase identity and private member state and globally unsubscribes its email address from newsletter categories. Provider suppression and unsubscribe evidence may be retained by Resend in accordance with its service and retention practices. PostHog events, including the anonymous visit counts made when analytics is rejected, are retained for up to 12 months, and PostHog screen recordings for up to 30 days. Anonymous no-result search statistics are kept for up to 90 days. Daily page-view totals are kept for two years. Billing, payment and invoice records, including a church's record of charges, are kept for six years after the end of the financial year they relate to, as UK tax and company law requires.

International transfers

Several of our service providers process data outside the UK, mainly in the United States. Where that happens, the transfer is made under Article 46 of the UK GDPR, relying on the International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses as incorporated into each provider's terms, together with the additional safeguards those providers apply. Providers that may process data outside the UK include Google (Cloud hosting, Analytics and Cloud Translation), Anthropic, Voyage AI, Sentry, Resend, Upstash, Cloudflare, Stripe and Opus Clip. PostHog is used on its EU Cloud infrastructure.

Your rights

You have the right to ask us for a copy of the personal data we hold about you; to have inaccurate data corrected; to have data erased; to restrict or object to how we use it, including any use based on legitimate interests; to receive data you gave us in a portable format; and to withdraw consent at any time where we rely on it. Where the data relates to your account, most of these can be exercised directly in My Library Preferences, which lets you change your choices, clear activity, or delete the account outright.

For anything else, email [email protected] and tell us what you would like. We will respond within one month. Exercising these rights is free, and we will not treat you differently for doing so.

Complaints

If you are unhappy with how we have handled your personal data, please contact us first at [email protected] so we can try to put it right. You also have the right to complain to the Information Commissioner’s Office, the UK supervisory authority, at ico.org.uk or on 0303 123 1113. Complaining to the ICO does not affect any other rights you have.

Correcting or removing published directory entries

This is separate from your rights over your own account data above. If you believe information published in the directory is inaccurate or should be removed, use the contextual correction or report action on the relevant church or sermon page. You may also email [email protected] with details of the entry and the nature of your request.

Changes to this policy

This privacy notice may be updated as the service develops. Significant changes will be reflected on this page and, where they materially affect you, brought to your attention. Last updated: 14 November 2026.

Contact

For privacy-related enquiries, email [email protected]. Misppelled Ltd’s registered details and formal notice address are on the legal information page. See also the contact page.
Guided discovery

Find a sermon for where you are.