Cookie Policy
Last updated: July 14, 2026
1. Summary
Forge does not set any HTTP cookies. We use only localStorage — a browser-managed key/value store that lives on your device and is never transmitted over the network. There is no GDPR consent banner because there is nothing to consent to.
2. localStorage Entries
The following keys may be written to your browser's localStorage when you use Forge:
| Key | Purpose | Required? |
|---|---|---|
| forge.apiKey | Your client-generated API key | No |
| forge.settings | Optional fallback provider key | No |
| forge.orchestrator.tools | Tools you authored in the playground | No |
| theme | Your light/dark theme preference | No |
3. No Tracking
Forge does not use Google Analytics, Mixpanel, Segment, Facebook Pixel, or any other third-party tracking SDK. There are no fingerprinting scripts, no A/B testing infrastructure, and no advertising integrations.
4. Clearing localStorage
You can clear all Forge-related data at any time by:
- Opening your browser's DevTools → Application → Local Storage → forge.ai → Delete
- Using "Clear browsing data" in your browser settings
- Running
localStorage.clear()in the console on forge.ai
After clearing, you will need to regenerate an API key in Settings. No historical data is lost because we never stored any.
5. Third-Party Resources
Forge loads fonts from Google Fonts and icons from Lucide. These resources may set their own cookies in transit; please refer to Google's privacy policy for details. No Forge functionality depends on these cookies.