Terms of Service

1.The short version

• You buy credits. $1 buys 10 credits. [for counsel review]
• Every task is priced in credits before it starts. Its credits are held when it's dispatched and charged only when its code is merged. [for counsel review]
• You don't pay for work you don't merge, or for tasks that fail. [for counsel review]
• Credits never expire. They're non-refundable and are never exchanged for money. [for counsel review]
• Your code stays yours, and so does the code we write for you.
• Use Code Legion in good faith. If an account is used to take work without paying for it, we'll close it.

The rest of this page is the full agreement. It's written to be read.

2.Who we are

These terms are an agreement between you and Woden, Inc., a Nevada corporation ("Wōden," "we," "us"). They cover Code Legion and every other service we offer at woden.ai (the "Service"). By creating an account or using the Service, you agree to them. If you use the Service for a company, you agree on its behalf and confirm you have the authority to do so.

3.Your account

You must be at least 18 and give us accurate information. You're responsible for everything done under your account and for keeping your password safe. Tell us right away if you think someone else has access.

4.Credits

• Prepaid. Credits are bought in advance, in US dollars, through our secure payment provider. $1 buys 10 credits. [for counsel review]
• Never expire. Credits never expire. Unused credits stay on your account for as long as it's open. [for counsel review]
• Non-refundable. Credits are non-refundable and are never exchanged for money. [for counsel review]
• Not transferable. Credits belong to the account that bought them.
• Large purchases. Purchases over $10,000 can be paid by bank transfer, against an invoice. [for counsel review]

5.What you pay for

• Priced before it starts. Every task is sized and priced in credits before it starts. [for counsel review]
• Held, then charged on merge. Dispatching a task holds its credits. Held credits are charged only when the task's code is merged. [for counsel review]
• What "merged" means. A task's code is merged when the delivered code reaches your default branch by any route: merging its pull request, squashing, rebasing, cherry-picking, or committing the same code another way. We may compare code that reaches your default branch with pull requests we delivered, and charge for any that match. [for counsel review]
• Unmerged pull requests. If a pull request isn't merged within 14 days, its hold is released, nothing is charged, and the pull request is closed. [for counsel review]
• Failed tasks. Failed tasks are not charged. [for counsel review]
• Bigger than quoted. If a task needs a larger size, it pauses and asks for the extra credits, unless you've pre-approved increases within a limit. You can approve the extra credits, or accept the work as is at its original price. Work accepted as is is delivered as a pull request, and its held credits (the original quote) are charged only if that pull request merges; they're released if it isn't merged within 14 days. With no decision within 14 days, the work is delivered as is under the same rule. [for counsel review]
• Revoking access. If you revoke Code Legion's access to a repository while it has open pull requests from Code Legion, their held credits are charged. [for counsel review]

6.Fair use

Paying only for merged work depends on good faith. To protect it:

• A cap on unmerged work. Outstanding unmerged work is capped at the total credits you've bought. [for counsel review]
• Abuse. Accounts that abuse this model, for example by taking delivered code without merging it, may be warned, have credits deducted, or be suspended. Other examples: disputing legitimate charges, or running several accounts to get around limits. [for counsel review]

Tasks that fail because of a problem on our side never count against you.

If we close your account for misuse, unused credits are forfeited. [For counsel review: credits are never exchanged for money, so decide what happens to unused credits when we close an account for any other reason.]

7.Your code and our work

• Your code is yours. You give us permission to access the repositories you connect, only to do the work you ask for and to run the Service.
• Our work is yours. Code we produce for you belongs to you once you merge it.
• Training. [Decide: whether customer code may be used to improve our models. Recommended: "We don't use your code to train our models."]
• Your responsibility. You review work before merging it. You're responsible for what you ship.
• Your rights. Only connect code you have the right to share with us.

8.What you can't do

• Use the Service to build malware or to break the law.
• Try to access other customers' data, or probe, overload or reverse engineer the Service.
• Resell the Service without our written permission.

9.The usual protections

The Service and the code it produces are provided "as is." We work hard to make them good, but we don't promise they'll be error-free or right for every purpose. To the extent the law allows, we aren't liable for indirect or consequential losses, and our total liability to you is limited to what you paid us in the 12 months before the claim.

10.Ending things

You can close your account at any time. We can suspend or close accounts as described in section 6, or if required by law. Sections 4 through 9 survive after an account is closed.

11.Changes

We may update these terms. If a change matters, we'll tell you by email or in the product before it takes effect. Continuing to use the Service after that means you accept the new terms.

12.Law and disputes

These terms are governed by the laws of Nevada. Disputes go to the state or federal courts in Clark County, Nevada.

13.Contact

Questions about these terms: [contact email]