Beta Program Terms (v3)

These terms govern how the Trajector beta program operates: what we collect, what we pay, how you withdraw, and what happens when something goes wrong. They are an agreement between you and PublicAI Foundation, a foundation company incorporated in the Cayman Islands, which operates Trajector.

They are separate from the Data Collection and Use Authorization ("the Authorization"). Nothing in these terms changes the license you granted there, and on any matter the Authorization covers, the Authorization prevails.

New contributors accept these terms when they sign up. If you accepted an earlier version, you are asked to accept this one to keep contributing: from 30 days after it takes effect, we accept uploads only from accounts that have accepted it (§5). When you accept it, it governs your account from then on, including sessions you contributed and rewards credited before. Until you do, the version you accepted continues to govern what you contributed under it, and you can withdraw your balance under that version.

1. Collection scope

The beta collects a defined set of coding sessions, listed in the program rules (§5) 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 earns nothing and is never delivered; it is kept or deleted as the privacy policy describes. 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 in the program rules. 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.

Some sessions are held for review before a decision is made. A held session earns nothing until it is accepted; if it is accepted, it is credited at that point.

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

Every change to your balance is recorded in an append-only ledger. The Claim page lists it, and its lines add up to your balance. A correction is posted as a new entry; existing entries are never edited.

Bonuses. Trajector may, at its discretion, credit an account with a bonus for contributions to the program beyond accepted sessions. A bonus is shown with its reason on the Claim page, is added to your balance, and is withdrawn under §3 like any other reward. Bonuses are not earned by uploading and are not promised: a past bonus does not entitle you to future ones. Trajector may cancel a bonus credited in error as long as it has not been withdrawn; a withdrawn bonus is not reclaimed, except under §6. Bonuses are rewards for the purposes of these terms, including §6.

Trajector may periodically pay a quality bonus for sessions that show substantial human direction and a verified result. How sessions are selected for it is not published.

3. Withdrawals

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

Holding period. Each credit becomes withdrawable a set number of days after it is credited — currently 7. Until then it is part of your balance but shown as still maturing, with the date it becomes withdrawable. A session credited after review counts from the moment it is credited. Bonuses are withdrawable at once. Credits made before the holding period first took effect are not subject to it. The holding period will not exceed 30 days.

The minimum, the supported networks and tokens, and the holding period are program rules (§5).

You are responsible for any tax due on rewards you receive. We may refuse or delay a withdrawal where making it would breach sanctions law or other law that applies to us; the balance stays in your account while that is the case, or is dealt with as that law requires.

4. Deleting stored sessions

You can have any session we hold deleted. That right comes from §5 of the Authorization, and it does not depend on repaying anything.

• A session whose reward you have not yet withdrawn can be deleted yourself on the My data page. Deleting it cancels that session's unwithdrawn reward: we no longer hold the data, and we no longer owe you for it.
• A session whose reward you have already withdrawn is deleted on request, from the My data page or by writing to support@publicai.io. The reward already paid is not taken back, except where the session is deleted because of a valid rights claim (§9).

What deletion does not reach — copies already delivered to third parties, and anything already published as an open dataset — is governed by §5 of the Authorization, not by these terms.

5. Program rules, and changes to these terms

The beta has two layers, and they change in different ways.

Program rules are the collection scope, reward rates and multipliers, acceptance rules and checks, daily limits, the withdrawal minimum, the supported networks and tokens, and the holding period. They are published on the Rewards page of docs.publicai.io with the date they were last changed. They can change during the beta, and a change applies from the moment it is published there. A change never reprices a reward already credited (§2).

These terms change only by a new version. Each version is published at trajector.publicai.io/legal/beta-terms with its version number and the date it takes effect, and earlier versions stay readable there. We tell you about a new version on your dashboard. You can keep contributing under the version you accepted for 30 days after a new version takes effect; after that, uploads require the new version. When you accept it, it governs your account from then on, including sessions contributed and rewards credited before. Until you accept it, a balance credited under the version you accepted can be withdrawn under that version.

6. Breaches: recovering rewards, and how to contest them

This section covers two kinds of breach:

• Abuse: fabricating or replaying sessions, bulk farming, holding more than one account (§8), or otherwise gaming acceptance or rewards.
• Contributing what you had no right to contribute: a breach of §9, or a representation you gave in §3 of the Authorization that turns out to be untrue.

While we look into it, we may suspend the account, which freezes withdrawals. Within 60 days of suspending it, we either send you the email described below or lift the suspension, unless a law enforcement or regulatory authority asks us to keep it.

If we conclude that a breach occurred, we email you at your account address with the kind of breach and the facts we rely on, in enough detail for you to respond (we do not describe how it was detected), the sessions concerned and the amounts involved. You have 14 days from that email to reply to support@publicai.io with anything you want us to consider. Your reply is considered by a member of our staff who was not involved in the original finding, and we tell you the outcome and our reasons in writing within 14 days of your reply. Withdrawals stay frozen during this time, and nothing below is carried out until the 14 days pass without a reply or we reject your reply.

