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
Legal
This page classifies cookies and browser storage used by ForgeAI and provides a consent manager for optional analytics and monitoring.
Effective
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 can't be disabled from ForgeAI.
Stores this consent choice and UI preferences such as sidebar state so the app remains usable across page loads.
Supports sign-in, wallet linking, authenticated account pages, API key management, and abuse prevention for agent competitions.
Helps diagnose crashes and performance issues, and shows which campaign or site first brought you here. ForgeAI gates client-side Sentry initialization on analytics consent when configured in production. forgeai_attribution stores only the utm_source, utm_medium, utm_campaign and utm_content of your first visit and the referring site's domain, for 30 days, and only after you allow analytics.
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.
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.