WBC Safety

Privacy

Effective October 3, 2026

WBC Safety is a private coordination service for approved Waldo Baptist Church safety-team members. This notice covers the WBC Safety app and wbcsecurity.org. For support or privacy requests, contact the developer, Damen Troutman, at damentroutman@protonmail.com.

Information used by the service

We store your member name, phone number, role, account status, password verifier and sign-in sessions to provide and protect team access. The service also stores assignments, coverage requests, service history, Ponderance discussions, messages, reactions, files you choose to upload, team alerts and alarm activity.

Notification preferences, device notification tokens and delivery results support alerts. Security and administrative records help operate the service, investigate problems and manage access. Participation and content in a church team may reveal religious affiliation or beliefs. Uploaded files may contain personal information you choose to share.

For internal team administration, we record successful sign-in counts, the most recent successful sign-in and approximate most recent authenticated access for each platform: iPhone, Android, browser or installed web app. Administrators use this information and notification-registration status to understand adoption and coordinate team communication. We also summarize retained service-assignment history to help distribute scheduled work. These summaries do not prove attendance or notification delivery. Usage tracking starts with this update; earlier sign-ins are not reconstructed. This feature does not store IP addresses, full browser/device identifiers, browsing histories or message content, and does not use a third-party analytics service.

Who can see information

Approved team members can see shared team content and schedules. Individual conversations and their files are available to their participants through the app. Administrators manage team accounts, shared activity, platform-usage summaries and service-assignment summaries; they do not receive general browsing access to individual conversations.

Text that may be abusive is held before posting and shared with administrators for a decision. Only the flagged text is shared; files attached to held text stay in the author’s draft and can be sent separately. Administrators cannot browse the rest of an Individual chat or its files through this review queue. Authors can see decisions and withdraw pending text in My content reviews.

If you report a message or comment, its selected text, attachment names, your name and your explanation are shared with administrators for review. Reporting does not grant access to the rest of the conversation or the attached files. Administrators can remove the reported message and manage an account’s team access.

The service uses hosted infrastructure, including OpenAI Sites and Cloudflare, for application hosting, database and file storage. Apple processes iPhone push notifications; Google Firebase Cloud Messaging processes Android push notifications and installation identifiers; website notifications use the relevant browser’s push service. Google Analytics is not enabled for the Android app. These providers may process technical information needed to deliver and protect their services. Messages are not presented as end-to-end encrypted.

Phone permissions and biometric sign-in

Biometric sign-in is optional. iOS or Android performs fingerprint or face matching; WBC Safety receives an authentication result, not your fingerprint or facial scan. A saved sign-in uses protected device storage. The app does not request GPS location or upload your address book. Post details included in an alarm come from your team assignment, not GPS.

You choose whether to allow notifications and message previews. Your phone’s lock-screen, Focus and notification settings also affect what appears. Files are uploaded when you choose to share them. The app has no advertising or cross-app tracking features.

Retention and account closure

Ordinary removal from the team deactivates access and preserves archived team records. Deactivation is not permanent account deletion. Records are not automatically erased simply because an account becomes inactive.

To permanently delete your account, open Settings, expand Support & account in the app (Account controls on the website), and choose Delete account. Enter your current password and confirm the deletion. This removes your sign-in, platform-usage summaries, messages, comments, reactions, Ponderance contributions and notification registrations from the service. Shared service and alarm records are stripped of your identifying details. Your assigned posts become vacant. Files immediately become inaccessible and are queued for removal from storage, with retries if storage is temporarily unavailable. If you are the last administrator with other active members, choose a member to take over. Deletion is separate from ordinary archival deactivation. Contact the address above for access, correction or help; do not email your password or sensitive conversations.

Data already received or independently saved by other members cannot be removed from their devices by this service. Infrastructure backups and operational records may require separate handling; we do not promise that every backup copy disappears immediately.

Your choices

You can change notification and preview preferences, sign out, manage saved sessions, choose whether to use biometric sign-in, report messages and block individual messaging. Blocking individual chat does not hide shared Team Chat, assignments or operational alarms.

Changes and questions

Changes to this notice will be posted here with an updated effective date. Contact damentroutman@protonmail.com for questions about this notice or your information.

Help & support