Transparency layer

Cookie Policy

Cookies and parallel technologies shape how digital services remember preferences, defend against abuse, and—only with permission—measure performance. This expanded statement explains each layer applied to the Cortena experience.

1. Controller reference

Brexalonyzur.world
Østerbrogade 142, 2100 København Ø, Denmark
Email: chat@brexalonyzur.world

Brexalonyzur.world determines which tags fire on the Cortena website and how consent is recorded. Certain partners act as independent controllers when their scripts collect data for their own analytics; their policies apply in parallel.

2. Cookies and analogous technologies

A cookie is a small text file placed on your device. Similar tools include HTML local storage, session storage, pixels, and software development kits embedded in mobile experiences. Together they can recognise returning browsers, persist shopping carts, or attribute campaign traffic.

3. Legal framework in Denmark and the EU

Directive 2002/58/EC as revised by Directive 2009/136/EC (the ePrivacy Directive) informs national rules on storing or accessing information in terminal equipment. Denmark implements these principles through the Executive Order on Electronic Communications Services and Networks together with guidance from the Danish Business Authority and Datatilsynet on consent quality.

Where processing also constitutes personal data handling, the GDPR supplies complementary obligations regarding transparency, lawfulness, and rights.

4. Strictly necessary cookies

These technologies are indispensable for delivering a service explicitly requested by the user: load balancers, security tokens, fraud scoring during checkout, and the storage of cookie consent itself. They do not require prior consent under the ePrivacy exemption for strictly necessary purposes, though we still disclose them here for completeness.

5. Functional preferences

Optional features such as remembering language selection or interface density may rely on low-risk cookies. When they are not strictly necessary, we seek consent before activation and document your choice in our consent repository.

6. Analytics cookies

If you enable analytics, pseudonymous identifiers help us understand aggregate navigation patterns, referral quality, and conversion funnels. IP truncation, aggregation, and data-minimisation settings are applied where the vendor permits. You may disable this category at any time through the cookie centre.

7. Marketing and audience cookies

Marketing tags may build segments, attribute repeat visits to campaigns, or coordinate creative rotation. They fire only after explicit opt-in. Withdrawing consent stops future collection but does not erase historical logs that have already been lawfully processed.

8. Local storage and consent logs

We may mirror consent strings in both cookies and local storage to survive browser restarts and synchronise preferences across subdomains. These entries contain version identifiers and timestamps rather than free-form personal narratives.

9. Typical storage periods

Session cookies expire when the browser closes. Persistent cookies may last from several minutes to twenty-four months depending on vendor defaults. We review partner documentation quarterly and renegotiate shorter horizons when commercially viable.

10. First-party and third-party placement

First-party cookies are set by this domain. Third-party cookies originate from embedded partners. Third-party placement diminishes in modern browsers; where alternatives such as server-side forwarding are available, we evaluate them during privacy impact reviews.

11. Consent management interface

The banner and modal reachable from the footer let you accept all categories, reject non-essential tags, or customise selections. Saved preferences propagate across pages during the same session and reload on subsequent visits via stored consent artefacts.

12. Browser-level controls

Every major browser offers settings to block third-party cookies, delete existing files, or alert you before storage. Consult documentation for Chrome, Firefox, Safari, Edge, or Brave. Blocking strictly necessary cookies may impair checkout or consent recall.

13. Global Privacy Control and Do Not Track

Industry alignment on DNT signals remains incomplete. Where browsers transmit Global Privacy Control headers recognised by our stack, we treat them as requests to opt out of sale or sharing as defined under applicable US state laws when those laws apply to our processing.

14. Policy maintenance

When new tags are onboarded, this policy and the consent interface receive parallel updates prior to production deployment unless emergency security patching requires immediate action, in which case retrospective disclosure follows within seventy-two hours.

15. Questions about cookies

Write to chat@brexalonyzur.world with “Cookie inquiry” in the subject line. For data subject rights that extend beyond cookies, please reference the Privacy Policy.