LAST UPDATED: FEBRUARY 02, 2024
This policy outlines which cookies we use and how we use them. For more details on how we handle your data please see our privacy notice. Any further updates to this cookie policy will be posted here.
What is a cookie?
Cookies are small files stored on your computer or mobile phone (referred to hereby as a “device”) by websites that you visit. These cookies can be used to make websites work, provide features, provide statistics to the website owners etc.
What is local storage?
Local storage is another means with which websites can store data in your browser similar to a cookie. For the purposes of this policy we will refer to both forms of data storage as a ‘cookie’. Where necessary though we will distinguish between the two so you know where to look for the data that is stored in your browser.
What cookies does ChurchSuite use?
ChurchSuite uses two main types of cookies as part of using the marketing website (“this website”) and as part of using the ChurchSuite service (“the service”):
First party cookies
These cookies are created by ChurchSuite and used directly for the functioning of the service and this website.
Third party cookies
These cookies are not set by ChurchSuite but instead by other companies. Cookies that are used as part of us providing the service from sites like Helpscout and Stripe are listed under ‘How do we use cookies?’ whereas those from non-service related companies are covered by the section ‘Third party cookies’.
How do we use cookies?
Necessary cookies
These cookies are necessary for the correct operation of this website and the service. Without them the service and/or this website may not operate correctly and are, by default, switched on.
Cookie name | Where is it used? | How long does the cookie remain for? | What type of cookie is it? | What’s the purpose of the cookie? |
cf_clearance | This website and the service | 1-year | Third-party cookie | This cookie is set by CloudFlare, the security service we route all requests through. It stores whether or not you have passed the ‘proof of challenge’ and is a security feature required to access the service and the website. |
XSRF-TOKEN | The service | 24-hours | First-party cookie | A security token used by the service to ensure the request sent is legitimate. |
PHPSESSID | The service | Session | First-party cookie | A session token used to identify you and your session with the service after you have logged in. |
core | The service | 24-hours | First-party cookie | Another session token used by the core ChurchSuite service to identify you and your session with the service after you have logged in. |
__stripe_mid | The service | 1-year | Third-party cookie | This is a cookie set by Stripe and is required as a means of fraud prevention. |
__stripe_sid | The service | 30-minutes | Third-party cookie | This is a cookie set by Stripe and is required as a means of fraud prevention. |
Functional cookies
While these cookies are not required for the base operation of this website or the service but will be used if you interact with specific features as noted under the purpose column
Cookie name | Where is it used? | How long does the cookie remain for? | What type of cookie is it? | What’s the purpose of the cookie? |
lang | This website | No expiry | First-party local storage | When you select a different language we store this to remember it between pages. While not essential, if you delete this then your language will be reverted. |
hs-beacon-* | This website and the service | No expiry | Third-party local storage | Helpscout is our third-party support platform, part of their functionality includes a ‘Contact Us’ pop-up which this local storage is used for. While not essential it is required to use the contact support popup - it is not accessible outside of ChurchSuite. |
Marketing and analytical cookies
ChurchSuite does not use any cookies for the purposes of marketing, tracking, advertising or analytical purposes.
Changes to this policy?
We review this policy annually but will also update it if we change which cookies we use so we recommend checking back for updates in the future. Any changes relating to how we process your data will also be covered in our privacy notice.