One Small Offering
An empty wooden bench beside a path in a misty wood, morning light behind the trees.

Legal

Privacy Policy — One Small Offering

Version 5.41 · Last Revised: 2026-11-16

Revision history

Every version of this policy, newest first — 26 revisions since 1 October 2026.

Version 5.41 · Last Revised: 2026-11-16

What changed in this version: one addition. Section 2 now ends with a short subsection, 2a, describing what happens when you press the microphone — the recording goes from your browser to our server, which passes it to ElevenLabs to be transcribed and keeps neither the audio nor the words, and ElevenLabs processes the recording on our behalf as a service provider under its own privacy policy. The pointer in Section 1 that referred to this now points at it. Nothing else in this policy is changed.

Version 5.40 · Last Revised: 2026-11-13

What changed in this version: three additions, each describing something this policy did not previously name. Section 1 now describes the one-line question that sits under some Discernment answers — a vote, an optional note of up to 500 characters, and the moment it was sent, with no IP address, no device or browser detail, no session, no identifier, no cookie and no usage-reporting event, and never shown on an answer about a crisis. Section 1 also now describes signing in with Google, which connects a Google account to the optional account only from inside it: the site keeps the Google account's identifier and the email address it gives us, and never a name, a picture, contacts, or a lasting token that could reach your Google account again. Section 4 names one more cookie, oso_internal, which no visitor ever receives — our own testing browsers carry it so that the visits we make ourselves can be left out of the internal figures we read. Everything else in this policy is unchanged.

Version 5.39 · Last Revised: 2026-11-03

What changed in this version: the Discernment page's spoken answer is now free for three conversations on a browser with no account. To count those three, the site keeps one small note about the browser — a random identifier in the site's own cookie, how many have been used, and when — and nothing else: no question, no answer, no transcript, and nothing you said or heard. It is separate from the usage-reporting identifier, it is not stopped by turning usage reporting off, and it is deleted 90 days after the last free conversation, or sooner if you clear this site's cookies. Section 1 gains a row describing it, Section 4 names the cookie, and the places in this policy that said turning usage reporting off stops all counting now say it stops all usage counting. Nothing you type is affected: the typed question and the typed answer stay free, send nothing, and are never stored.

Version 5.38 · Last Revised: October 30, 2026

What changed in this version: our own anonymous aggregate counts can now say which campaign a Discernment submission arrived from. When you reach the site from one of our advertising links, that link can carry three short campaign tags — a source, a medium, and a campaign name — which we keep for the rest of that browser session and attach to the counts described in Section 1, so we can tell which advertisement actually helped someone. The tags are set by us on the link itself, are lowercase slugs of at most forty characters, and never contain anything you typed, the page you came from, or the full address you arrived at; they are held only in that browser session and are cleared when the tab closes. This is the same first-party counting as every other count — on by default, turned off with the same switch in Site Settings — with no third party, no sale, and no sharing. The “Anonymous aggregate usage counts” row in Section 1 now describes them. Everything else in this policy is unchanged.

Version 5.37 · Last Revised: October 29, 2026

What changed in this version: two things. First, the Discernment page now offers an optional star rating just below the question box — one to five stars and, if you want, a short note. It is a separate, consented form: nothing is sent until you tick its consent box, it is unchecked by default, and it never sees the question you typed above it. A rating is kept for up to 90 days, can be deleted at any time with the code shown when you send it, and is read only on an administrator-only screen; nothing from it is ever published. Section 1 gains a row describing it, and Sections 1, 5, and 9 name it where they name the other forms you may choose to send us. Second, this policy now describes the Discernment page's live AI exactly as it works: a strong or close match is answered from our reviewed library and your question is sent nowhere; only a question with no close match goes to Magisterium AI automatically, after you press Submit and with the page saying so beside the box; on a close match the live AI is reached only if you press it; and a crisis-shaped question is sent nowhere. Section 2 is rewritten, and Sections 1, 3, and 4 are corrected to match. No retention changes, no new recipient, and no new kind of data. Everything else in this policy is unchanged.

Version 5.36 · Last Revised: October 29, 2026

What changed in this version: the Discernment page's live AI is now reached automatically only when the reviewed library has no close match. A question that earns a strong or close reviewed answer is answered from our own reviewed library and is sent nowhere, and on a close match the live AI is offered only if you ask for it. The four places in this policy that said “no strong match” now say “no close match,” so this policy describes exactly what leaves your device: the same two labeled paths as before, on fewer questions. Nothing is stored or logged either way, and everything else in this policy is unchanged.

Version 5.35 · Last Revised: October 28, 2026

What changed in this version: the homepage now carries the Virtue Companion, a small card that answers “Where do you need grace in this moment?” with one virtue to consider. The words you type there are matched on your own screen — they are never sent, saved, spoken, or counted, and the companion adds no usage event of its own. Pressing the microphone there sends your spoken words to the same ElevenLabs transcription the Discernment page uses — we retain neither the audio nor the transcript, the microphone is live only between your two presses, and nothing is submitted until you press the companion's own button. Pressing Play on its spoken reflection generates the words through the same read-aloud service, using the site's own words, and neither the audio nor the text is stored or logged. Its two Share controls — “Share Reflection” and “Share as Card” — carry only the reflection's card, which is built from the site's own words (the virtue, the verse, and the small action) and never from anything you typed. Sections 1, 4, and 9 now describe these paths. Everything else in this policy is unchanged.

Version 5.34 · Last Revised: October 28, 2026

What changed in this version: the Discernment page’s two Share controls now carry the question you typed as well as the reflection. Pressing “Send to a Friend” puts both into the share sheet, your clipboard, or an email you send from your own mail app; pressing “Share as Card” draws both into an image on your device. The optional “Email me this reflection” form now sends your question along with the answer, not the answer alone. Neither path sends anything to us — the words go only to where you choose — and nothing new is stored or logged. Section 1’s table row for the one-off send, Section 1’s list of what is never stored, Section 4, and Section 9 now describe both Share controls and the question the email form carries. Everything else in this policy is unchanged.

Version 5.33 · Last Revised: October 24, 2026

What changed in this version: the Pricing page now ends with one optional question — what is holding you back from becoming a Supporter today — which is closed until you open it, with four fixed answers and an optional comment box. Sending an answer adds one anonymous aggregate count recording which of the four answers you chose, together with the page it was sent from and the same coarse device category every count carries. Anything you type in the comment box stays in your own browser’s storage, is never sent to us, and is not part of any count. A browser that has answered is not asked again. The “Anonymous aggregate usage counts” row in Section 1 now names this count. Everything else in this policy is unchanged.

Version 5.32 · Last Revised: October 24, 2026

What changed in this version: the free sample of the Discernment read-aloud voice now has its own anonymous aggregate count. Pressing play on that sample — in the homepage hero, or at the top of the Discernment page — adds one count, together with which of those two pages it was pressed on and the same coarse device category every count carries. Nothing about your question, the sample, or you is recorded, and no audio is requested at all until you press play. The “Anonymous aggregate usage counts” row in Section 1 now names this count. Everything else in this policy is unchanged.

Version 5.31 · Last Revised: October 24, 2026

What changed in this version: the operator's premium-ledger screen now shows each subscription's subscriber name and email, resolved at read time — the account's own name and address when the subscription is connected to an optional account, and otherwise the name and email on Stripe's customer record — so the operator can identify whose subscription it is before cancelling or servicing it. Nothing stored changes: the ledger row stays an opaque subscription number, the identity is resolved fresh on each admin page load, is never stored, cached, or logged, and appears only on the operator's authenticated screen. This version adds a short paragraph under "The account and your subscription" saying plainly who can see a subscription's name and address; the masked-address promise about your own browser is unchanged. Everything else in this policy is unchanged.

Version 5.30 · Last Revised: October 23, 2026

What changed in this version: the device-code and pairing-code rails are retired, and this policy now describes the account alone. The optional account is the only way Premium access is carried: signing in carries your Premium access with you on any device, and there is no three-device limit. This version removes the retired access-code row and the retired sign-in session-cookie row from the Section 1 table, retires the three-device limit, the hashed device keys, and the "unlink a device" wording from the payment rows, and leaves the account session (30 days) and the administrator session (8 hours) as the only session cookies on the site (Sections 1 and 4). Closing the account still cancels a connected subscription at the end of the period already paid for and ends the Premium access carried through the account. Nothing else in this policy changes.

Version 5.29 · Last Revised: October 21, 2026

Version 5.28 · Last Revised: October 20, 2026

Version 5.27 · Last Revised: October 19, 2026

Version 5.26 · Last Revised: October 17, 2026

Version 5.25 · Last Revised: October 14, 2026

Version 5.24 · Last Revised: October 11, 2026

Version 5.23 · Last Revised: October 10, 2026

Version 5.22 · Last Revised: October 10, 2026

Version 5.21 · Last Revised: October 8, 2026

Version 5.20 · Last Revised: October 7, 2026

Version 5.19 · Last Revised: October 5, 2026

Version 5.18 · Last Revised: October 5, 2026

Version 5.17 · Last Revised: October 1, 2026

Version 5.16 · Last Revised: October 1, 2026

