Transparency · cookies & storage
Cookie policy
How Neon Vector Arena uses cookies, local storage, and similar technologies on this venue website.
What “cookies” means here
We group browser storage with a simple priority model: essential systems first, optional telemetry second, and promotional tracking off unless explicitly enabled.
Your browser already ships with the strongest levers—block third parties, clear storage, rotate profiles. This document explains what we intend to set so those controls align with reality.
Ad measurement cookies, when used, help frequency-cap creatives and detect fraud; they do not control purchases or account settings on third-party platforms.
Last updated: May 8, 2026
This Cookie Policy explains how Neon Vector Arena (“we,” “us,” or “our”) uses cookies and similar technologies on our venue website. Cookies help us deliver pages reliably, remember interface preferences, and measure navigation patterns when consent is provided.
We do not use cookies to control payment accounts or external platform credentials. Treat claims like that as scams.
1. Definitions and scope
A cookie is a small text file placed on your device when you visit a site. Similar technologies include HTML5 local storage, session storage, pixels, and software development kits inside embedded players. For readability, we refer to the whole family as “cookies” unless a section needs finer distinction.
This policy applies to HTML pages served from our domain. Third-party tools (ad networks, embedded streams, social widgets) may set their own cookies governed by their policies.
2. Why we use cookies at all
Running a modern venue website benefits from basic telemetry: understanding how visitors reach planning pages and where they need more clarity helps us improve navigation and guest guidance.
We align cookie practice with reasonable expectations for advertising-supported venue websites: essential operations first, optional measurement second, and no deceptive “dark patterns” to trick you into accepting unrelated tracking.
3. Essential (strictly necessary) cookies
Some cookies are required for core functionality or security. Examples include load-balancer affinity cookies, bot-mitigation tokens, or a flag that remembers you closed a safety banner. These are not used for cross-site profiling and typically persist only as long as the session or a short maintenance window.
If your browser blocks all cookies—including essential ones—some features may fail unpredictably (for example, repeated CSRF challenges on future forms).
4. Analytics and performance cookies
If enabled, analytics cookies may assign a pseudonymous identifier so we can count returning visitors, measure planning-page engagement, and improve booking guidance.
We do not sell analytics identifiers to data brokers. Where an analytics vendor offers IP anonymization or shortened retention, we prefer those settings.
5. Functional preference cookies
Optional cookies may remember collapsed navigation states, font scaling, reduced-motion preferences mirrored from your OS, or a “high contrast” toggle if we add one. Clearing site data removes these preferences.
6. Advertising and marketing cookies
If we partner with ad networks, marketing cookies may help frequency-cap creatives, measure viewability, or attribute clicks. You can manage many ad cookies through industry tools linked from the ad itself (“AdChoices,” “Why this ad?”). We prohibit inventory that promotes fraud, account theft, or deceptive software offers.
Marketing cookies should not be confused with account-level purchase settings, which are controlled by payment providers and platform services.
7. Third-party libraries (fonts, icons, scripts)
We load fonts and icon packs from reputable CDNs. Those requests may cause the CDN to set technical cookies or store server-side logs. If you operate a strict blocking profile, expect fallback fonts and missing icons—we will still try to keep articles readable.
8. Embedded media (future)
If we embed external media, clicking “play” may allow providers to set cookies or local storage under their policies. Use private browsing if you want tighter separation.
9. Managing cookies: practical steps
- Use your browser’s settings to delete or block third-party cookies while allowing first-party essentials.
- Enable Global Privacy Control or “Do Not Track” where available; we honor reasonable signals where technically feasible.
- On mobile, review OS-level ad tracking controls separately from app-level advertising settings.
- Teach younger visitors that clearing cookies does not “reset” a booked session or scoreboard history on our floor—this misunderstanding is often exploited by bad actors.
10. Cookie lifetimes and refresh
Session cookies expire when you close the browser. Persistent cookies may last days to months depending on vendor defaults; we periodically review vendor dashboards to prune unnecessary persistence.
11. Updates
When we add newsletters, accounts, or real contact delivery, cookie usage may expand. We will revise this page, bump the “Last updated” date, and summarize material changes near the header when practical.
12. Contact
Cookie questions may be sent to [email protected] with “Cookie Policy” in the subject line.