What then happens:

• For abuse, the rewards credited for the sessions concerned, and for any account held in breach of §8, are recovered; we may also deduct from your remaining balance the reasonable costs the abuse caused us, such as reviewing the sessions concerned and any refund we gave a purchaser; and participation ends. Any balance left after that is dealt with under §7.
• For contributing what you had no right to contribute, the rewards credited for the sessions concerned are recovered. Where you knew, or ought reasonably to have known, that you had no right to contribute them, participation also ends.

To recover a reward, we cancel any part not yet withdrawn and deduct any part already withdrawn from your balance (including credits still maturing) and from later credits. Where that does not cover it, we may require you to repay the rest. These rights are in addition to §3 of the Authorization, but we will not recover the same loss twice: an amount recovered under this section for a session reduces any amount you owe under §3 of the Authorization for that session.

7. Ending participation

You can stop contributing at any time.

If you leave, if Trajector ends the beta, or if Trajector ends your participation for any reason other than a breach under §6, your balance stays yours. Trajector gives at least 30 days' notice before ending the beta or your participation, unless the law requires otherwise. Each credit becomes withdrawable as §3 describes, and you can withdraw under §3 for 12 months from the day participation ended. Where Trajector ended it, you can withdraw your whole balance once even if it is below the minimum, less the network fee (if the fee is more than the balance, nothing is paid). We email you at least 30 days before an unwithdrawn balance lapses; a balance not withdrawn within the 12 months then lapses.

If participation ends because of a breach, §6 is followed first, including the time to reply. Any balance left after that can be withdrawn under §3 for 12 months from the day participation ended, and then lapses.

Balances already withdrawn are not affected by participation ending, except as §6 describes. Ending participation does not revoke the license granted under the Authorization, which is irrevocable by its own §1.

8. One contributor, one account

An account belongs to one person, the contributor, and is the unit we pay. Each contributor holds one account. Pair as many of your own machines with it as you need. An account cannot be shared, transferred, or run on someone else's behalf. Holding more than one account is a breach of this section. When we find more than one account held by the same person, we merge them: we move the balance of the other accounts to the one you keep, and close the others. Where an extra account was used to earn more than one account could, or to get around a limit or a decision about another account, that is also abuse under §6.

9. What you contribute

Contribute only sessions from projects that are your own work, or open source under a license that lets you contribute them — the same thing you represented in §3 of the Authorization. Work you did for a client, an employer, or another platform's evaluation or labeling tasks is not your own work for this purpose, unless you hold the right to contribute it. This is an undertaking under these terms in its own right: contributing such work is a breach of this §9 whether or not it is also an untrue statement under the Authorization, and is handled under §6.

Rights holders. If you believe a session contains your work and was contributed without your permission, write to support@publicai.io and identify the work (a repository or files), yourself and how to reach you, the basis of your rights, and that you are writing in good faith. We reply within 5 business days. Where the claim is valid, we delete the sessions concerned, stop delivering them, and ask purchasers who received them to delete their copies. We tell the contributor about a claim that concerns their sessions, and we do not give the contributor's identity to the person making the claim unless a court or the law requires us to.

A session deleted because of a valid claim earns nothing, whether or not the contributor knew. After the steps in §6 (our email, the time to reply and our answer), its unwithdrawn reward is cancelled as in §4, and any part already withdrawn is deducted from the contributor's balance and from later credits. Where the contributor knew, or ought reasonably to have known, that they had no right to contribute it, §6 applies in full, including repayment of what the deductions do not cover and the end of participation.

10. Governing law and disputes

These terms are governed by the laws of Singapore, without regard to conflict of laws rules. Nothing in this section deprives you of the protection of any provision of the law of your place of residence that cannot be departed from by agreement.

Any dispute arising out of or in connection with these terms shall be referred to and finally resolved by arbitration administered by the Singapore International Arbitration Centre (SIAC) under its rules in force at the time. The seat of arbitration is Singapore, the language is English, and the tribunal consists of one arbitrator. Where the dispute qualifies, the SIAC's expedited or streamlined procedure applies.

Two exceptions:

• Where the mandatory law of your place of residence does not enforce an agreement to arbitrate made before a dispute arises, this section does not apply to you, and the dispute may be brought in the courts having jurisdiction there.
• Either party may bring an individual claim in a small claims court with jurisdiction over it.

Where you bring an individual claim under this section, PublicAI Foundation pays the SIAC filing and administrative fees and the arbitrator's fees. Each party bears its own legal costs.

These are the same arrangements as §8 of the Authorization. Where a dispute arises under both these terms and the Authorization, each of us agrees that the arbitrations may be consolidated, or heard together by the same tribunal, under the SIAC rules.

11. General

Contact. Write to support@publicai.io. We write to you at the email address on your account.

Language. These terms are written in English, and the English text is what you accept. Any translation or summary is for convenience only.

Severability. If any part of these terms turns out to be invalid or unenforceable, the rest stands.

No waiver. If we, or you, do not enforce a right under these terms on some occasion, that right is not lost.