What changed in this version: the site now offers an optional account for adults 18 and older. The free core still needs no account and no email — that promise is unchanged. An account exists so that a Premium membership can follow you from one device to another, and it remembers only what you put into it: whether you are a Premium member, your first name and your last name (both required, in two separate fields), and your email address. Creating one asks for your email address (stored encrypted), a password (stored only as a one-way hash we cannot read), your first name and last name (both required), a confirmation that you are 18 or older, and an optional, unchecked marketing choice — separate from your account, and leaving it unticked changes nothing. Sessions use a secure, HttpOnly cookie that expires after 30 days; sign-in and registration are rate-limited. If you are signed in when you start a subscription or its free trial, your email address is passed to Stripe with that checkout request, and the account is linked to the subscription by its subscription number so the membership follows you; you can close the account by writing to us, and closing it cancels a connected subscription at the end of the period already paid for and ends the Premium access carried through the account. The account adds no analytics, no tracking, no profiling, and no sale or sharing of anything. This policy now describes the account row in Section 1, the account session cookie, the account's email reaching Stripe, how an account is linked to a subscription, the masked address your browser is shown, closing your account and what that does to a subscription, the 18-and-older line, our security steps, and retention. Everything else in this policy is unchanged.

What changed in this version: the new free "Bible Stories" audio series is now covered by the two listening counts described in the entry below, exactly as "Today's Deep Dive with Alex & Maria" and "Weekly Gospel Insights" already are. Pressing play on a "Bible Stories" episode records one play count, and when a listening stretch ends we record how many whole seconds the audio was actually playing. Nothing new is collected: these are the same two counts, with the same two-hour cap on a single stretch, the same off-switch in Site Settings (which deletes the counts already kept), and the same 90-day retention. The play is counted on the page it happened on and carries which series it belongs to and nothing else — never the episode's title, never the position in the audio, and nothing about you. Section 1's list of named events is unchanged: those are our analytics provider's events, and these two counts are ours. Everything else in this policy is unchanged.

What changed in this version: two small counts about LISTENING are now part of the anonymous aggregate totals we keep ourselves, described in Section 1's table row for those totals. The first is that an episode was played: pressing play on a "Today's Deep Dive with Alex & Maria" episode, a "Weekly Gospel Insights" episode, or that series' free ninety-second preview records one count, and — since version 5.28 — so does pressing play on a "Bible Stories" episode, the free series described in the newest entry above. The second is HOW LONG it was listened to: when a listening stretch ends, we record how many whole seconds the audio was actually playing. This one is new and worth stating plainly, because it measures something the policy did not previously describe. It is a count of seconds only — never a clock time, never a date or a time of day, and never which part of the episode you heard or how far into it you got. It is measured while the audio is playing and stops the moment you pause; pausing ends one count and pressing play again starts a new one. If you listen with the page in the background — the screen off, the phone in a pocket, the tab behind another — the count keeps going, because the audio is still playing; that is the listening this feature is meant to measure, and we would rather say so than quietly under-count it. A stretch shorter than one second is not counted at all. Both counts are bounded (a single stretch can never record more than two hours) and both obey the same off-switch as every other count: if usage reporting is off in Site Settings, neither is recorded, and turning reporting off deletes the counts already kept. Nothing about you is added to either one beyond the coarse device category every count already carries, and nothing is sent to our analytics provider about them — like the rest of Section 1's aggregate totals, these two stay with us. Section 1's list of named events is unchanged: those are the provider's events, and these two are ours. Nothing else in this policy changes: no new kind of data, no new page tracked, and the events Section 1 already lists are exactly what they were.

What changed in this version: the Discernment page now offers an optional, small "Email me this reflection" form beneath an answer. If you use it, we send the text of that answer — the same words you just read — in a one-off email to the address you type, plus, when the answer carries sources, one "Sources:" line. Nothing else is added to that email: no tracking, no footer, no offer, and no unsubscribe link, because it is the single email you asked for, not a list email. The form's updates checkbox is a separate choice, unchecked by default: unchecked, we use your address for that one send and store nothing; checked, your address joins the optional updates list described in this policy, through the same encrypted store, with the same one-click unsubscribe. The reflection text is never stored and never logged, and the form is never counted in usage reporting. Section 1's table gains a row describing the one-off send, Section 1's "Sources" paragraph and Section 9 name the new surface, and the Discernment-page sections note that the answer can leave your device only because you ask for the email. Everything else in this policy is unchanged.

What changed in this version: the free ninety-second preview of a premium "Weekly Gospel Insights" episode now has a named event of its own. Pressing play on that preview — the free sample a visitor with no subscription recorded on the device sees on a premium episode page, directly above the notice that says the page is part of Premium — records "Weekly Gospel Insights: Preview played". It is counted separately from that series' full-episode play event, so a press on the free sample is never reported as a full episode listen. The event carries only its own name, the page path, and the kind of interaction: never which episode, never the position in the audio, and nothing about you, and nothing changes while the audio simply runs. Each play press counts once, so pausing and pressing play again counts twice. It obeys the same off-switch as every other event: if usage reporting is off, a play is never counted. Section 1's list of named events is updated to name it. Nothing else in this policy changes: no new kind of data is collected, no new page is tracked, and the existing page view and interaction events are exactly what they were.

What changed in this version: the "Weekly Gospel Insights" audio series has a named play event of its own, so a play in that series is counted separately from a play in the Deep Dive library. Pressing play on an episode of this series records "Weekly Gospel Insights: Episode played". The event carries only its own name, the page path, and the kind of interaction: never which episode, never how far into the audio you are, and nothing about you, and nothing changes while the audio simply runs. Each play press counts once, so pausing and pressing play again counts twice. It obeys the same off-switch as every other event: if usage reporting is off, a play is never counted. Section 1's list of named events is updated to name it. Everything else in this policy is unchanged.

What changed in this version: the "Today's Deep Dive with Alex & Maria" player now counts one small event, and it is the press of play that is counted and nothing else. Pressing play on an episode — on an episode page, or on the episode player at the top of the Discernment page — records "Deep Dive: Episode played". The event carries only its own name, the page path, and the kind of interaction: never which episode, never how far into the audio you are, and nothing about you, and nothing changes while the audio simply runs. Each play press counts once, so pausing and pressing play again counts twice. It obeys the same off-switch as every other event: if usage reporting is off, a play is never counted. Section 1's list of named events is updated to name it. Everything else in this policy is unchanged.

What changed in this version: the Discernment page's interaction events were reworked to match its new flow. Pressing Submit records "Discernment: Submitted"; when the reviewed library has no close match and a question goes to Magisterium AI automatically, "Discernment: AI asked" is recorded, counted whether or not an answer arrives, so a request that is throttled or fails is counted the same as one that succeeds. The former "Alternative read" event no longer exists — the page now gives one answer, not an alternative to read — and starting over records "Discernment: New question". Each of the three carries only the event name, the page path, and the kind of interaction: never the question you typed, never which answer was shown, and nothing about you. All three obey the same off-switch as every other event. Section 1's list of named events is updated to name them. Everything else in this policy is unchanged.

What changed in this version: a short "How we use AI" section now names the two places AI is used — the AI-generated narrators of the "Today's Deep Dive with Alex & Maria" audio library (previously disclosed in a visible one-line notice on every Deep Dive page; the 2026-10-08 revision keeps the site's AI mentions to a minimum, disclosing behind the library's single "AI disclosure" link, which points to this section) and the optional AI helper on the Discernment page, which Section 3 has always described. No data practice changes; this version only states the site's AI uses in one place and reduces every other mention to that one link.

What changed in this version: anonymous page views are now counted on every page of the site — including the Prayer Library, the premium libraries and their paywalls, and the seasonal packs — with the same on-by-default, opt-out usage reporting described throughout this policy. What is counted is unchanged in kind: the page address (path only, never a search term or query string), the page's title at the moment the count is sent, the coarse kind of browser and device, the country your internet address points to, and the same small interaction events on those pages — the fifteen named events and the ordinary click and form events described in Section 1, all under the same off-switch in Site Settings. Nothing new is collected by this change: no name, no email, no account, no cookies, and still never the words you write. The individual Prayer Library pages, /contact, and /support are no longer "events only, with no page view" — they now count a page view like every other page. This supersedes the Section 1 wording that three surfaces loaded the script for events only with no page view at all, and the version 5.7 entry that said the same. The entries for versions 5.6, 5.5, and 5.7, which describe where usage reporting runs, are updated to say the same. Everything else in this policy is unchanged.

What changed in this version: the optional updates list now sends one email a week — Monday morning, with that week's seven Daily Offerings — alongside occasional updates about new premium features as they launch. The list is still separate, never pre-checked, one-click unsubscribable, and for adults 18 and older. Everything else in this policy is unchanged.

What changed in this version: on the pages we track, the anonymous page view sent to Umami Cloud now also carries the title of the page — read from your browser at the moment the count is sent. That is the whole change: the page address is still sent path only, never a search term and never a query string, and the page view still carries no other browser or device details beyond those this policy already describes — the coarse kind of browser and device and the country your internet address points to — no name, no email, no account, no cookies, and nothing you write. Because the title is read at the moment the count is sent, a quick in-app move onto a page that is still loading can send the title of the page you just left — the same behavior as the analytics service's own tracker. The anonymous interaction events are unchanged and never carry a title: each still carries only the event name, the page path, the kind of interaction, and the small fields described in this policy. The entries for versions 5.6 and 5.5, which describe what the page view carries, are updated to say the same. Everything else in this policy is unchanged.

What changed in this version: The music-video previews on the Faithful Screen catalog now play for 90 seconds before the timer on our page stops them, instead of 60 (the duration first described in version 5.14). Everything else about previews is unchanged: a preview is a button that loads nothing until you click it, nothing autoplays, and the timer on our page is still the only thing that stops playback. This supersedes the 60-second wording in the 5.14 entry. Everything else in this policy is unchanged.

What changed in this version: The Discernment page now offers two of the owner's own talks — One Small Offering's own videos — playable in place through YouTube's own player, the same click-to-load pattern the Faithful Screen catalog's previews use: each talk is a button, no request goes to YouTube until you click it, and no talk autoplays. These are full-length talks, not short previews, so nothing on our page stops them early. Opening one records one small anonymous event, "Discernment: Episode opened," under the same off-switch as every other event, carrying only the page and the kind of interaction — nothing about which talk, nothing you typed, and nothing from inside the player. This version names that player in Section 3's list of third-party connections and adds the event to the named events in Section 1. Everything else in this policy is unchanged.

