Privacy Policy & Compliance

GDPR & Privacy Policy

Last Updated: June 2026. WorshipFlow AI (the "Service") is operated by Chris Renshaw (the "Operator", "we", "us", or "our"), trading as a sole trader in the United Kingdom. We are committed to protecting the privacy of church staff, administrators, and volunteer musicians in accordance with the UK Data Protection Act 2018 (DPA 2018), the UK General Data Protection Regulation (UK GDPR), and the EU General Data Protection Regulation (EU GDPR).

1. Roles: Data Controller vs. Data Processor

Under the GDPR, your church/organization is the Data Controller of the personal data of your volunteers, congregation members, and staff. WorshipFlow AI acts strictly as a Data Processor when syncing planning data (such as rosters, teams, and plans) from Planning Center Online (PCO). By using this Service, you warrant that you have obtained all necessary consents, notices, and legal bases required under applicable laws to process and transfer this data to our Service.

2. Information We Process

We process:
Administrative Credentials: Names, email addresses, payment tokens (handled securely via Stripe), and OAuth access tokens.
Church Directory and Planning Meta-Data: Repertoire song lists, arrangement keys, BPM tempo records, sermon outlines, and team schedule role classifications (e.g., Soprano, Bass, Keys) synced from PCO Services.
Roster Limits: The total number of active members in your team list is tracked solely to enforce plan billing thresholds. We do NOT collect or store volunteer telephone numbers, addresses, or other sensitive personal data.

3. Data Isolation & AI Safety Rules (Gemini LLM Boundaries)

To prevent volunteer data leaks, the Service enforces strict data boundary isolation:
No Personally Identifiable Information (PII)—such as volunteer names, emails, or personal contact details—is ever sent to third-party artificial intelligence engines or the Google Gemini API.
• Only anonymous, metadata-level descriptors (e.g. musical key transpositions, band instrumentation profiles, and sermon notes) are processed via LLM models to generate matches.

4. International Data Transfers & Server Location

WorshipFlow AI is hosted on secure Google Cloud Platform infrastructure. Data is stored in databases physically located in the UK/EU (specifically europe-west3). For organizations located outside the UK/EEA (such as in the United States), data transfers are protected under Standard Contractual Clauses (SCCs) and comply with cross-border data transfer directives.

5. Regulatory Registration

As a UK-based sole trader, the Operator registers and maintains compliance with the Information Commissioner's Office (ICO) in the United Kingdom to govern all data processor operations legally.

6. California Consumer Privacy Act (CCPA/CPRA) & US State Rights

For users and organizations based in California and other US states with consumer privacy regulations, we verify that:
No Sale or Sharing of Personal Info: WorshipFlow AI does NOT sell, rent, or share personal data (such as names, emails, or schedules of volunteers) for monetary value or cross-context behavioral advertising.
Data Minimization: We only collect names, emails, and role classifications to facilitate matching and scheduling features.
US Consumer Rights: If you wish to request access to or deletion of your church's roster data, contact us at .

7. Data Retention & Deletion Policy

We retain personal data only for as long as necessary to provide the Service, or as required by law:
OAuth Credentials: Access tokens to Planning Center Online are deleted immediately upon user logout, PCO token revocation, or when the user deletes their account.
Staged Repertoire & Schedules: All song libraries, matched setlists, and schedule data are stored in Firestore and retained as long as your account remains active.
Account Deletion: Users can request complete deletion of their account and all associated Firestore data at any time via the "Delete My Account" button in their Settings/Profile, or by emailing . All data will be permanently and securely deleted from active databases within 30 days of the request.

PCO Auditor Security Guide: Data Isolation Shield

This guide provides church administrators and Planning Center Online security auditors with technical details on how WorshipFlow AI isolates and protects sensitive church and volunteer data.

1. Zero PII Shared with Gemini API

WorshipFlow AI strictly separates structural planning data from personally identifiable information (PII). When analyzing setlist compatibility or generating team rehearsal briefs, we strip all volunteer names, emails, and contact details. Only anonymous metadata (such as the target musical keys, scheduled roles, and sermon outline notes) is passed to the Gemini API.

2. Database Isolation & Regional Hosting

All synchronized PCO data and generated setlists are hosted within secure Google Cloud Platform (GCP) Firestore databases physically isolated in the United Kingdom/European Union (specifically the europe-west3 Frankfurt region). Data is encrypted at rest and in transit.

3. OAuth 2.0 Token Lifecycle & Revocation

We access the Planning Center API via standard OAuth 2.0. Access tokens are stored securely in Firestore and updated via encrypted token rotation. Administrative users can audit or immediately revoke all access permissions directly from their Planning Center dashboard at any time, which automatically terminates token validity on our side.