Cookie Policy

We use the word “cookies” to include HTTP cookies, HTML local storage, session storage, and similar technologies that store small pieces of data on your device.

Locale / language routing: our internationalisation module may set a cookie such as i18n_redirected so repeat visits respect your language choice under our routing strategy.

Cookie consent state: we store your choice (for example “essential only” vs “accept all”) in local storage under the key blans_cookie_consent so the banner does not reappear until you clear it or use “Cookie preferences” in the footer.

These items are used to provide a stable Site experience. Depending on your jurisdiction, they may not require marketing consent, but we list them openly.

Only if you click “Accept all”, we dynamically load the OpenPanel client script from openpanel.dev and initialise it with our project configuration. OpenPanel may set or read additional technical identifiers to attribute events to a browser session.

Our configuration is intended to measure aggregate Site usage (for example page views, outbound link tracking, and screen-related events as enabled in settings). OpenPanel’s own documentation describes categories of events and retention in their ecosystem.

Event data is sent to the analytics ingestion endpoint configured for our property (currently opapi.teur.work). That endpoint is operated for our analytics pipeline; traffic should be treated as operational telemetry, not as a secure channel for secrets.

Functional cookies and local storage persist until you clear them or until they expire per browser rules. Analytics identifiers follow OpenPanel’s lifecycle and our minimisation choices; withdrawing consent stops new event collection from our integration point of view, but you may also need to clear existing identifiers in browser settings for a full reset.

Use the cookie banner when it appears, or “Cookie preferences” in the Site footer to reset your decision and reload.

Browser settings can block or delete cookies; aggressive blocking may break language memory or cause the banner to return frequently.

There is no single global standard for DNT. We rely on the explicit cookie banner for optional analytics rather than on DNT headers alone.

If we add materially new cookies (for example marketing pixels), we will update this policy and, where required, adjust the banner before or concurrent with activation.

Questions about cookies: team{'@'}blans.co.