Browser transparency

Cookie Policy

A precise inventory of what VENATRIQ stores in the browser, why it is needed, and what you can control.

Effective September 8, 2026All legal documents

Section 01

Our current approach

This Cookie Policy explains how Venatriq uses cookies and similar storage in VENATRIQ applications and websites. The browser-storage descriptions also apply when hosted web content is displayed in an application's embedded browser (WebView).

Our first-party cookies support requested sign-in, form security, and permission choices where the AI-processing consent flow is enabled. Browser storage also remembers preferences and map activity, and the map SDK uses provider usage identifiers as described below. We do not currently install advertising cookies or a separate website-analytics tracker.

The first-visit notice explains current storage; dismissing it is an acknowledgment, not consent to advertising, marketing emails, location sharing, third-party AI processing, or optional learning. Those choices need separate permission. Storage on venatriq.com and app.venatriq.com is generally separate.

Section 02

Cookies we use

Name	Purpose	Typical duration	Protection
`venatriq_referral`	Remembers the opaque invitation code when you choose a friend's invitation, so a new account can claim an eligible referral. It does not grant marketing consent or create a friendship.	Up to 7 days; cleared after a completed claim.	HttpOnly; Secure in production; SameSite=Lax; not an advertising tracker.
`venatriq_session`	Keeps an authenticated user signed in and allows the server to authorize account requests.	Up to 14 days, or until logout, deletion, revocation, or expiry.	HttpOnly; Secure in production; SameSite=Lax; available across the app.
`venatriq_oauth_flow`	Temporarily protects Google or Apple sign-in by preserving state, nonce, and related flow-verification information.	Up to 10 minutes and cleared after the callback.	HttpOnly; Secure for Apple and in production; SameSite=Lax for Google and SameSite=None for Apple; restricted to the OAuth route.
`__Host-venatriq_private_ai_processing`	Where the AI permission flow is enabled, records an explicit OpenAI-processing grant tied to this sign-in or the temporary pre-signup context. It is separate from Terms acceptance and optional learning.	Up to 14 days for a sign-in; up to 30 minutes before signup. A different session or disclosure version requires a new grant.	Signed, session/context-bound permission; HttpOnly and Secure in production. Local HTTP testing uses venatriq_private_ai_processing.
`__Host-venatriq_private_ai_anonymous`	Where enabled, identifies the temporary pre-signup context for the AI-permission flow. It does not by itself grant permission or create an account.	Up to 30 minutes.	Random context identifier; HttpOnly and Secure in production. Local HTTP testing uses venatriq_private_ai_anonymous.
`__Host-venatriq_early_csrf`	Protects early-access form submissions on the temporary landing site against cross-site request forgery.	Up to 30 minutes; a new form session can replace it.	HttpOnly; Secure on HTTPS; SameSite=Strict; path /. Local HTTP testing uses venatriq_early_csrf.

Section 03

Local device storage

Local storage is not a cookie, but it remembers information in your browser. VENATRIQ uses it for theme, map and terrain choices, recent searches and map view, dismissed guidance, selected Group Hunt, and cached app state or drafts. Some values can include location-related context; use care on a shared device.

venatriq-direction-preference-v1 remembers whether you prefer the phone compass or GPS movement direction on this browser until you change it or clear site data. This entry does not contain coordinates, compass readings, or a permission grant. Location and orientation permissions are controlled separately by your browser; saving a preference cannot bypass them.

venatriq-cookie-notice-v3 remembers dismissal of the current storage notice until browser data is cleared or the notice version changes. It is not a marketing-consent record.

Some local values may remain until you clear browser data, reset the related preference, or the app replaces them. Sensitive account authorization is not based solely on local storage.

An embedded browser can keep its own cookies, cache, and preferences separately from Safari, Chrome, or another standalone browser. Clearing one does not necessarily clear the others. Removing local data or uninstalling an application is not a request to delete server-held account data or cancel a subscription. Cached pages and map tiles do not provide a complete offline map or background GPS service.

Supported native builds separately keep device-protected installation credentials and an account-bound GPS recording journal. Signing out pauses and hides an unsaved native track; the same account must sign back in to review, save, or discard it. This protects interrupted work without exposing it to another account. Device permissions, notification opt-in, and Group Hunt sharing remain separate controls; native storage does not grant them.

Section 04

Map-provider storage and requests

When a map loads, Mapbox receives map and tile requests that can reveal the viewed geographic area, your IP address, and device or request information. Its SDK uses browser entries beginning with mapbox.eventData for usage-event metadata and a random usage identifier. Cached map tiles may also be retained under the SDK and browser cache lifecycle.

We disable the SDK's optional performance-metrics collection in our map instances. That does not disable the map requests or all provider usage and billing accounting. These provider entries are distinct from our sign-in cookies; we do not describe every provider identifier as strictly necessary in every jurisdiction.

See the provider's SDK storage disclosure and privacy policy for more about its handling of usage data. Clearing browser site data removes local entries, but using the map can recreate them.

Section 05

Third-party services

When you use Google or Apple sign-in, Stripe checkout, or an external link, that provider may use its own cookies under its policy. Hosting and security services may also use protective cookies depending on the deployment. VENATRIQ does not control cookies set on another provider's domain; browser controls may need to be applied separately to each site.

Section 06

Analytics and future changes

If VENATRIQ later adds optional analytics, personalization, or advertising technologies, we will update this inventory and, where legally required, ask for consent before those technologies load. We will not disguise optional tracking as an essential cookie.

Section 07

Your controls

Most browsers let you view, delete, or block cookies and site data. Blocking essential cookies will prevent sign-in and may interrupt account features. Clearing local storage resets saved browser preferences and can remove unsynchronized local drafts.

You can reopen the notice below. It does not provide a switch for provider accounting or change browser permissions. For other choices, review the Privacy Policy, manage email preferences, or use account privacy controls. Browser location permission and Group Hunt location sharing are separate settings.

Section 08

Contact

Questions about cookies or browser storage can be sent to support@venatriq.com.