Owner keeps everything

Capacity contribution agreement — owner keeps everything

1. Parties

This agreement is between {{ownerName}} (the "Owner") and {{contributorName}} (the "Contributor"), covering one project: {{projectTitle}}. It takes effect on {{effectiveDate}}.

2. What is being contributed

The Contributor commits {{ccuCommitted}} CCU of Claude Code capacity to the project. One CCU equals one percent of a Claude Pro weekly Claude Code allowance, so the number describes a slice of usage capacity, not a dollar figure or a promised outcome. Alongside that capacity comes the Contributor's actual time and labour: writing code, running sessions, reviewing output, and doing whatever the work requires. What counts as delivered is what the platform's ledger records as spent against this project, not whether any particular feature ships or works.

3. Ownership of the work produced

The Owner keeps everything. All code, designs, documentation, and any other output produced using the Contributor's committed capacity belong entirely to the Owner, from the moment they're created. The Contributor ends up with no stake, no equity, no royalty, and no claim on the project or its future value. This template exists for people who want to give capacity away outright. If that's not what the Contributor wants, they should sign a different template instead of this one.

4. Intellectual property

The Contributor assigns the Owner all right, title, and interest in anything they create for {{projectTitle}} using the committed capacity — code, prompts, configuration, documentation, and any AI-generated output that comes out of their sessions. This is a present assignment, effective as work is produced, not a promise to assign later. Where local law won't let moral rights be assigned, the Contributor waives them to the extent waiver is legally possible. If for any reason the assignment doesn't take effect in some jurisdiction, the Contributor instead grants the Owner an exclusive, worldwide, perpetual, royalty-free licence to use, modify, and distribute the work, with the right to sublicense it.

Each side keeps ownership of whatever they already had before this agreement — prior code, tools, or material either party brings to the project stays theirs. Bringing something pre-existing into the project gives the Owner a licence to use it as part of {{projectTitle}}, but doesn't transfer ownership of it.

5. Credit and attribution

Credit follows {{creditPreference}} — the option the Contributor chose when they agreed to contribute: public credit, private thanks only, or no credit. The Owner must honour whichever the Contributor selected. Unless the Contributor chose no credit, they may still say, in general terms, that they contributed Claude Code capacity to {{projectTitle}}, even without a specific public credit line.

6. Confidentiality

Both sides may see things that aren't public: private repository contents, credentials, unreleased plans, or internal discussion about the project. Neither side may share that information outside the working relationship, except for material that's already public or that they already knew independently before this agreement. Subject to clause 5, the Contributor may not describe the project's private details, even after this agreement ends.

7. No warranty

Everything here is provided as-is. Claude Code output can be wrong, incomplete, or insecure, and neither party guarantees that anything produced works correctly, is fit for any purpose, or doesn't infringe someone else's rights. Neither party is liable to the other for indirect, incidental, or consequential losses arising from this agreement or the work done under it.

8. Not a partnership, not employment

The Owner and Contributor are independent parties. Nothing here creates a partnership, joint venture, agency, or employment relationship between them, and neither can bind the other to anything. Each is responsible for their own taxes on anything they receive or earn. UseMyTokens is the platform that hosted this agreement; it is not a party to it and has no obligation to enforce it.

9. Termination

Either party can end this agreement with seven days' written notice, or immediately if both agree. Capacity already spent is not refundable in either direction. The assignment in clause 4 survives termination for any work already produced — the Owner keeps it regardless of how or when the relationship ends. Clauses 4, 6, 7, and 8 survive termination.

10. Governing law

This agreement is governed by the laws of {{governingLaw}}. Before either side takes a dispute anywhere else, they agree to try to resolve it directly between themselves first.

11. Signing

Both parties sign electronically through UseMyTokens by typing their full legal name. The platform stores a SHA-256 hash of this exact agreement text alongside each signature, so either party can later prove exactly what they agreed to.

---

Not legal advice. UseMyTokens produced this document from a template. It is a starting point written to be read, not a substitute for a lawyer. Nobody here has reviewed it against your situation, your jurisdiction or your project. If real money, employment, an existing NDA or someone else's intellectual property is involved, get it looked at before you sign.