Introduction from the controller
Chiphronthalfyro.world prepares this Cookie Policy so visitors to
chiphronthalfyro.world know how digital storage supports the Alira
experience. Contact our privacy desk at 45A Paul Matthews Road, Rosedale, Auckland 0632, New
Zealand, or email ask@chiphronthalfyro.world
with “Cookie Help” in the subject line.
The companion Privacy Policy explains broader personal data
flows, while this document narrows in on browser storage, pixels, and analogous technologies
that activate after you make a choice in our consent layer.
Definitions you can rely on
Cookies are small text strings that domains place on your device to remember preferences or
analyse traffic patterns. Local Storage and Session Storage offer larger containers for
similar purposes. Pixels (invisible images) notify servers when a page renders, helping
measure campaign performance when you opt into marketing.
We treat all of them as “cookies” for transparency even when the technology differs
technically.
How we bucket consent choices
- Strictly necessary tokens keep consent evidence, maintain security
during form submissions, and balance infrastructure loads. They do not require opt-in
because disabling them would break lawful service delivery.
- Analytics helps us understand aggregate journeys—think scroll depth,
click heatmaps, or referral tagging—without aiming to profile a single person. You may
refuse this bucket while still browsing.
- Marketing synchronises ad measurement, frequency capping, and creative
rotation when you explicitly enable it.
Our banner mirrors these buckets, and the “Cookie settings” modal reopens whenever you
want to fine-tune previously saved preferences.
Inventory with lifetimes
alira_cookie_prefs persists in Local Storage for twelve months, storing JSON
with boolean flags for analytics and marketing plus a timestamp. Legal basis: Art.6(1)(a)
for optional flags and Art.6(1)(f) for proving compliance with ePrivacy expectations.
Session identifiers issued by the hosting provider expire when you close the
browser unless infrastructure teams extend them for debugging with your consent.
We currently avoid third-party ad pixels on this static property, yet we maintain this
section so expansion work does not outpace disclosures. When a vendor activates, we will
name them, cite their privacy documentation, and block loading until you opt in.
Browser, operating system, and manual erasure
Major browsers include settings panels that delete stored data site-by-site or globally.
Mobile operating systems provide similar reset tools inside privacy menus. Clearing data may
log you out of preference centres and surface the banner again—as expected behaviour.
If technical barriers prevent you from exercising choice, email us with screenshots so
support staff can escalate to engineering.
International processors we may onboard
When analytics or advertising partners operate abroad, we require Standard Contractual
Clauses, supplementary measures such as encryption in transit, and data processing
agreements listing subprocessors. You retain the rights summarised in the Privacy Policy,
including access to copies of safeguards.
Escalation and accountability
Cookie complaints feed into the same channel as broader privacy grievances. Supervisory
authorities may include the NZ Office of the Privacy Commissioner or EU members where GDPR
jurisdiction exists.