Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
Webcool CMS is a content management system used to build and manage websites. Like most content management systems it sets first party cookies, such as a session cookie and an editor authentication cookie, and it does not add third party advertising or analytics by default. Its privacy profile is low risk and depends mainly on where it is hosted and on any third party tools the site owner integrates.
Webcool CMS is a content management system for building and managing websites. It provides the tools to create pages, publish content, and administer a site. Whether it is self hosted or offered as a hosted service shapes some of the data questions, but in both cases it is primarily a first party tool.
Webcool CMS sets first party cookies such as a session cookie and an authentication cookie for editors. It may store account, comment, or contact form data depending on the features in use. It does not add third party advertising or analytics by default, so the visitor facing footprint is limited to essentials.
You are the controller for personal data the CMS stores. Because the cookies are strictly necessary and first party, the obligations centre on security, retention, transparency, and handling data subject requests, rather than on consent for tracking that the CMS does not perform on its own.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
The strictly necessary first party cookies do not require consent. Consent applies to any analytics, embeds, or marketing tools you add to a Webcool site, which should be gated until the visitor accepts the relevant category.
If you self host or use an EU hosted plan, data stays in the European Economic Area. If Webcool CMS is delivered from outside the EEA, confirm the hosting location and ensure any transfer is covered by Standard Contractual Clauses or another valid mechanism.
Confirm the hosting model and location, sign a data processing agreement if it is a hosted service, set retention for stored data, and document the first party cookies as essential. Apply consent only to third party tools you integrate, and keep the installation secure and updated.
Websites using Webcool CMS must obtain user consent under GDPR regulations.
DPIA considerations
Focus on the first party cookies, any account, comment, or contact data the CMS stores, the hosting location, and any third party tools added on top. A DPIA is rarely needed for the CMS alone.
Sample consent text
This site is built with Webcool CMS and uses only strictly necessary first party cookies to function. Any analytics or marketing tools run only after you accept them.
Cookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| webcool_session | Functional | Session | First party session cookie that maintains the visitor session on the server. |
| webcool_auth | Functional | Session | First party authentication cookie that keeps logged in editors signed in to the admin area. |
This service may collect user data. Ensure GDPR compliance with FlowConsent.
It sets first party cookies such as a session cookie and an authentication cookie for editors. These are strictly necessary to operate the site and the admin area.
No, not for the strictly necessary first party cookies. Consent applies only to analytics, embeds, or marketing tools you add to a Webcool site.
Essential cookies rely on the ePrivacy exemption, and any personal data the CMS stores relies on a basis you set, such as consent or legitimate interest. You are the controller.
That depends on how it is hosted. A self hosted or EU hosted setup keeps data in the region, while a hosted plan outside the EEA would need Standard Contractual Clauses.
Rarely for the CMS alone. A DPIA is relevant only if you build high risk processing on top, such as large scale data collection or profiling.
Confirm the hosting location, set retention for stored data, document the first party cookies as essential, and add consent only for third party tools. Keep the platform secure and updated.
Alternatives include WordPress, Joomla, and other content management systems. Any first party CMS has a similar privacy profile that depends mainly on hosting and added tools.
List the first party session and authentication cookies as strictly necessary. The CMS does not set third party tracking cookies, so add entries only for tools you integrate.
