Scripture Reader Privacy Policy

Last updated: November 13, 2026

In short

Scripture Reader is a free Discord app with two parts: a voice bot that reads the Bible aloud in voice channels, and the study Activity, a shared Bible that people in a voice channel open together. Any server can add it: a server's managers choose to add the bot and the study. You can also add it to your own Discord account and read on your own in any server, even one that hasn't added it; nothing is posted to or kept for that server. It is run by Matt, one person who publishes as BilbroSwagginz; it is not run by a company or a church.

The voice bot on its own

Scripture Reader is a Discord bot, run by BilbroSwagginz, that reads the Bible aloud in voice channels. Use of the bot is governed by the Scripture Reader Terms of Service. Everything else we run is covered by our main Privacy Policy.

What the bot stores

For each server, the bot saves three settings, chosen by that server's managers:

Nothing else about servers or users is stored.

What it never stores

What it uses while running

To answer commands, the bot uses the commands you send, your display name (shown on the queue and the now-playing card) and who is in its voice channel. This is held in memory only, and it is gone when the reading session ends or the bot restarts.

Logs

The computer that runs the bot keeps short rotating logs, at most 30 MB in total, to fix problems. They hold server IDs, channel IDs and command names. They hold no message content and no user IDs.

Deleting your server's data

Remove the bot from the server, or have a server manager run /settings reset. Either one deletes the server's stored settings at once. In a server where Matt has blocked Scripture Reader, the bot doesn't answer /settings reset, so remove the bot instead. Backup copies of the settings file, when made, are deleted after 14 days.

Children

Scripture Reader is used through Discord, so Discord's age requirements apply to everyone who uses it. The bot collects nothing beyond what this page describes.

Credits

Scripture: Berean Standard Bible (BSB), public domain. Text file: Free Use Bible API (bible.helloao.org). Unless /about in your server names another recording, the audio is read by Barry Hays and dedicated to the public domain (CC0 1.0), and its verse timings also come from the Free Use Bible API. A recording named in /about is not covered by that dedication; its credit is the one /about shows, and its verse timings are made by Scripture Reader. Please do not record or share it.

Changes to this policy

If what the bot stores changes, this page changes with it. The date above shows the latest version.

Contact

Questions, deletion requests and problem reports: message bilbroswagginz on Discord, or email menoachcoach@gmail.com.

The study Activity

The study Activity is the shared Bible you open from the Activities menu (the rocket) in a voice channel. It runs on a separate server from the voice bot.

A server's managers choose to add Scripture Reader to their server, which brings the voice bot and the shared study. You can also add Scripture Reader to your own Discord account. Then you can open the study in any server, even one that hasn't added it, and read on your own there: the Bible, its notes, the older commentaries and search, with your own highlights and bookmark, and you can listen to the Bible read aloud on your own device, alone or in step with others in the call (below). A study room, raised hands and the voice bot reading aloud need the server to add Scripture Reader. In a server that hasn't added it:

Listening on your own: whenever you read on your own, in any server, you can play the Bible read aloud on your own device: the Berean Standard Bible, read by Barry Hays, a recording its publisher dedicated to the public domain. It is not offered in a study room, where the voice bot reads to the group.

Listening together: in a server that hasn't added Scripture Reader, people who open the study together in one call can listen in step. Each device plays the recording, and the study's web server keeps everyone's players at the same place. Anyone there can play, pause or move it, and the others see who did.

What it stores, and for how long:

What you type, in servers where typing is switched on:

Deleting your data, or the removal of your name (above), also deletes everything you typed and takes down the takeaway cards you posted. A leader can hide a typed item; a hidden item is deleted 30 days later unless the study's owner, or someone with the Reader role or Manage Server, shows it again.

In servers where detours, study pins and Read together are switched on:

In servers where the map, scheduled sessions, Compare and Words are switched on:

Reports: anyone can report a typed item. Matt then sees the item, who wrote it, the server and the reason, never who reported it, and can delete the item and stop its author typing in that server for 30 days. The app keeps who reported an item, only so it stays hidden for them, and deletes that with the item or with their data.

What it does not store: your voice, what you listen to, or who pressed "I'm lost" (the app remembers that for 3 minutes, only to count each person once).

