Privacy Policy

Effective date: February 18, 2026.

This policy explains how KBBQ Idle handles gameplay data for the WebGL service. The default deployment is designed to keep data collection minimal and service-focused.

Data We Process

• Gameplay state: save progress, inventory, upgrades, and settings needed to continue your session.
• Operational telemetry: basic runtime events used for debugging service stability and balancing.
• Support artifacts: issue reports you submit through GitHub Issues.

Storage and Retention

• Primary save data is stored in browser local storage / persistent data path.
• When backend integrations are enabled, only required fields for account/session operations are transmitted.
• Local gameplay data remains until you clear browser storage or reset in-game data.

Third-Party Services

• Cloudflare Pages: static hosting and delivery.
• GitHub: source hosting and support issue tracking.
• Google Tag Manager, Google Analytics 4, and Microsoft Clarity (optional): only active when valid IDs and tags are configured.
• AdSense (optional): ad delivery only when valid publisher configuration is enabled.

Your Controls

• You can stop gameplay data updates by closing the page.
• You can clear local save data through browser storage controls.
• You can request operational support using GitHub Issues.