Legal

Privacy Policy

Last updated: July 1, 2026

1. Who we are

Churchy (“we”, “our”, or “us”) operates churchy.app — an AI-powered church operations platform that includes guest follow-up, volunteer scheduling, service planning, and Eden, our AI assistant. We take privacy seriously, especially given the personal and sensitive nature of the data churches collect about their guests and members.

For the purposes of applicable data protection law, Churchy acts as a data processor on behalf of churches (the data controllers) with respect to guest and member data. Churchy acts as a data controller with respect to church account and billing data.

2. Data we collect

We collect the following categories of data:

Church account data

  • Name, email address, and password (hashed) of account holders
  • Church name, address, and pastor information entered during setup
  • Billing information (processed by Stripe — we do not store full card numbers)
  • Planning Center OAuth tokens and Asana credentials (encrypted at rest)

Guest and visitor data

  • Names, phone numbers, and email addresses of visitors (via Planning Center sync, SMS check-in, or manual entry)
  • Visit dates and check-in records
  • Follow-up message history and reply content
  • Journey stage and engagement notes entered by church staff
  • Prayer requests and personal notes logged by church staff

SMS check-in data

  • When a visitor texts your church's Eden number, we collect their phone number and the name they provide
  • Message content and timestamps from the check-in conversation
  • This constitutes prior express written consent to receive follow-up texts from your church via Eden

Eden AI conversation data

  • Messages sent to and from Eden by church staff
  • Church knowledge base content entered during Eden setup
  • Action items, meeting notes, and institutional memory stored in Eden
  • Eden's memory and learned preferences about your church

Usage data

  • Pages visited, features used, and interactions with the dashboard
  • Performance and error logs used to maintain and improve the service

3. Sensitive data — religious information

Churchy handles information that may be classified as sensitive under certain laws, including prayer requests, faith journey notes, and church membership records. We process this data solely to deliver the service to your church. We do not use this data for advertising, profiling, or any purpose beyond operating Churchy on your behalf. We apply the same encryption and access controls to sensitive data as to all other data.

4. How we use your data

  • To operate and deliver the Churchy service — sending follow-up messages, running Eden AI, syncing with Planning Center, and providing your dashboard.
  • To power Eden's AI features — your church knowledge, conversation history, and action items are used to generate Eden's responses.
  • To improve and debug the product using anonymized and aggregated usage analytics.
  • To communicate with you about your account, billing, and product updates.
  • We never sell your data or your guests' data to third parties. We do not use guest data for advertising.

5. AI processing — Anthropic

Eden is powered by Claude, an AI model developed by Anthropic, PBC. When you or your staff interact with Eden, your messages and relevant church context are sent to Anthropic's API for processing. Anthropic's privacy policy governs their handling of this data and is available at anthropic.com/privacy.

We do not send guest phone numbers, full guest records, or personally identifiable visitor data to Anthropic unless you explicitly include that information in a message to Eden. Eden conversations with church staff are processed by Anthropic; guest-facing automated follow-up messages are generated without real-time AI involvement.

6. Third-party services

Churchy uses the following third-party services to operate:

  • Anthropic: AI model powering Eden. Conversation data is processed per their privacy policy.
  • Supabase: Database and authentication. All data stored in Supabase-managed PostgreSQL databases in the United States.
  • Twilio: SMS delivery for guest follow-ups, check-in flows, and Eden alerts. Message metadata is processed by Twilio per their privacy policy.
  • Resend: Transactional email delivery for account notifications.
  • Planning Center: Guest and volunteer data accessed via OAuth with your explicit authorization. Data synced only while your integration is connected.
  • Asana: Task and project management integration, accessed with your authorization.
  • Stripe: Payment processing. We do not store full card numbers. Stripe's privacy policy applies to payment data.
  • Vercel: Application hosting and edge infrastructure.

7. SMS communications and opt-out

Churchy sends automated SMS text messages on behalf of churches to their visitors and members. Every automated SMS includes opt-out instructions (“Reply STOP to cancel”). When a recipient replies STOP, UNSUBSCRIBE, CANCEL, END, or QUIT (or any standard opt-out keyword), we immediately update their record and cease sending messages to that number. Twilio processes opt-outs at the carrier level as well.

Consent at point of collection:When a visitor provides their phone number via a church's guest check-in form (the QR code check-in page), consent language is displayed at the phone number field explaining that they will receive automated SMS messages from that church, that message frequency varies, that message and data rates may apply, and how to reply STOP to cancel or HELP for help. Submitting the form with a phone number constitutes prior express written consent to receive follow-up SMS messages from that specific church via Churchy's platform.

Churches are responsible for ensuring they have the legal right to contact individuals via SMS. We do not send SMS messages to individuals who have opted out.

8. Data storage and security

All data is encrypted at rest (AES-256) and in transit (TLS 1.3). Data is stored in the United States. We use row-level security on our database, role-based access controls for staff, and conduct regular security reviews. API credentials (Planning Center tokens, Asana tokens) are stored encrypted and never exposed in logs.

If we become aware of a data breach affecting your church's data, we will notify you within 72 hours of discovery.

9. Your rights

You (and your guests, where applicable) may at any time:

  • Request a copy of the data we hold about your church or its guests.
  • Request correction of inaccurate data.
  • Request deletion of your account and all associated data.
  • Disconnect the Planning Center or Asana integration to stop new data from syncing.
  • Opt guests out of follow-up messages from within the dashboard, or guests may reply STOP directly.

To exercise these rights, email us at privacy@churchy.app. We will respond within 30 days.

10. California residents (CCPA)

If you are a California resident, you have additional rights under the California Consumer Privacy Act (CCPA), including the right to know what personal information we collect, the right to delete it, and the right to opt out of sale. We do not sell personal information. To exercise your CCPA rights, contact us at privacy@churchy.app.

11. Children's privacy

Churchy is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe a child's data has been submitted to Churchy, contact us at privacy@churchy.app and we will delete it promptly.

12. Data retention

We retain guest and church data for as long as your church account is active. When you cancel, we delete your data within 30 days, except where retention is required by law. Billing records are retained for 7 years as required by applicable tax and financial regulations. Eden conversation logs are retained for 90 days then deleted, unless saved explicitly as church memory.

13. Cookies

We use essential cookies to maintain your login session and prevent CSRF attacks. We do not use advertising cookies, tracking pixels, or third-party analytics that collect personal data. You can disable cookies in your browser, but this will prevent you from staying logged in.

14. Changes to this policy

We may update this policy as the product evolves. We will notify you by email at least 14 days before material changes take effect. The “Last updated” date at the top reflects the most recent revision. Continued use of the service after the effective date constitutes acceptance of the updated policy.

15. Contact

Questions about this privacy policy? Email us at privacy@churchy.app.