What changed in this version: on the Faithful Screen catalog, the book entries we source from Christianbook.com — the titles Christianbook's own catalog carries — now draw three things from Christianbook.com: the description on the card is Christianbook's own product text, taken from their product data into the listing — the publisher's or bookseller's words, not words we wrote; the cover image loads from Christianbook's own image host, their server, not ours, which may set its own cookies under its own practices, just as any website you visit may; and the buy button links to Christianbook.com through CJ Affiliate's pre-tagged click URL — the same affiliate network the search uses — so following one passes through CJ's own click-tracking service before it reaches Christianbook's store, and CJ's own privacy practices, not this policy, govern what that service does on its own domains. Book titles Christianbook's catalog does not carry keep their existing Amazon.com buy buttons, and their descriptions remain our own team's. Those Christianbook-sourced cards are the one part of the catalog whose descriptions are no longer written by our own team: movies, TV series, music, and podcasts keep their Amazon.com buy buttons and their descriptions remain our own. No book card asks you to type anything, so nothing new you type leaves the site. This version also names Christianbook's product data and image host in Section 3's list of third-party connections. Everything else in this policy is unchanged.

What changed in this version: Many music entries in the Faithful Screen catalog now offer a preview the same way the movie and TV entries already do: a button that opens the track's music video in YouTube's own player, in a small frame on the catalog page. Nothing loads until you click it, nothing autoplays, and a timer on our page stops playback after 60 seconds. A music entry without a video simply has no preview. The player is the same YouTube embed described in Section 3 — the same host, reached only when you click, under the same terms already stated there. Opening one records the same single anonymous event, "Faithful Screen: Preview opened," under the same off-switch, and nothing from inside the player is collected or counted. Music previews no longer open in Apple's player — on the catalog, Apple's embed players now host podcast shows only — and Section 3's description has been updated to match, naming music videos alongside movie and TV trailers. Everything else in this policy is unchanged.

What changed in this version: Result cards in the Faithful Screen Christianbook search now show each title's cover image and the merchant's own short description of it. The description is plain text that arrives in the same server-to-server response described in the previous entry, so it adds no new recipient and no new connection from your browser. The cover image is handled differently, and this policy says so plainly: it is the one part of the search that your browser loads for itself, from Christianbook's own image host — their server, not ours. That host may set its own cookies under its own practices, just as any website you visit may; we do not place them, and we neither control nor read them. The words you type still travel only from our server to the product-search service and never from your browser, and no request goes from your browser to CJ until you follow a result. Section 3's description of the search now says the same. Everything else in this policy is unchanged.

What changed in this version: The Faithful Screen catalog now offers a search that looks through Christianbook's bookstore — the one place on that page where something you type reaches a server. When you search, the words you type are sent from our server to Christianbook's product-search service (which runs on the CJ Affiliate network) to find matching titles, and only that: the words are used for the lookup and nothing else, they are not tied to your identity — this site keeps no accounts — and they never enter our usage reporting. The account token that authorizes those lookups stays on our server and never reaches your browser; no cookie is set on your device by the search itself, because it is a single request from our server, not a connection your browser makes. The results carry the same buy buttons and the same plain-language disclosure as the rest of the catalog: if you buy through one of them, we may earn a commission. This version also names the search in Section 3's list of third-party connections. Everything else in this policy is unchanged.

What changed in this version: Premium — the optional paid tier for the Saint Reflections library, Prudence in Practice, and the Life of Christ timeline — is now available at $4.99 a month or $45 a year (see Section 1 and Section 3 for how a subscription works). Because Premium now exists, the premium waitlist has served its only purpose, and we have retired it: the waitlist signup has been removed from the site, the list holds no addresses, and it never sent an email. Joining it was never a purchase, a discount, or a subscription, and it creates none now. The optional "keep me updated" email list is now the site's one optional signup, and its promise is updated to match what is now true: instead of early access if premium features ever became available, it now offers updates about new premium features as they launch — on the same separate list, never pre-checked, with the same one-click unsubscribe and the same rule that the list is for adults 18 and older. The named interaction events in Section 1 are unchanged. The Section 1 feedback-form row is updated: the form no longer collects an optional email address — that field's only purpose, a one-time launch notice, is spent now that the site is live — and the row's wording no longer describes the site as a pilot. Everything else in this policy is unchanged.

What changed in this version: The Faithful Screen catalog now counts like the rest of the page: every button, form, and link on it records the same small, anonymous interaction event described in Section 1 — choosing a media type or the New releases view, clearing a search, closing a preview player or an enlarged cover, and following a buy link or an information link each record one small event, named from the control or where the link leads, with no search text, no query string, and no full web address. Opening a preview player records one new named event, "Faithful Screen: Preview opened," which carries only which catalog entry you opened — the entry's own type and catalog listing — nothing about you and nothing from inside the player. This supersedes the 5.9 note's statement that preview clicks were not counted: they now count as that single small event, under the same off-switch as everything else in this policy. Everything else in this policy is unchanged.

What changed in version 5.9: On the Faithful Screen catalog, six entries now offer a preview that plays without leaving the page — two Apple Music albums, two Apple Podcasts shows, and two official movie and TV trailers. Each preview is a button, and nothing loads until you click it; no preview autoplays. When you do click, the provider's own player opens in a small window on the catalog page — Apple for the music and the podcasts, YouTube for the trailers. We make no request to Apple or YouTube until that click, and we send them no data beyond the normal page context of their own embed; we collect nothing from the player itself, and a preview click is not counted in our usage reporting. Apple's and YouTube's own privacy practices apply inside their players, just as they would if you visited their players on their own pages. This version adds Apple and YouTube to the third-party list in Section 3. Everything else in this policy is unchanged.

What changed in version 5.8: Premium, the optional paid tier — the libraries for Saint Reflections, Prudence in Practice, and the Life of Christ timeline — is now covered in this policy. It is a subscription ($4.99 a month or $45 a year), paid through Stripe, Inc., our payment processor, on Stripe's own payment page: we never see or store your card number or billing address. To run a subscription and enforce the three-device limit, the site keeps a small non-identifying record — hashed device keys, a subscription number, and the end of the paid period, with no name, email, card, or reading history — deleted when you unlink a device and when a subscription ends (see Section 1 and Section 3). Everything else in this policy is unchanged: the Daily Offering and the heart of the site are free for everyone, usage reporting works exactly as described below, and nothing you type is ever collected. This version also adds the footer links to our public profiles (YouTube, Facebook, Instagram, Threads, and LinkedIn) to the third-party list in Section 3.

What changed in version 5.7: On the pages we track, usage reporting now counts a little more than page views. The same cookie-less service, Umami Cloud — the site's one analytics exception — also receives a few anonymous interaction events: a click on a link or button, a form submission, starting or completing the Stillness timer, beginning or completing the Daily Offering, viewing an individual prayer in the Prayer Library, or changing a display setting. Each event is tiny and fixed: an event name, the page path, the kind of interaction, and — only for links — where the link led (a site path, or just the hostname of an outside site), plus one small extra field for three of the named events: the timer length in whole minutes, the prayer's slug, or the setting's name only — never its value. Nothing you type, nothing inside a form, no email address, no phone number, and no search term ever ride along. The same off-switch in Site Settings that stops page views stops these events too, from the moment your choice is stored. Three pages load the script for events only, with no page view at all: the individual Prayer Library pages, Contact, and Support. The Daily Offering gate and the places where you write or type remain zero-tracking, exactly as before — that promise is kept. The details are in Section 1 and Section 3.

What changed in version 5.6: Usage reporting became on by default on the pages we track. There is no "Allow" banner to choose anymore: on those pages, a simple, anonymous page view is counted the first time you open one, and an anonymous identifier is created at that first counted page view — not at any click. You can turn usage reporting off at any time in Site Settings; from the moment your choice is stored, nothing further is counted, and the counts already kept for that browser are deleted. What is counted is deliberately small: the page address (path only, never a search term or query string), the page's title as it appears in your browser at the moment the count is sent, the kind of browser and device you are using, and the country your internet address points to — no name, no email, no account, no cookies, and nothing you write. Campaign codes from our social links and printed materials are counted the same way: on by default, part of the same usage reporting, and stopped whenever you turn usage reporting off. The Daily Offering gate and the places where you write or type remain zero-tracking, exactly as before — that promise is kept. The details are in Section 1 and Section 3.

What changed in version 5.5: We added a small, cookie-less analytics service called Umami Cloud to count page views. In this version the counter was consent-gated: it ran only after you chose "Allow" on the usage-reporting banner. Starting with version 5.6 (above), usage reporting is on by default on the pages we track instead; what that counter received had not changed then — the page address (path only), the kind of browser and device you are using, and the country your internet address points to — no name, no email, nothing you write, and no cookies; the newest addition is the page's title, described in the newest note above. Version 5.7 (above) adds anonymous interaction events to what the counter receives. It is the only analytics on the site that involves another company, and turning usage reporting off stops it.

What changed in version 5.4: Added campaign codes. If you reached us from one of our social links, or from a printed One Small Offering card or flyer that carried a short campaign code, that one coarse category is kept with your anonymous usage counts — a value such as "Instagram" or "parish table 2026," nothing more. It is counted only if you choose Allow, it never includes the web address you arrived from, and it is kept and deleted exactly like the other usage counts (90 days, or right away if you turn usage reporting off).

What changed in version 5.3: Clarified that anonymous usage counts are rolled into aggregate totals per day, week, or month (and may be combined into simple group-level overviews), rather than day-granular only — and that the optional lists are counted only in plain totals for internal reports.

