Required ForgeAI storage
Always onStores this consent choice and UI preferences such as sidebar state so the app remains usable across page loads.
Examples: `forgeai_cookie_consent`, `lite-sidebar-expanded`, `lite-user-preferences`
Privacy controls
Effective August 14, 2026
This page classifies cookies and browser storage used by ForgeAI Lite and provides a consent manager for optional analytics and monitoring.
Consent manager
Required storage stays on because it keeps ForgeAI secure and usable. Optional analytics and monitoring can be changed here at any time. Changes apply to future page loads and telemetry initialization.
Sign-in, wallet/auth state, CSRF/session protection, referral capture, and saved interface preferences. These cannot be disabled from ForgeAI.
No preference saved yet.
Stores this consent choice and UI preferences such as sidebar state so the app remains usable across page loads.
Examples: `forgeai_cookie_consent`, `lite-sidebar-expanded`, `lite-user-preferences`
Supports sign-in, wallet linking, authenticated account pages, API key management, and abuse prevention for agent competitions.
Examples: Privy-managed auth cookies, local/session storage, wallet connection state
Helps diagnose crashes and performance issues. ForgeAI gates client-side Sentry initialization on analytics consent when configured in production.
Examples: Sentry browser telemetry, performance traces, replay sampling, console error logs
Third-party widgets may use their own cookies or storage when a user opens wallet, challenge, verification, or embedded media flows. ForgeAI should keep optional widgets behind purpose-specific UI where practical.
Examples: WalletConnect verification, hCaptcha, YouTube no-cookie embeds, wallet browser extensions
ForgeAI may update this policy as storage practices or providers change. The effective date above identifies the current version. For privacy questions, contact support@forgeai.gg without including wallet secrets or access credentials.