Cookie Policy
Last updated: June 7, 2026
This Cookie Policy explains how Concentio uses cookies and similar technologies on its own website and, separately, how the Concentio Consent Management Platform (CMP) may use cookies or similar storage technologies when implemented on customer websites.
It is important to distinguish between:
- Concentio's own marketing website, where Concentio determines which cookies and similar technologies are used; and
- customer websites using the Concentio CMP, where the website operator is generally responsible for deciding how the CMP is configured and how consent-related technologies are described to visitors.
1. What are cookies and similar technologies?
Cookies are small text files that a website can store on your device through your web browser. Websites may use cookies and similar technologies, such as local storage, to remember preferences, preserve settings, support security, store consent choices, and enable certain website functions.
Some cookies are strictly necessary for a site or feature to work properly, while others may be used for analytics, advertising, personalization, or other optional purposes.
2. Cookies used on the Concentio website
The cookies and similar technologies in use on this website are listed below. Because Concentio runs on its own platform, this declaration is generated automatically from regular scans of this site, so it always reflects what is actually in use.
3. Cookies and similar technologies used when customers deploy the Concentio CMP
When a customer deploys the Concentio CMP on their own website, the CMP may use cookies and/or similar storage technologies on that customer's domain to store consent choices, preserve visitor preferences, support consent banner behavior, and maintain technical records associated with the CMP's functionality.
These technologies are typically configured by or on behalf of the customer as part of that customer's implementation of the Concentio platform.
Depending on configuration, these technologies may be used for purposes such as:
- storing a visitor's consent choices;
- remembering whether a visitor has already interacted with the consent banner;
- recording which version of a banner configuration was shown or accepted;
- supporting region-specific consent behavior;
- preserving opt-out or preference states; and
- supporting limited technical session or usage logic associated with the service.
The exact names, retention periods, and storage mechanisms may vary depending on product configuration and implementation.
4. Cookies and storage set by the Concentio script
When the Concentio consent script runs on a website, including this one, it sets the following first-party cookies and browser storage entries. None are used for advertising or for tracking visitors across other websites. They exist to remember consent, recognize a returning visitor, and count usage for billing.
Cookies
| Name | Purpose | Duration |
|---|---|---|
concentio_consent |
Stores the visitor's consent choices per category so the banner is not shown again and scripts stay correctly gated. Mirrors the local storage value so consent is recognized across subdomains. | 12 months |
concentio_vid |
A pseudonymous visitor identifier (a random ID) used to recognize a returning visitor across subdomains and to count unique sessions for billing. | 12 months |
concentio_cv |
Records which version of the consent banner the visitor responded to, so consent can be requested again when it changes. | 12 months |
Local storage
| Name | Purpose | Duration |
|---|---|---|
concentio_consent |
The primary record of the visitor's consent choices per category, together with the time of the decision. Consent is treated as expired after 12 months, after which the banner is shown again. | Until cleared by the visitor |
concentio_consent_version |
Records which version of the consent configuration the visitor last responded to. | Until cleared by the visitor |
concentio_optout |
Stores US privacy opt-out signals (sale or sharing of personal information, and targeted advertising) where they apply to the visitor's region. | Until cleared by the visitor |
concentio_visitor_id |
Stores the pseudonymous visitor identifier (a random UUID). It is not linked to advertising or to tracking across other websites. | Until cleared by the visitor |
concentio_session_sent |
Prevents the same session from being reported more than once per 24 hours, so usage is not over-counted for billing. | Until cleared by the visitor |
concentio_config_cache |
Caches the consent banner configuration so it loads faster on later visits. Refreshed at least once every 24 hours. | Until cleared by the visitor |
All of the above are first-party storage items set directly by Concentio. We do not set third-party cookies, and none of these items are used for advertising or to track visitors across other websites.
5. Local storage and similar technologies
In addition to cookies, the Concentio CMP may use browser local storage or similar browser-based storage on customer websites.
Local storage is not the same as a cookie, but it can serve a similar function by storing information in the visitor's browser for later use. Depending on configuration, this may be used to persist consent state, preference selections, pseudonymous identifiers, banner versioning, or region-specific settings.
Concentio's own marketing website does not currently use local storage for analytics or advertising purposes based on the current setup.
6. Analytics and advertising
Concentio has chosen to keep its own marketing website minimal from a tracking perspective.
Based on the current setup, the Concentio marketing website does not currently use:
- analytics cookies;
- advertising cookies;
- cross-site tracking technologies;
- session replay scripts; or
- third-party ad pixels.
If Concentio adds analytics, advertising, embedded media, chat, or other optional technologies to the marketing website in the future, this Cookie Policy should be updated before or at the time those technologies are introduced, and any required consent mechanisms should also be reviewed and updated.
7. Who controls product-side cookies on customer websites?
When the Concentio CMP is implemented on a customer website, the website operator is generally responsible for deciding:
- whether and how the CMP is deployed;
- which consent categories and banner configurations are used;
- how long consent-related records or browser storage should persist, where configurable;
- what information is provided to end users in the customer's privacy and cookie notices; and
- which legal basis or consent model applies in the relevant jurisdictions.
In that context, the customer is generally the controller of consent-related processing on their website, while Concentio generally acts as a processor or service provider for the customer.
8. How to control cookies
You can control or delete cookies through your browser settings. Most browsers allow you to:
- view stored cookies;
- block all cookies or selected cookies;
- delete existing cookies; and
- receive a notification before a cookie is stored.
Please note that blocking or deleting cookies may affect the functionality of websites, including language preferences on the Concentio website and consent-management behavior on customer websites that use the Concentio CMP.
If a customer website using Concentio offers a consent banner or privacy preferences center, you may also be able to update your choices directly through that interface.
9. Changes to this Cookie Policy
We may update this Cookie Policy from time to time to reflect changes in our website, our product, or applicable legal requirements.
When we make material changes, we will update the "Last updated" date above.
10. Contact
If you have questions about this Cookie Policy or about cookies and similar technologies used by Concentio on its own website, please contact us at:
- Email: [email protected]
- Postal address: TODO_REGISTERED_ADDRESS, Odense, Denmark
If your question relates to a website operated by a Concentio customer, you should also review that website operator's privacy and cookie notices, since they are generally responsible for the implementation on their own site.