What changed in version 5.2: Aligned the early-access sentence with the site's honest conditional framing — the updates list promises early access only if a paid tier is ever added.

What changed in version 5.1: Added the premium waitlist — a separate, optional email signup whose only purpose is telling you first if a paid tier is ever added. Joining it is a willingness signal only: no email is sent from it yet, and joining does not create a paid subscription.

One Small Offering, LLC ("we," "us") operates www.onesmalloffering.com, a Catholic daily-life companion for adults in the United States. The free heart of the site — the Daily Offering, Discernment, Prudence, Stillness, and the Prayer Library — needs no account and no email, and that never changes. An optional account exists for people who want to carry their Premium access with them across devices; it is never required for anything free, it is never created by accident, and it holds nothing about what you read, pray, or type. This Privacy Policy explains what personal information we collect, how we use and disclose it, and the choices and rights you have. We review and update this policy periodically and will post changes here. If you would like a printable copy, contact us using the information in Section 11.

This policy applies to www.onesmalloffering.com and any page that links to it. It does not apply to third-party sites we link to (see Section 3).

1. Personal Information We Collect and Disclose

"Personal information" means information that identifies, relates to, describes, or could reasonably be linked to you. One Small Offering is deliberately minimal: by default, almost nothing you do reaches a server. The table below enumerates every category we may collect, why, the legal basis we rely on, and how long we keep it — and only in the narrow ways stated.

CategoryWhat it isWhy we may have itLegal basisHow long we keep it
Account session cookie (first-party)A cookie on your device that keeps you signed in to your optional account. It holds a signed session value containing an opaque account number — not your email address, your name, or your password — and a page's own scripts cannot read it.To keep you signed in to your optional account from page to page.Necessary for the service to function.Expires after 30 days. Using the site does not extend it: when it expires you sign in again.
Optional account (email, name, password)Only if you create an optional account. The account remembers the small set of things you chose to put in it: whether you are a Premium member (the fact that a subscription is connected to the account — never payment details, which go only to Stripe), your first name and your last name (two separate fields, both required, kept as you typed them), and your email address, kept encrypted with a one-way keyed hash used to look it up — never in plain text. For the account to work at all it must also hold your password (stored only as a one-way hash — we cannot read it or recover it, and no plaintext is ever kept or written to a log), the time you confirmed you are 18 or older (that confirmation, not your birth date and not your age), your marketing choice and when you made it, and the dates the account was created, updated, and last signed in to. Nothing else is saved to the account — nothing you read, pray, or type, no history of any kind, and no location.To keep you signed in, let you back into your account, carry your Premium access with you, and honor your choices.Contract performance (providing the account you asked for); consent for the marketing box (a separate, unchecked choice).Until you delete the account (see "The optional account" below). The session cookie expires on its own after 30 days.
Administrator session cookie (first-party)A short-lived cookie used only for site administrators' authenticated sessions. Most visitors never have one.To protect the admin-facing site reports.Necessary for the service to function.Expires after 8 hours.
Display preference cookies (first-party)A small set of short-lived cookies that remember display choices you make on the site — color theme, whether the decorative window panels are static or animated, and text size. Each stores a single short value (such as your chosen theme name) and nothing that identifies you.To keep the site looking the way you chose from page to page.Legitimate interest.Deleted when you close your browser (session cookies — no fixed expiry date).
Usage-reporting choice (local storage)A small note stored in your browser's local storage recording whether you have turned usage reporting off on this device. While usage reporting is on, it also holds the anonymous identifier described in the next row. Nothing here is transmitted to us.To honor your choice on this device.Choice management.Stays on your device until you or your browser clears it.
Anonymous aggregate usage countsOn every page of the site, usage reporting is on by default: a few anonymous counts — which pages you opened, a successful sign-in, a resource link you opened, a Discernment result, a Stillness session started or completed, an episode you played, and how many seconds of it you listened to (total seconds only, never a clock time, and never which part of it you heard), a press of the free sample of the Discernment voice (only that it was pressed, and on which of the two pages it appears), one choice among four fixed answers to the single question we ask about Premium at the bottom of the Pricing page (the optional comment box beside it stays in your browser and is never sent, and the count never says who answered), and overall time on the site (total seconds only, never a clock time) — plus a coarse device category (phone, tablet, or computer) and a few supporting counts such as a return on a later day. Rolled into aggregate totals — per day, week, or month — never tied to you. Our internal reports describe the group as a whole — never your individual path or timing. Each count also carries a small server-derived environment label — the live site, the preview environment, or unknown — drawn from the address the site was reached at. It is a value like "live" or "preview" with no IP address, user-agent, referrer, or identity attached, and it exists so our reports can tell real visitor traffic apart from our own preview and testing traffic. If you reached us from one of our social links or a printed card or flyer carrying a short campaign code, we keep that one coarse category with your counts — such as "Instagram" or "parish table 2026," nothing more. And if you arrive from one of our advertising links, we keep the three campaign tags that link carries — a source, a medium, and a campaign name — as short lowercase slugs we set ourselves, held for that browser session and attached to the same counts; never anything you typed, never the full address you arrived at, and never the page you came from.To understand whether the site genuinely serves people.Legitimate interest (usage reporting is on by default on every page of the site; you may turn it off at any time in Site Settings, which deletes the rows).Up to 90 days, then deleted automatically. Turning reporting off in Site Settings deletes the counts already kept and stops all further usage counting from the moment the choice is stored.
Umami Cloud usage data (third-party, opt-out)On every page of the site except the parish-partners pages (which remain free of any usage reporting), usage reporting is on by default, and a small cookie-less script sends anonymous usage information to Umami Cloud, a third-party analytics service we use to understand which pages and interactions help people: the anonymous page view described above, plus a small set of anonymous interaction events — each an event name, the page path, the kind of interaction, and, for links, where the link led (see "The Umami Cloud usage information" below the table). No name, no email, nothing you write, and no cookies.To understand, in aggregate, which public pages and which interactions genuinely help people — the same purpose as our own counts, on every page of the site.Legitimate interest (usage reporting is on by default on every page of the site; you may turn it off at any time, which stops the script — and every page view and event — immediately, and deletes our own counts). For EEA/UK visitors, see Section 5b.Umami Cloud keeps records on its own schedule; we do not control their retention. Our own counts are deleted after 90 days.
Server request logFor each request: the page path name only — deliberately no query strings — plus a one-way scrambled marker of the connection source and a shortened browser/bot identifier (the "user-agent," truncated to 200 characters). No IP address is logged.Operational security and abuse prevention — keeping the site working for everyone — plus the anonymous aggregate usage snapshot described below.Legitimate interest.14 days, then deleted.
Aggregate AI-usage countA count that a question went to the live AI helper — automatically, because the reviewed library had no close match, or because you asked for it on a close match. The question text itself is never part of it.Rate-limiting, so the live helper stays available and fair.Legitimate interest.Aggregate only; the prompts themselves are zero-retention (see Section 2).
Discernment voice free-trial counter (first-party cookie)To give you three free spoken conversations without an account, we keep one small note about this browser: a random identifier in the site's own cookie, how many of the three you have used, and when — never your question, never the answer, and never anything you said or heard, and it is not linked to the usage-reporting identifier or to any account. It holds no words at all, and clearing this site's cookies starts the three over.To give three free spoken conversations on a browser with no account, and to stop the voice being used without limit — the typed question and the typed answer are not affected and are never counted. Separate from usage reporting: turning usage reporting off does not stop it.Necessary for the service to function.Deleted 90 days after the last free conversation — and sooner if you clear this site's cookies.
Feedback form submissionIf you choose to submit it: a small set of structured research answers and an optional comment (capped at 2,000 characters).Feedback and product research — evaluating whether the site is genuinely useful, safe, and calm to return to. Not used for profiling, advertising, or training.Consent (you choose to submit the form).Up to 90 days, then deleted automatically. After submitting you receive a one-time deletion token; entering it deletes the submission immediately and permanently.
Discernment star rating (1–5 stars, optional note)Only if you submit it: a star rating of 1 to 5 for the Discernment page, an optional note of up to 2,000 characters, the fixed label naming the page it came from, and a coarse environment tag — the live site, the preview environment, or unknown — worked out on our server from the address the site was reached at. No name, no email, no account, no IP address, no device data — and never the question you typed.To learn whether the Discernment page is genuinely useful, and to read what people say could make it better. Not used for profiling, advertising, or training, and never published or shown to other visitors.Consent — the form will not send until you tick its consent box, which is unchecked by default.Up to 90 days, then deleted automatically. After you send it you are shown a one-time deletion code, and only a scrambled hash of that code is stored — it is shown once and cannot be recovered for you. Entering it on the Discernment page deletes that rating immediately and permanently. Ratings are read only on an administrator-only screen, as a plain count, an average, a 1-to-5 breakdown, and the notes themselves.
Optional "keep me updated" email listA separate, voluntary list. You may ask us to email you occasionally with updates about One Small Offering, including new premium features as they launch. It is off by default, never pre-checked, never required for anything on the site, kept in a separate table, and every record is individually unsubscribable and individually deletable.Release updates and new premium feature notices, only if you actively ask for them.Consent (your explicit, separate opt-in; not required for or tied to anything else).Until you unsubscribe or ask us to delete your record. We honor every unsubscribe promptly and no later than 10 business days.
Payment information (Premium — processed by Stripe)Only if you subscribe to Premium: the fact of your subscription (plan, amount, renewal dates), processed on Stripe's own payment page by Stripe, Inc., our payment processor. We never receive, see, or store your card number, billing address, or other full payment details. To run your subscription the site keeps a small non-identifying record — a subscription number (the Stripe subscription number where you paid by card, which identifies a subscription, not a person, and a random generated number otherwise), and the end of your paid period — with no name, email, or reading history. The one exception is described in "Your email address and Stripe" below the table: an address you chose to give your own optional account, passed to Stripe when you start a subscription while signed in.To process the subscription you chose and keep it working — billing, renewal, cancellation, and refunds.Contract performance — processing is necessary to provide the subscription you purchased. Payment-fraud prevention may rely on our legitimate interest in preventing fraudulent charges.The non-identifying record described above is deleted when a subscription ends. Payment records themselves are kept by Stripe on its own schedule, which we do not control.
Discernment question sent to Magisterium AIOnly when our reviewed library has no close match: your typed question, sent through our server to Magisterium AI, a third-party AI service, in a zero-retention processing mode, and the answer returned to you, clearly labeled as third-party AI output that One Small Offering has not reviewed. A question that earns a strong or close reviewed answer is sent nowhere, and on a close match the live AI is reached only if you press it yourself.To return an answer when our own reviewed library has nothing close to match.Consent (you typed a question and pressed Submit, and the page says beside the box that a question with no close match goes to the live AI; on a close match, your press on the live-AI card).We retain nothing from the exchange (see Section 2).
Optional "Email me this reflection" one-off email (Discernment)After you receive an answer on the Discernment page, a small optional form — "Email me this reflection" — lets you type an email address and send yourself a one-off email with your question and the answer you just read, plus, when the answer carries sources, one "Sources:" line. Nothing else is added: no tracking, no footer, no offer, and no unsubscribe link, because this is the single email you asked for, not a list email. Beside it sits the same optional updates checkbox described in the "Optional 'keep me updated' email list" row, unchecked by default: left unchecked, we use your address for that one send and store nothing; checked, your address joins that list through the same encrypted, individually unsubscribable store — and never the reflection itself. The email comes from an honest sender address with a subject line that says what it is.To send you your question and the reflection you asked to receive.Consent (you typed the address and pressed the button; if you also check the updates box, that is the same explicit opt-in the updates-list row describes).Nothing when the updates box is left unchecked: the send itself is not stored. If you do check that box, your address is kept exactly as the "Optional 'keep me updated' email list" row describes — same store, same one-click unsubscribe, same deletion rights. The question and reflection text are never stored or logged.

