Trust
Security at Beespo
Beespo brings the operational work of local callings into one workspace. This page explains, in plain language, how covered workspace content is protected, how access is limited, and where the product’s boundaries are. Everything here describes how the product works today, not a roadmap.
Last updated: July 30, 2026
Workspace isolation
Every Beespo workspace is isolated at the database layer using PostgreSQL row-level security. Access rules are enforced by the database itself on every query — not just by application code — so one ward’s data is structurally invisible to every other ward. There is no shared pool of data that a bug in a page could accidentally leak across workspaces.
Access inside a workspace
Within a workspace, access follows roles: owner, admin, editor, commenter, and viewer. Beyond roles, two protections exist for the most sensitive workspace content:
- Leadership meetings are shared explicitly. Each meeting series has its own access list, granted person by person. Membership in the workspace does not grant access to the bishopric’s agenda or its meeting summaries.
- People notes have explicit visibility. A note is visible only to its author unless the author deliberately shares it with the workspace. That choice is enforced when the note is read, not merely hidden by the page.
Workspace owners can manage members, including changing roles and removing access. That control applies only inside the Workspace. Beespo does not currently give a bishopric authority over an independently owned organization Workspace, determine when a calling ends, or automatically remove the Workspace owner.
Authentication
Sign-in supports email and password (with mandatory email confirmation) and Google sign-in. Sessions are managed by Supabase Auth with short-lived, automatically refreshed tokens. Signup to the platform itself is invite-only.
Encryption and infrastructure
All traffic is encrypted in transit with TLS, and infrastructure storage is encrypted at rest. Covered workspace content receives another layer: Beespo encrypts it with per-workspace keys before it reaches the database, with the wrapping key held outside the database. Browsing or copying the database alone does not reveal that content.
This is not zero-knowledge encryption. The application server can decrypt content to serve an authorized user. Beespo runs on Supabase (PostgreSQL, hosted on AWS) and Vercel. Transactional email is sent through Resend from an authenticated domain with SPF, DKIM, and DMARC.
Data handling commitments
- We never sell your data, share it with third parties for their own use, or use it to train AI models.
- Workspace owners can request deletion of their Workspace, and we will honor it.
- Access by Beespo staff is limited to what operating the service requires — support and incident response — never browsing.
Intended use
Beespo is built for the operational coordination around a calling — meeting agendas, assignments, speakers, activities, calendars, and follow-up. That is the work the product models, and it is the work its protections are designed around.
Confidential member information belongs in Church-provided systems and approved channels, not in Beespo. Membership status, temporal needs, worthiness or pastoral circumstances, and proposed-calling deliberations should stay where the Church provides for them. Encryption and access controls do not change that boundary — they protect the operational work; they are not an invitation to bring confidential records into it.
Product boundaries
Beespo is an independent product. It is not affiliated with, endorsed by, or an official product of The Church of Jesus Christ of Latter-day Saints.
Beespo complements the General Handbook and official Church systems such as LCR; it does not replace them. Official systems remain authoritative for policy, membership records, and required reporting.
Monitoring and status
The platform is continuously monitored for errors, and abusive traffic is rate-limited. When something is wrong, we say so: active incidents are surfaced inside the app and as a live status indicator in the footer of this site.
Reporting a vulnerability
If you believe you’ve found a security issue, please tell us at security@beespo.com — we read every report and will respond promptly. Please give us a reasonable window to fix an issue before disclosing it publicly.
What we don't claim
Beespo is a young product, and we’d rather be plain about where we are: we have not yet completed a formal third-party audit such as SOC 2. We onboard wards one at a time partly for this reason — it keeps the blast radius of any problem small while the platform matures. As the product grows, this page will grow with it.