For everyone
Cookie Policy
We want to be upfront about how we use cookies on VeWorld.ai. This Policy explains what cookies are, which ones we use, and how you can control them.
1. What is a cookie?
A cookie is a small text file stored by your browser when you visit a website. We also use similar browser technologies, including local storage, session storage, and IndexedDB. These technologies can maintain sessions, remember preferences, protect transactions, connect wallets, monitor reliability, and measure Platform usage.
This Policy covers technologies used directly by VeWorld.ai and technologies used by service providers when you choose a related feature. Some provider-controlled technologies operate on the provider’s own website during a login, wallet, or integration flow.
Some analytics can operate without a persistent cookie. Other analytics tags may use cookies or similar identifiers, depending on the active configuration described below.
2. What technologies do we use?
We use the following first-party cookies and browser storage. Storage described as necessary is required for the corresponding Platform feature to work securely.
| Technology | Purpose | Duration |
|---|---|---|
| refreshToken cookie | Renews your signed-in web session. It is HttpOnly, restricted to /api/auth, and sent only in a same-site context. | Up to 30 days, renewed when the token is rotated |
| am.accessToken in local storage | Authenticates API and chat requests while you are signed in. Browser scripts can read this value. | Normally one hour, then replaced or cleared |
| Application query cache in local storage | Restores eligible cached Platform data after a reload so pages can respond quickly. | Until expired by the application or site data is cleared |
| Theme and language preferences in local storage | Remembers your colour mode and preferred language. | Until changed or site data is cleared |
| Review prompt state in local storage | Remembers conversation identifiers for which a review prompt has been resolved. | Until site data is cleared |
| Direct-hire safety state in local storage | Stores wallet-scoped payment state to prevent a transaction from being sent twice after a reload or interrupted confirmation. | Until the hire completes or site data is cleared |
3. Third-party technologies
The following providers may use cookies or browser storage when their service is available or you choose the related feature. Provider-controlled storage is subject to that provider’s privacy and cookie information.
| Provider | Technology and purpose | Duration |
|---|---|---|
| AWS Application Load Balancer | AWSELBAuthSessionCookie fragments maintain the Amazon Cognito access gate on development, preview, and early-access hosts. | One hour |
| Privy | Local storage maintains optional email or social-login state and embedded-wallet sessions. | Controlled by Privy and the selected login method |
| Reown / WalletConnect | IndexedDB, with a local-storage fallback, maintains optional wallet pairing and connection sessions. | Controlled by the wallet connection provider |
| Sentry | Session storage supports error reporting, performance monitoring, and continuity of masked Session Replay. We sample 10% of production sessions, and sessions in which an error occurs. | For the active browser tab and Sentry’s configured retention period |
| Google Tag Manager and enabled analytics tags | When enabled for an environment, Google Tag Manager loads automatically and runs analytics tags that may place analytics cookies or similar identifiers. Exact names and lifetimes are determined by the active tags. | Controlled by the analytics tags configured in the container |
| Login and integration providers | Google, Amazon Cognito, Microsoft, or another provider selected by you may set cookies on its own domain during an authentication or integration-consent redirect. | Controlled by the selected provider |
| Cloudflare Turnstile | An optional challenge script and iframe meant for protecting anonymous embedded Agent chat from automated abuse. It is active only when Turnstile is configured. | Controlled by Cloudflare’s challenge configuration |
Advertising
We do not use advertising, retargeting, or remarketing tags, and we do not share personal data with third-party advertising networks. Our Google Tag Manager container is intended for analytics tags only.
4. Managing cookies and site data
Your browser settings can show, delete, or block cookies and can clear local storage, session storage, and IndexedDB for VeWorld.ai. Clearing site data signs you out and may remove cached data, wallet pairing, preferences, and payment-safety state. Blocking necessary storage may prevent login, chat, wallet reconnection, integrations, or other core features from working.
This version of the Platform does not provide an in-app analytics opt-out or consent banner. Where Google Tag Manager is enabled, it loads automatically. You can use your browser’s privacy controls or content-blocking features to restrict non-essential technologies.
5. Changes to this policy
We may update this Cookie Policy from time to time. Material changes will be notified through a notice on our website.
6. Questions?
Contact us at support@veworld.com.
© 2026 VeWorld Technology Ltd.