Forge developer terms

Who these terms are for#

These terms apply when you write, save, run or publish code on Forge. They add to Oathra's Terms of Service, which still apply. Where the two differ about code on Forge, these terms decide.

Your code stays yours#

You keep every right in your code. Forge gets only what the content licence says. Oathra will not trade, publish or sell your strategies, or use them to build its own.

What you may not do#

• Do not reverse engineer, decompile or probe Forge, its engine or another person's protected script.
• Do not build licence keys, activation checks or anything else inside a script that limits who may run it.
• Do not collect, store or send personal data about the people who run your script.
• Follow the acceptable use policy.

Code you did not write#

When what you publish includes someone else's code, data or other work, make sure its licence lets you publish it here, keep its notices, and credit it. If someone makes a claim about it, you answer for it.

Publishing#

Publishing has its own rules, listed in the rules. Each time you publish, you accept the version of these terms that the publish step shows. The checks and rules are on the publishing rules, the licences and the performance claims pages.

When Oathra removes or limits content#

Oathra may hide, restrict or remove code or a listing that it reasonably believes breaks these terms, the rules or the law. When it does, it tells the author which rule applied, the facts it relied on and how to appeal, unless the law forbids telling. How a decision is made and appealed is on the moderation and appeals page.

Changes to these terms#

A change that matters is posted on the change log at least 14 days before it takes effect. The next time you publish, you are asked to accept the new version.

Ending#

You can stop using Forge at any time. Deleting your account and what happens to your work are on the data and deletion page.