This policy explains what Biblical Battle Plans collects, who can see it, who helps us run the Service, and how to delete it. It covers the website and the iOS app.
Last updated: October 7, 2026
Biblical Battle Plans (the "Service") is operated by ShirePath Solutions LLC ("we" or "us"). The Service is offered to users in the United States, and this policy is written for them.
Because the Service is about reading the Bible, using it can reveal your religious beliefs. We treat everything above as sensitive and use it only to run the Service.
Members of a guild you belong to can see:
Anyone with a guild's invite code can see its name, description and member count. Your email address, private journal, disciplines and preferences are never shown to other users.
The website uses a session cookie to keep you signed in. It also keeps some data in your browser on your device:
Signing out does not remove these copies. Clearing this site's data in your browser settings removes all of them, so do that after signing out on a shared device. If you turn on browser push notifications, we store the push subscription your browser gives us.
We use your IP address to limit repeated attempts at sign-up, password reset and error reporting, your email address to limit repeated sign-in attempts and password reset requests, and your account id to limit how often some actions can be repeated. Each is stored with a short attempt counter for that purpose only, and the counter is deleted about a day after its time window ends. Our hosting provider also records IP addresses in its standard request logs.
When the app or website hits an error, it sends us a report with these fields only, plus your account id when you are signed in:
These reports do not include your name or email address. Our server adds your account id to a report sent while you are signed in, so that report is deleted with your account. A report sent while you are signed out, or while the app's sign-in has expired, has no account id, but a plan or guild id in it can be linked back to your account. If the iOS app sends a crash report, it also includes the crashed thread's stack trace and the app binary's identifier. The iOS app reports a crash on a later launch, so a crash report carries your account id only if you were signed in for the whole period the report covers. Otherwise it carries no account id and is deleted 90 days after it is recorded, like any report without one.
When our server fails while handling a request, it records the route, the request method, a request id, how long the request took, the signed-in account id, your browser's or app's user agent and any database error details. The error message can include the data the request sent, such as chat or journal text, an email address or a hashed password. We use these records to fix the problem and send each one as an alert to our team in a private Slack channel. An administrator can also ask Anthropic's Claude to summarize the last day of error records, which sends those records to Anthropic. We do not use usage analytics.
We delete error and crash reports from our database 90 days after they are recorded. The alerts already sent to Slack are not deleted automatically; they stay in that channel until we remove them.
We do not sell your information, share it for advertising, or show ads.
When you report a message, a guild or a member, we record your account, the reason and any details you add, the reported item, its author and guild, and a copy (snapshot) of the reported content: the message text, the guild name and description, or the member's display name and username. We email that report to our moderation inbox (conner@shirepathsolutions.com) through SendGrid, and an administrator reviews it. The reported user is not told who reported them, and the reported message is hidden for you.
An open report keeps its snapshot. Once the report is resolved, the snapshot in our database is deleted after 90 days. The rest of the report stays as a record of the decision. The emailed copy of the report, snapshot included, stays in our moderation inbox, and SendGrid keeps its own delivery records under its policy. If you delete your account, reports you filed and reports about you are no longer linked to your account, but a snapshot can still show your message text, display name or username: in our database until it is deleted, and in the moderation inbox.
Blocks are private. Only you can see whom you have blocked, and the blocked user is not notified. A block lasts until you remove it or delete your account.
We share information only with providers that run the Service:
Each provider handles data under its own privacy policy. We may also disclose information when the law requires it.
You can delete your account at any time from your profile on the website or in the iOS app. Deletion happens immediately:
Some copies outlast the deletion:
The Service is not for children under 13, and we do not knowingly collect information from them. If you believe a child under 13 has an account, contact us and we will delete it.
Data travels over HTTPS, passwords are hashed with bcrypt, and iOS sign-in tokens live in the Keychain. No method of transmission or storage is completely secure, so we cannot guarantee absolute security.
You can view and edit your profile and preferences in the app. To ask for a copy of your information or a correction, email us at the address below.
We may update this policy. We will post the new version on this page and change the "Last updated" date.