> For the complete documentation index, see [llms.txt](https://vordai.gitbook.io/vordai-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vordai.gitbook.io/vordai-docs/legal/cookie-policy.md).

# Cookie Policy

Effective Date: August 17, 2026

This policy describes the cookies, analytics tags, pixels, and device storage used across Vord’s web surfaces.

### About this Policy

This Cookie Policy explains how VORD AI, INC. (“Vord,” “we,” “us,” or “our”) uses cookies, pixels, tags, local storage, IndexedDB, and similar technologies on vordai.io and related web surfaces. It should be read with our Privacy Policy.

### Technologies we use

Current web surfaces can use the following categories:

* Strictly necessary device storage. Local storage and IndexedDB keep security and recovery state, device-held wallet information, and a pseudonymous guest-device identifier used for quota and abuse prevention. The guest identifier is sent with guest requests but is not an account identifier.
* Functional device storage. Local storage and IndexedDB can remember encrypted conversation history, theme, language, selected model, onboarding state, input preferences, and other features you request.
* Analytics. Google Analytics helps us understand coarse page visits, referrers, devices, and product interactions. Google Tag Manager manages tags. Google Analytics may use identifiers such as the “\_ga” cookie. Our first-party analytics event code is designed not to include prompts or local conversation identifiers.
* Advertising measurement. Meta Pixel measures visits and campaign effectiveness and may use identifiers such as “\_fbp.”
* Payments and security. When payment features are offered and you choose to use them, Stripe and financial partners may use cookies or similar technologies for checkout, fraud prevention, authentication, and regulatory compliance. Account login and registration actions can load Cloudflare Turnstile when a security challenge is required.

### Current storage inventory

| Name or storage                | Purpose                                                          | Typical duration                                                           |
| ------------------------------ | ---------------------------------------------------------------- | -------------------------------------------------------------------------- |
| vord\_guest\_device\_id\_v1    | Guest quota and abuse prevention                                 | Until you clear site data or the identifier is rotated                     |
| Vord local storage / IndexedDB | Local product, wallet, recovery, history, and preferences        | Feature-dependent; generally until you delete or clear it                  |
| Account authentication storage | Necessary account authentication cookie and local-storage mirror | Until logout, expiration, or site-data removal                             |
| Account device identifiers     | Account security and device-session operation                    | Until cleared or rotated                                                   |
| Account session storage        | One-time OAuth, return-path, and purchase-flow state             | Current browser tab session or until consumed                              |
| Cloudflare Turnstile           | Security challenge, only when an account action requires it      | Provider-defined challenge or session duration                             |
| \_ga / *ga*\*                  | Google Analytics                                                 | Google default: up to 2 years, subject to configuration and browser limits |
| \_fbp                          | Meta advertising measurement                                     | Meta default: up to 90 days, subject to configuration and browser limits   |

### Why we use them

* Remember local settings and provide device-local product functions.
* Keep the Services secure and detect abuse or fraud.
* Measure site reliability, navigation, and feature usage.
* Understand marketing performance and improve outreach.
* Support payment and account flows you choose to use.

### Third-party providers

Third parties control their own technologies and retention periods. Their current practices are described in the Google cookie policy, Meta cookie policy, Stripe privacy policy, and Cloudflare privacy policy.

* Google: <https://policies.google.com/technologies/cookies>
* Meta: <https://www.facebook.com/privacy/policies/cookies/>
* Stripe: <https://stripe.com/privacy>
* Cloudflare: <https://www.cloudflare.com/privacypolicy/>

The exact cookies and durations can change when providers update their services. We will update this Policy when our use changes materially.

### Your choices

Some Vord web surfaces currently load analytics or advertising technologies when you visit. You can block or delete cookies through your browser and use device settings or provider opt-out tools. Blocking device storage can prevent conversations, preferences, wallet state, account access, or other local features from working correctly.

Browser controls do not always stop server requests or technologies that do not rely on cookies. Privacy extensions and platform-level controls may provide additional choices.

### Changes and contact

We may update this Policy as technologies or law change. Questions can be sent to <hi@vordai.io>.