Data and privacy information

Church content and publication

We store church profiles, uploaded branding, service plans, events, team instructions, submitted updates, and playbook drafts and history to provide the service. Manually entered and imported church content must be suitable for public sharing. Saving or importing information does not publish it: administrators review the playbook and choose when to publish. Published pages are available without signing in, and team filters do not restrict access. Do not enter confidential notes, personal prayer details, passwords, access codes, or sensitive security procedures as church content.

Account and service information

We use account and leader names and email addresses, authentication sessions, integration credentials, delivery records, and activity records to provide access, connect services, send service messages, protect the application, and provide support. These records are not public playbook content. Owner and authorized support staff can access church records to assist your church and administer the platform. We also retain agreement acceptance records, including the accepted version, text, date, and account identity. Stripe collects payment-card details securely; Sunday Playbook stores Stripe customer and subscription identifiers, the selected plan, billing status, and recurring-charge consent. Full card numbers and security codes are not stored in the church database.

Invitation requests

When you request an invitation, we store your church name, contact name and email, location, optional role and message, plan preference, contact permission, and request/review dates. Our owner and authorized support staff use these records to review and follow up on your request. They are stored in the hosted application database and are not published in playbooks. Submitting a request does not create an account or subscription.

Hosted storage and service providers

The public pilot runs on cloud services. Render hosts the application; Supabase provides the database, authentication, and uploaded-image storage. Church and account records are stored in this hosted infrastructure. Resend processes recipient addresses and message content to deliver application emails, including invitations, reminders, and publication notices. Authentication and recovery emails are handled through Supabase Auth and its configured email service. Providers process the information needed for their role under their applicable service and data-processing terms.

Provider information: Render, Supabase, and Resend. Processing locations and provider retention depend on the services and their configuration; we do not promise that all processing occurs in a particular country.

Payments

Stripe processes payment details and relevant customer information to set up trials, collect subscription payments, provide invoices, and manage payment methods and cancellations. See Stripe’s privacy policy.

Connected services

When an authorized church administrator connects Planning Center, we store the connection credentials and import selected Services and Calendar information into the church workspace. Imports are read-only: edits in Sunday Playbook are not written back to Planning Center. Disconnecting stops future access through that connection; it does not automatically erase information already imported or included in retained playbooks. Planning Center is a separate service with its own privacy notice. Other integrations are not currently available.

AI-assisted writing

When an administrator runs AI-assisted assembly, relevant church background, team descriptions and standing instructions, submitted answers, selected service and event information, and the weekly focus are sent to OpenAI to draft and review team instructions. Unsubmitted answer drafts are excluded. The generated wording and review information are saved in the church workspace for administrator review; AI does not publish the playbook. Church content may contain personal information, so only submit material appropriate for public sharing.

Our AI requests disable response storage. This does not eliminate all provider retention: OpenAI may retain data for abuse monitoring and other purposes described in its API data controls. OpenAI states that API data is not used for model training by default. AI wording can be inaccurate and must be reviewed before publication.

Retention, account closure, and requests

Closing a church account archives it rather than automatically deleting its information. Church-admin and leader access stop, public church pages are hidden, and pending deliveries are stopped. Church records, submissions, playbook history, invitation requests, and assigned addresses are retained for administration, support, continuity, and recordkeeping. There is currently no fixed automatic deletion schedule. Contact support to request an export, correction, or deletion review. We may need to verify your identity and authority for the church before acting. Applicable legal requirements and provider backup or retention processes may affect what can be removed and when. Copies of published material held by others may remain outside our control.

Website analytics

Google Analytics measures page visits, selected link and button clicks, control changes, form-submission attempts and scroll depth across our website automatically, unless you turn it off. In the US, analytics cookies are enabled by default; elsewhere, Google uses cookieless measurement until you allow analytics cookies. Cookieless measurement has reporting and visitor-count limitations. We retain prior opt-outs and honor the browser Global Privacy Control signal by disabling analytics. You can turn analytics off or allow analytics cookies in Analytics preferences below. Page addresses use general page types; church identifiers, slugs, query strings and tokens are excluded. We do not send form answers, names, email addresses, invitation codes, church content or payment details. No session replay, keystroke recording or advertising personalization is enabled. See Google’s privacy policy.

Cookies and browser storage

Authentication cookies and browser storage support sign-in and session behavior, including leader-link access. These are separate from the hosted church database. Protect shared devices, sign out when appropriate, and do not forward an invitation or leader link to someone who should not access the assigned forms.

Updates and questions

This notice describes the current public pilot. We will update it as providers or data uses change. Contact support@sundayplaybook.com about privacy questions, your church’s information, or a correction to this notice.