The one-line question under a Discernment answer. Some answers carry a single optional question — "Did this reflection help your pacing today?" — with two thumbs and, if you want, a short note of up to 500 characters; pressing one sends only your vote, your note, and the moment it was sent, and nothing else: no IP address, no device or browser detail, no session, no identifier, no cookie or storage on your device, never the question you asked or the answer you read, no usage-reporting event is recorded for it, it is never shown on an answer about a crisis, and leaving the note empty records the vote alone.

The optional account. Creating an account is a choice, not a requirement — the free core needs none. It exists so that a Premium membership can follow you from one device to another, and it holds nothing about what you read, pray, or type; it never joins or crosses any other data on the site. The account remembers only what you put into it: Premium membership, your first name and last name, and your email address — nothing else. The marketing box on the sign-up form is a separate, unchecked choice: leaving it unticked changes nothing about your account, and ticking it adds your address to the optional "keep me updated" list described above, on that list's own terms, with its own one-click unsubscribe.

Signing in with Google. If you connect a Google account to your optional account from inside it — never automatically — you can then sign in with Google as well as with your password, which still works exactly as before; we keep only the Google account's identifier and the email address it gives us, and never your name, your picture, your contacts, or a lasting token that could reach your Google account again.

Your email address and Stripe. If you are signed in to an account when you start a subscription or its free trial, the checkout request we send to Stripe carries your account's email address, so Stripe uses the customer record it already has for that address instead of creating a second one for the same person. That is the only time an account's address goes to Stripe, and it travels inside that checkout request only — never in a link address, never in the stored link between the account and the subscription, and never back to a browser. If you are not signed in, no email address goes to Stripe at all, exactly as before.

The account and your subscription. When a subscription started from a signed-in account is confirmed, the account is linked to that subscription by its subscription number, so your membership is read back for the account on any device you sign in on. The account keeps the link only: whether you are a Premium member is always read fresh from the subscription record at the moment we answer, so an ended or cancelled subscription closes Premium on the account with no extra step. The account is the only way Premium access is carried: no device link, no code, and no set limit on the devices where the account can be used.

Who can see a subscription's name and address. The subscription record we keep stays deliberately small — an opaque subscription number, the plan, the status, and the dates — with no name or address written into it. But a subscription has to be answerable to a person before it can be cared for, so the person who operates this site can see, on one administrator-only screen, the name and email address attached to each subscription: the account's own name and address when the subscription is connected to an optional account (the address read from its encrypted storage at that moment), and otherwise the name and email Stripe's customer record holds for that subscription's payer — or, when neither source returns one, the screen simply shows that no subscriber is on record. This is the operator identifying and servicing the subscription a member asked for — cancelling it, refunding it, or answering for it — and it is not a sale and not a share with any third party: the name and address go to no other company, they are resolved fresh each time that screen is opened, they are held only in that moment's answer — never stored again, never cached, never written back into the subscription record — and that screen is the only place a subscription shows them. What your own browser is shown about your account is still only the masked address described next.

What your browser is shown. So that you can see which account is signed in, your own browser asks the site whether that account has Premium right now, and the answer includes your email address in a masked form only — for example "m•••[email protected]" — never the whole address. No name and no account number come back with it, and nothing about what you read.

Closing your account. Write to [email protected] and a person will delete the account and its one-time tokens; the account page offers the same email link. Deleting removes the account record — your email address, your first and last name, your password hash, your saved account choices, and the confirmation that you are 18 or older — permanently. If a Premium subscription is connected to the account, closing the account cancels it — not immediately, but at the end of the period you have already paid for: the end of the current month on a monthly plan, or the end of your year from when your subscription began on a yearly plan. You keep Premium through that date, and you are not charged again after it. Closing the account also ends the Premium access carried through it: Premium access is the account's, and it does not survive the account — nothing about it is kept on a device. Closing an account does not, by itself, remove your address from the separate updates list — that list keeps the address until you unsubscribe from it there, exactly as before.

How we protect the account. Passwords are stored only as one-way hashes — even we cannot read them, and they are never written to a log. Sessions use a secure, HttpOnly cookie that a page's own scripts cannot read. Sign-in, registration, and password changes are rate-limited to slow guessing without getting in the way. We take these steps because we hold this small amount of identifying information at all — but no one can promise that no breach is possible, and we do not.

What the account does not add. No sale, no sharing for advertising, no new tracker, no profiling, and no new analytics: no account event is counted in usage reporting, and signing in to an account is counted no differently from any other page visit — our counts do not know whether you have an account. The account record is kept until you delete it, and our own anonymous usage counts, the request log, feedback, the Discernment star ratings, and the updates list keep their existing retention exactly as the table above describes.

How we use AI

Artificial intelligence is used in two named places on this site, and nowhere else. The narrated audio in "Today's Deep Dive with Alex & Maria" is voiced by AI-generated voices: Alex and Maria are not human narrators, and the audio is generated rather than read by a person. And the live AI helper on the Discernment page — described in detail elsewhere in this policy — sends your question to Magisterium AI only when our own reviewed library has no close match (and, on a close match, only if you ask for it yourself), and never stores anything you type. Nothing else on this site is generated for visitors to consume: every other page is written, sourced, and reviewed by people before it is published.

The anonymous usage snapshot. We also draw simple, honest aggregate usage numbers from the same request log — how many page views, how many distinct visitors, and how many returned — shown to administrators in an aggregate, day-granular report. The report shows only totals: no user-agent strings, no source markers, no individual events, nothing finer than one day. Automated traffic (bots and crawlers), our own administrative and testing traffic, and non-page plumbing (images, media, API calls, robots.txt, sitemap) are filtered out of the headline numbers and disclosed separately so the counts are not inflated; single-visit fetchers are disclosed rather than hidden. Because a shared or proxied network can make several people appear as one source (and a spoofed or automated device can inflate counts), the numbers are honest approximations of people, not exact counts. The snapshot needs no consent because it is drawn only from this already-collected, short-lived log and reveals nothing that identifies you.

Where people came from. If you reached us from one of our social links or a printed One Small Offering card or flyer that carried a short campaign code, a simple count of that campaign is kept with your anonymous counts — on by default, like the rest of usage reporting: one coarse category, such as "Instagram" or "parish table 2026." The full web address you arrived from is never stored — only that single category — and no search terms, no location, and nothing else about the card or link is kept. Campaign counts appear only as day-granular totals in an administrator-only report, are kept for the same 90 days as the other usage counts, and are deleted the same way if you turn usage reporting off. If usage reporting is off, the campaign is never counted by us: the only trace is a small note kept on your own device, which is never transmitted. Those three advertising tags are counted the same way and under the same switch: a source, a medium, and a campaign name, kept only for the browser session they arrived in, and never the full web address, the page you came from, or anything you typed.

