Cookie Policy

Last updated: 19 March 2026 · Controller: Throxxeneaglox, Queenstown, New Zealand

This Cookie Policy describes how Throxxeneaglox (“we”, “us”), Corner Brecon and, Isle Street, Queenstown 9348, New Zealand, uses cookies and similar technologies on https://throxxeneaglox.world. It supplements our Privacy Policy. Contact: feedback@throxxeneaglox.world, phone +64 3 441 0590.

1. What are cookies and similar technologies

Cookies are small text files stored on your device when you visit a website. Similar technologies include local storage, session storage, pixels, tags, and software development kits embedded in pages or emails. Together we refer to them as “cookies” unless a distinction is required.

2. Why we use cookies

We use cookies to: operate the website securely; remember your cookie consent choices; measure aggregate traffic and performance when you allow analytics; support marketing measurement when you allow marketing tools; reduce fraud; and improve accessibility and error diagnostics.

3. Legal bases

Under the GDPR, strictly necessary cookies rely on our legitimate interest in providing a secure, functional service or, where required, compliance with legal obligations. Analytics and marketing cookies are used only after you provide consent via our banner or settings panel, except where a specific technology is strictly necessary (for example, a security cookie that does not track behaviour across unrelated sites).

4. Categories of cookies

4.1 Strictly necessary

These cookies are required for core functions such as load balancing, security tokens, bot management, storing your cookie preferences, and maintaining session integrity during form submission. They cannot be disabled through our banner because the site would not function reliably without them. Typical duration: session to twelve months for consent storage.

4.2 Analytics

If you enable analytics, we or our partners may set cookies to collect pseudonymous identifiers, page URLs, referrer information, device category, and interaction events. We use this information in aggregate to understand which content is useful and to fix technical issues. Typical duration: six to twenty-four months depending on the vendor configuration. You may withdraw consent at any time through the cookie settings or by clearing storage in your browser.

4.3 Marketing

If you enable marketing, cookies or pixels may help us measure ad performance, build anonymised audience segments, or cap how often you see a message. We do not intentionally serve marketing cookies to visitors who reject them. Durations vary by partner, commonly up to ninety days to two years. Withdrawing consent stops future collection but may not delete historical logs on partner systems; you may exercise partner-specific opt-outs where offered.

5. Local storage for consent

Our consent tool stores a JSON object in localStorage under the key aligned with our script (for example, preferences including necessary, analytics, and marketing flags and a timestamp). This record demonstrates consent for auditing. Clearing site data removes the record and will cause the banner to reappear.

6. Third-party recipients

Where analytics or marketing tools are activated, data may be processed by subprocessors located in New Zealand, the EEA, the UK, or the United States under appropriate safeguards such as Standard Contractual Clauses. A current list of categories of recipients is available on request; specific vendor names may change as we update tooling.

7. Your choices

You can: use our “Cookie settings” button to adjust optional categories; use browser controls to block or delete cookies; enable global privacy signals where we support them in future (we will update this Policy if we implement automatic recognition); or contact us to discuss your preferences. Blocking strictly necessary cookies may break parts of the site.

8. Retention of consent logs

We retain records that demonstrate consent and essential server logs in line with the retention table in our Privacy Policy, typically aligned with legal, security, and accounting needs.

9. Do Not Track

There is no uniform industry standard for “Do Not Track” browser signals. We currently rely on our explicit consent interface rather than automated DNT interpretation. If standards stabilise, we will review practices and update this section.

10. Children

Our website is not directed at children. We do not knowingly use behavioural advertising cookies aimed at minors.

11. Changes

We may update this Cookie Policy when we introduce new technologies or legal requirements change. Check the “Last updated” date and review the Policy periodically.

12. Summary table (illustrative)

The exact cookie names may vary after deployments. This table summarises typical purposes:

  • Consent storage: localStorage entry, up to twelve months, strictly necessary.
  • Session security: session cookie, session length, strictly necessary.
  • Analytics ID: first-party or third-party cookie if enabled, six to twenty-four months, analytics consent.
  • Marketing pixel: third-party cookie if enabled, up to two years, marketing consent.