Live Demo: Try this and other plugins live — no installation, no risk: demo.markus-michalski.net
The Klaro library and the stylesheet ship with the module and are served by your shop server. The configuration the module hands to Klaro contains no external endpoint. The module itself loads no third-party scripts.
Scripts of services you control through cookie services (for example Google Analytics) come from their own servers. They are executed only after consent if you mark them as described under Blocking scripts.
| What | Where | Content | Lifetime |
|---|---|---|---|
| Consent decision | Cookie or localStorage, depending on the "Storage Method" setting | The visitor's decision per service | For the cookie 365 days, adjustable from 1 to 730 |
The name of the entry is klaro by default and can be changed with "Storage Name".
The module creates two tables, mmd_klaro_cookie_service and mmd_klaro_cookie_service_translation. They contain only your service definitions (name, purpose, cookie rules, title, description). The module does not log individual visitors' consents on the server.
On activation the module creates the service session:
| Property | Value |
|---|---|
| Purpose | Functional |
| Required | Yes |
| Default enabled | Yes |
| Title | "Technically necessary" (German "Technisch notwendig") |
| Cookies | sid, sid_key, oxidLanguage (path /) |
The service is marked as required, visitors cannot switch it off. The module creates no other services.
When the option is on, the module sets the defaults of all Google consent types except security_storage to "denied". It sends no data to Google and loads no Google script. See Storefront.
/datenschutz does not fit every shop.