Cookie policy

This Cookie Policy explains how EcclesiaOne uses cookies and similar technologies. EcclesiaOne is operated by Orravo Web Technologies. This policy should be read with our Privacy Policy.

1.What cookies are

Cookies are small text files stored on your device when you visit a website. They let a site remember your actions and preferences, keep you signed in, and understand how the site is used. Similar technologies, such as local storage and pixels, work in comparable ways. This policy uses "cookies" to refer to all of them.

2.The categories we use

2.1 Strictly necessary cookies

These are required for the platform to work and cannot be switched off. They include cookies that keep you signed in, protect against cross-site request forgery, and remember your cookie choice. The cookie that records your consent decision (named eo_cookie_consent) is itself a strictly necessary cookie. It stores whether you accepted or declined non-essential cookies, lasts one year, and is restricted to first-party use.

2.2 Analytics and other non-essential cookies

Orravo sets none of these. EcclesiaOne does not load Google Analytics, Plausible, PostHog, Segment, Hotjar, or any comparable product, and we do not build a profile of how you browse. There is no Orravo analytics cookie to accept or decline.

Institutions that publish their own websites through EcclesiaOne have a field where they can add custom markup to their pages. As things stand, that field strips out script tags, embedded frames, and event handlers before anything is stored or shown, for security reasons, so an analytics snippet pasted into it will not run. The practical position today is that no analytics or tracking script runs on EcclesiaOne, whether ours or an institution's.

The consent banner stays in place as a safeguard. Whatever an institution has put in that field is rendered only if you accept non-essential cookies, and if we ever widen what may be placed there, your choice will govern it from the start.

Separately, and regardless of your cookie choice, some pages load typefaces from Google Fonts, and a page where an institution has added a map or a video will load that embed from Google or YouTube. These are not cookies we set, but they do mean the provider of that resource sees your IP address and browser when the page loads. An embedded YouTube video may also set that provider's own cookies once you play it.

3.How we ask for consent

When you first visit, a banner asks whether you accept or decline non-essential cookies. Strictly necessary cookies are set regardless, because the platform cannot run without them. Non-essential cookies and any third-party scripts that depend on them are loaded only if you accept. If you decline, those scripts are not loaded.

Your choice is stored for about one year. After that, or if you clear the choice, the banner appears again.

4.Changing your choice

You can change your decision at any time by clearing the eo_cookie_consent cookie in your browser, which makes the banner reappear. You can also block or delete cookies through your browser settings, though blocking strictly necessary cookies may stop parts of the platform from working.

We should be straightforward about a limitation here: the platform does not yet offer a permanent "manage cookies" link or preference centre, so changing your mind takes more effort than making the original choice did. Clearing the cookie is currently the way to do it. If you would rather we did it for you, write to [email protected].

5.A note on granular consent

The consent banner offers a single accept-or-decline choice for non-essential cookies rather than per-category toggles. That single choice governs everything non-essential on a page, so declining blocks all of it. Since Orravo sets no analytics cookies of its own, and institution-added scripts do not currently run, there is at present very little for that choice to govern. We keep the banner because the position could change, and because it is better to have asked.

6.Changes to this policy

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

7.Contact

Questions about cookies can be sent to [email protected].