Browser data

Cookies where needed, browser storage where it makes the product work

Jungle Grid uses browser-side storage and analytics to keep sessions, preferences, onboarding flows, and page measurement working. This page explains what is stored and why.

Last updated: April 29, 2026Contact: legal@junglegrid.dev

Create account View docs

Cookies + web storage

Storage types

The current frontend uses local storage, session storage, and analytics-style tracking across product surfaces.

Auth + preferences

Primary reasons

Storage is used for sessions, theme choice, workflow continuity, onboarding, and measurement.

April 29, 2026

Updated

This page reflects the browser behavior present in the codebase today.

Policy details

Why Jungle Grid uses browser-side storage

Jungle Grid uses cookies and similar browser technologies to remember interface state, preserve signed-in browser sessions, measure page activity, and support signup or workload flows that would otherwise break if the browser refreshed or navigated away.

Some of this behavior uses local storage or session storage instead of classic cookies. We describe them together here because they serve related purposes from a user perspective.

Strictly functional storage

Certain storage is used to make the site or product function correctly. The current frontend stores signed-in session data in session storage, saves theme preference in local storage, and uses temporary workflow state for things like guest inference draft continuation and dismissed homepage UI state.

Without this category of storage, core experiences such as authentication continuity, theme persistence, or resume flows would be less reliable or would fail entirely.

Session storage for signed-in browser sessions.
Local storage for theme preference.
Local storage for guest inference resume state and certain landing-page UX memory.
Session storage for lock or continuation state tied to resume flows.

Analytics and page measurement

Jungle Grid uses analytics tooling to record page views and understand how visitors and users move through the site. In the current frontend, page-view telemetry is sent through PostHog.

Analytics helps us understand usage patterns, landing-page performance, navigation paths, and product adoption so we can improve the experience and detect issues.

Promotions and attribution

Signup and promotion flows can store promotional tokens or onboarding state that connects a visitor to a current offer, referral, or credit flow. These values help Jungle Grid honor the intended onboarding experience and connect the browser session to the correct account path.

Promotional behavior may change over time, and some temporary identifiers may expire automatically or stop working after use.

Managing browser storage

You can usually manage cookies and browser storage through your browser settings, including blocking or clearing stored values. Clearing storage can sign you out, reset preferences, remove saved draft state, or interrupt onboarding continuity.

If you disable storage that the site needs to function, some parts of Jungle Grid may no longer work as intended.

Changes and contact

We may update this page if the site adopts new measurement tools, new browser storage patterns, or new onboarding and product flows.

For questions about browser storage or tracking on Jungle Grid, contact legal@junglegrid.dev.

Related legal pages

Use the adjacent page when your question is narrower than the policy you started with.

Core policyPrivacy PolicyHow Jungle Grid collects, uses, and protects account and usage information.Core policyTerms of ServiceThe rules for using the Jungle Grid website, portal, CLI, and provider surfaces.Privacy rightsData RequestsHow to request access, correction, deletion, or other privacy help from Jungle Grid.TransparencyOperational DisclosuresThird-party services, public embeds, payments, analytics, email, and outbound integrations.