What the voice bot shares with it: while anyone has the study open in a voice channel, the voice bot tells the study's web server who is in that channel (Discord user IDs, server nicknames, avatars, and whether each person can control or move the reader or has the Reader role or Manage Server), so the study can check who belongs in it. The study's web server keeps this in memory only and saves only the people who open the study themselves. For every server that uses the voice bot, the voice bot also tells the study's web server what it is reading there and where (the voice and text channels, the voice channel's name, the passage and the next few readings), so a study opened in that server can follow it. This is kept in memory only too, apart from the name of a voice channel where someone opens the study, which is saved with that room (above). The voice bot also tells the study's web server which chapters it can only read as a whole and, for a detour, who started it, in memory only. The voice bot's card in the voice channel's chat names the person whose request started each reading or detour; for the parts of Read together that the reader reads, that is the leader who opened it, or else a study leader in the voice channel (the study's owner, someone with the Reader role, a server manager, or whoever started the reader's session). The card is a normal Discord message.

Who sees it: highlights marked "Just me", your bookmark, your settings, "You missed", your reading progress, your takeaways and your Journal are visible only to you. Hand-up notes, and questions and prayer requests marked for leaders, are visible only to you and to the study's owner, the Reader role and server managers. A prayer request for the group is visible only to the people the voice bot confirmed in the room when it was added, and to those leaders. A takeaway card you post is visible to anyone who can read that voice channel's chat, including people who were never in the study. A reported item, with its author, is visible to Matt. A scheduled session's study name, passage and time show in the server's Events list to anyone who can see that voice channel, with no names. The usage record (below) is visible only to Matt. Everything else is visible only to people in the same voice channel's study. Recaps a leader posts to a Discord channel contain no names. Recaps go to the voice channel's own chat unless a leader picks another channel. Matt, who runs the app, can see stored data when fixing a problem or handling a report or a deletion request.

Deleting your data: open the Activity, then Settings, Your data, Delete my data. It works anywhere you can open the study, and deletes your data from every server. If you can't open it (for example after leaving the server), or you'd rather ask, message bilbroswagginz on Discord from your own account. You can also email menoachcoach@gmail.com; Matt will then ask you to confirm from your Discord account, so nobody can delete someone else's data. After you delete your data, a one-way fingerprint of your ID is kept for 8 weeks on the study's web server, with a daily copy on Matt's home server when copies are made there, only so that restoring a backup can't bring your data back. If a report led to a mute, the mute (your ID, the server and its end date) stays until it ends, at most 30 days, even if you delete your data. A one-way fingerprint of your ID, with the server and the end date, is also kept for 8 weeks, only so that restoring a backup can't lift the mute early. If you post a takeaway card, a one-way fingerprint of your ID with the card's Discord message IDs is kept for 8 weeks, only so that restoring a backup can't stop Delete my data from removing the card. These fingerprints are kept in the same deletion log, with the same daily copy on Matt's home server when copies are made there (if the study's web server loses its disk, a deletion or a mute made in its last day may have to be repeated, and a card posted that day may have to be deleted by a server moderator). Requests are handled within 30 days. If the bot is removed from a server, that server's study data is deleted 30 days later, apart from its usage record (below). If the voice bot or the study's web server was offline when it happened, it is deleted within 37 days of both being back online. Your "Just me" highlights, your bookmark, your takeaways and your reading progress are not that server's data, so they stay with you until you delete your data or your name is removed (above).

Where it runs and copies: the study's web server runs on Railway, in the United States. A copy of its database is made every night on Railway (7 kept) and, when copies are made there, every week on Matt's own server at his home (8 kept). Anything deleted, by you or by these time limits, is gone from every copy within 8 weeks; the usage record and its copy are described below. Railway keeps the server's logs, which contain no user IDs, names or typed text.

Usage record: the study keeps its own record of how it is used, to see how many people use it and to fix launches that fail.

The Bible text the study shows is the Berean Standard Bible (BSB), which is public domain.

Sharing: no data is sold or shared. There are no ads, and no analytics, trackers or scripts from anyone else; the study keeps only its own usage record (above). Discord's own handling of your data is covered by Discord's Privacy Policy.