Legal
Privacy Policy
What we collect when you use Forjo, why we collect it, who helps us process it, and how to get it deleted.
Last updated 11 November 2026Effective [EFFECTIVE DATE]
On this page 16 sections
The short version
- We collect what we need to run Forjo, bill you and keep it safe.
- To build your app, we send your prompts and project files to AI providers. They process them to produce the agent’s answers.
- We do not sell your data, show ads, or use analytics or tracking cookies.
- We do not use your projects or prompts to train AI models.
- You can delete your account and projects at any time.
Who we are
Forjo is run by [COMPANY LEGAL NAME], [REGISTERED ADDRESS]. We decide how your personal data is used for the service, which makes us its “controller” under data protection laws such as the GDPR. Contact us at [email protected].
What we collect
Account details
Your name, email address and password (stored only as a secure hash). If you sign in with or connect GitHub or Figma, your username or account ID there and an access token. Your workspaces, their members and roles, and invitations you send or receive.
Your projects and prompts
Everything in your projects: files, code and git history; what you ask the agent and what it replies; screenshots and documents you attach; settings and secrets you store for an app; published builds; and the custom domains you connect.
Usage and cost records
Each agent run: when it happened, which model it used, how much AI usage it took, what that cost and how many credits it used. Also how much container time and storage your projects use, and when you publish.
Billing details
Your plan, invoices and payment status. Card details go straight to [PAYMENT PROVIDER]; we never see your full card number.
Device and security data
IP address, browser and device type, and sign-in times, so you can see and sign out your devices and so we can spot misuse. Our servers also keep short technical logs and error reports.
Messages to us
What you send to support or the abuse address, including any report you make about someone else’s app.
Visitors to published apps
When someone visits an app you publish, our hosting keeps standard request logs, such as their IP address and the page they asked for. Anything else the app collects is up to you; see your app’s users.
Why we use it
- To provide the service: run the agent, your containers and your published apps. (Needed for our contract with you.)
- To bill you and keep the records tax law requires. (Contract and legal obligation.)
- To keep Forjo safe: prevent fraud, abuse of free credits and attacks, and enforce our Acceptable Use Policy. (Our legitimate interest in a secure service.)
- To support you when you contact us. (Contract and legitimate interest.)
- To send account email: sign-in links, password resets, invitations, billing notices and changes to our terms. We do not send marketing email unless you opt in, and you can opt out at any time.
- To fix and improve Forjo, using error reports and totals such as how many runs fail. (Legitimate interest.)
- To meet the law, for example when a court or authority lawfully asks us for information.
We do not sell your personal data or share it for advertising.
What we send to AI providers
The agent works by sending context to an AI model: your request, the parts of your project it needs to read, the output of commands it runs, and any images or documents you attach. Which provider gets it depends on the model you use (see the list below).
We use these providers’ business services, under terms that let them use your data only to provide the service to us, and not to train their models. They may keep it for a short time for safety and abuse checks, as their own policies describe.
Do not paste passwords, API keys or other secrets into prompts. Store them as app secrets instead. The agent may still read secrets in files you ask it to work on.
Who processes data for us
We use these companies (“sub-processors”) to run Forjo. Each one only gets the data it needs for its job.
| Provider | What for | What data |
|---|---|---|
| Anthropic | Runs the Claude AI models that power the agent. | Prompts, the project files and command output the agent needs, screenshots and documents you attach. |
| OpenRouter | Routes requests to other AI models when you choose one. | The same as above, for runs on those models. |
| Model providers behind OpenRouter | The company that runs the model you picked, such as the maker of that model or a hosting partner. | The same as above, for runs on that model only. |
| Fly.io | Hosts Forjo: the app, the database, project containers and published apps. | Everything stored in Forjo, including account details and project files. |
| Cloudflare | Network, security and certificates for published apps and custom domains. | Domain names, IP addresses and the traffic to published apps. |
| Resend | Sends account email, such as sign-in, password reset and invitations. | Your email address, name and the message. |
| GitHub | Only if you connect it: sign-in, importing repositories and pushing code. | Your GitHub username and access token, and the repositories you push or import. |
| Figma | Only if you connect it: importing designs. | Your Figma account ID and access token, and the files you choose to import. |
| [PAYMENT PROVIDER] | Takes payments and manages subscriptions and invoices. | Name, email, billing address, payment details (collected by them directly) and purchase history. |
| [ERROR TRACKER] | Records errors so we can fix them. | Technical details of the error, browser type, IP address and your user ID. |
We will update this list before we add a new sub-processor. Paid customers who need notice of changes can ask at [email protected]. We may also share data if the law requires it, to protect people’s safety, or with a buyer if Forjo is sold, who must then follow this policy.
International transfers
Our providers run servers in several countries, including the United States, so your data may be processed outside the country where you live. Where the law requires it, we rely on approved safeguards for these transfers, such as the European Commission’s Standard Contractual Clauses.
How long we keep it
| Data | How long |
|---|---|
| Account details and projects | While your account is open. Deleted when you delete them or your account. |
| Backups | Overwritten on a rolling basis, within 30 days of deletion. |
| Billing and usage records | As long as tax and accounting law requires, usually up to 7 years. |
| Server logs and error reports | Up to 90 days. |
| Support and abuse messages | Up to 2 years after the matter is closed. |
| Records of accounts closed for abuse | As long as needed to stop the same person signing up again, up to 3 years. |
| Data held by AI providers | As set out in each provider’s own policy, usually 30 days or less. |
Deleting your data
You can delete any project, or your whole account, in Settings. Deleting your account removes your projects, their containers, published apps and their domains, workspaces you own and your user record. If a workspace you own still has other members, remove them or hand it over first.
Code you pushed to your own GitHub account stays there; delete it on GitHub if you want it gone. If you cannot delete something yourself, email [email protected] and we will do it.
Your rights
Depending on where you live, you have the right to:
- get a copy of the personal data we hold about you;
- correct data that is wrong;
- delete your data;
- take your data with you (your code is always a git repository you can push to GitHub);
- object to, or ask us to limit, some uses of your data;
- withdraw consent you gave us, at any time; and
- complain to your local data protection authority.
To use any of these rights, email [email protected] from the address on your account. We will reply within 30 days, and may ask you to confirm who you are. We will not treat you differently for using your rights. We do not sell or share personal data as California law defines those terms.
Security
We protect your data with encrypted connections, hashed passwords, a separate container for every project, short-lived tokens limited to one branch for code pushes, and a list of signed-in devices you can sign out. No system is perfectly secure. If a breach affects your data, we will tell you and the authorities as the law requires.
Your app’s users
If an app you publish collects personal data from its users, you decide how that data is used, so you are its controller and we process it only on your behalf. You need your own privacy notice for your app. If you need a data processing agreement with us, email [email protected].
Children
Forjo is not meant for anyone under 18, and we do not knowingly collect their data. If you think a child has given us personal data, email [email protected] and we will delete it.
Changes to this policy
We will update this page when our practices change and change the date at the top. If a change matters, we will email you or show a notice in the app before it takes effect.
Contact
Privacy questions and requests: [email protected]. By post: [COMPANY LEGAL NAME], [REGISTERED ADDRESS].