Terms of Service

Last updated: 23 October 2026

The short version

• >commit_ is in closed beta: we let projects and people in a few at a time.
• When it opens, >commit_ keeps a record of who agreed to what share of a project’s revenue and shows the numbers. The agreement is between you and your teammates. We are not a party to it.
• Unless we publish your app for you, we don’t move money. Paying each other is your team’s job.
• You keep the copyright in what you make. Your project gets a licence to use it. We claim no rights in your work.
• The basic split sheet is free. Connected revenue is free up to $2,500 a month per project, then 1% of revenue above that. If we publish your app, we keep 7% of what the stores pay out, fixed for that project.
• We are not your lawyer, accountant or bank. Get advice where it matters.

1. Who we are and what these terms cover

1.1. These terms are a contract between you and Commit Split, Inc., a Delaware corporation (“>commit_”, “we”, “us”). They cover the website at commit.cx and the >commit_ product, including the API and MCP access (together, the “Service”).

1.2. Our Privacy Policy explains how we handle personal data. Our Security page explains how we protect the record and your data. Both are part of how the Service works, but the Privacy Policy is not a contract term you are agreeing to.

1.3. By signing up, posting on the board or using the Service, you agree to these terms. If you use the Service for a company, you confirm you can bind it, and “you” means that company too.

2. Closed beta

2.1. We open the Service to projects and people a few at a time. Until your project has access, you can describe it, sign up, invite teammates and use the Find a team board, but nothing is signed, connected, charged or paid out for it.

2.2. Plans, prices and features may change during the beta. A change never alters a split version already signed, and never raises the 7% rate of a project already signed for We publish it (section 17).

3. Who can use >commit_

3.1. You must be at least 18 years old and able to enter a binding contract where you live. A split is a contract about money, so we do not allow minors to sign one.

3.2. You may not use the Service if you are barred from receiving services from us under the laws that apply to you or to us, including sanctions laws.

4. Your account

4.1. You sign in with your email address. We send a link or code there; there is no password. Keep access to your email account secure: whoever controls your inbox can sign in as you.

4.2. Give us an email address you control and keep it current. Use one account per person. Don’t share it, and don’t sign up for someone else without their permission.

4.3. Tell us at [email protected] if you think someone else has used your account.

5. Plans and fees

5.1. Split sheet (basic). Free. You enter revenue by hand.

5.2. Connected revenue. You connect Stripe, RevenueCat, App Store Connect or Google Play with read-only access, and >commit_ reads revenue from the source. Free while the project’s revenue is under $2,500 a month. Above that, the fee is 1% of the revenue above $2,500 for that month. We bill the fee monthly through Stripe, to a card on file. If an invoice stays unpaid for 30 days, we pause reading revenue from connected sources until it is paid; you can still enter revenue by hand. An unpaid fee never changes or deletes the record of your split.

5.3. We publish it. We publish the app under our developer account and pay the team by the split (section 10). Our fee is 7% of what the stores pay out, after the store’s own fee. There is no setup fee and no minimum, and we don’t recoup costs or advances. The 7% rate is fixed for that project once its split is signed, and we will never raise it for that project.

5.4. Prices exclude taxes unless we say otherwise. We may change prices for new projects with notice (section 17). A change never applies retroactively, and never changes the 7% rate of a project already signed for We publish it.

6. The split sheet and our role

6.1. What it is. A project’s split sheet records who joined, for what share, and how that share grows: contribution points, time and milestones, a trial period or cliff, and the rule that an inactive member’s points stop growing. Each change creates a new version. Members sign a version with a click in the app after signing in by email. That click is your electronic signature under the US ESIGN Act and the EU eIDAS Regulation, and you agree it binds you the same way a signature on paper would. Everyone who signs gets a receipt.

6.1a. Defaults. Unless the members agree otherwise in their split:

• a new member starts with a one-month trial;
• shares vest over 12 months;
• changes that need only a majority go ahead if the other members stay silent for 7 days after the change is proposed. We send them email reminders during those 7 days.

6.2. The agreement is between members. A signed split is an agreement between the members of the project. >commit_ is not a party to it. We keep the record, show the numbers and, where the data is connected, compute who is owed what under the rules the members signed.

6.3. The record. Each version is linked by its fingerprint (hash) to the one before, and the record is time-stamped daily by an outside service. Every signer gets a receipt with the version’s fingerprint; a PDF copy is available on request. No one, including us, can change a signed version without it showing. How this works is on our Security page.

6.4. Recorded, not enforced. Unless we publish the app for you (section 10), >commit_ does not collect or pay out money. The split sheet shows who is owed what; paying them is the team’s responsibility. We don’t guarantee that anyone will be paid.

