About MySpiritualBattle

Battle Signals and disclosure levels

What it does. A member names what they are facing by choosing a category, writes a title and an optional private note, then picks a disclosure level and an audience. For the Shield Circle, connections and group audiences, the "Enter Battle" screen shows how many people will receive it before it is sent. There are limits of 10 signals per day and 20 open signals.

Four disclosure levels.

• Just pray for me (status only): people see only that prayer is needed.
• General battle (category): people see the category but not the title or note.
• They can ask (details): people see the title and category and may check in.
• Full context: trusted people can also read the private note.

Five audiences. Shield Circle, connections, one prayer team or small group, the whole church, or only me (recorded privately, nobody notified). Group signals go only to that group and never widen to the church.

Who sees what. Only the audience chosen, and only up to the level chosen. The default level is the general category.

What leaders can do. Leaders see a signal only if it was shared with them as a member, or in a report from a member who could read it. A leader can restrict a member's church-wide sharing (see Moderation). Holding the church leader role gives no access to groups. A leader sees a group's signals only as a member of that group, or in a report from a group member who could read it, limited to what that member could read.

The Battlefield dashboard

What it does. The home screen after sign-in. It shows the member's current signal and who is praying, their active signals, signals from others that need cover, and the allies in their Shield Circle, with shortcuts to start a battle, open the Armory or open the circle. Counts of prayers and Scripture received are plain tallies. Updates arrive live.

Who sees what. Each member sees only their own signals and signals shared with them, at the level shared.

What leaders can do. Nothing extra. There is no leader dashboard of members' battles.

Battle detail: prayer and responses

What it does. For supporters: raise a shield (pray), stand watch on a schedule, send a short word of encouragement, or send Scripture found by topic. For the owner: see who prayed, the encouragement and Scripture received, and who is standing watch; post updates; mark the battle as improving or needing more help; then declare victory or end it quietly.

Who sees what. Supporters see only what the owner chose to share, and are told to pray without pressing for details when there is no note. Updates notify only the people who prayed or stand watch. They are not a broadcast.

What leaders can do. As members, the same as anyone. Supporters can report the owner from this screen.

Shield Circle and connections

What it does. Members search for others by name or handle and send a connection request. Connected members can be invited into a Shield Circle, a small set of people the member personally trusts. Invitations can be accepted, declined, withdrawn or removed at any time.

Who sees what. Circle membership never exposes private notes by itself. Every signal still carries its own disclosure level. People who turn off "Discoverable in search" can be found only by existing connections and church members.

What leaders can do. Nothing special. Circles are personal, not managed by the church.

Prayer Watch

What it does. A supporter commits to check in on a battle every 12 hours, daily, every 3 days or weekly. Check-ins that come due appear in the Watch queue, where the supporter can mark them done and add an optional word, which is delivered as encouragement. The next check-in is then scheduled.

Who sees what. The owner sees who is standing watch and how often. The queue shows only the battles the supporter can already read.

What leaders can do. Nothing special.

Messages

What it does. Private one-to-one messages between connected members, with unread counts and live delivery. A reference such as John 3:16 can be looked up and added to a message.

Who sees what. Only the two people. Blocking stops messages.

What leaders can do. The moderation console shows reports and an audit trail. It has no inbox for browsing members' messages.

Accountability partners

What it does. A member asks a connection to hold them to one specific thing, such as "Scripture before my phone each morning", on a rhythm of daily, every 3 days, weekly or every 2 weeks. The other person accepts or declines. Either side can nudge the other and either can end it.

Who sees what. The two people involved. Accountability is offered only between connections.

What leaders can do. Nothing special.

Victory Reports

What it does. When an owner closes a battle they may tell what God did: a title and a short story. It is optional. They choose who sees it (the people who prayed, their Shield Circle, or their whole church) and may share it without their name. Publishing closes the battle. The Victories page lists the reports shared with the member.

Who sees what. The audience chosen. Sharing anonymously hides the name, the link to the battle and the sender from the Victories list and the notification. The category is shown only to people who could already see the category. People who prayed may still recognise the story from its timing or details. A Shield Circle report itself is shown only to accepted members of the author's own Shield Circle. Everyone who prayed is still told that a report was shared (without the name if it was shared anonymously). Only the owner is shown, on the battle page, whether a Victory Report exists for it; people who prayed are notified when one is published.

What leaders can do. Nothing special. Reports are never scored or ranked.

Signals inbox and notifications

What it does. The "Signals" page lists what reached the member: signals, prayers, Scripture, connection and circle invitations, watch check-ins, updates, Victory Reports, accountability requests, group invitations and messages. An unread count shows in the menu and a bell, and everything can be marked read.

Who sees what. Each member sees only their own. In Settings they can turn off five kinds: Battle Signals, prayers, reinforcements, connection requests and Shield Circle invitations.

What leaders can do. Nothing special.

Groups and prayer teams

What it does. Anyone can start an invitation-only small group, with no church needed, and invite their connections to it. Inside a church there are two more kinds: small groups open to any church member, and prayer teams, which are invitation-only and can be created only by a church leader. A church group's leader invites members of that church. Members see their groups, accept or decline invitations, leave, and open each group's queue of open signals. A group leader can use Hand over leadership to choose an accepted member as the new leader, and may either step down to member or stay on as co-leader; the new leader is told. A group's last leader hands over before leaving, and cannot leave while other members remain. In Demo Mode, hand-over uses sample members and resets on reload.

Who sees what. A signal sent to a group is visible only to that group's members, at the level the sender chose, never to the wider church. Group membership can be read only by the group's accepted members; someone with a pending invitation sees only their own row.

What leaders can do. Create prayer teams. Holding the church leader role gives no access to groups. Only a group's accepted leader can invite, and no one can invite themselves. A church leader can still join an open small group like any member, and then sees its open signals at the level each sender chose. A member under a moderation restriction cannot post to, join, or accept an invitation to that church's groups.

