WARDENSEED - COOKIE POLICY
Effective Date: May 20, 2026 Version: 1.0
This Cookie Policy explains how Wardenseed uses cookies, local storage, and similar technologies. It supplements our Privacy Policy.
1. WHAT ARE COOKIES AND LOCAL STORAGE?
Cookies are small text files stored by your browser. Local storage and session storage are browser mechanisms that can persist identifiers, preferences, or session state on your device.
Wardenseed may use these technologies to operate the Platform reliably. We do not use cookies for aggressive cross-site advertising or sale of personal data to data brokers.
2. CATEGORIES WE USE
2.1 Essential (strictly necessary)
Required for core Platform operation. Without these, sign-in, realm continuity, security checks, and wallet-session flows may fail.
| Purpose | Examples | |---------|----------| | Authentication | Session cookies (`ww_session`, game session identifiers) | | Security | CSRF-style protections, abuse-prevention signals | | Wallet / play state | Wallet-link state, feature flags needed for safe resume |
Legal basis: performance of services, security, legitimate interests.
2.2 Wallet and session persistence
Supports wallet-connected play, SIWE session continuity, and preference recall across visits.
| Purpose | Examples | |---------|----------| | Session resume | HttpOnly session tokens, linked account continuity | | Interface | Theme or guidance preferences stored locally where applicable |
Legal basis: performance of services, user consent where required.
2.3 Performance and reliability
Helps us measure latency, error rates, and degraded API states so we can keep gameplay and commerce surfaces stable.
| Purpose | Examples | |---------|----------| | Diagnostics | Aggregated performance telemetry, route health | | Resilience | Client-side cache TTL hints for read models |
Legal basis: legitimate interests in operating a reliable product.
2.4 Analytics (limited)
We may use privacy-conscious, first-party or infrastructure-level analytics to understand feature adoption and failure modes. We do not run invasive ad-tracking pixels.
| Purpose | Examples | |---------|----------| | Product usage | Aggregate page or feature counts | | Abuse detection | Anomaly signals tied to sessions or IPs |
Legal basis: legitimate interests; consent where required by local law.
If we introduce optional marketing analytics in the future, we will request separate consent before enabling them.
3. THIRD-PARTY TECHNOLOGIES
Wallet extensions, RPC providers, hosting vendors, and crash-reporting tools may set their own cookies or storage outside Wardenseed's direct control. Review their policies before connecting a wallet or installing software.
4. YOUR CHOICES
You can block or delete cookies and clear local storage through browser settings. Blocking essential cookies may prevent login, wallet linking, or gameplay.
Browser “Do Not Track” signals are not uniformly honored across the industry; Wardenseed focuses on minimal, purpose-limited storage rather than cross-site tracking.
5. UPDATES
We may update this Cookie Policy when technologies or legal requirements change. Continued use after the effective date constitutes acknowledgment of the revised Policy.
6. CONTACT
Wardenseed [email protected]