6.5. Numbers come from your sources. Revenue is what you enter or what the connected source reports. We show it as received. We are not responsible for errors, delays or restatements by stores or providers, or for figures you enter yourself. If a source corrects its data, the numbers may change; signed versions of the split do not.

6.6. Disputes between members. Disputes about a split are between the members. You can export the project’s full history as one file at any time and use it however you like. If members can’t settle a dispute themselves, the team picks a mediator, and the mediator’s cost is split equally between the members in the dispute unless they agree otherwise. We may give a neutral copy of the record to the members, a mediator or a court, but we do not decide who is right.

6.7. Not advice. >commit_ is a tool, not a law firm, accountant, tax adviser or financial adviser. Default terms and presets are a starting point, not advice about your situation. A revenue share can have tax, employment, securities and other legal effects that depend on where you and your teammates live. Get your own advice where it matters.

7. Your content and your work

7.1. Content you give us. Project details, posts, profiles, messages and split data you add are “Your Content”. You keep all rights in it. You give us a worldwide, non-exclusive, royalty-free licence to host, copy, display and process Your Content only to run, secure and improve the Service, and to show it to the people you choose (for example, your teammates or, for board posts, the public). This licence ends when Your Content is deleted, except for copies we must keep by law, copies in backups until they expire, and signed split versions, which stay in the record (section 13.4).

7.2. Default terms for the work itself (members can agree different terms in their split):

• Each person keeps the copyright in what they make for the project.
• By signing the split, each member grants the project an exclusive, permanent, irrevocable licence to use their work in this product, its updates and its ports.
• A member who leaves can’t take their work out of the product, and keeps the share they earned up to the day they left.
• If the product is sold, the licence moves with it.
• If the team forms a company, members assign their rights in the work to that company.
• Members may show their work in a portfolio, with credit to the project.

7.3. We claim no rights in your work. Apart from the limited licence in 7.1 and, when we publish, the distribution licence in section 10, >commit_ gets no rights in your product or in anyone’s work.

7.4. Your promises. You confirm that you have the rights to the content and work you bring, and that using it as agreed won’t infringe anyone else’s rights.

8. Find a team board

8.1. Roles and profiles you post on the board are public, apart from your contact details. We never show your contact details in public feeds. A profile may include a nickname, skill, hours a week, number of projects shipped, a short pitch, tools and an optional portfolio link.

8.2. We store applications and contact details and may use them to put people in touch. We don’t forward them automatically.

8.3. Post only real roles and true facts about yourself. No ads, spam, recruiting for unpaid work presented as paid, or requests for money. We may edit the formatting of a post, hide it or remove it.

8.4. We don’t vet the people on the board. Agreements you make with them are between you and them.

9. Inviting people

When you invite someone by email, we send them one email on your behalf, with your email as the reply-to address. Only invite people you know who would expect to hear from you about the project. Don’t use invites for marketing or spam.

10. We publish it

10.1. What we do. If your team chooses this plan, we publish the app in the App Store and Google Play under >commit_’s own Apple and Google developer accounts, receive what the stores pay out, and pay the team by the signed split. In the stores, >commit_ is shown as the seller, and the team is credited in the app description.

10.2. Distribution licence. The team grants us a non-exclusive licence to distribute the app and its updates in the stores, and nothing more. This licence ends on the day the team takes the app back. We get no other rights in the app.

10.3. Our fee. 7% of what the stores pay out, after the store’s fee, as set out in 5.3. No setup fee, no minimum, no recoup, fixed for that project.

10.4. Payouts. We pay through Stripe Connect. The provider’s fee comes out of each payout and is shown to you before the payout. Team funds are held in an account kept separate from our own money. We pay within 5 business days after each store payout lands. Shares are calculated in the currency the store pays in. Each member is paid in their local currency at Stripe’s exchange rate, shown before each payout. We pay out to every country Stripe pays out to. To receive payouts, each member must set up a payout account with our payment provider and accept its terms.

10.5. Refunds and chargebacks. The stores take refunds and chargebacks out of their next payout, so they come off the next split. Nobody is asked to pay money back.

10.6. Taxes. Each member is responsible for their own taxes. We withhold only what the law requires us to, and collect the tax form our payment provider needs once per member.

10.7. Store rules. The app must meet Apple’s and Google’s rules. We may decline to publish an app, or remove it, if it breaks store rules or the law, or puts our developer accounts at risk. We will tell you why.

10.8. Taking the app back. The team can take the app back at any time, with no fee. We start the store transfer to the team’s own developer account within 14 days of the request. Everything already earned is paid out by the split.

10.9. If >commit_ shuts down. We will give at least 90 days’ notice. Every listing is moved to the team’s own developer accounts, and everything owed is paid out by the split. Team money sits in a separate account and is never mixed with ours.