Church Hall

What it does. A person belongs to one church. They can join by entering its code when registering, or later find a verified church and send a request with a short message. A church leader approves the request; a decline is silent, so nothing is sent to the person. A church that is not yet listed can apply, and a site reviewer, designated by the operator, approves the application and the church is verified. A person with no church can still use the app and start their own small groups. The Hall shows the church name and place, whether it is verified, a member directory (up to 60 members) with search and a Connect button, and its groups. Leaving removes the person from the church's groups and prayer teams, withdraws signals they shared with the church or its groups, and ends watches that depended on the church. Their own church-less groups are not affected. The last leader cannot leave while members remain.

Who sees what. Members see the directory of their own church. Church membership never widens what a signal reveals. Leaders and admins (unless blocked with the requester) see the join requests sent to their church.

What leaders can do. Approve or decline join requests, see the church code and rotate it, create prayer teams and use the moderation console.

The Armory

What it does. Scripture by topic. A member searches what they are facing (anxiety, anger, grief) and opens a topic to read its passages and related topics. A full chapter reader lets them read a passage in context and move between chapters. They can save verses to "My armor", send a passage into a battle, or send it to a friend. Verse text is the World English Bible, which is public domain. A verse lookup by reference is also available when writing messages.

Who sees what. Saved verses are the member's own. Search words that signal crisis lead to Get Help rather than a list of results.

What leaders can do. Nothing special.

Get Help and crisis care

What it does. A Get Help page is reachable from every app screen, the sign-in pages and the site footer. Without an account it shows the international emergency number (112) and a helpline directory; the lists for the United States, Canada, the United Kingdom and Australia appear after signing in. When someone chooses a sensitive category, crisis resources appear before they write and again after the signal is sent. A sensitive category never stops the signal from being sent. Titles and notes are also screened automatically for crisis wording so that help can be offered, and supporters of a sensitive signal see guidance on standing with someone carefully.

Who sees what. Choosing a sensitive category does not alert the church, the circle or anyone else. Below the category level, everyone sees the same generic note.

What leaders can do. The page invites leaders to review the list against the referral paths their church already uses. Numbers change, so this should be checked before members are invited. This app cannot call emergency services.

Reporting and blocking

What it does. From a signal or a connection, a member can report a person (harassment, safety concern, inappropriate content, spam, impersonation or other) with a reason and optional details, mark it urgent, or block instead. Blocking removes the connection, circle membership and shared signals in both directions, stops messages, and can be undone in Settings. Members can see the status of reports they filed but are never told who handled them.

Who sees what. If the two people share a church with another leader, that church's leaders see the reporter's name, reason and details, and the parts of the signal the reporter could already read. A report is never shown to the person it is about. If there is no shared church, no leader receives it, but blocking still works at once.

What leaders can do. Review and act on reports (see Moderation).

Moderation and audit trail

What it does. A Moderation page appears only for church leaders and admins. Its queue lists open reports, urgent ones marked, with the reason, details, a snapshot limited to what the reporter could read, and how many earlier actions that account has had in this church. A leader can start a review, warn, restrict for 7 days (while restricted, their church-wide signals are not shared with that church, and they cannot post to, join or accept an invitation to that church's groups; Shield Circle, connections and only-me still work), remove from the church (which also removes them from that church's groups and removes their signals from those groups), close as actioned or dismiss, adding a note. An Audit trail tab lists moderation activity.

Who sees what. Leaders see reports routed to their church and never a private note that was not shared with the reporter. Every action is logged with the leader's name. A leader cannot restrict or remove another leader (a fellow leader can still warn them or close a report about them), and a reported person cannot review a report against themselves. A leader's note on an action can be read by the person it concerns.

What leaders can do. Everything on this page. Restricted members can still post to their Shield Circle, connections or only me, and crisis resources stay open to all.

Settings

What it does. A member edits their display name, handle, favourite Scripture and region (which decides the crisis numbers shown). They can show that they are available to talk, choose whether they are discoverable in search, set notification preferences, unblock people and review the reports they filed.

Who sees what. Discoverability and availability control how others find and see them.

What leaders can do. Nothing special.

Installable app

What it does. The site has a web app manifest and a service worker, so a phone or computer can install it with its own icon and window. If the network is down, the cached home and app start page are shown. The error pages show an emergency number (112) and a link to Get Help.

Who sees what. No extra data is shared. Nothing is installed through an app store.

What leaders can do. Nothing to configure. Members install it from their browser.

Demo Mode

What it does. Anyone can explore the app at /demo with no account. Sample data is shown, and what a visitor enters stays in their own browser (local storage). It is not sent to the server. Creating battles, Armory searching and saving, Victory Reports, messages, accountability and Watch check-ins work in the browser. Features that need other real people, such as people search, reports and live delivery, are previewed or explained instead. Creating your own group, asking to join a church and applying for a church work in the browser. A leader's approvals, code changes and leaving, and the site reviewer page, are samples that reset on reload. Inviting people and joining real groups need an account.

Who sees what. Only the visitor. Clearing browser data removes it.

What leaders can do. Use it to show the church what the app looks like before anyone signs up.

Accounts and password recovery

What it does. Members register with their name, email and a password of at least 8 characters, and may add a church code, or find a church after signing in. Email confirmation may be required. A forgotten password is reset through an emailed link. If the operator has configured it, sign-in and registration use a Cloudflare Turnstile human check.

Who sees what. Accounts are handled by Supabase Auth. See the Privacy page for what is stored.

What leaders can do. Share the church code, shown to leaders and admins, with members, and rotate it if it spreads too far. Leaders cannot read member passwords or sign in as a member.