Trajector

This is the authorization contributors accept from their dashboard before contributing data. During the closed beta it also serves as Trajector's terms of service.

Data Collection and Use Authorization (v2)

This Authorization is granted by you (the Contributor) to PublicAI Foundation (the Licensee, identified in §10). It is granted by an individual, in their own name; if you contribute on behalf of an organization, contact the Licensee (§10) before accepting. It is a standalone document: everything the Licensee relies on is written here. Operational matters — reward rates, withdrawal thresholds, collection scope, acceptance rules — are governed by the separate Beta Program Terms — or whatever terms succeed them when the program leaves beta; every mention of them in this document includes their successors — and the license granted in §1 does not change when those terms change.

1. License granted

You grant the Licensee a non-exclusive, perpetual, irrevocable, worldwide, sublicensable and transferable license to use, reproduce, modify, create derivative works from, distribute and publish the desensitized (redacted) coding session data you contribute — under copyright and any similar or related right you may hold in that data, including database rights — and to do so commercially, for research, or both — for the purposes set out in §1.1, and for operating the platform itself (storing, redacting, reviewing and paying for contributions).

"Desensitized" means secrets and credentials are scrubbed on your machine before anything is uploaded, and the platform runs its own redaction checks after upload.

You keep every right in your own code. This is a license, not an assignment, and it is not exclusive: contributing here does not restrict what you do with the same work anywhere else.

1.1 The three things this material is used for

A license this broad should say what it is for. These three are it. A use outside them requires a new version of this document, which you would be asked to accept.

  1. Sale to data purchasers. Datasets — the contributed sessions themselves, or material compiled and combined from them — are supplied to identified buyers under a written contract. This is what funds the rewards in §4. It includes use of the material for training, evaluating and improving AI models, by the Licensee or by a purchaser.
  2. Research. The same material, raw or compiled, may serve as the sample or source material for research, including research published as academic papers — the Licensee's own or a third party's.
  3. Public release. The Licensee may publish a selected portion of the material as an open dataset, typically alongside published research so that others can reproduce it. Note: this one is different from the other two; §1.2 says how.

1.2 Public release is permanent, and it is not automatic

The first two uses place material with parties the Licensee can name and has a contract with. Publication does not: once a dataset is public, anyone may hold a copy, the Licensee cannot say who does, and it cannot be recalled. Deletion cannot reach those copies — see §5, which states this in full rather than leaving you to discover it.

Because of that, publication is a separate decision, not an automatic consequence of contributing. The Licensee undertakes that:

  • only a selected portion is ever published, never everything contributed;
  • anything selected is reviewed again before publication — for personal data, and for third-party material that may not be redistributable — in addition to the redaction described above;
  • no contributor identity is published. Not your name, your email address, your account, nor any identifier that resolves to you. §6 lists what the Licensee records about you; none of it is published.

Publication here means any way the material becomes public, not only a dataset release: an excerpt reproduced inside a published paper is publication too, and it passes through the same selection, review and anonymity rules above.

Important: material published as an open dataset carries an open license to the public. What recipients then do with it is outside the Licensee's control, and this document does not restrict them. That is what publication means, and it is why §1.1 lists it separately rather than folding it into "distribute".

1.3 Moral rights

You keep your moral rights — including the rights of attribution and integrity — in what you contribute. This section does not take them away.

However, exercising the license in §1 requires two things your moral rights could otherwise block: modifying the material (redaction, compilation), and — under §1.2 — publishing it without your identity. So you agree, only to the extent needed for the Licensee (including any successor under §10) and those exercising rights derived from §1 (including data purchasers) to do what §1 and §1.2 describe, not to assert your rights of attribution and integrity against them. Beyond that extent, your moral rights are untouched.

Where the law that applies to you does not give this effect, you instead grant the Licensee, to the extent that law permits, the rights needed to use the material without attribution and to make the adaptations described above.

2. What this Authorization covers

This Authorization covers every batch received by the platform after you accept it.

A batch is the unit the client uploads; a batch cannot straddle the moment of acceptance. Data received by the platform before that moment is governed by whatever you accepted at the time, and this Authorization does not retroactively re-authorize it.

3. Your representations and warranties

You represent and warrant that:

  • you are at least 18 years old and have full legal capacity to grant this Authorization — and if the law where you live at the time you accept this Authorization sets the age of majority higher than 18, you have reached that age too;
  • you contribute sessions only from code you own or that is open source under a license permitting this contribution;
  • you contribute only from projects you have explicitly enabled for collection;
  • you have the right to grant the license in §1, and — to the best of your knowledge — doing so breaches no agreement, employment obligation or third-party right.

Collection is opt-in per project. Nothing is captured from projects you have not enabled.

If a third party brings a claim against the Licensee because a representation in this §3 was untrue, you agree to indemnify the Licensee for the losses and reasonable costs that result. This covers breaches of this §3 and nothing else: it does not make you responsible for the Licensee's own use of the material, or for its business generally. Your total liability under this paragraph is limited to the total rewards you have received from the Licensee — the same amount §4 describes as the entire compensation for the license.

4. Rewards

You grant the license in §1 in consideration of your participation in the program and of any rewards payable to you under the Beta Program Terms. A dispute about, or the non-payment of, any particular reward does not revoke or suspend that license; your remedy in that case is under the Beta Program Terms.

