How we handle your information
When you use any tool on apps.reedlightbooks.com, the words you give us
— a song lyric, a sermon manuscript, a set of preaching notes, a fragment of imagery —
are sent to the AI provider that does the analysis, the result is returned to your
browser, and the original text is discarded. We do not save it. Below is the full story,
in plain language, of what we keep, what we never keep, and why.
The principle. A worship song is the labor of the composer, the publisher, and the congregation that has carried it. A sermon is the labor of the preacher and the local church that received it. Those words belong to them — not to us. It would not be honoring to the creative work of composers or to the pastoral work of preachers for Reed Light Books to warehouse their material on our servers, much less to study or train against it.
It is also not in our best interest to hold that material. A server full of pastoral writing is both a security target and a temptation. The cleanest way to behave well is to never possess it in the first place — analyze the text, return the result, let the words go.
The following is true for every analysis run by every user, on every tool in the apps suite. None of it is written to a database, a log file, a backup, or a cache:
Each tool handles the words you give it the same way at the bottom of the stack — send, analyze, return, discard — but the persistence story above that differs in small, honest ways:
You paste lyrics (or give a song title, or paste a URL we fetch on your behalf). The lyrics are sent to Anthropic with the analysis prompt. The structured result is returned to your browser. The lyrics, the URL, and the analysis body are not written to disk on our server. Each analysis is one-shot — if you want to keep the result, print it or save the page; we won't have it tomorrow.
paste → AI → result → vapor
Same flow as Clear Worship. The lyric, the lens selections, and the lens analysis pass through and are returned to you. Nothing about the song or the analysis is stored on our side.
paste → AI → result → vapor
You submit a sermon manuscript, outline, or imagery notes. The text is sent to Anthropic for analysis. The result is returned. The sermon manuscript itself is never written to disk on our server.
What is saved — to your own user record, on your line, only — is the produced analysis notes: the synopsis, the paraphrased doctrinal claims, the named imagery, the pastoral observations across each lens. These are the AI's notes about the sermon, kept so you can revisit them later from your History sidebar. The original manuscript is gone.
We cap the analysis history at the most recent 5 (Free) / 25 (Pro) / 100 (Admin) entries — older ones are dropped automatically. You can delete any entry yourself at any time from the sidebar. If you delete your account, your history goes with it.
paste → AI → result returned → manuscript discarded → notes only on your record
The current Trend Map runs on a built-in demo library. You cannot upload your own song list to it yet (that's Phase B). No data of yours touches the server.
demo data only
Sermon Lens ships with four pre-loaded sample sermons so a first-time visitor can try the tool without uploading their own work. Those four are all publicly available material, used here for demonstration:
These ship as static files inside the app. They are not user data, and using them does not consume coins. The pre-baked analyses you see when you open a sample are fixtures we prepared once — the model is not being re-run on them every time.
To deliver the analysis, your request necessarily passes through a few services. Each one is listed below with what it sees and what it doesn't:
api.allorigins.win CORS proxy).
When you use Clear Worship's Search by Title, your browser sends only
the title string. No credentials, no lyrics, no account information.
mail.supremecluster.com).
Delivers transactional email — verification, password reset, receipts. Carries
only the message body of those emails, never your lyrics or sermons.
First, because it is honoring. The worship songs we analyze are the labor of the people who wrote them, the publishers who carry them, and the congregations that have sung them into being. The sermons we analyze are the labor of preachers and the local churches that received them. Those words are theirs. We are a tool that helps you think about them — not a vault that owns them.
Second, because it is wise. A growing pile of pastoral writing on our servers would be both a security target and a temptation. The cleanest way to refuse temptation is to never possess the material. So we don't.
Third, because it makes our promises easy to keep. "We don't sell your data" is a much harder promise to keep when you have a lot of it sitting around. The discipline of not storing it in the first place keeps us honest by default.
If we ever change how data is handled — add a feature that requires storing something new, change a retention window, swap a third-party service — we will update this page and note the change in the public changelog. The effective date at the top will reflect the most recent revision. Material changes will also be flagged on your next sign-in.
Write to legal@reedlightbooks.com and we'll answer plainly. If you'd like the full legal statement, see our Privacy Policy and Terms of Use.