Railway application logs and Better Stack availability checks are used to operate and monitor the service. Google Analytics 4 measures traffic and acquisition; PostHog EU Cloud measures product funnels, feature use, member adoption, content popularity and engagement. Both services are disabled on staging and remain off on production unless you explicitly accept analytics cookies. PostHog product events are retained for up to 12 months. Cookie names, providers and durations are set out in full in the
Cookie Policy, and your choice can be changed at any time through Cookie settings in the footer.
GA4 and PostHog receive sanitized, query-free route paths. On public sermon or church pages, PostHog also receives the public slug, internal database ID and content type for views, result opens and engagement. Consenting signed-in members are associated in PostHog only with their opaque Supabase account UUID and coarse account, library and newsletter status; administrators are associated only with that UUID and coarse role/status. Finder events record only step completion, outcome and a bucketed result count. Member events record coarse signup, login, verification, activation, section use, save/remove, completion, onboarding, preference-setting, newsletter and deletion outcomes. A save or completion action performed on a public detail page may carry that page’s public sermon or church identifiers. Neither analytics service receives finder answers, raw searches, query strings, hashes, separate sermon-title or church-name fields, scripture or topic values, preacher or denomination data, progress, sermon history, newsletter selections, form contents, email addresses, personal names, IP addresses or error text. PostHog IP capture, autocapture, session replay, heatmaps, surveys, exception capture and performance capture are disabled. PostHog traffic passes through relay.sermonregistry.com but is processed by PostHog as our analytics processor. 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.