OpenChurch platform · version 2026-11 · last updated 17 November 2026
These terms govern the use of OpenChurch — an open-source church website platform. By creating an account or using an instance of the platform you agree to them. If you are using a self-hosted instance, the operator of that instance may add their own terms; theirs prevail for that instance.
You are responsible for the activity on your account and for keeping your password safe. Provide accurate information, do not share accounts, and use a unique password. Accounts may be suspended for abuse, unlawful use or security violations.
Churches keep ownership of the content they publish. You grant the platform the technical licence needed to store and render that content on the church's public website. You may delete content at any time. Prayer requests and counselling enquiries submitted through church websites are confidential by default and must be handled only by authorised church personnel.
OpenChurch does not process payments and never stores card details. When a church links an external payment provider, the giving transaction happens entirely on the provider's platform under the provider's terms. Demonstration payment destinations are fictional and clearly labelled — no real money moves through them.
The software is provided under the MIT Licence, “as is", without warranty of any kind. The platform does not guarantee uninterrupted availability of any instance. To the maximum extent permitted by law, the authors and contributors are not liable for damages arising from use of the software. See the licence page or the LICENSE file in the repository for the full licence text.
These terms may be updated as the platform evolves; material changes are reflected in the version and date above, and users may be asked to re-accept the terms on their next sign-in. Continued use of the platform after changes constitutes acceptance.
OpenChurch is an open-source project. Questions about these terms: contact the operator of the instance you use, or reach the project via its public repository (linked from the homepage). Security issues can be reported responsibly — see the repository's SECURITY.md.
See also our Privacy Policy · OpenChurch home