What you're agreeing to, and what we can touch.

The straight version of the legal and money questions.

01What a signature means

When you sign in >commit_, you confirm a specific version of the split. We record who signed, when, from which account, and a fingerprint of that exact version, so nobody can later claim they signed something else.

How you sign

A click in the app after logging in by email. Everyone gets a receipt with the version's fingerprint, and a PDF copy if they want one.

Is it a contract?

Yes: an agreement between the team members. Electronic signatures like this count for most contracts in the US and EU. >commit_ isn't a party to it; we keep the record.

Can it be used in a dispute?

Yes. The full history exports as one file, with every version, signature and money entry. How much weight it carries depends on local law.

Can anyone rewrite it?

No, not even us. Each version is chained to the one before it, everyone holds a receipt, and the record is time-stamped every day by an outside service.

Can an agent sign for me?

No. An agent can read the split and draft a change. Signing always takes you.

02Who owns the work

Code, art, sound and text stay with the person who made them. The project gets an exclusive, permanent licence to use them in this product. It's part of what everyone signs, on the record next to the shares.

Who owns what

You keep the copyright. The project gets an exclusive, permanent licence to use your work in this product, its updates and ports. If the product is sold, the licence goes with it. If the team forms a company, the rights go into the company.

If someone leaves

The licence for what they already delivered stays, and so does the share they earned. They can't take their work out of the product.

Showing your work

Yes. You can show what you made in your portfolio, with credit to the project.

Does >commit_ own anything?

No claim on your work. When we publish, we get a licence to distribute the app in the stores, and it ends when you take the app back.

03What we can see

We only ask for read-only access, and only if you connect a store. You can start a project and lock the split without it.

What we read

Sales and payout reports from App Store Connect, Google Play or RevenueCat.

What we can't do

Change your listing, prices, builds, users or payouts. The keys don't allow it.

Players' data

Store sales reports don't include your players' personal data, and we don't ask for it.

Revoking

Delete the key in the store console. We stop reading at once; the history already recorded stays.

How it's stored

Encrypted in transit and at rest; store keys are encrypted separately. We open a project only when you ask for support, and every access is logged.

04Money and payouts

If you publish, the money never touches us: we show who's owed what, and paying them is on you. If we publish, the stores pay us and we pay the team by the split.

Whose account

When we publish: our developer account. Details on the publish page.

Payout providers

Stripe Connect. Each person adds their own payout account. Stripe's payout fee comes out of that person's payout and is shown before it's sent.

Where the money waits

In a separate account for team funds, never mixed with ours, and only until the payout goes out.

05Taxes

Each payout is recorded with its date, amount and currency, so everyone has what they need for their own tax return.

Who pays the tax

Each person, on what they receive. When we publish, we withhold only what the law requires.

Forms

When we publish, each person fills in the tax form our payout provider asks for, once.

06Documents