Website builder and publisher terms

These terms apply when an institution uses the EcclesiaOne website builder to create and publish a public website, including any custom domain, embedded media, photo galleries, and custom code. The platform is operated by Orravo Web Technologies. These terms form part of the Master Subscription Agreement, and the publishing institution is the "Publisher".

1.What the Publisher controls

The Publisher decides what content to publish on its site, including text, images, galleries, embedded videos, and any analytics or custom code it adds. The Publisher is responsible for that content and for ensuring it is lawful, accurate, and does not infringe anyone's rights. Orravo provides the building and hosting tools and is not responsible for the Publisher's content.

2.Lawful content and consent

The Publisher must have the right to publish everything it puts on its site. This includes:

• the right to use images and video, including any licences required; and
• the consent of people who appear in photographs or video, especially children. Photographs of minors must only be published with the consent recorded under the Children's Privacy Notice, and the Publisher must honour any request to remove or blur a minor's image.

The Publisher must not publish content that breaks the Acceptable Use Policy or applicable law.

3.Custom code and embedded content

The website builder gives the Publisher a field for custom head markup and a field for markup at the end of the page body. The Publisher is responsible for anything it adds and for the privacy and security implications, including disclosing third-party cookies and tools in its own cookie and privacy notices.

What those fields accept is deliberately narrow. Custom markup is filtered both when it is saved and again when the page is served, and only a small set of tags is kept: meta, link, title, base, style, and span, with a matching set of attributes. Script tags, embedded frames, objects, embeds, forms and form controls are removed, as are inline event handlers and javascript: URLs. A snippet that relies on any of those, including most analytics and tag-manager snippets, will not run.

Custom markup is also served only to visitors who have accepted non-essential cookies.

Orravo may change, restrict, or disable what these fields accept, and may remove markup that poses a security or privacy risk, without notice where the risk is immediate.

4.Custom domains

Where the Publisher connects a custom domain, the Publisher is responsible for owning and controlling that domain and its DNS configuration. The Publisher authorizes Orravo to serve the site at that domain and to verify control of it. Orravo is not responsible for domain registration, renewal, or DNS errors outside its control.

5.Analytics and visitor data

If the Publisher adds analytics or tracking tools, the Publisher is the controller for the visitor data those tools collect and is responsible for obtaining consent and providing notices. The platform's cookie-consent mechanism gates non-essential scripts until a visitor consents; the Publisher must not circumvent it.

6.Moderation and takedown

Orravo may review published sites and may remove, disable, or restrict content or code that breaches these terms, the Acceptable Use Policy, or the law, or that poses a security risk. Where practicable we will tell the Publisher. A diocese or other supervising authority may also have rights over content published by institutions within its structure.

7.Availability

We aim to keep published sites available but do not guarantee uninterrupted service. Maintenance, suspension of the Publisher's subscription, or removal of offending content may affect availability.

8.Liability

To the fullest extent permitted by law, Orravo is not liable for the Publisher's content, custom code, embedded third-party content, or custom-domain configuration, or for claims arising from them. The disclaimers and limitation of liability in the Master Subscription Agreement apply. The Publisher will indemnify Orravo against third-party claims arising from its published content or code, to the extent permitted by law.

9.Changes

We may update these terms. When we publish a new version, the version number and date on this page change.

10.Contact

For questions about publishing, contact [email protected].