The Umami Cloud usage information. The Umami Cloud script described in the table sends two kinds of anonymous usage information on every page of the site except the parish-partners pages (which remain free of any usage reporting): the page view, and a small set of interaction events layered on top of it, governed by exactly the same off-switch. Every event carries the event name, the page path only (never a query string, never a #hash), and the kind of interaction — a button, an internal or external link, a mailto or tel link, a download, or a form submission. Links and downloads also carry where they led: a site path such as /pricing, or just the hostname of an outside site such as example.org. Buttons, forms, mailto, and tel events carry no destination at all. Three of the named events carry one small extra field and nothing else: "Stillness: Timer started" carries the timer length in whole minutes, "Prayer: Viewed" carries the prayer's slug (such as memorare), and "Settings: Changed" carries the setting's name only — text-size, color-scheme, or window-art — never the chosen value. The fifteen named events are: "Stillness: Timer started" and "Stillness: Timer completed" (on /stillness), "Daily Offering: Begun" and "Daily Offering: Completed" (on /daily-offering — the event does not distinguish the two closing choices), "Prayer: Viewed" (on an individual Prayer Library page), "Settings: Changed" (on /settings), and "Discernment: Episode opened" (on /discernment, when you open one of the owner's own two talks in the page's episodes section), and "Faithful Screen: Preview opened" (on /faithful-screen, when you open one of the catalog's preview players), plus the three Discernment page events named in this revision:"Discernment: Submitted" (on /discernment, when you submit a question — the press alone is counted, never the question, and never which answer, if any, it produces),"Discernment: AI asked" (on /discernment, when your question goes to Magisterium AI — automatically when the reviewed library has no close match, or because you asked for the live AI on a close match — counted whether or not an answer arrives, so a request that is throttled or fails is counted the same as one that succeeds), and "Discernment: New question" (on /discernment, when you start over with another question). Each of the three carries only the event name, the page path, and the kind of interaction: never the question you typed, never which answer was shown, and nothing about you. Beside them, the Deep Dive library's player has one named event of its own, named in this revision: "Deep Dive: Episode played" (on a "Today's Deep Dive with Alex & Maria" episode page, when you press play — the press alone is counted, never which episode, never how far into the audio you are, and nothing about you). The "Weekly Gospel Insights" series' player has one named event of its own as well, named in this revision: "Weekly Gospel Insights: Episode played" (on a "Weekly Gospel Insights" episode page, when you press play — again the press alone is counted, never which episode, never how far into the audio you are, and nothing about you). The free ninety-second preview of a premium episode of that series has a named event of its own, added in this revision: "Weekly Gospel Insights: Preview played" (on that same episode page, when you press play on the free sample that sits above the notice saying the page is part of Premium — again only the press is counted, never which episode, never how far into the audio you are, and nothing about you). The new event records only which catalog entry you opened — the entry's own type and catalog listing, nothing about you, nothing you typed, and nothing from inside the player. It obeys the same off-switch as every other event: if usage reporting is off, a preview click is never counted. Opening a talk on the Discernment page records only that it was opened — the event carries the page and the kind of interaction and nothing else: not which talk, nothing you typed, and nothing from inside the player — and it obeys the same off-switch: if usage reporting is off, an episode is never counted. The Faithful Screen catalog page is tracked like the other pages here: its media-type and New releases buttons, its search form and clear-search control, its close and enlarge buttons, and its buy and information links each count one ordinary button, link, or form event of the kind described in the next sentence — never the search words you typed, never a query string, and never a full web address. Beside these, an ordinary click or form submission is counted with a fixed, derived name — for example "Home: Begin Daily Offering", "Nav: Prayer Library", "Footer: Privacy", "Signup: Updates submitted", "Contact: Email link", or "Link: /pricing" — at most one event per click (the nearest clickable element wins, so a link inside a button is reported once, never twice), named always from a fixed label or the page path, never from anything you type. A click or keystroke that begins in a place where you write or type records nothing at all. No event ever contains text you typed, an input or form value, an email address, a phone number, a mailto or tel address, a search term, a query string, a #hash, a full URL, the visible text of a control, the day's Scripture or reflection text, the journal, or which of the two Daily Offering choices was made. No event is ever sent for the Daily Offering gate, for typed content, or for the off-switch itself: in Site Settings, turning usage reporting off — and turning it back on — is never counted. A page view is counted on every page of the site except the parish-partners pages (which remain free of any usage reporting), and the interaction events described above are counted on every page except the Daily Offering gate, the journal, the places where you write or type, and the pages that host only administrative tools.

The optional email signup. You never need an email address to use One Small Offering. The Daily Offering and every other part of the site work with no email at all. Separately — and only if you actively check the box — you may ask us to email you occasionally with updates about One Small Offering, including new premium features as they launch. That request is a separate, voluntary choice: it is never pre-checked, never required for anything on the site, and it does not mix with Feedback, access, or any other data. Emails come from an honest sender address, with subject lines that say what the email is about, and every email includes a one-click unsubscribe link (honored no later than 10 business days, as federal law requires) and our physical mailing address.

What happens to my address: We use it only to send you the updates you asked for. It is kept on a separate list, apart from all other site data — never merged with feedback, access, or anything else. It is never sold, shared, or used for any other purpose. You can stop it with one click using the unsubscribe link in any email, or ask us to delete your record at any time.

If you unsubscribe from the updates list, or ask us to delete your record, you receive nothing further — and nothing else about the site changes. There is no feature, price, or content difference for saying yes, no, or nothing.

We count this list only in plain totals for our own internal reports — such as how many people joined or stopped in a given week — never in a way that identifies anyone on it.

The optional "Email me this reflection" form on the Discernment page. After you receive an answer, a small optional form may appear beneath it. If you use it, we send your question and the answer you just read, in a one-off email to the address you type, and, when the answer carries sources, one "Sources:" line naming them. Nothing else is added: no tracking, no footer, no offer, and no unsubscribe link, because it is the single email you asked for, not a list email. The same optional updates checkbox described above sits beside it, unchecked by default. Left unchecked, we use your address for that one send and then it is gone: nothing about the request, the address, or the reflection is stored. Checked, your address joins the optional updates list exactly as described above — the same encrypted store, the same one-click unsubscribe, the same rights — and the reflection itself is still not stored. The question and reflection text and full addresses are never logged; we count nothing about who uses this form, and not using it changes nothing about the site.

The premium waitlist (retired). Premium now exists — the optional paid tier described in this policy — so the waitlist's only purpose is gone, and we retired it on September 28, 2026. The waitlist signup has been removed from the site, the list holds no addresses, and it never sent an email. Joining it was always only a way to say you would like to hear first; it was never a purchase, never a discount, never a subscription, and never a promise of access. If you would like Premium now, you can subscribe on the pricing page; nothing about the Daily Offering or the free heart of the site depends on any list.

Categories we do NOT collect:

  • No name, postal address, IP address, precise device data, or full browser profile. (The server log does briefly hold a shortened browser/bot identifier — see the table above. The usage-reporting counts are keyed to an unlinked random identifier generated on this device when usage reporting is on — never a name, email, or account — see the table above. On every page of the site, the Umami Cloud service described above receives a coarse device/browser type and the country your internet address points to, plus the anonymous interaction events described there — never a name, email, account, or anything you type — see the table and the paragraph below it.)
  • No commercial information, geolocation data, or inferences or profiles about you. (If you subscribe to Premium, payment details are collected and held only by our processor, Stripe — we never receive or store them; see the Payment information row above.)
  • No sensitive personal information — no health data, no precise geolocation, and no payment details (those go only to Stripe, our payment processor, on Stripe's own payment page). The one new exception is the optional account described in this policy: it holds an email address (encrypted), a one-way password hash that we cannot reverse, the fact that you confirmed you are 18 or older, and the small set of things you chose to save to it — whether you are a Premium member and your first name and your last name (both required) — never a birth date, and never anything you read or pray.
  • No prayer, reflection, or Discernment question text is ever stored, and what you type into the homepage's Virtue Companion is matched on your own screen and never sent anywhere. The free text we do keep is only what you deliberately send us in a form of your own choosing — the optional note on the Discernment page's star rating, or the optional comment on the Feedback form — each capped at 2,000 characters, kept for up to 90 days, deletable with the code shown when you send it, and never published; both forms ask you not to include anything that could identify you or another person. On the Discernment page or the homepage's Virtue Companion, text or speech can leave your device only through the labeled paths below, and none of it is ever retained by us: (a) when the reviewed library has no close match, your typed question is sent to Magisterium AI in a zero-retention processing mode, labeled as live and unreviewed (Section 2), and on a close match it is sent only if you ask the live AI yourself; (b) if you press the microphone, your spoken words are sent to ElevenLabs to be transcribed, and we retain neither the audio nor the transcript (Section 2a); (c) the optional "Email me this reflection" form sends your question and the answer you just read to an address you type, in a one-off email, and nothing about it is stored (see the Section 1 table); (d) the Discernment page's two Share controls — "Send to a Friend" and "Share as Card" — carry your question and the reflection directly from your device to where you choose — the share sheet, your clipboard, an email you send from your own mail app, or an image on your device — and nothing is sent to us; and (e) the Virtue Companion's spoken reflection is generated for you through the same read-aloud service, using the site's own words — neither the audio nor the text is stored or logged. The Virtue Companion's two Share controls — "Share Reflection" and "Share as Card" — carry only the reflection's card, which is built from the site's own words (the virtue, the verse, and the small action) and never from anything you typed. What you type in the Daily Offering, Prudence, Stillness, the Virtue Companion, or the hero's intention box stays on your device and is never transmitted to or stored by us.
  • No directory searches: Resource Directory ZIP lookups run entirely in your browser, and nothing about the lookup is sent to us.

Sources.

Directly from you (the Feedback form, an optional star rating on the Discernment page, an email address on the optional updates signup, an address you type on the optional "Email me this reflection" form on the Discernment page, or a question that goes to the live AI helper because our reviewed library has no close match) and indirectly from your device (anonymous usage counts on every page of the site — on by default and easy to turn off in Site Settings — the short request log described above, and the anonymous usage information sent to Umami Cloud — page views and, on the surfaces described above, interaction events — as described above). If you subscribe to Premium, your payment details are given directly by you to our payment processor, Stripe — not to us (see Section 3).

Disclosure to third parties.

We disclose personal information only to service providers who help us deliver what you asked for (for example, an email delivery service, or Magisterium AI when our own reviewed library has no close match for your question — or when you ask for the live AI yourself on a close match — or Stripe, our payment processor, when you subscribe to Premium), under confidentiality obligations and for no other purpose. We do not disclose personal information to advertising partners. The one analytics processor that sees anything is Umami Cloud: on every page of the site except the parish-partners pages (which remain free of any usage reporting) — usage reporting is on by default — it receives the anonymous usage information described in Section 1 — page views and interaction events — with no name, email, or account, and we disclose nothing else to it (see Section 3).

2. Artificial Intelligence — the Reviewed Library First, the Live Helper After

The Discernment page answers from our own reviewed library first. Your question is matched against that library on our server, and four things can follow — and only one of them sends anything to an AI service without your pressing anything:

  • (a) A strong or close match is answered from our reviewed library, and your question is sent nowhere. That reflection was written, edited, and approved by people, and producing it makes no request to any AI service at all.
  • (b) When our reviewed library has no close match, your typed question is sent to Magisterium AI automatically — you do not have to press anything beyond Submit, and the page says so beside the box before you submit. Your question goes through our server to Magisterium AI in a zero-retention processing mode, and the answer comes back to you labeled as third-party AI output that One Small Offering has not reviewed. We retain nothing from the exchange: no prompt, no reply, no citation is logged or stored by us. Only an aggregate count of live-AI uses — never the text — feeds the rate-limit metering described in Section 1. We do not use your question to train anything we build or operate.
  • (c) On a close match, the live AI is offered, never taken. The reviewed reflection is your answer; beside it, a clearly labeled card invites you to ask the live AI as well. Nothing goes to Magisterium AI unless you press it, and when you do, the same paragraph above applies to that send.
  • (d) A crisis-shaped question is sent nowhere. If what you type is recognized as describing a crisis, the page answers with the site's own crisis handoff — call 911 if you or someone else is in immediate danger, and call or text 988 in a mental-health crisis — and no part of your question goes to Magisterium AI or to any other AI service. Crisis help is never behind Premium and never counted as a use.

2a. When You Press the Microphone

The microphone is the same on the Discernment page and on the homepage's Virtue Companion: pressing it records your spoken question in your browser and sends the clip to our server, which passes it to ElevenLabs for transcription and returns the words to your screen. Our server reads the clip into memory for that one request and writes nothing else — no database row, no file, and no log of the audio or the words — so we keep neither the recording nor the transcript.

ElevenLabs processes the recording on our behalf as a service provider, under its own privacy policy, which you can read at elevenlabs.io/privacy-policy.

3. Sale and Sharing of Personal Information

We do not sell your personal information, and we do not share it for cross-context behavioral advertising or "targeted advertising." We have no advertising partners. The only third-party analytics on the site is the Umami Cloud usage-data service described in Section 1 — it carries no advertising, and you can turn it off at any time in Site Settings (it is on by default on every page of the site). There is therefore nothing to opt out of for advertising — but we will honor an opt-out or deletion request regardless.

The optional account adds no sale and no sharing for advertising either. It adds no new tracker, no profiling, and no analytics, and the account itself is never sent to any advertising or analytics service.

The third-party connections on this site are functional, not advertising: (a) on the Discernment page, a question with no close match in our reviewed library is sent to Magisterium AI (a third party) automatically, and on a close match it is sent only if you ask for the live AI; its output is clearly labeled as unreviewed third-party AI — we retain nothing from that exchange (see Section 2); (b) public-domain Scripture (WEB-CE) is fetched from eBible.org with nothing stored; (c) decorative saint videos and still artwork stream from our own cloud storage; (d) font files load from Google Fonts; and (e) the "You may have heard" section of the Welcome page links to videos on third-party sites (such as catholic.com) — links only, not embedded players; and (f) on every page of the site, anonymous usage information — a cookie-less page view and, on the surfaces described in Section 1, anonymous interaction events — goes to Umami Cloud, the third-party analytics service described in Section 1; it is the only analytics connection on the site, and nothing beyond what Section 1 describes is sent to it (it is on by default; turn it off in Site Settings); and (g) the footer links to our public profiles on YouTube, Facebook, Instagram, Threads, and LinkedIn — links only, opening in a new tab on those platforms' own sites); and (h) if you subscribe to Premium, your payment is processed by Stripe, Inc. on Stripe's own payment page — the site only links you there and, beyond the small non-identifying subscription record described in Section 1, we never see or store your payment details. If you start a subscription while signed in to an optional account, that checkout request also carries the account's email address so Stripe reuses the customer it already has for it (Section 1 describes this in full); with no account signed in, no address is sent. Stripe's own privacy policy, not this one, governs what it collects and how long it keeps it. This connection exists only when you subscribe; it carries no analytics and nothing else described in this policy. and (i) on the Faithful Screen catalog page, many entries in the catalog offer a preview you can play in place: podcast shows play in Apple's own embed players, and movie and TV trailers and music videos play in YouTube's own video player (YouTube is a Google service). Each preview is a button; no request goes to Apple or YouTube until you click it, and no preview autoplays. Clicking opens the provider's player in a small frame on the catalog page, and inside that frame the provider's own cookies and analytics apply, just as they would if you had visited their embed page yourself — we send them no data beyond the normal page context of their own embed, and we collect nothing from the player. Opening a preview counts in our usage reporting as one small anonymous event, "Faithful Screen: Preview opened," described in Section 1, under the same off-switch as every other event. Apple's and YouTube's own privacy policies, not this one, govern what their players collect inside their frames. This connection exists only when you click a preview button. and (j) when you search the Faithful Screen catalog's Christianbook search, the words you type are sent from our server to CJ Affiliate's product-search service — the network Christianbook's bookstore runs on — so it can find matching titles and build the buy links shown in the results. That exchange happens server to server: the words come to us, our server passes them to CJ's product-search service, and the matching titles come back; the account token that authorizes those lookups stays on our server and never reaches your browser. The words are used only for that lookup and nothing else, they are not tied to your identity — and if you have an optional account, they are never tied to that either: the search words are not kept — and they do not enter our usage reporting (the interaction events described in Section 1 still never carry search text); we do not keep them. Results also carry two honest additions: the merchant's own short description of the title — plain text that returns in the same server-to-server response, so it introduces no new recipient and no new connection from your browser — and the title's cover image, which is the one part of the search your browser loads for itself, from Christianbook's own image host. That host is their server, not ours: it may set its own cookies under its own practices, just as any website you visit may, and we neither place, control, nor read them. No cookie is set on your device by the words you type, because the request that carries them goes from our server, not from your browser; and no request goes from your browser to CJ until you follow a result. Every result carries the catalog's plain buy button with the same disclosure beside it — "Affiliate link; we may earn a commission" — and if you follow one, the link passes through CJ's own click-tracking service before it reaches Christianbook's store, and CJ's own privacy practices, not this policy, govern what its click-tracking service does on its own domains. This connection exists only when you submit a search. and (k) the catalog's book entries that we source from Christianbook — the titles Christianbook's own catalog carries, not necessarily every book on the shelf — carry two things supplied by Christianbook: the entry's description, which is Christianbook's own product text, taken from their product data into the listing — the publisher's or bookseller's words, not ours — so viewing it adds no new connection from your browser; and the cover image, which is the one part of a book entry your browser loads for itself, from Christianbook's own image host. That host is their server, not ours: it may set its own cookies under its own practices, just as any website you visit may, and we neither place, control, nor read them. A Christianbook-sourced book's buy button is the same plainly labeled affiliate button used across the page — an affiliate link to Christianbook.com built from CJ Affiliate's pre-tagged click URL, the same network the search uses: if you follow one, the link passes through CJ's own click-tracking service before it reaches Christianbook's store, and CJ's own privacy practices, not this policy, govern what its click-tracking service does on its own domains. Book entries Christianbook's catalog does not carry are unchanged: their buy buttons are Amazon.com affiliate links and their descriptions are our own. This connection exists when you view a Christianbook- sourced book entry (for its cover) and, for the buy link, only when you follow one. and (l) on the Discernment page, two of the owner's own talks — One Small Offering's own videos — play in place through YouTube's own video player (YouTube is a Google service), loaded from YouTube's privacy-enhanced host when you open one. Each talk is a button; no request goes to YouTube until you click it, and no talk autoplays. Clicking opens YouTube's player in a small frame on the page, and inside that frame YouTube's own cookies and analytics apply, just as they would if you had visited the video on YouTube's own site — we send it nothing beyond the normal page context of its own embed, and we collect nothing from the player. The talks play in full; nothing on our page stops them early. Opening a talk counts in our usage reporting as one small anonymous event, "Discernment: Episode opened," described in Section 1, under the same off-switch as every other event. YouTube's own privacy policy, not this one, governs what its player collects inside the frame. This connection exists only when you open a talk — the "Open on youtube.com" link beside each player is a plain link to YouTube's own page, opening in a new tab, not an embedded player. The privacy practices of the sites we link to, including any analytics their players run, are their own, and their policies apply when you follow a link. The Resource Directory links to external organizations, whose privacy practices are their own.

4. Cookies and Local Storage

We use a small set of first-party cookies, none used for tracking: an administrator-only session cookie that expires after 8 hours (Section 1), a cookie that keeps you signed in to your optional account and expires after 30 days (Section 1), and three short-lived display-preference cookies — color theme, whether the decorative window panels are static or animated, and text size — each of which stores a single short value and is cleared when you close your browser. And one more: a cookie that names this browser so the Discernment page's three free spoken conversations can be counted (Section 1). It holds a random identifier and nothing else, and it is deleted 90 days after your last free conversation. Everything else lives in your browser: the usage-reporting choice is stored in local storage on your device and never transmitted. Your reflections and questions stay on your device except on the labeled paths described in Sections 1 and 2: a question with no close match goes to Magisterium AI in zero-retention mode, and on a close match it goes only if you ask the live AI; pressing the microphone — on the Discernment page or on the homepage's Virtue Companion — sends your spoken words to ElevenLabs for transcription; the optional "Email me this reflection" form sends your question and the answer you just read to an address you type, in a one-off email; and the Virtue Companion's spoken reflection is generated through the same read-aloud service, storing neither the audio nor the text. Each path runs only when you choose it — except the question with no close match, which is sent to Magisterium AI as soon as you press Submit; we retain nothing from the first two, and the email path stores nothing unless you also check the optional updates box (see Section 1). Two Share controls on the Discernment page work the same way: pressing "Send to a Friend" puts the question and the reflection into the share sheet, your clipboard, or an email you send from your own mail app, and pressing "Share as Card" draws them into an image on your device; the words go only to where you choose, and nothing is sent to us — and the homepage Virtue Companion's two Share controls work the same way for its card, which is built from the site's own words and never carries anything you typed. We set no third-party cookies. The only script we load from another company is the Umami Cloud script described in Section 1: on every page of the site except the parish-partners pages (which remain free of any usage reporting) it loads on your first visit automatically (usage reporting is on by default), it sets no cookies, it does not read or write local storage, and it sends only the anonymous usage information described there — a page view and, on the surfaces listed there, interaction events. You can stop it at any time in Site Settings; from the moment your choice is stored, nothing further is counted in usage reporting. The site works fully without allowing any cookie you do not want.

One more cookie exists that no visitor ever receives: our own testing browsers carry a first-party cookie named oso_internal, set by our tooling and not by the site, holding nothing but the value 1, so that the visits we make ourselves can be left out of the internal figures we read — it identifies no person, is not a fingerprint, unlocks nothing, is not needed for the site to work, expires on its own after a year, and clearing this site's cookies removes it.

5. Your Privacy Rights

Depending on your location, you may have certain privacy rights. In general, you may exercise the following:

RightDescription
Right to Know / AccessConfirm whether we process your personal information, and request what we have collected, used, or disclosed about you.
Right to DeleteRequest deletion of personal information we have collected about you.
Right to CorrectRequest correction of inaccurate personal information we maintain (in practice, the email you may have provided).
Right to Opt Out of Sale / Sharing / Targeted AdvertisingWe do not sell or share personal information for advertising, so there is nothing to opt out of for advertising; we honor the request regardless. (Separately, usage reporting — including the Umami Cloud page views and interaction events — is on by default on every page of the site and can be turned off at any time in Site Settings; turning it off stops all usage counting from the moment the choice is stored — see Section 1.)
Right to Data PortabilityWhere we hold personal information you provided (in practice, an email address, a feedback submission, or a Discernment star rating), we will provide it to you in a portable, readily useable format on request.
Automated Decision-MakingWe do not use automated decision-making or profiling.
Sensitive Personal InformationWe do not collect sensitive personal information.
Right to Non-DiscriminationWe will not discriminate against you for exercising any of these rights.

5a. Your Rights under the California Consumer Privacy Act (CCPA / CPRA)

If you are a California resident, the CCPA and the California Privacy Rights Act give you specific rights.

  • Right to Know — to confirm whether we process your personal information and request details of what we have collected, used, or disclosed.
  • Right to Delete — to request deletion of personal information we have collected about you (with the exceptions the law allows).
  • Right to Correct — to request correction of inaccurate personal information (in practice, the email you may have provided).
  • Right to Opt Out of Sale and Sharing — we do not sell your personal information and do not share it for cross-context behavioral advertising, so there is nothing to opt out of; we honor the request regardless.
  • Right to Limit Use of Sensitive Personal Information — we do not collect sensitive personal information as the CPRA defines it, so there is nothing to limit.
  • Right to Non-Discrimination — we will not treat you differently for exercising any of these rights. There is no price, feature, or content difference for saying yes, no, or nothing.

To exercise these rights, follow the instructions in Section 6. You do not need an account, and there is no charge for a request (up to two per year, as the law provides). California's "Shine the Light" law is addressed separately in Section 8.

A note on applicability. One Small Offering is a small US adult site that holds almost nothing. Premium subscriptions are now available and bring in revenue, which may change how the CCPA's business thresholds apply; we have asked counsel whether this sentence should be removed or rephrased now that subscriptions have launched. Whatever the thresholds, we honor these rights for California residents anyway. Usage reporting is on by default on every page of the site; California residents can turn it off at any time in Site Settings, and this policy (linked from the site's footer and from the usage notice) is the notice of that collection.

5b. Your Rights under the GDPR (visitors in the EEA or UK)

The General Data Protection Regulation protects individuals located in the European Economic Area or the United Kingdom.

If you are in the EEA or the UK, you have the right to:

  • Access the personal information we hold about you (in practice, very little — see Section 1);
  • Rectification of inaccurate information;
  • Erasure ("the right to be forgotten") of your personal information;
  • Restriction of processing in the circumstances the law allows;
  • Data portability — to receive personal information you provided to us in a structured, commonly used, machine-readable format, and to transmit it elsewhere;
  • Object to processing based on our legitimate interests;
  • Withdraw consent at any time, where processing is based on consent (this does not affect the lawfulness of processing before withdrawal);
  • Not be subject to automated decision-making that produces legal or similarly significant effects — we do not do this;
  • Lodge a complaint with your local supervisory authority if you believe we have not handled your data lawfully.

To exercise these rights, follow the instructions in Section 6. Because the site holds almost nothing, a request will in most cases be answered by confirming that we hold nothing about you, or by deleting the small amount we do hold (for example, an email you provided).

A note for visitors in the EEA or UK. This site is aimed at adults in the United States, but it is reachable from anywhere. Usage reporting — including the page views and interaction events sent to Umami Cloud — is on by default on every page of the site and does not ask for your consent before the first count or event; you can turn it off in Site Settings. We have asked counsel whether a default-on counter can rely on legitimate interest for EEA/UK visitors, and whether an opt-in choice must be shown to them; we may change this practice for those visitors based on counsel's answer.

6. How to Exercise Your Rights

To exercise any right, email [email protected] and tell us which right you wish to exercise and what information it relates to. If you have an optional account, the easiest way to verify a request is to sign in to it first — and most deletion requests can be answered the same way a person can delete the account themselves, as "The optional account" in Section 1 describes. If you do not have an account, we will verify your request based on what you can tell us about your interaction with the site, exactly as before. You do not need an account to make a request. You may designate an authorized agent; contact us to do so.

7. Responses to Your Requests

We will confirm receipt of your request and generally respond within forty-five (45) days (this may be extended by an additional forty-five (45) days where permitted by law, with notice). We respond electronically in a portable, readily useable format where feasible. There is no charge for a request (up to two per year); we may decline, or charge a reasonable fee for, requests that are unfounded or excessive, with notice and reason.

8. California "Shine the Light"

Under California Civil Code § 1798.83, California residents who have an existing business relationship with us may request information about our disclosure of certain personal information to third parties for the third parties' direct marketing, if any. We do not disclose personal information for third-party direct marketing, so there is no such disclosure to report. You may make this request no more than once per calendar year.

9. Children's Privacy

The site is intended for Catholic adults aged 18 and older. It is not directed at children, and we do not knowingly collect personal information from anyone under 18. If you are under 18, please do not use the site — in keeping with our Terms of Service (§7).

Because we collect almost nothing by design, a child could not ordinarily provide us personal information even by using the site: nothing typed inside the Daily Offering, Discernment, Prudence, Stillness, or the homepage's Virtue Companion is ever transmitted to us. The only paths by which personal information could reach us are the consent-based Feedback form and the consent-based star rating just below the question box on the Discernment page (both of which ask respondents to keep identifying details out), an email address entered on the optional updates signup, an address typed on the optional "Email me this reflection" form on the Discernment page (used for that one email; when the updates box is left unchecked, nothing is stored), or the optional AI helper. The Discernment page's two Share controls also carry typed text out of the site, but only when you press them: the question and the reflection go from your device directly to where you choose — the share sheet, your clipboard, an email you send, or an image on your device — and never reach us. The homepage's Virtue Companion adds two more Share controls, and they work the same way for its card — built from the site's own words, never from anything typed — and its microphone and spoken reflection use the same services as the Discernment page's, which retain nothing (see Sections 1 and 4). The one other place typed text leaves the site through a service we use is the Faithful Screen Christianbook search — the words you type pass through our server to Christianbook's product-search service to find matching titles (see Section 3) and are not kept by us. The updates signup is for adults 18 and older. The optional account is for adults 18 and older too: creating one asks you to confirm that, and we record that confirmation — not your age. If you believe a child has provided us personal information through any of these paths, contact us at [email protected] and we will delete it promptly and confirm the deletion to you.

10. Other Terms That Apply

This policy is about privacy. Two related legal topics are governed by our Terms of Service, which apply when you use the site, and we do not repeat them here:

  • Disclaimers and limitation of liability. The Terms of Service (§11) describe the site's "as is" status, honest disclaimers about content and third-party AI, and the LLC's limitation of liability. Those provisions apply to your use of the site and are not altered by this policy.
  • Governing law and venue. The Terms of Service (§15) state that the site is governed by the laws of the State of Illinois and that disputes are resolved in the state and federal courts located in Cook County, Illinois. That applies to your use of the site; this policy does not change it.

11. Contact Us

Email: [email protected]
Mail: One Small Offering, LLC, 980 N Michigan Ave Ste 1090, PMB 935469, Chicago, Illinois 60611-4521

One Small Offering, LLC is a formed Illinois entity.