1. Scope and data controller
Better Day Works develops and operates the Church Manager platform. The organization managing a church workspace determines what church records its authorized staff enter. Church Manager is currently restricted to fictitious test data; real church member, attendance, donation, or financial information must not be uploaded during the pilot.
2. Information we collect
For accounts and sign-in, Church Manager may store your name, email address, account identifiers, password verifier (not your plaintext password), email-verification status, session and device metadata, invited church roles, and security audit records. The service also stores church workspace details and the test member records and changes that authorized users choose to enter.
For the offline-first web client, your browser may store a session token, selected church, locally entered test records, pending synchronization operations and change cursors through localStorage and IndexedDB. Current browser storage is not encrypted at rest; use only trusted devices and no real church records.
3. Google sign-in
When you choose Google sign-in, Church Manager requests only the basic openid, email and profile permissions. Google supplies an account identifier, name, email address, and email verification information to authenticate and link your Church Manager identity. The application uses the stable Google account identifier to recognize your sign-in. We do not request access to Gmail messages, Google Drive, Google Calendar or your Google password.
Google sign-in is optional and available only to approved pilot accounts when activated. If enabled, Google processes authentication under its own privacy practices. Church Manager will not use Google profile data for advertising or sell it to data brokers.
4. How data is used
Account data is used to sign you in, protect sessions, identify the churches you can access, enforce role permissions, investigate security issues, and support account recovery where enabled. Test church records are used only to provide application functionality and sync permitted changes across authorized devices.
5. Access and sharing
Church information is available only to users who have been assigned a role within that church’s workspace. Authorized church owners and administrators may invite other users. Google receives information necessary to authenticate your Google session; server infrastructure providers process information as needed to operate the hosted application. We do not sell account or church data.
6. Storage, security and retention
The application server stores account and test workspace data in a private database on the Better Day Works VPS. Access control, HTTPS transport, sessions, and backups are used to protect service availability and restrict access. No security method eliminates all risk. Browser-side records and session data are not encrypted at rest in the current pilot.
Data is kept while needed to operate the pilot, administer accounts, meet security or legal obligations, or complete a requested deletion. Backup copies may persist until their normal backup retention cycle or are removed through a verified deletion procedure. No specific automatic deletion deadline is promised at this stage.
7. Your choices and rights
You may request access, correction, or deletion of your account information. Church workspace owners coordinate requests involving records belonging to their church. See Account & Data Deletion for the current manual request process. Google sign-in permissions can also be revoked from your Google Account settings; revocation alone does not erase Church Manager data.
8. Children and sensitive information
Church Manager is designed for authorized church administrators, not for children to sign up independently. Do not submit personal information about minors, sensitive pastoral notes, financial data, real membership rosters, or other live records during the pilot.
9. Changes and inquiries
This policy will be updated before opening public registration or adding new data collection. Pilot participants should contact the project operator through their original invitation channel for questions or privacy requests. A dedicated public support mailbox is not yet active; see Support.