Cookie Policy

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 mapping services use provider requests and usage identifiers as described below. VENATRIQ does not add advertising cookies. The public venatriq.com website offers optional Google Analytics after an explicit choice; it is not installed by this feature in private app pages or native app views. Integrated mapping providers process requests under their own policies. Public how-to guides use the separate first-party measurement described below.

How-to guide measurement, added October 24, 2026. Public guides count view events and explicit store-button clicks by guide, day and a fixed source label such as Facebook or website. A random token stays in page memory for up to ten minutes to prevent repeat requests from being counted twice; it is not a cookie, a persistent browser identifier, an account identity or a fingerprint. The measurement tables do not store IP addresses, user agents, hunting locations or customer records. Expired token receipts and aggregates older than 90 days are removed by bounded cleanup during subsequent measurement requests. Counts do not establish unique visitors, installations or purchases. Guide links continue to work if measurement is blocked or unavailable.

The app's 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. The public website separately asks whether to allow optional analytics. Storage on venatriq.com and app.venatriq.com is generally separate.

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. Browser caches alone do not provide the iOS app's dedicated offline map download or a background GPS service. In supported iOS builds, an eligible member can separately save a device-protected, account-bound field snapshot and selected native Mapbox map areas. This is app storage, not a browser cookie; removing browser site data alone may not remove it. Use the Offline field kit's removal control or remove the app's local data.

Offline pin drafts use separate encrypted native app storage and device Keychain keys. They are not browser cookies. Signing out and removing map downloads do not discard unsynced pin drafts; use Pins on this phone to remove individual drafts or remove the app's local data.

Pending edits to downloaded pins and boundaries are encrypted native application data, not browser cookies. They follow the same account isolation, locked retention after sign-out, explicit synchronization and deletion controls as unsynced pin drafts. Use the offline changes review to discard an individual pending edit.

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.

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.

The native iOS offline map uses the Mapbox Maps SDK, which stores downloaded style and tile resources on the device and sends map-resource requests when it downloads or loads uncached data online. Mapbox states that its mobile SDK can send de-identified location and usage telemetry when gathered; its attribution control provides a telemetry opt-out. These native SDK files and controls are separate from the browser entries described above. Mapbox's privacy policy explains its processing.

Google True 3D. Choosing to open this view loads the Google Maps JavaScript SDK and requests Google map content for the area you view. Those requests expose the viewed area and network or device request information to Google. Google describes its use of cookies, browser storage, device identifiers and caches in its Privacy Policy; provider-managed data is separate from VENATRIQ's sign-in cookies. Closing True 3D removes the map view but does not clear existing browser or provider data. VENATRIQ does not offer an offline download of Google imagery. Account-linked viewing-allowance counters are kept on our server, not as a new browser cookie.

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.

On public pages at venatriq.com, Google Analytics loads only after you choose Allow analytics. Before that choice, or after you turn it off, this integration does not send measurement requests. We measure public page views, scrolling and explicit App Store or how-to guide link clicks. A store click is not proof of an install or purchase.

Google receives device and browser information, network request information, public page paths, an origin-only referring site and the permitted interaction events. Page URL query strings and fragments are excluded from our measurement settings. We do not send account identities, email addresses, private hunting records, map coordinates or form entries. Advertising storage, advertising personalization and Google signals are disabled by this integration.

When enabled, host-scoped _ga and _ga_9BCRMPSC00 cookies distinguish browser visits and sessions for up to 90 days without extending that expiry on each visit. Browser settings can shorten that period. venatriq-website-analytics-v1 stores your yes/no choice and its date in local storage for up to 180 days, including when you decline. This preference does not identify your account or enable marketing emails.

Use Analytics settings in the public website footer to turn analytics off or on. Turning it off disables future measurement by this integration and removes its host-scoped cookies; it does not undo data already sent to Google. Clearing website storage also clears the preference, so the website asks again. Google explains its processing in its Privacy Policy. Private app controls and first-party guide counts remain separate.

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.

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