Congregation Assistant
Your data. Clear answers.
Who can see congregation records?
Standard mode stores records in Supabase in Mumbai, India. The service operator can technically access server-stored data with production credentials. Application role restrictions do not remove that ability.
| Role | Access in the app |
|---|---|
| Main administrator | Congregation administration and records. |
| Secretary / Service Overseer | Authorized people and service-report tools. |
| Group Overseer | Assigned group records and scoped report links. |
| Meeting / duty overseers | Their approved scheduling tools and minimal authorized people lists. |
| Publisher | Authorized personal and linked-household reporting. |
| Public link holder | The form or published schedule granted by that link. |
How is it protected?
HTTPS protects connections. Database role and congregation checks restrict application access. Public bearer links grant access to their scoped form; share them privately and revoke unwanted links. Current devices can retain authorized cached records for offline use.
Private mode
Private mode is unavailable until the full encryption tests pass. Current records use Standard mode.
On-device assistant
The command parser runs in your browser. Prompts are not sent to a server, retained as history, or used for training. It uses records your account is already allowed to access. Only the structured record you confirm is saved.
Where the limits are
A compromised device, shared account, screenshot, forwarded link, or downloaded document can expose records. Protect your devices and exports. An independent security review is planned. We do not present that as a completed audit.
Report a security concern to your congregation administrator (security email is not active yet). Please send no private congregation records initially.