Cookie Policy

1. Scope of this policy

This Cookie Policy explains cookies and similar browser-storage technologies in relation to talandrixa.com. It should be read with the Privacy Policy, which describes technical logs, correspondence and privacy rights more broadly.

The policy covers code controlled by Talandrixa. A website you visit after following an external link may set its own cookies under its own policies. We do not control those external technologies.

2. What these technologies mean

Cookie

A small text value that a website asks a browser to store and return with later HTTP requests to the relevant domain. Cookies may be session-based or persistent.

First-party cookie

A cookie associated with the domain shown in the browser address bar. It may support essential functions, preferences, measurement or other purposes.

Third-party cookie

A cookie associated with a different domain, commonly introduced through advertising, embedded media, social widgets or cross-site services.

Local storage

A browser key-value store associated with a site. Unlike a cookie, a localStorage value is not automatically attached to every network request.

Session storage

Browser storage generally limited to a single tab session. Talandrixa does not intentionally use it at the effective date.

Pixel or beacon

A small resource request or script event that can report page viewing or interaction. Talandrixa does not deploy advertising or marketing pixels.

Server log

A hosting-side record of a network request. A log is not a cookie and may exist even where browser storage is disabled.

Cache

Copies of files retained by a browser or intermediary to load pages faster. Caching is distinct from user profiling.

3. Current storage inventory

The following table is the complete intentional browser-storage inventory for the current version of Talandrixa.

The values do not contain a name, email address, user ID, unique advertising identifier, gambling behaviour or the pages you have read. Site JavaScript reads them locally to apply the selected behaviour. It does not transmit them to an analytics endpoint.

4. Why preferences are stored

Age acknowledgement

The publication concerns an adult industry and is restricted to readers aged 18 or over. Remembering the acknowledgement reduces repetition while maintaining a clear entry notice. It is not a reliable identity or age-verification mechanism and should not be interpreted as one.

Colour theme

The theme value is an accessibility and comfort preference. If no value exists, the site may initially follow the device’s prefers-color-scheme setting. Selecting the theme control saves the explicit choice for later visits.

These functions can operate without an account or server-side reader profile. That is why localStorage is used rather than a registration system.

5. Technologies we do not use

At the effective date, Talandrixa does not intentionally deploy:

• audience analytics cookies or scripts;
• advertising, retargeting or conversion pixels;
• affiliate attribution cookies or click IDs;
• cross-site identifiers, browser fingerprinting or probabilistic identity matching;
• social-media widgets or embedded social timelines;
• embedded casino games, operator widgets or gambling account integrations;
• personalisation based on inferred gambling interest;
• A/B testing identifiers or heat-map/session-recording tools;
• push-notification identifiers; or
• payment, wallet or deposit technologies.

6. Server logs, caching and delivery

Disabling cookies or localStorage does not prevent the ordinary technical exchange required to load a website. Your device still sends a request that can include an IP address, user-agent, requested path, accepted file types and a referrer. The host may record some of this information in security or access logs.

Browsers and hosting infrastructure may cache HTML, CSS, JavaScript and image files. Cache-control headers tell browsers when files can be reused or should be checked for updates. Cached assets improve speed and do not by themselves create a reader profile.

Security infrastructure may temporarily process technical characteristics to rate-limit abusive traffic, identify automated attacks or keep the service available. If a future provider introduces a cookie for load balancing or security, the inventory will be updated with the name, purpose and duration.

7. External links and third parties

Articles may link to New Zealand government agencies, regulators, legislation databases, event organisers, manufacturers, project owners and independent support services. These are ordinary links, not embedded content. No request is sent to the destination merely because the link appears on a Talandrixa page.

When you choose to follow a link, the destination may use cookies or similar technologies according to its own policy. Review the destination’s notice and controls. Talandrixa cannot remove a cookie set by a different domain.

8. Your browser choices

Clear Talandrixa preferences

You can remove the two localStorage entries through your browser’s site-data or privacy settings. Look for stored data associated with talandrixa.com and choose the option to clear or delete it. The next visit will show the 18+ notice again and revert to the device colour preference.

Block storage

Many browsers can block cookies, clear data on exit, limit persistent storage or use private-browsing mode. Blocking localStorage may cause the age notice to return on each page and prevent theme persistence, but editorial content should remain available after each age confirmation.

Delete cached files

Cached files can be cleared separately from cookies and site data. Doing so may make the next page load slower but does not change your rights or the content available.

Browser-specific instructions

Control names change by browser and version. Consult the official help pages for your browser rather than relying on outdated step-by-step instructions. Search the settings for “site data”, “cookies”, “local storage” or “clear browsing data”.

9. Consent and future changes

The current local preferences support user-requested display and access-notice functionality and do not perform tracking. If Talandrixa later proposes a materially different technology — such as optional analytics, embedded media that sets third-party cookies, or advertising measurement — we will:

1. document the provider, cookie names, purpose, data involved and lifespan;
2. assess whether prior consent or an opt-out is required;
3. keep optional technology disabled until the appropriate choice has been made;
4. make withdrawal as straightforward as acceptance; and
5. update this policy’s effective date and version.

Consent, where required, will be specific and informed. Continuing to browse will not be treated as consent to unrelated cross-site tracking.

10. Do Not Track and global privacy signals

Some browsers transmit Do Not Track or Global Privacy Control signals. Because Talandrixa does not sell or share personal information for targeted advertising and does not deploy behavioural trackers, there is no separate tracking workflow to disable when such a signal is received.

We nevertheless support the principle behind these signals: readers should be able to access public-interest information without being silently profiled. If the site’s practices change, recognised signals will be considered as part of the control design.

11. Questions and contact

Questions about browser storage, an unidentified value or a suspected inconsistency can be sent to:

Please include the browser, device type, page address and storage name where known. Do not send passwords, gambling account details or payment information.