---
title: Why doesn’t the ChurchTools Website require a general cookie banner?
description: "The ChurchTools Website uses only functional cookies, which do not require a cookie banner. If you use \"external services\" such as YouTube, Spotify, etc., on your website, each service must be enabled with its own consent banner before a website…"
url: "https://churchtools.academy/en/help/website-and-finder/other-website/why-doesnt-the-churchtools-website-require-a-general-cookie-banner/"
updated: "2026-09-16"
category: Website / Other
---

# Why doesn’t the ChurchTools Website require a general cookie banner?

The ChurchTools Website uses only functional cookies, which do not require a cookie banner.

If you use "external services" such as YouTube, Spotify, etc., on your website, each service must be enabled with its own consent banner before a website visitor can access it. The consent banner is automatically displayed as a placeholder at the location where the service is embedded until the visitor confirms it, thereby enabling the service. Only then is a connection established to the external roles.

For external roles, this consent banner therefore replaces a general cookie banner for each role.

**Important**

The privacy policy must, of course, still be adapted by website operators—in your case, your church congregation—so that external roles are also covered.

## Read more

- [How to integrate an external service into the ChurchTools Website?](https://churchtools.academy/en/help/website-and-finder/content/how-to-integrate-an-external-service-into-churchtools-website/)
- [How to create and edit posts, appointments and groups?](https://churchtools.academy/en/help/website-and-finder/content/14-how-to-create-content/)