# Cookie Policy

**Last Updated:** May 15, 2026  
**Effective Date:** May 19, 2026  
**Version:** v1.0.0

This Cookie Policy explains how LenserFight uses cookies and similar technologies on LenserFight websites, hosted applications, documentation, public arena surfaces, and related services (collectively, the "Platform").

Cookies and similar technologies help the Platform operate securely, remember preferences, manage sessions, measure performance, prevent abuse, and improve experimental AI, agent, battle, and workflow features.

---

## 1. What Are Cookies?

Cookies are small text files stored on your device through your browser when you visit a website. Cookies may enable basic functionality, remember preferences, support authentication, and generate statistical reports.

LenserFight may also use similar technologies, including local storage, session storage, secure storage, pixels, SDK-based analytics, device/session identifiers, attribution links, and comparable tools.

---

## 2. Why We Use Cookies

LenserFight may use cookies and similar technologies to:

- keep the Platform secure and available,
- manage authentication and user sessions,
- remember language, theme, consent, and interface preferences,
- support public arena, documentation, battle, workflow, and account features,
- detect malicious traffic, fraud, credential abuse, spam, and resource abuse,
- measure product performance, error rates, and aggregate usage,
- understand how users discover and use LenserFight,
- improve documentation, onboarding, and experimental AI workflows.

---

## 3. Types of Cookies and Similar Technologies

### 3.1 Essential Cookies

Essential cookies are required for basic Platform functionality and security. Without them, login, session management, CSRF protection, rate limiting, security controls, or preference persistence may not work.

Examples include:

- **Authentication/session technologies:** used to keep users signed in and protect sessions.
- **Cloudflare cookies:** used for security, DDoS protection, bot detection, traffic management, and CDN reliability.
- **Supabase auth storage:** used where configured for authentication and session continuity.
- **Local/session storage:** used for language, theme, consent, onboarding, and product state where necessary.

Essential cookies are generally processed without separate consent because they are necessary to provide the requested service.

### 3.2 Analytics and Performance Cookies

Analytics and performance cookies help us understand aggregate usage, page visits, route changes, feature usage, performance issues, and errors.

Examples include:

- **Google Analytics:** website and documentation traffic analytics where enabled.
- **PostHog:** product analytics, behavior analytics, and error monitoring where enabled.

Analytics and performance cookies are enabled only where permitted by applicable law and consent settings.

### 3.3 Preference Cookies

Preference cookies and local storage may remember language, theme, UI state, dismissed notices, consent choices, and similar preferences.

### 3.4 Security, Abuse-Prevention, and Reliability Technologies

Security technologies may help identify malicious traffic, suspicious sessions, bot activity, excessive requests, prompt-injection abuse, API abuse, and other attacks against the Platform.

### 3.5 Attribution and Campaign Technologies

Where enabled, attribution technologies may help us understand referral links, campaign parameters, documentation links, or community launch traffic. Optional campaign or marketing technologies are managed according to consent requirements.

---

## 4. Cookie Duration

Cookie duration depends on the technology and purpose:

| Type | Purpose | Typical Duration |
|------|---------|------------------|
| Session | login, CSRF protection, security state | until the browser session ends or logout |
| Persistent preference | language, theme, consent, interface state | up to 1 year |
| Analytics | aggregate product and documentation usage | up to 13 months, subject to provider settings and consent |
| Security logs | abuse prevention and incident investigation | retained according to the Privacy Policy |

Specific providers may apply their own retention rules under their own policies.

---

## 5. Consent and Managing Cookies

You can manage cookies through:

- the cookie consent interface where available,
- your browser settings,
- private browsing controls,
- device settings for mobile or embedded browser contexts,
- Platform account or session controls where available.

Blocking essential cookies may prevent login or core Platform features from working. Rejecting analytics cookies will not prevent access to essential Platform features, but it may reduce our ability to diagnose errors and improve the service.

---

## 6. Third-Party Cookies and External Destinations

Third-party providers may set cookies or similar technologies when they provide infrastructure, authentication, analytics, AI, payment, support, embedded media, or external link services.

If you open GitHub, Google, payment pages, OAuth flows, model-provider pages, external links, issue trackers, support channels, or other third-party destinations, those third parties act under their own terms, privacy policies, and cookie policies.

---

## 7. Updates

This Cookie Policy is effective as of **May 19, 2026**. LenserFight may update this policy when necessary. Updated versions become effective when published unless a later effective date is stated.

---

## 8. Contact

For cookie-related questions:

**Email:** omer@chainabit.com
