Privacy
Last updated 9 September 2026
The short version. FORGE runs on your computer. Your conversations, your files, your prompts and your models never reach us, because there is nowhere for them to go — the app has no analytics, no telemetry and no crash reporting. The only personal data we hold at all is an email address, and only if you choose to link an account for optional hosted features.
What stays on your machine
All of it. Specifically:
- Every chat and every message, stored as files in FORGE's data folder
- Every file the agent reads or writes, and every command it runs
- Your settings, prompts, permissions and API keys for other services
- Models you download and images or video ForgeWorks generates
None of that is transmitted anywhere by FORGE. If you point FORGE at a third-party model provider — OpenAI, Anthropic, or any other endpoint you add yourself — then your prompts go to them, under their privacy policy, because you asked FORGE to send them. FORGE is the pipe, not the destination.
What we collect, and why
If you never link an account: nothing. Chat, models, the runtime, tools, research, ForgeWorks and the local API all work without an account and send us nothing.
If you choose to link an account through the provider shown on the account page, we receive and store:
- your email address — it identifies your account
- your display name and the provider's account identifier
- the date you signed up and the dates of sign-ins
We ask the provider for no other permissions. We cannot read mail, contacts, files or anything beyond the identity fields above.
What the app talks to
FORGE makes network requests only to do things you asked for:
- GitHub — to check for FORGE updates and download llama.cpp builds; if you connect GitHub in the workstation, it also lists repositories you ask to see and transfers only the repositories you explicitly clone or pull
- Hugging Face, ModelScope, hf-mirror, Ollama's library — when you search for or download a model
- forge.shadow-lancer.com — the update manifest, and account checks if you are signed in
- DuckDuckGo and whatever page you asked for — only when the agent uses web search or fetch, which ask permission first
None of these carry your conversations. An update check sends a version number; a model download asks for a file. A GitHub token used by the workstation is stored locally and is sent only to GitHub for the repository operation you requested.
Cookies
This website sets exactly one cookie, and only after you sign in: a session token so the site knows it is still you. There is no advertising, no tracking and no third-party analytics on any page here.
Keeping it, and deleting it
Account records are kept while the account exists. Ask us to delete it and the account row and everything attached to it is removed — there is no backup archive of user data to forget about, because we do not keep one.
Your own data needs no request: it is files on your disk. Delete FORGE's data folder and it is gone, including anything we could never see anyway.
Children
FORGE is not directed at children and we do not knowingly hold data from anyone under 13.
Changes
If this policy changes in a way that affects what we collect, the date at the top changes and the release notes will say so. We are not going to quietly start collecting more.
Asking us anything
Questions, deletion requests, or a complaint: kevinklubeck@gmail.com.