Monroe First App Privacy Policy
Prepared November 10, 2026
Effective date: November 10, 2026
1. Who we are and what this policy covers
This policy explains how Monroe First Methodist Church, registered in Georgia, USA (“the church,” “we,” or “us”), handles personal information in the Monroe First church app, including the account information used to sign in to the app.
The app provides church information, events, announcements, locally saved activities, and links to worship media and other services. You can browse public church content as a guest without creating a church account.
This policy covers only the church app. It does not govern the church’s main website www.monroefirst.church, its forms, or other services opened from the app. Those destinations have their own privacy practices. The separate Daily Bible Reader also has its own accounts and reading progress.
The app and companion church website use the same church sign-in account. Although this policy covers only the app, deleting that shared account also removes the website sign-in account. It does not delete the separate Bible Reader account or reading progress.
2. Information handled by the app
Church account information. If you create or use a church account, Clerk, our authentication service, handles your email address, password or chosen sign-in provider, account identifiers, and sign-in/session information. If you add a name while signed in, it is saved with your church account. A connected sign-in provider may supply profile information according to the permissions you authorize.
Date of birth for the age check. The login page requires your full date of birth, including month, day, and year, to check that you are at least 16 before you proceed with email or Apple/Google authentication. This check runs on your device. The entered birth date is not saved to your account or sent to the server.
Device-local preferences. A guest name, guest-browsing choice, and saved public event snapshots are stored on your device. This preferences feature does not upload them to a church account or synchronize them between devices. Other people using the same device may be able to see them.
Connection information. Loading events and announcements or using sign-in sends network requests to the app’s server or authentication service. The receiving services can receive connection information such as IP address and request details.
Messages you choose to send. If you email or otherwise contact the church, the church receives the contact information and message you provide. The native app does not have its own prayer-request submission form; its prayer link opens the church website.
3. How information is used
The church will not use your information without your permission.
The app uses account information to create and authenticate church accounts, verify email addresses, recover access, maintain sign-in sessions, and display your account name. Local preferences let you continue as a guest and view activities you saved on the device. Network requests deliver public church content. Information you send to the church allows the church to respond to your request.
4. Service providers and outside destinations
We do not share your personal information with other app users or make it public. Clerk and hosting providers process information to provide sign-in and app services, as described in this policy.
Clerk — church authentication: processes church account and sign-in information. Clerk’s privacy information describes its own policy scope; that page expressly says end-user Customer Data is governed by customer policies and applicable agreements. It is not a substitute for this church policy.
Replit — app hosting infrastructure: Replit provides hosting infrastructure for the app’s services. Requests to the app’s server pass through this infrastructure and include connection and request information.
The main church website — information and forms: visit, care, prayer, calendar, and event links may open the church’s existing website. Its prayer form asks for a name, optional email address, and prayer request. Prayer requests are seen only by church staff unless the person making the request states otherwise. The native app does not collect the request itself.
SermonCloud — worship media: live and archived worship links open SermonCloud. The media service handles information under its applicable policies.
Google Maps — directions: the directions link sends the church’s public destination address, not GPS coordinates gathered by this app. Maps may handle additional information when you use its service.
Daily Bible Reader — separate reading service: the Bible Reader maintains its own account and progress arrangements. The church app does not import or synchronize your private reader progress.
Email, phone, and other event links: these open the relevant app or destination, which handles the interaction under its own practices.
5. Cookies, tracking, and device permissions
The native app does not add advertising tracking and does not request access to your contacts, camera, photos, microphone, or device location. Local guest preferences and saved activities are not advertising profiles.
Authentication and browser destinations have their own storage and session mechanisms. A guest option does not prevent network requests or remove providers’ privacy responsibilities.
6. Storage, security, and retention
Church authentication information is handled through Clerk. The app does not maintain a separate church password database. Local preferences are stored on the device.
We keep your app account information until your account is deleted by you or an administrator. Members can delete their own accounts. After deletion, your information no longer remains in the app.
7. Your choices and account deletion
Browse as a guest: a church account is optional for public content.
Change a name: use More to update your name. A signed-in name is associated with your church account; a guest name is stored on the device.
Clear local preferences: choose More → Clear data on this device. This removes the saved name, guest choice, and saved activities on that device. It does not delete your church account or separate Bible Reader progress.
Delete your church account: open More, sign in if needed, select Delete my account, and confirm. This deletes the shared church sign-in account used by this app and the companion church website. You may need to sign in again before deletion for security.
Separate Bible Reader: deleting the church account does not delete your separate Daily Bible Reader account or reading progress. Manage those through the reader and its own support arrangements.
Contact the church if you need help with account deletion or have a question about information you provided. The membership administrator handles privacy requests.
8. Children and families
Church accounts are for people age 16 and older.
The login page requires a full date of birth for sign-in and account creation. It rejects incomplete, invalid, future, and under-16 dates before starting authentication. The cutoff follows the current date on the device rather than a fixed calendar date. Guest browsing of public church content remains available without a birth date.
9. Changes to this policy
When privacy policies are updated or tightened, users will be informed in advance.
10. Contact the church
Monroe First Methodist Church
400 South Broad Street
Monroe, Georgia 30655
Email: office@monroefirst.church
Phone: (770) 267-6525
Website: monroefirst.church
The church office is the contact for privacy and app-support requests using the email address and phone number above. For privacy requests, ask for the membership administrator.