ForgeOSby Medina19
Sign in Create account

Draft

Terms of service

This is a working draft. It is not an agreement.

No lawyer has reviewed this document. Nobody has accepted it, it binds nobody, and using ForgeOS today does not put you under it. Where commercial terms are agreed in writing with us, that written arrangement is what governs — not this page.

It is published so the shape of the eventual agreement is visible before anyone is asked to sign anything.

Drafted 15 August 2026. Not in force until reviewed terms replace this page and say so on their face.

The short version: you own your software, you decide what ForgeOS is allowed to do, and we do not claim the output is correct without review.

1. What is on offer today

You can create a workspace by signing in with an account you already have. There is still no published price, no payment collection and no subscription, so nothing you do here today is a purchase.

Because none of that exists yet, this draft says nothing about fees, renewal, auto-renewal, refunds or taxes. Those clauses will be written when there is a real commercial offer to attach them to, and pricing explains what we have already committed to about them.

2. Your software stays yours

You own your code

Your repositories, and the changes ForgeOS produces in them, are yours. We claim no ownership of either.

You own the output

Code, tests, documentation and artifacts produced for your goals belong to you.

We own ForgeOS

The product itself, and anything we build that is not specific to your repositories, remains ours.

Licence to operate

You grant us only what is needed to run the work you asked for — read, change and store your content for that purpose.

3. Authority, and what we will not do without it

ForgeOS acts only inside authority you have granted. Reading a repository is not permission to write to it; writing is not permission to deploy; none of it is permission to touch customer data or spend money. Each is a separate grant you make and can withdraw, visible in Trust & control.

We intend to be bound by that in the agreement, not merely by the software: we will not take a consequential action on your systems without the corresponding grant.

4. What we would ask of you

5. What we do not promise

This section matters more than the rest, so it is written plainly rather than in capitals.

Not that the software is correct

Generated software can be wrong. Review exists because of that. ForgeOS tells you what was verified and by what — never that the result is correct.

No availability commitment

There is no SLA, no uptime figure and no credit scheme, because none has been measured over a meaningful period.

No compliance certification

We do not certify your compliance with any standard and hold no audit report.

No guarantee of a given outcome

A goal may fail. When it does, ForgeOS stops and tells you rather than retrying quietly.

Left deliberately blank for the lawyer. Limitation of liability, indemnities, governing law, jurisdiction and dispute resolution are not drafted here. Numbers and jurisdictions invented by the software would look authoritative and be worthless, which is worse than their absence.

6. Ending it

You can stop at any time

Withdraw our access, and ForgeOS stops. Revoking a grant halts future work that depended on it rather than silently downgrading.

You can take your work with you

Your goals, work records and evidence are exportable. Your code was always in your own repositories.

We would give notice

If we end your access other than for a serious breach, we intend to give reasonable notice and time to export.

Deletion

On request we delete your content, subject to the audit-integrity and backup limits described in the privacy draft.

7. Changes

When reviewed terms replace this draft they will carry a date and say plainly that they are in force. We intend to give notice of material changes before they take effect, and never to make a change retroactive.

Reviewing this?

If something here is wrong, missing or would not survive scrutiny, we would rather hear it now than after somebody has relied on it.