Privacy Policy
Effective date: November 6, 2026
This Privacy Policy explains how Irongold Inc. ("Irongold", "we", "us") uses information when you use War Factory (app.usewarfactory.com, usewarfactory.com, the MCP connector and sites on warfactory.app, together the "Service"), what we collect, who we share it with, how long we keep it, and how to have it deleted.
The Service is not offered to people in the European Union, and we do not knowingly collect information from them.
How we use it
- To run the Service: sign you in, run your threads and sandboxes, push to GitHub when you ask, serve your published sites, and show you your usage.
- To keep it safe: approve accounts, enforce usage limits, stop abuse of sign-in and publishing, review reported sites and take down sites that break the Acceptable Use Policy.
- To fix and improve it: find errors, understand which features are used, and measure sandbox reliability.
- To contact you about your account, sign-in and changes to these policies.
- To meet legal obligations and enforce our Terms of Service.
We do not sell your personal information, share it for cross-context behavioural advertising, or use your content to train machine-learning models. The model providers that run your threads handle your prompts under their own terms for your account.
What we collect
Account. Your email address, the name you give us if any, your access status (pending, approved or suspended), whether you are an admin, and the usage limits set for you.
Sign-in. Sign-in codes and links (hashed, single use, expiring after minutes), passkey public keys (we never get the private key), and sessions. Each session records the IP address and browser user agent it started from. To stop abuse of sign-in email, we also count recent requests per email address and per IP address.
Your work. Projects, threads, messages, prompts, the agent's replies and tool calls, files, diffs, sandbox contents and snapshots of a thread's working files, skills you save, and mode presets.
Connected accounts.
- Model accounts: the sign-in tokens the provider issues when you connect, and the account email or id the provider reports. We use them only to run your threads.
- GitHub: your GitHub user id, login and name, and which GitHub App installations you can reach. We use GitHub's sign-in once to learn these and do not keep your personal GitHub token. Repository access runs through our GitHub App's own installation tokens.
Usage. For each turn: the model used, token counts and an estimated cost, and sandbox time. Admins can see this per person.
Published sites. The files you publish, the site address, who it is open to, and when it was published or taken down.
Reports. When anyone reports a published site: the category, the details they give, the contact email they choose to give, and a salted one-way hash of their IP address that we use only to limit how many reports one address can send.
Access requests. When you ask for access on usewarfactory.com: what you type in the form.
Product and error data. We record a small set of product events (signed up, signed in, model connected, thread started, thread shipped, site published, sandbox failed), keyed to your account id and never to your email. We record errors and performance traces from the app and the server, with personal data scrubbed before they leave. Our hosting provider keeps request logs.
In your browser. A session cookie that keeps you signed in, and local storage for your theme, unsent drafts and whether you dismissed the setup panel. We don't use advertising or cross-site tracking cookies.
Who we share it with
We share information only as needed to run the Service:
- Service providers that host the Service, run sandboxes, send email, and monitor errors and product use for us. They may use it only to provide their service to us, and receive only what their job needs.
- The model provider you connect. Your prompts, files and tool output in a thread are sent to the provider of the model that runs it, under your own account and that provider's terms.
- GitHub, when you ask War Factory to push branches or open pull requests to repositories you linked.
- People you choose, when you publish a site: whoever you let open it.
Some of this processing happens in the United States and other countries.
We may also disclose information if the law requires it, to protect the rights, safety or property of our users, the public or us, or as part of a merger, acquisition or sale of assets, in which case this policy continues to apply to it.
How long we keep it
- Sessions end after 7 days of inactivity, and always 30 days after sign-in.
- Sign-in codes and links expire within minutes. Sign-in email counters are pruned regularly once their window has passed.
- Sandboxes pause when idle. A paused sandbox is deleted when it's no longer needed.
- Threads, projects and usage records are kept until you delete them, ask us to delete your account, or we end the Service.
- Published sites stay up until you unpublish them, we take them down, or your account is deleted.
- Site reports are kept while needed to handle them and to spot repeated abuse.
- Error reports and product events are kept for 1 year.
- Backups: the database keeps point-in-time recovery for up to 30 days, so deleted data can remain there that long.
Deleting your data
You can delete some data yourself:
- Delete a project in its settings. This removes its threads' records from War Factory, not the GitHub repository.
- Disconnect a model account in Settings > Accounts.
- Disconnect GitHub in Settings > GitHub, and remove the War Factory app from your GitHub account or organization in GitHub.
- Unpublish a site from the thread's Publish dialog, or in Settings > Published sites.
- Remove passkeys in Settings > Passkeys.
To delete your whole account, email success@usewarfactory.com from the address you sign in with. We will confirm the request, then within 30 days delete your account, sessions, passkeys, connected model accounts, GitHub links, projects, threads, sandboxes and published sites, except for records we must keep by law, records about abuse, and data in backups until it expires. Pull requests already pushed to GitHub stay on GitHub. Your account id may remain in aggregated product and usage figures that no longer identify you.
Your rights
Depending on where you live, you may have the right to know what personal information we hold about you, get a copy of it, correct it, delete it, object to or restrict some uses, and withdraw consent. Email success@usewarfactory.com to make a request. We will verify it comes from you and answer within the time the law requires. We will not treat you differently for using these rights.
Security
We use encryption in transit, single-use and expiring sign-in codes, passkeys, isolated sandboxes, and access limited to the people and systems that need it. No service is perfectly secure; tell us at success@usewarfactory.com if you find a problem.
Children
The Service is not for anyone under 18, and we do not knowingly collect their information.
Published sites you visit
Sites on warfactory.app are written by War Factory users, not by us. Their owners decide what those sites collect. We serve them and, for every request, keep the same request logs as for the rest of the Service.
Changes
We will post changes to this policy here with a new effective date, and tell you in the app or by email before material changes take effect.
Contact
Irongold Inc. Privacy questions and requests: success@usewarfactory.com.