Information we process
ChatGPT sign-in supplies account identity information such as your account identifier, name, and email address. Parish Commons uses this information to recognize you and apply access permissions. The app does not ask you to submit your ChatGPT password.
The app stores the profile and timezone you choose, your home parish and memberships, assigned roles, submitted prayers and other records, prayer days and their selected prayer or Scripture titles and references, book bookmarks, book-club membership and meeting dates, event responses, offers of help, invitations, permission attestations, policy acceptance, moderation results, and support requests. Some submissions can reveal religious affiliation, health information, bereavement, or other sensitive circumstances. Share as little identifying information as possible.
Hosting and security systems may process connection, request, and error information needed to deliver and protect the service. Browser storage is used for features such as retaining a pending invitation during sign-in and playback preferences. Invitation links can contain access tokens; share them only with their intended recipient.
Personal prayer calendar and book clubs
The personal prayer calendar stores only entries you explicitly record, including the date, selected prayer or Scripture identifier, title, references, and recording time. Opening a text or playing audio does not record a prayer day. The app shows your calendar only to your account; parish staff and other members cannot see it through their roles. It is stored in the service database and is not an end-to-end encrypted journal. Selected catalogue entries are not sent for AI screening.
You can backdate an entry, remove an entry from your active calendar, choose whether to display streaks, and export entries through Preferences. Days follow your saved account timezone; changing timezone does not move past entries. Earlier check-ins without titles remain labeled Prayer time. Streaks describe recorded dates, not the value of prayer.
Book clubs use private group membership. Invited members can see the selected book, description, reading deadline, meeting date and place, and discussion guide. The creator manages invitations and membership. Club text is subject to the same screening rules as prayer circles. Creating an invitation produces a shareable link; it does not send an email.
Calendar links open Google or Microsoft event drafts for you to review and save. Choosing one shares the book title and meeting details with that provider. Downloaded calendar files contain the reading deadline and meeting details. These are copies, not a connected calendar integration or automatic subscription; update your saved event when club dates change. Calendar sharing settings, outside-provider policies, and any copies you share determine who can see the exported details.
Optional location search — no tracking
Location is requested only after you select Find nearby parishes. The app first loads the same public church-location dataset for every visitor, then requests one browser-provided position for that search. The browser may use GPS, Wi-Fi, or other device information. A previous permission grant may be remembered by the browser, but Parish Commons still requires a fresh tap for each lookup. Declining permission does not prevent ZIP or town search or ordinary use of the app.
The distance calculation happens entirely in your browser. Parish Commons does not send your device coordinates to its servers or a mapping provider, place them in URLs, logs, browser storage, cookies, account records, or backups, or retain them for reuse. They are not shared with parish staff, sold, used for advertising or AI screening, or linked to your account. There is no continuous location watch, background collection, automatic location retry, arrival detection, or record of visits or movements.
After calculation, the app retains only the displayed church results and approximate distances in temporary page memory. Clear nearby results removes them. Leaving the directory section, hiding the page, or closing or reloading it also clears them. Canceling an unfinished search makes the app ignore a late location response; the browser controls the underlying permission prompt and location request. You can remove a remembered location permission using the site-permission controls in your browser or device settings.
This browser-only promise concerns the optional location feature. ZIP or town text that you submit through ordinary directory search is sent to the app server, and opening a church page requests that listing by its identifier. Hosting systems may process ordinary connection and request information, including IP addresses, to deliver and secure the site. The feature does not create a server-side location history. Your browser, operating system, and location provider have their own controls and policies, which Parish Commons does not control.
There is no embedded external map or location-tracking SDK in this feature. If you choose an outside map or directions link, the link contains the church destination without your device position or an origin parameter. That service may separately ask for your location under its own policy. Nearby results are approximate and limited to listed churches; the current Rochester pilot is not a complete national parish directory.
How information is used
Information is used to provide the features you request, remember your parish, enforce permissions, coordinate permitted community activity, screen submissions, review reports, respond to support and data requests, and maintain security. Audit records track administrative actions; they are not intended as a record of private prayer text.
Following a parish is a choice you make in the app. It does not prove sacramental status, registered parish membership, or institutional endorsement. Do not treat another user’s parish selection or activity as a verified religious record.
Audiences and parish boundaries
Private prayer intentions and prayer logs are not shown in ordinary parish staff views. Group records are limited by group access. Published shared content is shown to the audience supported by that record. Public content may be viewed by visitors who can access this pilot.
Remembrance entries and their tributes are restricted to the associated parish, with the applicable author and authorized staff access. Choosing a different parish does not turn a remembrance into an app-wide post. Parish-only content requires administrator-approved membership or an applicable author or staff permission. Following or selecting a parish alone does not grant that access. App membership is not the same as a verified sacramental register or a private conversation with clergy.
Household coordinator details are stored separately from the shared story and are available to the submitter and authorized care staff. Relevant coordinators may see the names, emails, and responses of people offering help. Parish administrators can see membership information needed to manage their workspace. Reviewers see material needed for their assigned review duties.
The operator and infrastructure providers may access information as necessary to operate, secure, troubleshoot, or meet legal obligations for the service. Private does not mean end-to-end encrypted or inaccessible to system administrators. Authorized viewers can also copy or share what they see; technical controls cannot prevent every such disclosure.
AI screening and your choice
Before submitting text, you are asked to consent to AI screening. When AI screening is enabled, submitted text, including a private prayer, is sent to OpenAI’s moderation service to check for categories of harmful content. AI screening may be unavailable in this pilot; the app shows its configuration status. It does not verify facts, fraud, doctrine, or consent. Do not submit sensitive information you do not want processed this way. You can decline and continue browsing without posting.
The screening request excludes authentication credentials, invitation tokens, account and recipient-email fields, and dedicated private coordinator-detail fields. Support requests go privately to the operator for manual review instead of AI screening. Information you type into the submitted text itself can still reach the provider, so omit unnecessary names, contact details, and medical information. The service records the screening outcome needed to enforce its publication workflow.
AI screening can incorrectly flag acceptable material or miss harmful material. A flag is not a factual finding about you. Use Help / Support to request human review. If AI screening is unavailable, content with a review queue remains pending, and other screened changes may be refused. It is not automatically published. An authorized reviewer may approve a human override with a recorded reason. You can request human review through Help / Support.
Service providers and external links
ChatGPT provides the sign-in service. Cloudflare provides application hosting and database infrastructure. OpenAI processes submitted text through its moderation API when that integration is configured, as described above. These providers may process information outside your location under their applicable arrangements and policies. Do not assume that a provider’s consumer-chat settings govern a separate API request.
The pilot does not process card details or donations. Charity websites, historical sources, map and parish links, and other outside services receive information you provide directly to them and may receive ordinary connection information when opened. Their privacy notices apply to their services. This pilot does not send invitation emails or text-message notifications on your behalf; invitation links are shared manually.
Retention, withdrawal, and requests
Information is kept as needed to operate your account and community features, handle moderation and support, protect security, resolve disputes, and meet applicable legal obligations. Different records have different purposes; this pilot does not promise a single automatic deletion deadline. Withdrawn records, audit records, and backup copies may remain after a record disappears from ordinary views.
Use Preferences to download available account data. Use a submission’s withdrawal control when available to remove it from its ordinary audience. For correction, account removal, deletion, or another privacy-rights request, use Help / Support. The operator may need to verify your identity and authority before acting. Applicable legal rights depend on your circumstances and location; these controls do not limit rights that apply to you.
Deletion is not currently a one-click account feature. A support request receives operator review. The operator will explain any information that must be retained and any limits on fulfilling a request. Copies already made by other viewers or external services are outside the app’s direct control.
Adults-only pilot and security concerns
Accounts and submissions are limited to adults aged 18 and over. Do not create an account for a child or publish a child’s identifying details. If you believe a child has supplied personal information or someone has shared information without permission, report it through Help / Support so the operator can investigate and take appropriate action.
Access controls and screening reduce risk but cannot guarantee security. Report suspected unauthorized access or a privacy incident through Help / Support. Do not include passwords, access tokens, financial account numbers, or additional copies of sensitive content in your report.
Changes and contact
The operator may update this notice as the pilot changes. Review the effective date and version. Material changes to processing or consent requirements will be presented in the app as appropriate. To contact the operator, return to Parish Commons and open Help / Support; that queue is not an emergency service.