Beam Church
Privacy notice (pilot)
This is a working notice for MVP pilot churches. It is not legal advice. Each church remains the controller of its congregational data; seek counsel before a public launch, especially where religious belief may be special-category data under GDPR.
What we process
Account identity (name, email), church membership and roles, optional profile fields you choose to share, attendance records, form submissions, event RSVPs, visitor welcome submissions (with consent), QR destination configuration, and audit logs of sensitive admin actions.
Public surfaces
Churches may publish a discoverable profile (name, location, about, contact, service times, public links). Visitor welcome forms only create a visitor record when someone voluntarily submits with contact consent. Scanning a QR code alone does not create a visitor or member.
Your choices
Members control optional profile visibility where the product supports it. Church administrators can export church-scoped data from Settings → Data export. Deletion and retention workflows remain open pilot items — contact your church administrator for requests during the pilot.
Security
Access is enforced per church (and optional branch) in the API. Demo accounts are labeled [DEMO] and must not hold real pastoral data.