Legal information
Cookie Policy
How CoreBase uses local storage, cookies, tags, and consent controls.
Last reviewed: August 16, 2026
Consent-first operation
Optional categories are denied by default. Before you make a choice, CoreBase does not request Google Tag Manager and does not send analytics or advertising data through that container. The consent interface lets you accept all optional categories, reject them, or select categories individually. You can reopen it at any time from “Cookie settings” in the footer.
Cookie categories
- Essential
- Required for security, page delivery, requested functions, locale behavior, and remembering your consent choice. It cannot be disabled through the consent panel.
- Analytics
- Allows Google Analytics and Microsoft Clarity tags used to understand site usage, navigation, interaction, and technical performance.
- Preferences
- Allows optional settings that remember how you prefer to use CoreBase.
- Advertising
- Allows Google AdSense advertising delivery and measurement, advertising storage and signals, personalization where permitted, and fraud or abuse prevention.
Technologies and providers
Google Tag Manager container GTM-N9PCWBW6 is the controlled delivery layer for Google Analytics, Microsoft Clarity, and Google AdSense. Each tag inside the container must be assigned the correct consent category and must not fire without the required consent. Google Search Console may use verification metadata and aggregated search-performance data; it is not enabled by an analytics-cookie choice.
Storage and duration
CoreBase stores your consent choice in first-party browser local storage under “corebase-consent-v1”. The record contains category choices, a consent-policy version, and an update time. Provider cookies and their duration depend on the tags and retention settings configured in Google Tag Manager and the corresponding provider policies. The exact provider cookie inventory must be revalidated whenever the container changes.
Changing or withdrawing consent
Open “Cookie settings” in the footer to change your choices. Rejecting optional categories prevents their tags from loading on a fresh page and sends denied consent signals to supported providers. Clearing browser site data also removes the stored CoreBase choice, so the consent interface will appear again on your next visit.