Introduction
Cookies are small text strings stored on your device when a site responds to your browser. Pixel tags, SDK snippets, and HTML5 storage behave similarly even when the label “cookie” does not appear in developer tools. This Policy covers all lightweight identifiers we intentionally place or instruct vendors to place after you make a choice.
We separate technologies into strictly necessary, analytics, and marketing groups. Strictly necessary items power security basics, load-balancing affinity, and remembering that you dismissed or configured the banner—without them the site cannot reliably remember your consent state.
How we describe technologies
- HTTP cookie: a key/value pair returned through Set-Cookie headers or JavaScript APIs scoped to our domain or subprocessors.
- Local storage: larger key/value persistence kept entirely in-browser unless scripts explicitly transmit values.
- Session storage: tab-scoped storage erased when you close the browsing session.
- Pixel: a tiny graphic request used to confirm email renders or attribute campaigns—only active when marketing consent exists.
Synchronised messaging
If marketing pixels remain inactive because you rejected that category, downstream dashboards simply show “no signal”—we do not reconstruct identities through illicit fingerprinting.
Purpose categories
Strictly necessary
Includes preference tokens that remember cookie choices, anti-abuse rate limiting, secure session continuity after login-style flows (if introduced later), and resilience cookies issued by content delivery networks.
Analytics
Aggregates visit counts, approximate geography at city level, landing pages, scroll depth proxies, and technical errors. Identifiers rotate periodically so profiles remain coarse.
Marketing
Supports measuring campaigns we intentionally run, attributing conversions to creative variants, and suppressing duplicate advertisements after you convert.
Functional extras
Optional convenience layers such as remembering preferred studio location across visits—loaded only when we expose matching toggles.
First-party and third-party recipients
First-party cookies stay tied to vorghalxkhimxun.world or subdomains we operate. Third-party cookies originate from analytics or advertising partners embedded through script tags you approve; those partners maintain their own privacy notices and retention clocks.
When possible we configure subprocessors to behave as first-party data processors rather than independent controllers, but some advertising networks inherently operate as joint or independent controllers under GDPR definitions.
Typical lifetimes
- Session cookies: expire within minutes or hours after your visit ends.
- Consent snapshots: persist up to twelve months unless you reset preferences sooner.
- Analytics identifiers: often thirteen months to align with quarterly reporting cycles.
- Marketing identifiers: vary by network policy but generally refresh after ninety days of inactivity.
Analytics processing
Analytics scripts load only after you enable the analytics toggle or choose “Accept All”. Data feeds into dashboards summarising traffic peaks around launch announcements or seasonal programmes. IP truncation may occur inside subprocessors before logs reach analysts.
Coaches do not receive individually identifiable analytics dossiers about named participants; insights remain aggregated unless you separately consent to personalised surveys.
Marketing signals
Marketing cookies measure whether promotional pathways remain understandable and compliant with advertising platform policies. They may sync hashed identifiers provided by those platforms rather than raw email addresses collected through training bookings.
Promotional discipline
If we are not actively funding campaigns in your region, marketing containers remain dormant even when toggled on—they simply establish readiness without firing unnecessary requests.
Local storage entries
Our banner writes consent choices into local storage when browsers permit that mechanism instead of traditional cookies. Clearing site data removes both cookies and parallel storage entries simultaneously.
Managing preferences
Use any combination of these tools:
- In-site “Cookie Settings” link reopening the overlay tied to this Policy.
- Browser settings blocking third-party cookies or clearing stored data per schedule.
- Industry opt-out portals offered by advertising alliances where available in your jurisdiction.
Blocking strictly necessary technologies may cause forms or preference recall to fail until you allow minimal storage again.
Updates
When subprocessors change materially we revise this Policy and refresh the hero date. Minor vendor patches may occur without separate notification beyond updated timestamps.
Questions
Email mailuse@vorghalxkhimxun.world or write to 1A/155 Queen Street, Auckland CBD, Auckland 1010 with “Cookie enquiry” in the subject line so routing stays efficient.