Cookie policy sections
Cookies and comparable tools help our static site remember your privacy preferences, protect forms from abuse, and—if you opt in—tell us which articles people read longest. This expanded Cookie Policy narrates each technology, names retention defaults, and explains how to reopen the settings panel after your first choice.
1. Policy overview & reading guide
Glixarexphim operates https://glixarexphim.world. We minimise tracking by design, yet transparency matters even for lightweight sites. Sections below alternate between storytelling and tables so compliance teams can screenshot structured disclosures while curious visitors skim the prose.
2. Definitions & browser mechanics
A cookie is a small text file placed on your device when you browse. A first-party cookie is set by our domain; a third-party cookie belongs to another domain embedded in our page (for example a future analytics partner). Local Storage and Session Storage APIs behave similarly for consent keys.
Pixels are invisible images that can report when loaded; we reference them only hypothetically under marketing—none fire today without consent.
3. Joint versus independent roles
For strictly necessary cookies, we act as independent controller. Should we deploy analytics supplied by an external vendor, that vendor becomes a processor acting on documented instructions, while certain aggregate reporting might make them an independent controller for their dashboards—we will flag that relationship before activation.
Contact: Glixarexphim, De Ruijterkade 24a, 1012 AA Amsterdam, Netherlands · +31 20 235 7822 · touch@glixarexphim.world
4. Detailed cookie categories
| Category | Purpose snapshot | Representative duration | Legal basis |
|---|---|---|---|
| Strictly necessary | Load balancing hints, secure session continuity, fraud screening signals, consent string persistence. | Session up to 12 months | Art. 6(1)(f) GDPR + Art. 5(3) ePrivacy implementation via national law |
| Analytics | Aggregated visit counts, scroll depth buckets, outbound link clicks, Core Web Vital estimates. | 6–24 months depending on vendor defaults | Art. 6(1)(a) consent |
| Marketing | Attribution IDs, frequency capping, creative rotation experiments if campaigns launch. | 30–180 days typical | Art. 6(1)(a) consent |
| Functional extras | Optional UI tweaks such as remembering expanded FAQ panels if we implement them. | Browser-dependent | Art. 6(1)(a) consent when not strictly necessary |
Cookie names evolve with releases; this policy focuses on categories to remain accurate between deployments.
5. Lifecycle, renewal, & proof of consent
Session cookies expire when you close the browser. Persistent cookies carry explicit expiry timestamps. Renewing consent happens when we materially alter purposes—users see the banner again pre-selected with their latest choice for transparency, not to trap them into broader permissions.
We retain consent logs (timestamp, version, categories) for twenty-four months to satisfy accountability obligations under Article 5(2) GDPR.
6. Similar technologies beyond cookies
Technologies include:
- localStorage keys mirroring consent JSON for instant client-side checks.
- Service workers only if introduced later for offline reading; we would update this Policy beforehand.
- ETags for cache validation—normally not personal data unless combined with other logs.
7. Advertising & Google-related technologies (marketing toggle)
If you enable Marketing cookies, our Site or embedded tags may allow partners to read or set cookies used for ad measurement or remarketing, subject to partner policies and your platform settings. Google’s use of advertising cookies is described at policies.google.com/technologies/ads. You can manage many ad personalisation choices through your Google account and industry tools where available.
We do not sell personal data. Marketing cookies are off by default until you accept them on our banner or in Cookie settings.
8. Third-party content & CDN transparency
Our pages currently request typography and icon fonts from Google Fonts and jsDelivr over HTTPS. Those requests transmit technical data such as IP address to those networks under their policies. We continue evaluating self-handling for stricter control.
Embedded media players, maps, or social feeds would only appear after dedicated notice blocks—none are live on this iteration.
9. Managing & revoking consent
You may clear site data through browser settings, use private windows, or reopen our banner after deleting the localStorage key named tdde_cookie_v1. Global opt-out initiatives (e.g., industry programmes) may supplement but not replace GDPR consent where required.
Employees assisting clients should follow organisational IT policies; this public Policy complements—not overrides—enterprise agreements.
10. Version history & communication
We archive prior versions internally with change logs. If an update reduces your rights, we seek fresh consent before applying downgraded protections—not that we intend to, but accountability language matters.
11. Questions & data subject channels
Email touch@glixarexphim.world with “Cookie enquiry” in the subject. For broader privacy rights, see our Privacy Policy.