Trajector

For contributors·v2 · Effective 30 August 2026·All legal documents

In short

  • These are the operating rules of the beta: what is collected, what is paid, how withdrawal works, and what gets an account removed.
  • They can change. The Data Collection and Use Authorization cannot: the two documents are kept separate so that one can change without the other.
  • Changing these terms does not change the license you granted in the Authorization.

This summary is not part of the document and is not what you accept or rely on. Where it and the text below differ, the text below governs.

Beta Program Terms (v2)

These terms govern how the Trajector beta program operates: what we collect, what we pay, how you withdraw, and what gets you removed. They can change — see §5.

They are separate from the Data Collection and Use Authorization, and changing them does not change the license you granted there.

1. Collection scope

The beta collects a defined set of coding sessions, posted on the site and reported by the CLI (trajector status). Uploads outside the current scope are rejected: they earn nothing and never enter anything Trajector delivers.

Rejected data is cleared under the retention policy in effect at the time. Rejected data is not retroactively accepted if the scope later widens. Sessions awaiting manual review are kept until a decision is made.

Trajector is not a storage or backup service. The CLI deletes its local copy once an upload is acknowledged, and acceptance is decided after that — keep your own copies of anything you need.

2. Rewards

Accepted sessions are credited in USD per token at the rate posted on the site. The rate in effect at the moment a session is credited is written permanently into that ledger entry: a later rate change is never retroactive, up or down.

Acceptance decisions appear in your dashboard and in the CLI (trajector status). We do not send decision emails.

3. Withdrawals

You can withdraw your balance as a stablecoin (USDC or USDT) on Ethereum or BSC once it reaches the posted minimum (currently $10). The network fee is deducted from the payout.

Withdrawals are open during the beta; the minimum, the supported networks and the supported tokens may be adjusted as posted (§5).

4. Deleting stored sessions

On the My data page you can read every session we hold and delete any session whose reward you have not claimed yet — deleting it also reverses that reward. Sessions you have already been paid for can be removed too, but require a manual request so accounts can be settled first.

What deletion does not reach — copies already delivered to third parties — is governed by §5 of the Data Collection and Use Authorization, not by these terms.

5. These rules can change

During the beta, the collection scope, reward rates, limits and acceptance rules may change, as posted on the site. Changes apply from the moment they are posted; rewards already credited are never repriced (§2).

6. Abuse forfeits rewards

Fabricating or replaying sessions, bulk farming, coordinated multi-account abuse, or otherwise gaming acceptance or rewards — once determined by Trajector — forfeits the account's unwithdrawn rewards and ends its participation. Trajector may suspend an account while this is investigated, which freezes withdrawals.

7. Ending participation

You can stop contributing at any time. Trajector may end the beta, or an individual account's participation as described in §6; balances already withdrawn are unaffected.

Ending participation does not revoke the license granted under the Data Collection and Use Authorization, which is irrevocable by its own §1.