11. Connected accounts and agents

11.1. Read-only access. When you connect Stripe, RevenueCat, App Store Connect or Google Play, we ask for read-only access and use it only to read revenue data for the project. You can disconnect at any time. You must have the right to connect the account and to share its revenue data with your teammates.

11.1a. Git repositories. A project can also connect its git repository (GitHub, GitLab or any git host) with read-only access. We read only commit authors and commit counts or dates, never store source code, and use them to mark a shipped title “checked” on a member’s profile when the title has a live store listing and the member’s work is in the project’s git history. Members who don’t commit, such as artists or sound designers, are checked when the project owner confirms them. The project owner must have the right to connect the repository and confirms only work they know to be real. You can revoke access at any time by deleting the token on the git host.

11.2. Third-party services. Connected services are run by other companies under their own terms. We are not responsible for them, and they may change or end their APIs.

11.3. API, MCP and agents. The split sheet can be read over an API and MCP. Access is read-only by default. Each agent gets its own key, which you can revoke at any time. An agent can propose a change to the split, but it can never sign. Every change drafted by an agent shows who asked for it. You are responsible for the agents and keys you create and for what they do with your access. Keep keys secret.

12. Acceptable use

12.1. Don’t use the Service to:

• break the law or help anyone else break it, including sanctions, tax and money-laundering laws;
• record a split you know is false, or add people to a project without their consent;
• impersonate anyone, or sign for someone else;
• post spam, malware, or content that is illegal, hateful, or infringes someone’s rights;
• probe, scan or attack the Service, bypass rate limits or access controls, or scrape it beyond what the API allows (good-faith security research under our Security page is welcome);
• resell the Service, or use it to build a competing product from our data.

12.2. We may remove content or suspend access that breaks these rules. Where we can, we will warn you first and tell you why.

13. Suspension, closing your account, and what stays

13.1. You can stop using the Service and ask us to close your account at any time by writing to [email protected].

13.2. We may suspend or close an account for a serious or repeated breach of these terms, if the law requires it, or if it puts other users or the Service at risk. We will give notice and a reason where we can.

13.3. If we stop offering the Service, we will give at least 90 days’ notice and let every member export their project’s full history.

13.4. Closing an account does not erase a signed split. Signed versions are part of an agreement other people rely on, so they stay in the record and stay available to the other members. Personal data we no longer need is handled as set out in our Privacy Policy.

13.5. Sections 6.2, 6.4 to 6.7, 7, 10.6, 13.4 and 14 to 18 survive the end of these terms.

14. Disclaimers

14.1. The Service is provided “as is” and “as available”. To the extent the law allows, we make no promises beyond those in these terms, including any implied promises of fitness for a particular purpose, accuracy or uninterrupted availability.

14.2. We don’t promise that a project will earn anything, that a teammate will do their part, or that any person will pay what they owe.

14.3. Nothing in these terms limits rights you have as a consumer that the law says can’t be limited.

15. Limitation of liability

15.1. To the extent the law allows, we are not liable for indirect or consequential loss, lost profits or revenue, lost data, or loss caused by your teammates, stores, payment providers or other third parties.

15.2. To the extent the law allows, our total liability to you for all claims about the Service is limited to the greater of the fees you paid us in the 12 months before the claim and US$100.

15.3. Nothing in these terms limits liability for fraud, for death or personal injury caused by negligence, or for anything else that can’t be limited by law. In the We publish it plan, this section does not limit our duty to pay out team funds we hold.

16. Indemnity

If someone makes a claim against us because of content you posted, work you contributed that you didn’t have the rights to, or your breach of these terms, you will cover our reasonable costs of that claim. This does not apply where the claim is caused by us.

17. Changes to these terms

17.1. We may update these terms as the product changes. For material changes we will email you at least 30 days before they take effect, except where a change is needed sooner by law or for security.

17.2. Changes never alter a split version that has already been signed, and never raise the 7% rate for a project already signed for We publish it.

17.3. If you don’t agree with a change, you can stop using the Service and close your account before it takes effect.

18. Governing law, disputes with us, and general terms

18.1. These terms are governed by the law of the State of Delaware, USA. Disputes with >commit_ go to the state or federal courts in Delaware, unless the law where you live as a consumer gives you the right to bring a claim there.

18.2. Before starting a formal claim, write to us at [email protected] and give us 30 days to try to fix it.

18.3. If part of these terms can’t be enforced, the rest still applies. If we don’t enforce a term right away, we can still enforce it later. You may not transfer these terms without our consent; we may transfer them to a company that takes over the Service, with notice to you. These terms, with any plan terms you accept in the app, are the whole agreement between you and us about the Service.

19. Contact

Questions about these terms: [email protected], or use our contact page. Security issues: [email protected].