OpenChurch platform · version 2026-11 · last updated 17 November 2026

Privacy Policy

OpenChurch is an open-source platform that helps churches publish their own websites. This policy describes what the platform collects, how it is used, and the controls available to you. Your own deployment operator (the person or organisation running this OpenChurch instance) is the data controller for the content stored on it.

1. Account information

When you create an account we store your name, email address and a bcrypt-hashed password (we never store passwords in plain text). Sign-in creates a session record containing a cryptographically hashed session token and its expiry — the token itself lives only in your browser's httpOnly cookie. Your acceptance of our Terms of Service at registration is recorded with a version and timestamp.

2. Church website information

Content published through the platform — church profiles, service times, ministries, leadership, events, sermons and media — is stored on behalf of the church and rendered on its public website. Published content is publicly accessible by design; draft content is not.

3. Forms, enquiries and prayer requests

When a visitor submits a contact form, prayer request, testimony or counselling enquiry, the submission is stored against that church only. Prayer requests and counselling enquiries are treated as sensitive personal information:

  • they are private by default and never shown on public websites;
  • access is restricted to authorised church personnel via server-side authorisation;
  • submission contents are not logged in application logs;
  • they are never exposed through public API responses;
  • one church's submissions are never visible to another church.

4. How information is protected

  • Passwords and session tokens are hashed; cookies are httpOnly and SameSite.
  • State-changing requests are CSRF-protected; responses carry standard security headers.
  • Sign-in, registration and form submission are rate-limited.
  • Dashboard APIs verify both authentication and church-scoped permissions on every request.
  • Self-hosted deployments keep all data in the operator's own database.

5. Retention, export and deletion

Export. A church owner can download a complete JSON export of their church's content — pages, sermons, events, ministries, leaders, giving settings, forms and enquiry submissions — from Dashboard → Website Settings → Your data, at any time. A platform administrator can export any user account's data (profile, memberships and audit metadata — never passwords) from the platform admin panel.

Deletion. Submissions, pages and media are deleted from the church dashboard; deletion removes the underlying records. A user account that does not own any church can be deleted by the platform administrator on request. An entire church (with all of its data) can be deleted only by the platform administrator, with typed confirmation.

Retention. Sessions expire after 30 days, and password-reset tokens are single-use and expire after one hour; expired records are pruned automatically. Operators should define retention periods for enquiry data in line with their own data protection obligations. To have your personal data removed from an instance, contact the operator of that instance; if you cannot reach them, use the support address below.

6. Your data protection rights

Depending on where an instance operates, data protection law may give you rights over your personal data — for example the Nigeria Data Protection Act 2023 (NDPA) for deployments serving people in Nigeria, or the GDPR/UK GDPR in Europe. Typically the deployment operator acts as data controller (and a church may be a controller for the enquiries it receives).

  • Right of access and portability — served through the export tools described above.
  • Right to rectification — edit your profile, or ask the church to correct an enquiry record.
  • Right to erasure — served through the deletion tools described above.
  • Right to object / withdraw consent — ask the receiving church to stop processing your enquiry.

Exercise these rights by contacting the operator of the instance. This page is a technical summary written by the software's authors, not legal advice; operators should obtain qualified legal review for their own deployment and publish their own controller identity and contact.

7. Third-party services and processors

OpenChurch itself does not run third-party analytics or advertising. A church may link to external services it has configured — for example payment pages (such as Paystack or Stripe payment links), video hosting (such as YouTube) or maps. When you follow those links, the third party's own privacy policy applies. Giving is processed by the external provider, never by OpenChurch: the platform never receives or stores card details.

The platform's own processors depend on the deployment: self-hosted installations keep data on the operator's own infrastructure; managed deployments may involve a hosting provider (such as Vercel), a managed database provider and, where email recovery is enabled, an SMTP provider. Deployment operators should list the processors that apply to their instance in their own privacy notice.

8. Contact

Questions about this policy, data export or deletion requests: contact the operator of the OpenChurch instance you use. Self-hosted deployments configure their own support address. The software itself is open source under the MIT licence — see the licence page; when the operator has configured a repository link it appears on the homepage.

See also our Terms of Service · OpenChurch home