Clear expectations about information.

1. Scope

This notice covers the public Church Staff Meeting site and the separate application at app.churchstaffmeeting.com. It does not cover the COL storefront, customer portal, Leadership 360 confidential service, or third-party services under their own notices.

2. Information Church Staff Meeting handles

The product may handle account identity, church-workspace membership and roles, team and meeting-series setup, preparation, agenda progress, individual opening and closing ratings, decisions, Meeting Notes, Action Steps, meeting history, invitation and integration state, and content-minimized operational and security records.

We use Auth0 to verify your email address and sign you in. Auth0 processes sign-in information, and Church Staff Meeting receives your verified email address, basic profile information when provided, and an account identifier. Your sign-in does not grant access to a church workspace without an authorized membership.

Billing identifiers and subscription state are handled separately from church-workspace authorization. Stripe processes payment-card information under Stripe's own privacy terms; Church Staff Meeting does not use payment status as workspace authority.

3. Why information is used

Information is used to authenticate identity, authorize church-workspace access, prepare and run meetings, preserve approved meeting records, support follow-through, operate requested integrations, provide support, protect the service, and maintain reliable operations.

Opening ratings remain individual and are not averaged. Closing ratings remain individual; only their average becomes the Meeting Score.

4. Integrations and disclosures

Planning Center remains read-only and preview-only. Basecamp receives nothing until an authorized person chooses a destination and approves the Meeting Notes or Action Steps to send. The current subprocessor register identifies Cloudflare for hosting, D1, Access, and Images; Auth0 for customer identity authentication; Resend for transactional email; and Stripe for billing and tax. Planning Center and Basecamp are optional customer-connected services used only when the customer connects and approves them.

Information may also be disclosed when legally required or directed by an authorized customer, while minimizing the information shared. The payment provider does not grant church-workspace membership.

5. Retention, export, and deletion

Meeting history and workspace records persist rather than reset on login. Customer content remains customer-controlled while active. A verified workspace owner may request export or deletion; active records are targeted for deletion within 30 days after an approved request or termination, and recovery copies are targeted to age out within 30 days. Legal or security holds are exceptions. These owner-selected policies do not claim that hosted recovery or RPO/RTO has been proven.

6. Security and access boundaries

Workspace membership and roles are server-authorized. Church Staff Meeting remains separate from other COL product databases, and external writes remain gated. No compliance certification or absolute-security guarantee is made.

7. Choices and requests

Authorized users and workspace owners may contact Carlo@carloorlando.com about access or privacy questions.

8. Contact and changes

Privacy questions may be sent to Carlo@carloorlando.com. Email intake is accepted 24/7; staffed support is Monday-Friday, 9:00 AM-5:00 PM Eastern Time, excluding US federal holidays, with a target first response within 1 business day. Privacy requests require identity and organizational authority verification and are handled under applicable law. Material changes receive 30-day email or in-app notice when practicable; urgent legal or security changes receive prompt notice. This notice is effective August 29, 2026.