Copied tegeljb@gmail.com to clipboard

Privacy Policy

Last updated: 2026-08-08

Draft — written to accurately describe our real data flow, not reviewed by a lawyer yet. Needs a real GDPR compliance pass before public launch.

What we collect

DataWhyWhere it lives
Email addressLogin (from your GitHub account), waitlistSupabase (EU-hosted)
Forum posts / commentsCommunity featuresSupabase
Feature votesPrioritizing what we buildSupabase

What we don't collect

Crash reports

If Forge crashes with an unhandled error, it automatically sends a crash report so we can fix the bug. The report contains: a random crash ID, the app name and version, your OS and Python version, and the error traceback with file paths and your Windows username stripped out before sending. It does not contain your code, prompts, or file contents — only the error itself and where in Forge's own code it happened.

This report goes to Sentry.io (a third-party error-tracking service) and, when reachable, to our own Main Engine server. There is currently no in-app toggle to opt out of this — if that matters to you, email tegeljb@gmail.com and we'll add one or tell you how to disable it manually in the meantime.

Optional diagnostic telemetry

During setup, Forge shows a separate, unchecked-by-default checkbox: "Send anonymous diagnostic data (errors, not personal data)." If you turn it on, Forge occasionally sends us error/warning events (e.g. "an AI call failed") — file paths and your Windows username are stripped out first. This only goes to our own Main Engine, never a third party, and only while it's reachable; if you leave it unchecked, nothing on this channel is ever sent.

Cloud AI providers

If you add your own API key for a cloud provider (Claude, GPT, etc.) inside Forge, requests you send through that provider are subject to that provider's own privacy policy, not this one. Your API key stays encrypted on your local machine.

Your rights

You can ask us to delete your account and associated data at any time by emailing tegeljb@gmail.com.

Cookies and analytics

We use a minimal cookie/local-storage setup for login sessions and to remember your cookie-notice choice. See the cookie banner for details.

If you accept the cookie banner, we load PostHog (hosted in the EU, Frankfurt) to see aggregate usage of this website — which pages get visited, roughly how people move through the site. This only loads after you click Accept; if you don't, no analytics script runs. We don't use it to build cross-site ad profiles or sell the data.

Contact

Questions: tegeljb@gmail.com