Cookie Policy

1.1Cookies

A cookie is a small piece of text that a website asks your browser to store and to send back with later requests to the same site. It is how a website recognises that two requests come from the same person, which is the thing that makes staying signed in possible at all. A cookie cannot run code, it cannot read anything on your device, and it cannot see other websites’ cookies.

1.2Similar technologies

We mention these explicitly, because “cookies” has become a shorthand that lets a site describe its cookies honestly and say nothing at all about what else it stores in your browser. This product stores nothing in local storage, session storage or IndexedDB. The four cookies in the next section are the whole of what is kept in your browser by this Service, and there is no fifth thing hiding behind a different name.

1.3Where this policy sits

This policy covers our public websites and the workspace alike — they are the same application and they set the same cookies. It sits alongside the Privacy Policy, which deals with personal data generally; section 9 of that policy summarises this one. Where the two say anything different about cookies, this policy is the fuller account and the one to rely on.

4.1What the notice does

When you first visit, a bar appears at the bottom of the page. It names the four cookies, links to this page, and has one button reading “Got it”. It does not cover the page, it does not stop you reading or doing anything, and if you ignore it entirely the whole product still works. If you dismiss it, you are not shown it again for a year.

4.2Why there is no switch to turn anything off

A consent banner exists to let you refuse something. There is nothing here to refuse. Every cookie above is necessary for the Service to work, so a toggle beside them would offer you a choice that is not real — and a switch that cannot be turned off is worse than no switch, because it implies the cookies are optional and that not pressing it would stop them. Neither is true. Consent that cannot be withheld is not consent, and presenting it as though it were would be a way of looking compliant rather than being honest.

So this is a notice, not a permission. It tells you what is stored and why, which is the part that is genuinely owed to you, and it does not pretend to hand you a decision you do not have.

4.3If that ever changes

If a cookie that is not necessary is ever added to this Service — an analytics product, say — then this page will change and the notice will change with it, to ask rather than to report, before that cookie is set. We are stating that here so that the absence of a switch is a promise about this product rather than an accident of how it was built.

5.1What you can do

Every browser lets you see the cookies a site has set, block cookies from a site, and delete the ones already stored. Those controls are in your browser’s settings, usually under Privacy or Security, and they work on this site as they do on any other.

5.2What happens if you block them

Blocking the cookies above will stop you using the Service. Without the session cookie you cannot sign in, and without the Google state cookie a connection cannot be completed. We would rather say that plainly than offer a “manage your preferences” page that only leads back to the same four cookies with no way to remove them.

5.3If you delete them

Deleting them signs you out and resets your sidebar to its open position, and the notice will appear once more the next time you visit — because the cookie that remembered you had read it is one of the ones you deleted. None of that affects anything held about your church, which lives on our servers rather than in your browser.

6.1Changes

We may change this policy as the Service changes. A change is published on this page with a new version number and effective date, in the way section 18.2 of the Terms of Service describes. Where a change would add a cookie that is not necessary, section 4.3 above is the promise that the notice will ask rather than report before it is set.

6.2Questions

Questions about this policy go to support@vultion.com. Where your question is about personal data rather than about cookies, section 9 of the Privacy Policy explains what is held and names the Data Protection Officer to write to.