Those rewards are also the entire compensation for the license: no royalty, fee or other payment accrues to you from any use §1.1 permits, however often or however commercially the material is used.

5. Deletion, and the limit of deletion

You may ask us to delete session data we hold, through the My data page or by request.

Deletion reaches our systems, every future delivery, and any future publication. It has no retroactive effect on copies already delivered to third parties, and the license granted in §1 continues in force for the portion already delivered.

Important: for anything already published as an open dataset (§1.1 item 3), the limit is harder. With a purchaser there is at least a named party and a contract. With a published dataset there is neither: copies are held by people we cannot identify, and your deletion request cannot reach them. That portion cannot be undone. What deletion still does is stop the material being used or published again by us.

This is the plainest reason publication is restricted the way §1.2 restricts it — a selected portion, reviewed again first, and never carrying your identity.

We say all of this plainly because the alternative is worse: you would believe the data was gone, a buyer would believe their copy was clean, and both beliefs would rest on a gap we had chosen not to mention.

6. Identity and what we do and do not verify

We ask for your full legal name so the record reads as a document about a person rather than about an account number.

We do not verify names. The name you enter is your own statement, and we make no representation to anyone that it is correct. What binds this Authorization is your account — the email address we have verified, the third-party identity you signed in with, and the record of this action — not the name you typed.

We record, at the moment you accept: your account identifier, your email address and the fact that it had already been verified, the third-party identity linked to the account (if any), the exact bytes of the document you accepted, the time, your IP address and your browser's user-agent string.

That record outlives your account. If your account is later closed, the record of this acceptance is retained, because it is the only thing that proves this Authorization exists and what it says — for you, for the Licensee, and for anyone the material was delivered to. It is kept for that purpose and used for no other.

Rights you may have over the personal data described in this §6 — including any right to withdraw consent to its processing — are separate from the license in §1 and are unaffected by it. Exercising them does not revoke that license, and that license does not limit them.

7. Electronic records and electronic signature

Accepting this Authorization electronically is how it is granted; no paper copy is required, and the electronic record is the record.

Singapore's Electronic Transactions Act 2010 recognizes electronic records and electronic signatures for agreements of this kind. Beyond what any law requires of us, we have adopted the following practices:

  1. Delivery and retention. A copy of this Authorization as accepted, together with the record of your acceptance, is available for download from your dashboard for as long as you have an account, and a link to it is emailed to your verified address. If your account is closed, you may still obtain a copy on request, for as long as the record is retained under §6.
  2. Withdrawing consent to electronic records. You may tell us you no longer wish to transact electronically. Doing so stops future electronic delivery; it does not revoke this Authorization, which is irrevocable under §1.
  3. What you need to read and keep it. A current web browser, an internet connection, an email address that can receive our messages, and the ability to open PDF files and to save or print them.

8. Governing law and dispute resolution

This Authorization is governed by the laws of Singapore, without regard to conflict of laws rules.

Any dispute arising out of or in connection with this Authorization — including any question about its existence, validity or termination — 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, and they are not decoration:

  • Where the mandatory law of your place of residence does not enforce an agreement to arbitrate made before a dispute arises, this §8 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. Nothing in this §8 removes that option.

9. General provisions

Severability. If any part of this Authorization turns out to be invalid or unenforceable, the rest of it stands.

Relationship to other documents. This Authorization governs the license and everything else written here. The Beta Program Terms govern how the program operates. Neither changes the other: on the matters this document covers, this document prevails, and no change to the Beta Program Terms changes what you have licensed. The privacy policy published on the platform describes how the personal data in §6 is handled; it is referenced for information and is not part of this Authorization — changing it cannot change this document either.

No waiver. If the Licensee, or you, does not exercise a right under this Authorization on some occasion, that right is not lost.

Language. This Authorization is written in English, and the English text is what you accept. Any translation or summary is provided for convenience only; where they differ, the English text governs.

Survival. §1 (including §1.2 and §1.3), §3, §5, §6, and §8 continue to apply after your account is closed or you stop contributing. That is the same thing §1 already says — the license is perpetual — stated once for the sections around it.

No assignment by you. What binds this Authorization is your account (§6), and your side of it cannot be transferred or assigned to anyone else. The Licensee's side is transferable as §10 states.

10. The Licensee

The party to whom the rights under this Authorization are granted is:

Legal Name:        PublicAI Foundation
Entity Type:       Foundation company incorporated under the laws of the Cayman Islands
Jurisdiction:      Cayman Islands
Contact:           support@publicai.io
Website:           https://publicai.io

The Licensee's registration number and registered office address are stated in full in the document as you accept it — in your archived copy, and in any copy supplied to a data purchaser. They are omitted from this public page only.

The license granted in §1 is transferable, so it may pass to a successor in interest of the Licensee. It is granted to the entity named above alone; no affiliate is a party to this Authorization.

11. Version

This is version v2 of the Data Collection and Use Authorization. A later version does not automatically supersede this one: what a future version covers, and whether it re-covers data authorized under this one, is decided when that version is published.

How a new version happens is the mechanism §1.1 and §2 already imply, stated here in full: the Licensee publishes the new version and asks you to accept it. Until you do, nothing changes — this version continues to govern every batch it covers, and no use that requires the new version happens to your data. Declining a new version never affects what this one already granted, in either direction. What it may affect is whether you can keep contributing: the Licensee may require the new version to be accepted before it receives further batches from you. That is a condition on contributing, not a change to this Authorization.