Cookie Policy

A cookie is a small file a website asks your browser to keep, so that it can recognise you on your next request. Related technologies — local storage, session storage — do much the same job, and everything in this policy applies to them too, whatever the underlying mechanism.

Cookies are how being signed in works at all: without one, every page load would look like a stranger arriving. That is why the first category below cannot be switched off.

Strictly necessary — always on

These make the Service function and cannot be declined, because without them it does not work:

• Session cookies — hold your signed-in session and let it be refreshed securely. They are HTTP-only, so page scripts cannot read them.
• Preference cookies — remember choices such as whether you asked to stay signed in.
• Consent record — once you answer the cookie banner, your answer is itself stored in a cookie. That is what stops us asking again on every page, and it is the record that proves what you chose.
• Security and payment cookies — set when you use a feature that depends on a third party, most notably a card payment or donation, where the payment provider needs them to detect fraud and complete the transaction.

Statistics and marketing

We currently set no analytics, advertising, or tracking cookies of any kind. There are no third-party advertising pixels on the Service, no cross-site tracking, and nothing that profiles you for marketing. The only third-party code that runs in the page is our error monitor, which records crashes so we can fix them.

We have a consent manager in place so that if that ever changes, nothing in these categories can be set before you have agreed to it — rather than us adding a banner after the fact.

One thing that is not a cookie but is worth stating plainly here: bulk email sent through the Service does use an open-tracking pixel and wrapped links, so your Organization can see whether a message was opened. That happens inside the email, not on this site, and it sets nothing on your device — see the Privacy Policy for the detail.

The list below is generated automatically from a recurring scan of this site, so it reflects the cookies actually present rather than a description of them. It names each cookie, its provider, its purpose and how long it lasts.

Withdrawing consent should be as easy as giving it. You can reopen the cookie dialog at any time and change or withdraw what you agreed to — your choice takes effect immediately, and anything you decline is not set.

You can also manage cookies in your browser: every major browser lets you view and delete cookies, refuse them from particular sites, or block third-party cookies entirely. Be aware that blocking the strictly necessary cookies above will stop you being able to sign in.

On the mobile app, the equivalent controls are device permissions rather than cookies — notifications, camera and location — described in section 9 of our Privacy Policy.

Some cookies come from the providers who run parts of the Service for us — payments, messaging, video, in-app chat, push delivery and error monitoring. We do not control what those providers name their cookies or how long they keep them, which is another reason the declaration above is generated from a scan rather than written by hand. The providers themselves are listed, with what each one does, in section 5 of our Privacy Policy.

We may update this policy as the Service changes or the law does; the date at the top always reflects the current version. The cookie declaration updates itself on each scan, so it can be newer than the surrounding text.

Questions about cookies or your choices: office@synaiconnect.com.

See also our Privacy Policy and Terms and Conditions.