Cookie Policy

Overview

This Cookie Policy explains how Jumbly uses cookies, localStorage, browser storage, PWA caching, analytics identifiers, and similar technologies. During closed beta, many features work without accounts or external services and may be saved on this device.

Essential Cookies

• Strictly necessary cookies or similar storage may be used to keep Jumbly running, save gameplay progress, enforce replay prevention, remember preferences, protect sessions, support PWA behavior, and keep security controls working.
• If optional accounts are enabled, authentication cookies or provider-managed session storage may be necessary to keep you signed in.
• Blocking essential cookies or site storage may make account features, preferences, progress, sharing, or installed-app behavior less reliable.

localStorage Usage

• Jumbly uses localStorage to remember streaks, stats, last played dates, onboarding state, app settings, feature flags, anonymous session ids, puzzle feedback, and unfinished game state.
• Game-specific storage may include guesses, attempts, selected tiles, solved groups, rotations, timers, hints, result states, and share status.
• Storage saved on this device keeps Jumbly playable without an account.
• Clearing site data, using private browsing, switching browsers, or uninstalling the PWA may remove saved progress.

Analytics Cookies

• Jumbly may use analytics cookies or similar identifiers only after analytics consent to understand puzzle quality, retention, reliability, performance, and which features feel useful.
• Analytics events may include game id, puzzle id, puzzle number, attempt count, result, difficulty, anonymous session id, device type, route, and timestamp.
• Analytics is controlled by cookie preferences. If you reject non-essential storage, analytics events should not be sent by the client.
• If analytics services are not enabled or consent is not granted, Jumbly uses device-saved fallback behavior instead of sending analytics to a provider.
• Analytics providers may include PostHog or another privacy-appropriate provider when configured.

Optional Auth Cookies

• Optional accounts are not required for core gameplay.
• If account features are enabled, Jumbly or its auth provider may use cookies or similar storage to keep you signed in and protect sessions.
• Session cookies may support account sync, saved stats, streak recovery, subscription state, fraud prevention, and security when account services are enabled.
• Signing out, clearing cookies, or blocking cookies may affect account features.

PWA Caching

• If you install Jumbly as a Progressive Web App, your browser or operating system may cache app shell files, icons, route data, and offline fallback assets.
• PWA caching helps Jumbly open faster and keeps previously loaded routes available where possible.
• The PWA may also use browser storage for gameplay progress, settings, streaks, and install prompt state.
• Removing the installed app or clearing site data may remove cached files and saved progress.

Browser Storage

• Browser storage may include cookies, localStorage, sessionStorage, IndexedDB, Cache Storage, and service worker caches.
• Session storage may be used for temporary UI state or one-session flows.
• IndexedDB or Cache Storage may be used by the browser or service worker to improve speed and offline resilience.
• Your browser controls how long storage remains and may remove it based on device, privacy, or storage settings.

Share Functionality

• Jumbly share buttons may use browser APIs such as the Web Share API or clipboard access.
• Share features may remember whether a result was copied or shared, and may store compact result text, challenge codes, puzzle ids, timestamps, or game result metadata locally.
• When you share to another app or platform, that platform's cookies, storage, and privacy practices apply.
• If native sharing is unavailable, Jumbly falls back to copy-to-clipboard where supported.

Challenge and Session Persistence

• Challenge systems may store challenge codes, local game state, result comparisons, rematch references, streak status, and timestamps in browser storage.
• Anonymous sessions may use browser storage to keep gameplay and feedback functional without accounts.
• Future database-backed challenges may sync some of this data to a backend when configured, while keeping local fallback behavior available.

Optional Future Cookies

• Future subscriptions may use cookies or similar storage to support checkout, billing portal access, subscription status, fraud prevention, and payment processor flows.
• Future challenge, multiplayer, or social systems may use cookies or identifiers to prevent abuse, compare results, or maintain lightweight sessions.
• Future advertising is not active by default. If advertising, marketing pixels, or cross-site tracking are introduced, they should load only after marketing/ads consent and through feature flags.

Your Controls

• Jumbly shows a calm cookie banner on first visit with Accept all, Reject non-essential, and Manage choices options.
• You can update analytics and marketing/ads choices later from /privacy/controls.
• You can clear cookies and site data through your browser or device settings.
• You can uninstall the PWA to remove installed-app storage controlled by your browser or operating system.
• You can use private browsing, though it may reduce persistence and cause streaks, puzzle state, stats, or onboarding choices to disappear.
• You can block cookies in your browser, though account, analytics, subscription, and share features may work less smoothly.

Retention

Local and browser storage can remain until you clear it, uninstall the PWA, or your browser removes it. Analytics retention depends on provider settings. Account, subscription, support, and challenge retention will be finalized before those systems are fully launched.

Updates

We will update this policy as Jumbly adds production analytics, optional accounts, subscriptions, challenge systems, new providers, consent tools, or additional storage technologies.